Our process
How a requirement becomes a live system.
A small senior team, a tightly scoped first release, and working software on a staging environment throughout. This page describes the four stages of an engagement and what you receive at each.
What holds it together
Four commitments
The people who scope it build it
You talk to the engineers doing the work. There is no sales layer that hands a brief to a team you never meet.
You own everything
Source code, infrastructure, and accounts are set up in your name from the start. Leaving us should never be a technical problem.
Working software over status reports
Progress is shown on a staging environment you can open, not in a slide deck.
Honest about AI
We tell you when a rule, a report, or a simpler integration will solve the problem better than a model.
The four stages
From first call to live system
- Stage 01
Discover
We start with the business problem, not a feature list. In the first sessions we map who uses the system, which decisions or tasks it supports, which existing systems and data it has to work with, and which parts are genuinely uncertain. The output is a written scope for the first release, a technical approach, and an estimate you can take to your stakeholders.
You receiveScope for the first release, technical approach, estimate. - Stage 02
Design
Most expensive mistakes happen in the data model and in integration assumptions. We design those first, alongside clickable screens for the core flows so the people who will use the system can react to something concrete.
You receiveData model, integration map, clickable prototype. - Stage 03
Build
Engineering runs in short cycles. Each cycle ends with working software deployed to a staging environment you can open, with a short note on what changed and what to test. Difficult paths such as integrations and permissions are built early, not left for the end.
You receiveWorking software on staging at the end of every cycle. - Stage 04
Launch & scale
Go-live includes monitoring, backups, access handover, and documentation. After launch we can stay on for support and the next set of improvements, or hand over cleanly to your team. Either way, the code, infrastructure, and accounts are yours.
You receiveLive system, documentation, and a plan for what comes next.
The fine print, up front
Ownership, changes, and what happens after launch
- Repositories, cloud accounts, and third-party services are created in your name or transferred at handover.
- Scope changes are written down with cost and timeline impact before work on them starts.
- Every cycle ends with a deploy to staging and a short note on what to test.
- After launch you can retain us for support and improvements or take over with your own team.
Start small: talk the requirement through before anything is built.
A short call with an engineer, not a salesperson. You describe the process or system, we ask questions, and you leave knowing whether it is worth scoping and roughly what that involves.
Talk to an engineer
Let's build the first release.
Book a 30-minute call with an engineer, at no charge. Tell us the problem and the systems involved, and you leave with questions answered and a suggested first step, not a sales deck.