How we work
How we work: a clear process and the engagement model that fits
Every project follows the same four phases — discovery, architecture, build and support — with a written scope before any code, a working demo every Friday and the code in your accounts from the first commit. Choose a fixed scope, a dedicated team or time and materials.
How we work
Engagement models
| Model | How it works | Best for |
|---|---|---|
| Fixed scope | After a 1–2 week discovery we agree scope and launch date in writing. Changes are estimated and approved before they are built. | A defined system, MVP or integration with a clear goal |
| Dedicated team | Senior engineers work as part of your product team, in your tools, rituals and time zone overlap, with a monthly plan. | Long-running products and ongoing development |
| Time & materials | Flexible scope billed for the work actually done, with weekly reports and a shared backlog you prioritise. | Evolving requirements, R&D, support and improvements |
Most clients start with a fixed-scope first release and move to a dedicated engineer or time and materials after launch. Describe your project and we send a written scope and timeline after a short call.
The process
- Intro call · 30–45 minutes. Your goals, current tools and constraints. NDA signed before the call if you need one.
- Discovery · 1–2 weeks. Interviews with the people who will use the system, a map of the current process, a written specification and a milestone plan. The documents are yours even if you build elsewhere.
- Architecture · 1–2 weeks. Data model, integrations, infrastructure and a milestone schedule.
- Build · two-week iterations. A working demo every Friday and a staging environment you can open at any time.
- Launch. Deployment to your cloud account, data migration, documentation, handover and training.
- Support & development. Monitoring, fixes and new features, sized to the business.
Full cycle under one contract
- Business analysis and written specification
- UX/UI design and clickable prototypes
- Web, mobile and backend development
- Integrations with accounting, telephony, email, calendars and marketplaces
- Testing, deployment and DevOps
- Support, monitoring and further development
What you always get
- Senior engineers you talk to directly — the people who build the system join the calls.
- Code, accounts and data in your name from the first commit.
- Transparency: a shared backlog, weekly demos and a staging environment.
- Business-hours overlap with the United States and Europe, communication in English or German.
Related: technology stack · security & compliance · case studies.
FAQ
Questions we are asked most
Which engagement model should we choose?
For a defined system or MVP, a fixed scope after discovery. For a product you will develop for years, a dedicated team. For evolving requirements or support, time and materials. We recommend one after the intro call.
How does a project start?
After a short call and a 1–2 week discovery you receive a written specification and a milestone plan before the build starts.
Can we start small?
Yes. Many clients start with a discovery or a focused first release and extend the system after launch.
How do we follow progress?
A working demo every Friday, a staging environment you can open at any time and a shared backlog with priorities you set.
Contact
Talk to the people who will build it
Describe what you need in two minutes. We reply within one business day and send a written scope and timeline after a short call.