How we work
Before we start
Every build starts with a written scope: what we'll build, what we won't, the timeline in weeks, and the price. For anything bigger than a single automation, that comes out of a one-week Discovery that's credited to your build.
Will my project get your attention if you have your own startups?
We take on a limited number of client builds at a time, each with a dedicated delivery schedule and weekly demos.
Communication
You get the same rhythm on every project, so you always know where things are.
- A shared channel (Slack or WhatsApp) for day-to-day questions, answered within one business day
- A written update every Monday: what's done, what's next, anything blocking
- A live demo every Friday on staging, recorded if you can't make it
- A single senior lead who owns delivery from kickoff to launch
You own the code
We work in a repository in your GitHub organisation from day one. Infrastructure runs in accounts you own. When the final payment clears, code and IP transfer to you in writing. No lock-in, no licence fees, no hostage situations.
Changes along the way
Something always changes. Small changes are absorbed. Bigger ones get a short written change request with the effect on time and price, and nothing moves until you agree.
After launch
Launch week is the start. Care plans keep a senior engineer on your product each month: monitoring, updates, and a block of hours for improvements.
How a 6-week MVP ships
Every Friday you see working software. Here's what each week delivers.
Week 1
Scope and design
Kickoff workshop, user flows and a clickable prototype. You sign off the scope in writing before we build.
Friday demo: A clickable prototype of the core journey
Week 2
Foundations
A repository in your GitHub organisation, automated deploys, a staging environment, sign-in and analytics wired up.
Friday demo: A staging link you can open on your phone
Week 3
Core feature
The main user journey, built end to end on staging with real data, not mock screens.
Friday demo: The first complete flow, start to finish
Week 4
Complete the journey
Edge cases, emails and notifications, payments if they're in scope, and the admin basics your team needs.
Friday demo: The full journey, including the awkward paths
Week 5
Harden
Testing with real users, performance and error tracking, and App Store or Play Store submission if it's a mobile app.
Friday demo: A release candidate, with the test notes
Week 6
Launch
Production deploy, handover docs, a launch-week checklist, and a call to plan what v2 should be.
Friday demo: Your product, live
Tell us what you're building.
A 30-minute call. You'll leave with a rough scope, a price range and a timeline, whether or not you build with us.