Let's start the scope week.
Stage 01 is 5 working days. By the end of it you have a scope document, a realistic timeline, and a go / no-go decision — all before a single line of production code is written.
Services · PROCESS
Our process, documented.
Every engagement follows the same four stages. We publish them here so you know exactly what to expect before we ever sign a SOW. No mystery process, no 'trust us', no mid-project surprises.
Section 01Stages
Four stages, in order.
01
Scope week
Five working days. We have a 30-min kickoff, then write a scope doc you can show investors, engineers, or an acquirer. Includes: user flows, data model, tech stack, delivery timeline, milestones, price.
- Scope document (6–10 pages)
- Wireframes (low-fi)
- Fixed price + timeline
- Go / no-go decision
02
Design + setup
Week 2. Design system or visual design finalised. Repo, CI/CD, hosting, staging environment, database, analytics — all set up and documented. By end of week 2 you have a 'hello world' deployed on your domain.
- Design files (Figma)
- GitHub repo in your org
- Staging + production environments
- Monitoring and alerting
03
Build sprints
Weeks 3–5 (for 6-week MVP). Two-week sprints with mid-sprint demo and end-sprint review. You see the product in your browser every Friday. Feedback goes into the backlog for the next sprint.
- Deployed build every 2 weeks
- Loom demo every Friday
- Burndown chart + velocity report
- Real users invited starting week 4
04
Launch + handover
Final week. Final QA, performance audit, security audit, documentation pass. Full handover meeting with your team or successor developer. Repo access, credentials, runbook, architecture doc, 30-day bug-fix support.
- Production launch
- Handover doc (12–20 pages)
- Recorded handover meeting
- 30-day bug-fix window
Section 02Principles
Non-negotiables of every engagement.
Principle 01
Every week you see working software in a browser. If you don't, the engagement is paused and diagnosed.
Principle 02
All communication is in writing. Meetings are recorded. Decisions have dated owners.
Principle 03
The price in the SOW is the price on the invoice. Scope changes are quoted and approved before work starts.
Principle 04
If we miss a milestone, we eat the delay. If you delay feedback, the timeline shifts with written acknowledgement.
Section 03FAQ
Process questions.
Q/01 What if my project doesn't fit this process?+
Then we say so. The 4-stage process is optimised for fixed-scope MVPs and web apps. For rescue projects, dedicated-developer engagements, or multi-phase programs, we adapt. We still write a scope doc and run weekly demos — the rest flexes.
Q/02 Do I have to be technical to work with you?+
No. About half our clients are non-technical founders. We translate between your business language and engineering language. Scope docs are written in plain English with diagrams, not in developer jargon.
Q/03 How do you track progress?+
GitHub Issues + Projects for engineering. Linear for some clients who prefer it. You have read access from day one. Weekly status email with burndown + blockers.
Q/04 What if I don't like the work?+
Weekly demos exist so you cannot be surprised at the end. If in week 3 you tell us the direction is wrong, we course-correct in week 4. If in week 4 you tell us the entire engagement was a mistake, we refund the remaining milestone and part ways professionally. This has happened exactly once in our history.
CorrespondenceGet in touch