Current view

Launch Plan

Sandpaper Engine

Launch Plan

A deterministic roadmap that converts the current mock scan into a prioritized pre-launch fix order.

Launch readiness

68%

Your app is 68% launch-ready.

Launch status

Needs Work

Based on the current mock scan score and open launch blockers.

Required fixes

8

Must resolve before launch

Prompt phases

9

Cursor, Lovable, Claude Code actions

Next recommended fix

Selected by severity, launch phase, blocker status, and prompt availability.

Criticaldeployment

Env vars must be configured

Missing production env vars can break Vercel deploys, auth callbacks, billing, and AI routes.

Document and verify required production environment variables.

Trust guardrails

Score/status caps that prevent overstating launch readiness.

No score guardrail warnings for the current plan.

Required Before Launch

8 items

Criticalauth

Auth must work

Verify login, signup, password reset, protected routes, and onboarding redirects.

Criticalbilling

Billing must sync

Verify checkout, webhook signature handling, subscription sync, and customer portal behavior.

Criticaldatabase

Database must protect user data

Verify user_id ownership, RLS policies, and service-role safety.

Criticaldeployment

Env vars must be configured

Document and verify required production environment variables.

Criticaldeployment

App must build/deploy

Run lint/build and fix blocking deployment errors before feature polish.

Highai

AI usage limits

Add rate-limit and token/usage tracking guards before provider calls.

Criticaldeployment_risk

Production environment variables are undocumented

Create a complete environment variable reference and verify required keys during setup.

Highmissing_feature

Checkout success state has no verification path

Add a mocked success state and clear next action until Stripe wiring is implemented.

Recommended Before Paid Launch

13 items

Highsupport

Users must be able to contact support

Add support email, contact page, or support link in the app shell.

Highlegal

Privacy/terms pages must exist

Add privacy and terms pages with clear review placeholders.

Mediumcustomer_success

Welcome email

Add welcome email copy or a placeholder integration plan.

Mediumobservability

Error logging

Add lightweight error logging notes or a scaffold compatible with the app.

Mediumobservability

Analytics

Add analytics placeholders for signup, onboarding, checkout, and activation events.

Mediumbilling

Customer portal

Add customer portal path or clear management placeholder.

Mediumbilling

Upgrade prompts

Add upgrade copy around limited or premium features.

Mediumoperations

Admin visibility

Add a minimal admin visibility plan without exposing public admin routes.

Optional After Launch

5 items

Lowgrowth

Team accounts

Plan team invites and roles after single-user launch readiness is verified.

Lowgrowth

Referral tracking

Add referral tracking later as a growth feature.

Lowproduct

Advanced reports

Defer advanced reporting until after launch blockers are removed.

Lowintegrations

More integrations

Add integrations after the core launch path is reliable.

Lowautomation

Auto-fix agent

Keep auto-fix as a post-launch feature.

Fix order

Prioritized roadmap from deploy blockers through final smoke test.

Phase 1: Build/deploy blockers

3 launch plan items to resolve.

Criticaldeployment

Env vars must be configured

Missing production env vars can break Vercel deploys, auth callbacks, billing, and AI routes.

Document and verify required production environment variables.

Criticaldeployment

App must build/deploy

A launch is blocked until the production build and deploy path are reliable.

Run lint/build and fix blocking deployment errors before feature polish.

Criticaldeployment_risk

Production environment variables are undocumented

A missing env contract can break the first Vercel deployment and hide billing failures.

Create a complete environment variable reference and verify required keys during setup.

Phase 2: Auth/onboarding

1 launch plan item to resolve.

Criticalauth

Auth must work

Users need a reliable way to sign up, log in, recover access, and reach protected pages.

Verify login, signup, password reset, protected routes, and onboarding redirects.

Phase 3: Billing/subscription access

4 launch plan items to resolve.

Criticalbilling

Billing must sync

Paid launches fail if checkout, webhook sync, and subscription access are unreliable.

Verify checkout, webhook signature handling, subscription sync, and customer portal behavior.

Highmissing_feature

Checkout success state has no verification path

Users may pay and land in an ambiguous state, creating support and trust issues.

Add a mocked success state and clear next action until Stripe wiring is implemented.

Mediumbilling

Customer portal

Paid users need a way to manage subscription changes and cancellations.

