How a build runs
The short answer
A build moves through seven stages: discovery, architecture, build, migration, testing, launch, then ongoing optimisation. You approve the architecture before any code is written, and you see real progress during the build rather than waiting for a reveal at the end. Most platforms launch in two to eight weeks depending on scope.
1. Discovery
Forty-five minutes to an hour, with the founder. We map what your business does, which tools you pay for, which parts of the day are wasted, and what has to keep working exactly as it does now.
- We need: your current tool list, who does what, and the workflows that cannot break.
- You get: a clear picture of what a platform would replace and what it would cost.
2. Architecture
We design the whole platform before building it: the capabilities, how they connect, what your team sees against what your customers see, the roles, and where the data lives.
You approve this blueprint before any code is written. Changing the plan at this stage costs a conversation. Changing it after launch costs a rebuild, so this is where we slow down deliberately.
3. Build
We build in short cycles with a live link you can open at any point. No black box, no monthly status email standing in for progress.
Within seven to ten days of starting, we walk you through what exists so far and adjust from your feedback rather than guessing.
4. Migration
Existing customers, jobs, invoices, documents, and history move across. We do a test migration first, check the counts and the edge cases with you, then run the real one.
- Old system stays live until the new one is verified. Nothing is switched off on a promise.
- Records that cannot be mapped cleanly are flagged for a decision rather than silently dropped.
- Existing URLs are redirected so search rankings and old links survive the move.
5. Testing
- Every workflow walked through as each role: owner, staff, and customer.
- Permissions tested by attempting access that should fail.
- Payments, emails, and integrations tested end to end with real sends.
- Phone, tablet, and desktop checked, not assumed.
- Speed and technical audits run before launch, not after.
6. Launch
Launch is a planned switch, not a surprise. The domain moves, redirects go live, and your team already knows the system because the tutorials sit inside the platform itself rather than in a manual nobody opens.
We stay close during the first days, when the real edge cases surface, and fix them as they appear.
7. Optimisation
After launch the subscription covers support, maintenance, security updates, and continued development. New capabilities get added as your business needs them, and new frontier AI models land in your platform the same day they release.
This is the part that separates an owned platform from a project handoff. It keeps changing the week you need it to.
Common questions
Questions about how a build runs
How long does a build take?
Two to eight weeks from approved architecture to launch. Simple builds land near two to three weeks, standard builds four to six, and complex platforms six to eight.
What do you need from me during the build?
The discovery meeting, your business knowledge, content and brand assets, and feedback turnaround. Slow feedback is the most common reason a build sits still.
Will my existing data come across?
Yes. We test the migration first, verify counts and edge cases with you, then run the real one, and the old system stays live until the new one is verified.
What happens after launch?
The monthly subscription covers hosting, support, maintenance, and continued development, including same-day access to new frontier AI models.
Start with the discovery meeting
Forty-five minutes, no pitch. We map what your platform would replace and what it would take to build it.