Keep shipping after launch. Without hiring a team.

It’s priced to each month’s work, so there’s no number on this page. Each month’s work and price are agreed in writing before it starts, and the price only moves when you approve a change. If someone else built your product, a paid code review comes first.

If we built it, the month after launch, with the same lead and no ramp-up. If someone else built it, the code review takes one to two weeks, then your first month starts.

You should, once the product needs a full team every day. Until then, a senior hire takes months to find, months more to learn the code, and covers one skill. When you’re ready, we bring your engineers into the code at their pace.

Yes. The code review tells you plainly what’s solid, what’s fragile and what to fix first, before you commit to a month. If it’s worth building on, we build on it. If it isn’t, we’ll say so.

An engineer who knows the system is on call. How fast depends on how serious it is: an outage comes before everything else. Afterwards you get a written account: what happened and what changed so it doesn’t happen again.

Your lead stays your lead. The new engineer overlaps with the one leaving, at our cost, and works from the decisions and runbooks already in your repo. Nothing starts over.

Every change goes through staging and your approval first, ships on a day you know, and can be rolled back if anything goes wrong. Bigger changes go to a few customers first, then everyone.

Yes. Your repo, your tracker, your chat and your alerts. Anyone who touches your code is under contract and NDA with us.

Yes. The month’s plan can grow for a big release, with about two weeks’ notice, or shrink for a quiet quarter. You approve it at each roadmap review, and there’s no hiring round either way.

Start with the build. The lead who runs it can stay on after launch: Custom software.