Add customer portal path or clear management placeholder.

Mediumbug:validation

Plan selector accepts an unsupported billing tier

Generated plan list includes a legacy tier not present in checkout copy.

Constrain plan selection to the current pricing tiers.

Phase 4: Database/RLS

1 launch plan item to resolve.

Criticaldatabase

Database must protect user data

User-owned data needs RLS and ownership rules before production traffic.

Verify user_id ownership, RLS policies, and service-role safety.

Phase 5: AI usage/cost protection

1 launch plan item to resolve.

Highai

AI usage limits

AI routes can create runaway cost without rate limits and usage tracking.

Add rate-limit and token/usage tracking guards before provider calls.

Phase 6: Legal/trust

1 launch plan item to resolve.

Highlegal

Privacy/terms pages must exist

Legal and trust pages are expected before account creation and paid checkout.

Add privacy and terms pages with clear review placeholders.

Phase 7: Customer success

8 launch plan items to resolve.

Highsupport

Users must be able to contact support

Early customers need a clear support path when launch issues appear.

Add support email, contact page, or support link in the app shell.

Mediumcustomer_success

Welcome email

A welcome email reinforces activation and gives users a recovery path after signup.

Add welcome email copy or a placeholder integration plan.

Mediumbilling

Upgrade prompts

Users should understand plan limits and paid value before upgrading.

Add upgrade copy around limited or premium features.

Lowgrowth

Team accounts

Teams can expand account value after the first launch path works.

Plan team invites and roles after single-user launch readiness is verified.

Lowgrowth

Referral tracking

Referral tracking is useful after core activation and billing are stable.

Add referral tracking later as a growth feature.

Lowproduct

Advanced reports

Advanced reports can improve retention after the MVP proves value.

Defer advanced reporting until after launch blockers are removed.

Lowintegrations

More integrations

Integrations increase value, but they should not block the first launch.

Add integrations after the core launch path is reliable.

Lowautomation

Auto-fix agent

Auto-fix can reduce manual work later, but it increases risk before launch.

Keep auto-fix as a post-launch feature.

Phase 8: Observability

3 launch plan items to resolve.

Mediumobservability

Error logging

Launch issues are hard to diagnose without runtime error visibility.

Add lightweight error logging notes or a scaffold compatible with the app.

Mediumobservability

Analytics

Analytics show whether users reach activation and paid conversion points.

Add analytics placeholders for signup, onboarding, checkout, and activation events.

Mediumoperations

Admin visibility

Founders need visibility into signups, payments, and errors during launch.

Add a minimal admin visibility plan without exposing public admin routes.

Phase 9: Final smoke test

4 launch plan items to resolve.

Highduplicate_conflict

Duplicate dashboard route patterns conflict

Conflicting route ownership makes future fixes unpredictable and slows launch QA.

Pick the App Router dashboard as canonical and remove the stale generated page.

Highbug:runtime_error

Settings page assumes a loaded user profile

Mock inspection found profile.name usage before a loading or empty state.

Add an explicit loading and empty state before rendering profile fields.

Highduplicate:route_conflict

Competing dashboard implementations

Both routes describe the same product surface with different data assumptions.

Remove or archive the legacy pages route before launch QA.

Mediumduplicate:component_duplicate

Repeated metric card components

Styling and number formatting can drift across launch surfaces.

Consolidate to one shared component after launch blockers are fixed.

Final smoke test checklist

Run these checks after phase fixes are complete.

[ ]

Signup works for a new user.

[ ]

Login works for an existing user.

[ ]

Password reset flow renders and is linked from login.

[ ]

Protected routes reject unauthenticated users.

[ ]

Stripe checkout works in the intended test/live mode.

[ ]

Stripe webhook signature verification is present.

[ ]

Supabase RLS prevents cross-user data access.

[ ]

AI routes have rate limits.

[ ]

AI routes record usage or cost-tracking evidence.

[ ]

AI-generated output is labeled for users.

[ ]

Customer portal route is protected by auth.

[ ]

Onboarding works from first login to dashboard.

[ ]

Dashboard loads with empty-state guidance.

[ ]

Key environment variables are documented and configured.

[ ]

Privacy and terms pages exist and are reachable.

[ ]

Support path exists and is reachable.

[ ]

Production build passes.

[ ]

Deployment configuration is reviewed.