Process
From your first idea to software you use every day.
Every project starts with a conversation and ends with custom software your business runs on. Here is what happens before we build, what happens while we build, and how your project stays private the whole way through.
Before we build
Seven steps from idea to deposit.
First we agree what to build and what it costs. You see a fixed quote, then a short paid discovery gives you a clickable mock and confirms the scope. Nothing is built until you pay the deposit.
- Step 01Idea
What happens
You tell us what you want built and the problem it solves for your business, through the form on this site or a free call.
You get
A reply within one business day
Where you come in
Describe the idea in your own words. No technical detail needed.
- Step 02Interview
What happens
We ask the questions that shape the software: who uses it, what it must do and what it connects to. For each one we suggest an answer, so you mostly confirm.
You get
A written project brief with our recommended answers
Where you come in
One call, usually about 45 minutes
- Step 03Quote
What happens
A fixed-scope quote, priced piece by piece, so you can see what each part of the software costs and choose what goes in first. It names the price of a short paid discovery that comes before the build.
You get
A fixed quote, itemised by piece
Where you come in
Decide what belongs in the first version
- Step 04Discovery
What happens
A short paid discovery confirms the quote before any build starts. We design the main screens as a clickable mock you can try, and settle the open questions.
You get
A clickable mock of your app and a confirmed scope
Where you come in
Try the mock and tell us what feels wrong
- Step 05Decompose
What happens
Break it into pieces: we split the software into small working pieces and lay them out in a delivery plan with milestones you can see.
You get
A delivery plan with milestones
Where you come in
Check the order matches your priorities
- Step 06Follow up
What happens
We walk you through the quote and the plan, adjust the scope with you and answer every question. No pressure and no deadline.
You get
A final quote and plan you agree with
Where you come in
Ask anything, change anything
- Step 07Deposit
What happens
A deposit books your build slot. We set up your private sandbox and the build starts.
You get
A start date and your private progress report
Where you come in
Pay the deposit when you are ready to go
How we build it
Seven stages, from kickoff to launch.
The first five stages settle exactly what to build and how. Then the factory builds it one small working piece at a time. Each piece goes around the same loop and lands in your private preview, so you can use it while the next one is being built.
- Stage 01Kickoff
What happens
We start from the brief and plan you agreed, and meet the people who will use the software day to day.
You get
A confirmed project brief and a first-week plan
Where you come in
One kickoff call
- Stage 02Requirements
What happens
We grow the interview into a full list of every feature, user and workflow, and write down the facts that decide each one.
You get
A requirements list with our recommended answers to open questions
Where you come in
Answer the few questions only you can answer
- Stage 03Design
What happens
We choose the architecture, hosting and security model, and confirm the pieces and milestones in your delivery plan.
You get
A design document and the confirmed delivery plan
Where you come in
Approve the plan
- Stage 04Mocks
What happens
Clickable screens before any code, so you can try the flow and catch problems while they are cheap.
You get
A clickable mock of every main screen
Where you come in
Click through it and tell us what feels wrong
- Stage 05Spec
What happens
Each piece gets a short written spec: what it does and how we will prove it works.
You get
A spec and acceptance checks for every piece
Where you come in
Optional review
- Stage 06Factory
What happens
AI agents and our engineers build each piece, test it, fix what fails and release it. Then the next piece starts.
You get
A new working build after every piece, plus a live progress report
Where you come in
Open your preview anytime. Your feedback shapes the next pieces.
BuildCode and its tests are written for one piece.TestAutomated tests in real browsers and devices, plus independent review.FixAnything that fails is traced to its cause and fixed before it moves on.ReleaseThe piece lands in your private preview. - Stage 07Demo
What happens
At each milestone we walk you through what works, then put it into production.
You get
A production release and handover notes
Where you come in
Sign off on going live
Private by design
Your project is built in its own private sandbox.
Every client project is developed in an isolated sandbox. Your code, your data and your ideas never mix with another client’s work, and what we show you is visible only to your team.
Every piece follows the same core process
Same loop, different kinds of work.
A mobile app and a data migration look nothing alike, but both go through design, mocks, testing and release. Here is what each step means for each kind of project.
| Step | Mobile app | Web app | Desktop app | Data migration | Environment build-out |
|---|---|---|---|---|---|
| Design | Screens, offline rules, and the backend API the app talks to | Pages, user roles, data model and hosting | Windows, installer and how updates reach each PC | A field-by-field map from old data to new, plus cleanup rules | A diagram of dev, staging and production, and who can reach each |
| Mocks | Clickable phone screens you can try on your own phone | A clickable browser mock of every main flow | A clickable mock of each window and dialog | Sample migrated records and the reports you will run on them | A walkthrough of a release, from merged change to live site |
| Test | Automated taps on Android and iOS emulators and real devices | Automated clicks in Chrome, Safari and Firefox | Automated clicks on a real Windows desktop | Row counts, totals and spot checks reconciled with the source | Deploy, rollback and restore drills that must pass |
| Release | A test build on your phone after each piece; signed store package at launch | Your private preview link updates after each piece; production at each milestone | A signed, versioned installer with release notes | A rehearsal run in the preview, then a planned cut-over | Each environment goes live in turn, with a written runbook |