Ship in 30 days,
or we extend you free
Follow the ten phases and if a step does not boot, we fix the kit as our top priority or extend your Pro access free until it does. No fine print, and no arguing about whose fault it was.
Start a buildHow it works
A kit failure is our emergency
If a phase does not boot when you follow it, that is our problem and it jumps the queue: a 48 hour fix priority, or your Pro access extended free until it works. You are never left holding a broken step on your own at any point.
Follow the sequenced path
The kit drips one phase at a time with pre-written fixes for the exact places builders get stuck. Following it is what makes the guarantee apply to your build.
If it does not boot, we act
If you follow the path and a kit step fails to reach a running MVP, we fix the kit fast or extend your Pro access free until it does.
Proof, not a promise
Smoke-tested to a running MVP
57 of 200 kits carry a logged test: built end to end on a real stack until the MVP booted. The rest are being worked through, and the log below is the newest runs as they happened.
QA logged with stack and date
Every pass records the stack, the agent, and the date, so the proof is auditable rather than asserted. An untested kit shows as untested.
The guarantee needs three legs
Your progress here, our own check of your live URL, and the kit's QA. An agent's word never decides it, because that is the one thing a determined person could fake.
| Kit | Stack | Result |
|---|---|---|
| Bundleready | Next.js + R2 | MVP booted |
| Sourcegate | Next.js + Postgres | MVP booted |
| Splitrate | Next.js + Postgres | MVP booted |
| Authchain | Next.js + Postgres | MVP booted |
What the guarantee covers
What keeps you eligible
Start from a published kit
Pick an idea from the catalog and start its kit. The guarantee is on our path, not on a build you assembled yourself.
Ship the phases in order
The sequence exists because it works. Skipping ahead is allowed, but the guarantee tracks the sequenced path.
Report a failure when you hit it
Tell us the phase that failed from inside your dashboard. That opens the 48-hour fix priority.
If it fails, here is the clock
You report the phase that failed from your dashboard. It lands in the refund-risk queue, which is the highest priority class of work we run. You get a fix, or free time, or both.
Verified Builder, when it boots
When your MVP answers on your own live URL, we check it ourselves and the Verified Builder badge is yours. It is real proof you shipped, not a participation mark, and it is never awarded from a number that you have simply reported to us yourself.
Frequently asked
What exactly do I get if a kit fails?
We fix the kit as the top priority, and if the fix takes time we extend your Pro access free so the delay costs you nothing.
How fast is the fix?
Kit failures reported by paying builders carry a 48-hour fix priority. They are the highest-priority class of work we have.
Does the guarantee cover my own code?
No. It covers our kit and our context files. Once you diverge from the path, the guarantee cannot follow you, though the blocker library still can help you.
Is there a refund too?
Yes, separately: a new paid plan has a 7-day money-back window, no questions asked.
Do I have to finish in 30 days?
No. Thirty days is the pace the kits are built for, not a deadline that voids anything. Rest days are expected.
Who decides if it failed?
Not an agent report. We check your live deploy URL ourselves against the kit's QA log, so eligibility is never someone's opinion.
The risk is on us, not you
Start free, pick a proven idea, and build with a kit that has already been shipped once.