03
Small SaaS
Small on purpose. We build the version that answers whether anyone wants this, on boring infrastructure you can afford to run before it earns anything — and we tell you which parts are deliberately unfinished.
What you actually receive
- A working product with real authentication, real billing and real error handling.
- A deployment pipeline, so shipping is not an event.
- The repository, the infrastructure definition and the accounts, all in your name.
- A written list of the shortcuts we took and what each one will cost to undo.
Small on purpose
The failure mode for a first version is not that it is too simple. It is that it took nine months and answered nothing.
- Weeks one to two
- Discovery. What is the smallest thing that tells you whether this is worth building, and what does it cost to run?
- The build
- Boring infrastructure, one deployment path, real auth and real billing from the start — the three things retrofitting punishes.
- At launch
- A written list of every shortcut and what undoing it will cost, so scaling decisions are informed rather than discovered.
- After
- A support window. Somebody has to be there the week people first use it.
What this is not
- We do not build a platform before you have a product.
- We do not put a machine-learning feature in because it is fashionable.
- We do not disappear at launch. Somebody has to be there the week after.
- Typical duration
- 6 to 14 weeks for a first version
- Engagement
- Staged, with a decision point after discovery
- Best fit
- A tool for a market you already understand
Four stages, start to handover
- 01
A brief, then a conversation
You send four short answers. We read them and reply within one working day, either with questions or with a straight answer about whether we are the right studio for it.
- 02
Scope written down
What is being built, what is not, what it costs and when. If we cannot describe it clearly enough to price it, that is a sign the scope is not ready — and we will say so.
- 03
Build, in the open
Work lands in your repository from the first week. You see progress as commits and working previews, not as a status meeting.
- 04
Handover that survives us
Documentation for the next developer, the accounts in your name, and a walkthrough with whoever has to run it. Then a support window while you settle in.
Ready when you are.
Four short questions, about two minutes. A reply within one working day.