FOR FOUNDERS · PRE-SEED TO SERIES A

Startups.

You have somewhere between nine and eighteen months to prove this is real. The wrong architecture call does not announce itself in week three — it surfaces in week twelve, as a rewrite you cannot afford.

01–09 SPENT 12 LAST MONTH A PIVOT IS CHEAP 18 RUNWAY ENDS
01 — THE CLOCK

Runway is the only currency you actually spend.

Most of a startup's technical risk lands in the first 90 days — the architecture call, the build-versus-buy call, the assumption nobody thought to test
A wrong call at week three does not surface until week twelve. By then it is a rewrite, not a fix
Hiring that judgment in-house takes months and a package you cannot justify at this stage
A generic dev shop builds the spec exactly — including the parts of it that are wrong
02 — WHAT SURVIVES THE TEST
solution-startups-runway

RUNWAY SPENT LEFT TO RIGHT · THE ASSUMPTION TESTED AT THE MARK · ONLY WHAT SURVIVES IT CLIMBS

03 — THE FIRST DECISION

We test the assumption before you build around it.

We map the real gap — technical, market or organisational — before a line of code gets written
An MVP built to disprove the riskiest assumption, not to look complete in a demo
CTO-level architecture judgment and hands-on build, from the same people
Instrumentation for real product-market-fit signal — activation and retention, not vanity metrics
04 — WHAT IT COSTS YOU

No equity. No four-month hire. No lock-in.

What founders ask first
What actually happens
Do we give up equity?
No. A paid technical partner, not a co-founder search. You keep full ownership.
Can we afford a senior team?
Scope is sized to your runway, not to a headcount plan.
Do we get locked into you?
Documented and transferable from the first commit — built to be owned by whoever you hire next.
What are we billed on?
Outcome-owned pricing: what shipped, what was adopted, what moved. Not hours logged.

You do not have to decide about us to find out what the risk is.

A short call, the assumption written down, and an honest read on whether it is a six-week question or a six-month one.

Tell us the assumption →
05 — PROOF AT YOUR STAGE

AirBills went from MVP to $6M ARR.

Validated before it was scaled. The same order we would run on yours — prove the thing works, then make it big.
Fintech rigour at startup speed. The same engineering standard as our regulated work, so what you validate does not need re-architecting the moment it matters.
Built to survive your next hire. Handed over in a state your own engineers can run without us in the room.
WHO WE HAVE SHIPPED WITH
AirBills
BotSupply
ALMO
ViralGet
ekhoo
NeuralSpace
MOXCI
Billtrim
Jatana
Hourworth

Teams that were pre-product when we met them.

06 — THE FIRST NINETY DAYS

Where we start, and in what order.

01

The architecture and stack calls that are expensive to reverse later

02

An MVP built to disprove the riskiest assumption first

03

Instrumentation for real product-market-fit signal — activation and retention, not vanity metrics

04

Scaling what survived into a fundable, production-grade product

07 — BEFORE YOU ASK

What founders raise on the first call.

Do you take equity?

No. A paid technical partner, not a co-founder — you keep full ownership of the company and the code.

How fast to something testable?

Typically weeks, not months, because the scope is one assumption rather than a feature list.

What is the engagement model?

Embedded and sized to your stage — from a few focused weeks to an ongoing technical team through your next raise.

What happens once we hire in-house?

A clean hand-off. Everything is documented so a new engineer picks it up without us.

Who is this not for?

Teams who already know exactly what to build and want it typed out cheaply. We are the wrong call if nothing needs proving.

Before you build it, find out whether it is the right thing to build.

Tell us the riskiest assumption in your product — the one where, if it is wrong, none of the rest matters.

Talk to us →