Service

A version one you can charge for

Not a prototype, not a clickable mock. Software real customers can sign up for and pay for, small on purpose and complete where it counts.

Typically 2–4 weeks

Version one, built to be charged for

We build the smallest product a real customer can sign up for and pay for. That means it is complete where it counts — someone can create an account, use the thing, and be billed for it — and deliberately thin everywhere else. Prototypes get thrown away the moment they start working; this does not. You end the first month with software in front of real users, not a demo that has to be rebuilt before launch.

Auth, data model, billing and admin as needed
Deployed on your accounts with monitoring
A demo every Friday from week one
Two weeks of post-launch support

What's in the box

Accounts and authentication, the data model, payments, and an admin screen so you can run the business without asking us to write a database query. These are the parts founders consistently underestimate, and the parts that quietly eat three weeks when they are left until the end. We build them first, with patterns that have already survived real traffic, so the interesting part of your product sits on a foundation that works.

How the month runs

You add requests to a queue and we work them one at a time, deploying as we go rather than saving everything for a reveal at the end. There is a working demo every Friday, whether the week went well or not — if something slipped, you hear it with weeks left to react instead of on the deadline. Priorities change, so you can reorder the queue whenever you like; you are paying for a build slot, not a fixed list agreed months ago.

Yours from the first commit

Everything lives in your GitHub organisation, runs on your cloud accounts, and bills through your Stripe. That is true from day one, not on final payment. Cancel the subscription and nothing stops working — there is no runtime of ours in the middle, no licence to keep paying, nothing proprietary to unpick. Handover is a document and an access list, not a negotiation.

How it runs

Same four steps, every project

01
Scope
A call, then a one-page scope: what gets built, what it costs, what date it lands, and what is explicitly not included.
02
Build
The core of the thing first, on your infrastructure from day one. A working demo every Friday, whether the week went well or not.
03
Harden
The parts everyone skips — empty states, errors, retries, analytics, and the case where a user does something strange.
04
Ship
Live, with monitoring and a handover doc. Two weeks of support included, then you take it or we stay on.