Builder ModeEveryone can build now.
Almost nobody finishes.
Either you want the tools and you will do it yourself, or you want the thing to exist and you would rather that were somebody’s job. Four options, priced on this page in US dollars, with dates that mean something.
Prompt Pack
Every build prompt, in a private repo, kept current.
US$99paid in full, once — not a subscription. Priced in US dollars.
instant
You are building it yourself and want to stop starting from a blank box.
- Prompts grouped by task: specs, schema design, review, debugging, naming
- The failure cases each one is written to avoid
- Rewrites when a model or a stack moves — you pull, you have the current one
- The scoring rubric and the cost model, so you can run them yourself
Don’t buy this if: You want a finished product. This is a set of tools, not a build.
MVP Mini
A landing page, or a site up to three pages, built and deployed.
US$1,000paid in full, once — not a subscription. Priced in US dollars.
1 to 3 working days from kickoff
You need something at a real address this week, not this quarter.
- One to three pages, written, built and live on your domain
- Copy drafted from what you tell us the page is for
- A contact or signup form wired to an inbox, and tested
- Your repo from the first commit, yours to keep
Don’t buy this if: People need to sign in, or it has to take money. That is the MVP.
- Most people start here
MVP
One clearly-scoped product, built, deployed and handed over.
US$5,00050% now to book the week, 50% on completion. Priced in US dollars.
5 working days from kickoff
US$2,500 today, US$2,500 at handover.
One platform included. Each extra adds US$5,000.
You can describe the thing in a paragraph and you want it to exist.
- One primary flow done properly, not six done badly
- Your data model and your domain, with the repo transferred on completion
- Deployed and running on your domain, not a zip file
- One round of changes after you have used it
- Documentation: how it works, how to run it, how to change it
Don’t buy this if: It has to survive real users on day one. That is the Full Build.
Full Build
The version you would put a paying customer in front of.
US$10,00050% now to book the week, 50% on completion. Priced in US dollars.
2 weeks from kickoff
US$5,000 today, US$5,000 at handover.
One platform included. Each extra adds US$10,000.
It has to work when strangers use it, and you want that to be somebody’s job.
- Everything in the MVP, plus the parts that make it real
- Auth, billing or integrations — pick the two that matter
- Error handling, rate limits and the security traps that apply
- Two rounds of changes, and a handover call
- Documentation: architecture, deployment, and the decisions behind both
Don’t buy this if: You are still deciding what it is. Scope it as an MVP first and grow it.
How it runs
Five steps, and you only do two of them.
- 01
You pay half and take a slot
Prices are on this page, not behind a call. Half up front reserves a build week — only a couple run at a time, which is why the dates are real and why the slot is what you are actually buying. The Prompt Pack is a download and is paid in full.
- 02
You send the brief
A few questions, plus anything you already have: designs, reference URLs, a spreadsheet of how it works today, access to whatever it has to connect to. Ten minutes, and it is the ten minutes that decides how this goes.
- 03
The scope is agreed in writing
One page: what is being built, what is explicitly not, and the date. You approve it before anything is written.
- 04
You see it early
A working URL well before the end, not a reveal at the finish. Changes are cheap while it is being built and expensive afterwards, which is the entire reason you see it early.
- 05
Handover
The balance falls due, the repo transfers to you and it goes live under your own account. Then your round or rounds of changes.
What you need to bring
Not the ability to write code. What decides whether this goes well is whether you know which part of your product is being made, and can hand over the detail behind it.
A clear idea of which part is being built
Not the whole roadmap — the piece. Knowing that this build is the booking flow and not the billing is worth more than any technical vocabulary.
The detail behind it
The rules that live in your head: who is allowed to do what, what happens on the awkward Tuesday, the customer who always asks for the exception. That context is the difference between something that works and something that demos.
Coding knowledge, if you have it
Helpful, never required. It makes the review conversations quicker and it means the handover documentation lands sooner. Plenty of people buy a build having never opened an editor, and it goes fine.
One person who decides
Somebody who can answer a question the same day. Most delays on a short build are not technical.
What you get asked
Five at most, and only the ones your build needs. Every one changes what gets made or what it costs, and there is no sixth — scoping should not feel like a mortgage application. The Prompt Pack asks none of them: it is a repo, not a job.
- What is it, in a paragraph?Plain words. If you can’t write it, that is the first thing to fix — and it is free to fix now.
- Who uses it, and what do they do first?The primary flow. Everything else is decoration until that one works.
- What does it have to connect to?Stripe, a calendar, an existing database, a spreadsheet somebody maintains by hand.
- Is there anything it must not do?Compliance, data that cannot leave a country, a competitor you would rather it did not resemble.
- Who signs off?One name. Two people with different opinions is the most expensive thing that can happen to a two-week build.Full Build only
Send whatever you already have with it: Figma files, screenshots, reference URLs, a spreadsheet of how the process works today, sample data with the real names taken out. None of it is required. All of it makes the result closer to what was in your head.
Questions people actually ask
Do I need to be able to code?
No. Coding knowledge helps — it makes reviewing quicker and the handover land sooner — but what actually matters is that you understand which part of your product is being built and can give the detail behind it. The rules in your head are the thing nobody outside your business can guess, and no amount of technical vocabulary substitutes for them.
What currency is this?
US dollars, every figure on the page. Checkout will offer to show the amount in your local currency with the conversion made for you, and you can pay in either — paying in US dollars avoids the conversion fee that the localised amount includes.
Why is the price on the page?
Because you were going to ask, and a call whose only purpose is finding out whether you can afford it wastes an afternoon on both sides. If the number works, the rest of the conversation is about the actual thing.
What does “5 working days” actually mean?
Five days from kickoff, and kickoff is when the brief, the materials and any access are in — not when you pay. The date is one you control rather than one imposed on you: send the brief a week later and the week moves.
What if the brief turns out to be bigger than the tier?
You hear that at the scope stage, in writing, before anything is built — not halfway through. Either it gets cut back to fit, or you move up a tier and pay the difference, or you get a refund and nothing was lost but a conversation. The published limits on each tier page exist so this is recognised early rather than discovered late.
Can I keep adding things once it has started?
You can ask, always. Anything new gets an estimate and a date before it begins rather than being absorbed silently, because absorbed changes are how a fixed date stops being real. Swapping something in for something out is free — that is a trade, not an addition.
Why half up front?
Because it reserves a build week that nobody else can have, and because you should not be handing a stranger the full amount before there is a written scope. The second half falls due at handover, when the repo transfers and it goes live on your domain — so neither of us is relying on the other's goodwill. MVP Mini is the exception: it does not reserve a week, so there is nothing to hold and it is paid once.
Do I own it?
Entirely, once the price is paid in full — the repo transfers to you and it goes live on your domain. Until then you have read access and a working URL, so you can see exactly what you are buying. After that there is no licence, no hosting to keep renting, and nothing that stops working if we never speak again.
Is it AI-generated code?
It is written with AI tooling and reviewed by someone who has to answer for it. That is the honest answer, and it is why the documentation and the handover exist — you should be able to change it without us.
What if I don’t like it?
That is what seeing it early is for. If it is genuinely not what the scope document agreed, it gets fixed. If you have changed your mind about what you want, that is a new scope and an honest conversation about it.
What is the difference between MVP Mini and the MVP?
Whether anybody signs in. MVP Mini is a site — up to three pages, a form that reaches your inbox, live on your domain in one to three days. The moment it needs accounts, stored user data or payments, it is an MVP, and that is a different job rather than a bigger version of the same one. If you are not sure which you need, start by describing what a visitor does; if the answer ends at “sends you a message”, it is the Mini.
Can I buy the Prompt Pack and a build?
Yes, and there is no discount for it — they are different things rather than tiers of the same thing. Most people who buy a build never want the pack.