Frequently asked questions
Straight answers, including the ones that limit what this tool claims.
Founders and small teams about to ship a website, web app, or SaaS product — especially first-time founders and solo builders who don't have a launch checklist from experience yet. It's also useful before a major relaunch, a pricing change, or a big marketing push, when the cost of a broken launch is highest.
Yes. The questions ask whether you have backups, monitoring, and analytics — not which vendor you bought them from. No question rewards a particular hosting provider, framework, or tool. The playbooks name categories of tools, not brands.
No. The score checks that you've done the important things — it doesn't do them for you or verify the quality of how you did them. It is not a substitute for QA testing, load testing, penetration testing, a security review, or legal review. A 100 means you checked the boxes that most often cause launches to fail; it doesn't mean your code is correct. See the methodology page for the full honest limits.
Nowhere. The assessment runs entirely in your browser: your answers are saved to your own device's local storage so you can resume later, and the score is computed locally. There is no backend, no account, and no analytics tracking your answers.
Nothing. It's a readiness signal, not a guarantee — it measures launch execution discipline, not product-market fit, code quality, or demand. Treat a high score as "we did the homework," not "we can't fail."
Mark it N/A. N/A answers are excluded from the denominator entirely — they neither help nor hurt your score. If a whole dimension is N/A, that dimension drops out and the remaining weights are re-normalized. Mark N/A honestly: if you're unsure whether something applies, it probably does.
Yes — two ways. The Copy checklist button exports your results as markdown (score, blockers, partials, dimension scores) to your clipboard, ready to paste into a doc, ticket, or chat. The Print report button renders a clean printable version. Both are on the results screen of the assessment.
No — explicitly not. This is a self-serve tool: we give you the score, the ranked blockers, and the playbooks, and you do the work. We don't touch your accounts, run your launch, or take incident liability. If you need hands-on help, hire a launch consultant or a DevOps freelancer; the checklist export makes a great brief for one.
Ready = 1 point, Partial = 0.5, Missing = 0, N/A = excluded. Each dimension scores 0–100 from its answered questions, then dimensions combine by weight: Technical 20%, Launch mechanics 20%, Content 15%, Discovery 15%, Trust 15%, Post-launch 15%. The same answers always produce the same score. Full formula, a worked example, and the score bands are on the methodology page.
A planned paid tier: continuous readiness monitoring with scheduled re-assessments, drift alerts, and advanced playbooks. It's honestly marked coming soon — it isn't built yet, so there's no price, no checkout, and no waitlist. See pricing for the roadmap.
Run it once when a launch date first appears on the calendar, again after you've worked the blocker list, and a final time in the 48-hour preflight window. For major relaunches or after big infrastructure changes, treat it as a fresh assessment rather than an update.
Yes. The full assessment, the score, the blocker list, the checklist export, the printable report, and all six playbooks are free with no account. The only paid tier is LaunchStack Monitor, which doesn't exist yet.