The 7-Day Launch Readiness Sprint is a $99 guided programme that takes a working AI-built app from “it works in preview” to an evidence-backed Ready, Conditional release or Hold decision. You test the running system against the nine-area Zenveus Production Readiness Standard, one focused session a day.
No code access neededSeven 60–120 minute sessionsClear-decision guarantee
The product
It is a self-guided sprint for founders who built an app with AI and need to know whether real customers can safely use it. Each day covers specific Production Readiness Standard areas, gives you exact tests and AI prompts, and adds evidence to one launch report.
An honest boundary
Take it if your app already works, real users or paying customers are next, and you can open your repository, hosting dashboard and database console yourself. It suits apps built mostly with Lovable, Bolt, Replit, Cursor, Claude Code, v0 or Supabase.
RIGHT FIT
NOT THIS PRODUCT
Free, DIY or reviewed
The free production readiness self-check reads your repository and reports what the code shows. The sprint goes further: you restore a backup, replay a webhook, double-submit a payment and trigger an alert. Most “not verified” gaps become proven passes or confirmed fails.
| Free self-check | Launch Readiness Sprint | 48-Hour Verdict | |
|---|---|---|---|
| Who does the work | Your AI assistant | You, guided daily | A named senior engineer |
| What gets checked | The code | The code and the running system | Code, system and your evidence |
| Result | Provisional score | Evidence-backed decision and fix backlog | Signed decision, keep/refactor/rebuild, effort bands |
| Price | Free | $99 | $299, or $199 after the sprint |
How the week works
Each day takes 60 to 120 minutes and ends with evidence in your workbook. You map the system first, then test users and data, money, failure paths, recovery and visibility. Day 7 turns the evidence into a scored decision and a ranked fix list.
Run the baseline self-check, map every service and secret, and pick the workflows that would hurt most if they failed.
Prove one user can’t read or change another user’s data, sessions expire, and no production key reaches the browser.
In test mode, double-click Pay, replay a webhook and deliver events out of order. Pairs with the Webhook Integrity Checker.
Bad input, killed requests, timed-out APIs, oversized files. Record what users see and what your data looks like.
Restore a backup to a copy, roll back a deployment, and check a failed test actually blocks a release.
Error tracking, uptime checks and alerts for payments and jobs, each confirmed to reach a person.
Rescore all nine areas, apply the critical-failure cap, choose Ready, Conditional release or Hold, and rank the fixes.
Exact output
You finish with a Launch Readiness Report you can act on, share with a developer, or send to Zenveus. It contains your scored decision, the evidence behind each of the nine areas, every confirmed risk, and the fixes ranked by what blocks launch first.
Decision, score, critical workflows and the reasoning in plain language.
What you tested, how, the result and where the proof lives.
Each risk with severity, owner, acceptance test and launch blocker yes/no.
46 tests you can rerun before every release.
Read-only prompts for Cursor, Claude Code or your builder’s agent.
A completed report for a fictional app, so you know what good looks like.
Your code stays yours
Nothing. You run every test yourself, and your code, data and credentials never leave your environment. If you later want an engineer’s opinion, you choose to send your report. The engineer starts from your evidence instead of from zero.
After the decision
A Hold is useful: it tells you what to fix before customers find it. Your fix backlog lists blockers first. Your own developer can work through it, or you can ask a Zenveus engineer to verify the findings and estimate the work.
Low risk
You get your $99 back. Finish all seven days. If you don’t end up with a clear Ready, Conditional release or Hold decision and a ranked fix list, send your completed workbook within 30 days of purchase and we’ll refund you in full.
Complete the seven modules and send the workbook within 30 days. If the sprint didn’t give you a decision and a fix list, we refund the full $99.
Reply to any sprint email with the day and step number. A Zenveus engineer answers within 1–2 hours during business hours. Sprint steps only, not a code review.
Sprint buyers get the 48-Hour Verdict for $199 instead of $299. That’s $100 off, with no expiry.
Your tools
The tests apply to any web app with users, a database and a deployment. The prompts are written for Cursor, Claude Code and builder agents, with notes for Supabase, Firebase, Stripe, Vercel, Netlify and Replit deployments where their behaviour differs.
Save with a bundle
Yes. If you expect to need the next stage too, a Founder Bundle includes this product for less than buying each one separately. Every product keeps its own guarantee, support and the $199 Verdict upgrade, and nothing expires, so open each one when you reach that stage.
Includes the Last 20% Sprint and the Launch Readiness Sprint.
You save $29
See the bundle FOUNDER BUNDLEBuilder-to-Business Bundle$199Includes the Launch Readiness Sprint, Scale Readiness Sprint and Developer Handoff Pack.
You save $128
See the bundle FOUNDER BUNDLEFounder Technical Survival Pack$299Includes all six founder products, from finishing the app to investor diligence.
You save $405
See the bundleStraight answers
No, but you need to be comfortable opening your repository, hosting dashboard and database console, and pasting prompts into an AI coding assistant. Each step says exactly where to click or what to run.
No. The prompts are read-only unless a step explicitly says otherwise. Destructive tests run on a staging copy, and payment tests run in your provider’s test mode.
It means you have an evidence-backed decision. A Ready result is your own assessment against the Standard, not a certification or a signed Zenveus Verdict.
After buying the sprint, you get a separate Verdict checkout at $199 instead of $299. It never expires. Your report becomes the engineer’s starting baseline.
Yes. Finish all seven days. If you don’t have a clear Ready, Conditional release or Hold decision and a ranked fix list, send your completed workbook within 30 days of purchase and we’ll refund the full $99.
Reply to any sprint email with the day and step number. A Zenveus engineer answers within 1–2 hours during business hours. Support covers the sprint’s steps, not a review of your code.
Day 1 shows you how to create a safe copy for the destructive tests. If that isn’t possible, those tests are marked “not verified” instead of being run on production.
Yes. Days are sessions, not calendar deadlines. Most people take a week because the restore and alert tests need some waiting.
The next decision
Seven sessions, one decision, and a fix list you can act on.
Covered by the clear-decision guarantee: finish the sprint, and if you don’t have a decision and a fix list, get your $99 back within 30 days.
