Founder engagements, done honestly.

We take on a small number of founder engagements a year. When the problem is real, the scope can be honest, and you'd rather have a senior team for twelve weeks than a junior team for six months — we're a fit. When you need a code factory to ship someone else's spec, we're not.

Engagement process diagram

What a founder engagement looks like

01.

A paid scoping week

Before we build anything, we spend a week understanding what you're actually trying to ship and why. The output is a written scope, a technical plan, a fixed price, and a date for v1. If we agree the work fits, the scoping fee is credited against the build.

02.

A senior pod, two to four engineers

The team is small and senior. The people you scope with are the people writing the code. No juniors get parachuted in after kickoff. Weekly demos in writing, transparent burn-down against the date on the wall.

03.

First release in twelve weeks, durable enough to scale

We build for first paying customers, not for a hypothetical Series B. Production-grade infrastructure (observability, on-call patterns, rollback) ships from week one. Documentation your future in-house team can actually use ships at handover. No throwaway code, no rewrites in six months.

01.

A paid scoping week

Before we build anything, we spend a week understanding what you're actually trying to ship and why. The output is a written scope, a technical plan, a fixed price, and a date for v1. If we agree the work fits, the scoping fee is credited against the build.

02.

A senior pod, two to four engineers

The team is small and senior. The people you scope with are the people writing the code. No juniors get parachuted in after kickoff. Weekly demos in writing, transparent burn-down against the date on the wall.

03.

First release in twelve weeks, durable enough to scale

We build for first paying customers, not for a hypothetical Series B. Production-grade infrastructure (observability, on-call patterns, rollback) ships from week one. Documentation your future in-house team can actually use ships at handover. No throwaway code, no rewrites in six months.

The shape of founder engagements

From scoping week to first paying-customer release, on a typical founder engagement
NOVA
12 weeks
Founder engagements we take on per year — a small number, on purpose
NOVA
[N]
Two-to-four-person team, the same people from week one to handover
NOVA
1 senior pod
We charge for work, not for a slice of the company
NOVA
0 equity

When we say yes — and when we don't

When the problem is real (you've spoken to customers, not just had the idea), the scope can be honest (we agree on what v1 is and what it isn't), and you'd rather pay for senior engineering than try to manage a cheaper team for twice the time. Best when you have a budget for a focused twelve-week sprint and want a v1 that won't need rebuilding inside a year.

When you need a code factory to ship a fully-specified design with no room to push back. When the budget assumes offshore-rate pricing. When you want equity-for-build (we don't take equity — we charge for work). When you need a CTO replacement — we'll point you at fractional CTOs who fit better.

No. Equity-for-build creates a relationship where neither side is honest — we're never sure if we're shipping for the customer or for the cap table. We charge fixed price, in cash. If you want a long-term technical advisor with skin in the game, we'll introduce you to people who do that.

A live product your first customers can use and pay for. Discovery, design, build, and a production deploy — all by the same team, in one flow. Plus documentation, observability, and a thirty-day post-launch window where we're still on call.

Sixty minutes. Bring the problem you're stuck on — not a polished pitch. We'll leave you with a one-page memo on how we'd approach it. If we're a fit, we book a paid scoping week within the next two weeks. If we're not, we'll usually suggest someone who is.

An agency runs many projects at half-attention and ships them with juniors. A freelancer ships fast but can't carry the design / infra / handover the way a small senior team can. We're closer to an in-house early team you rent for a quarter — same depth, none of the hiring.

Distributed, with an anchor presence in [primary hub] and team members across [secondary hubs]. We work async-first, but we'll fly to you for kickoff if the engagement is right and the geography makes sense.

Tell us what you're trying to ship.

Bring the problem, not the spec. The first call is a working session, not a pitch. You'll leave with a one-page memo on how we'd approach it.