7-Day SaaS Build Challenge
Build a testable landing-page copy-grader prototype in 7 days. Wire up the Claude API, add Supabase auth with a 3-grade free tier, connect a Stripe test checkout, build results history and public share links, then prepare it for review. No coding experience required. This challenge does not guarantee production readiness, security, revenue, or a successful launch.
7-day roadmap
Design the product and write the grading prompt
Decide exactly what the tool does and write the Claude system prompt that powers it. Test it manually until it gives honest, specific feedback.
Build the input form and deploy it live
Scaffold a Next.js app with the four-field form, style it with Tailwind, and deploy to a real Vercel URL.
Wire up the Claude API and display results
Create an API route that sends copy to Claude and renders the graded scorecard below the form.
Add Supabase auth and the 3-grade free limit
Add Google sign-in, track usage per user in Supabase, and gate the 4th grade behind an upgrade prompt.
Add Stripe test billing and webhook checks
Create a $15/month test subscription, verify webhook signatures, handle duplicate events, idempotency, retries, delayed events, and test user entitlements separately.
Build results history and public-safe share links
Use sample/test data to build history and public share URLs that expose only approved result fields. Keep emails, auth IDs, payment state, private rows, and admin data out; verify Supabase RLS and share-link access separately.
Review the prototype and prepare next steps
Build the marketing landing page, verify Supabase RLS and user-data isolation, review privacy policy, terms, refund/cancellation wording, and document rollback/recovery. Do not enable live mode until payment, webhook, and user-access checks pass.
Before any real users or live payments
This challenge prepares a prototype for review. It does not guarantee production readiness, security, revenue, or launch approval.
- Verify payments on the provider side and in the application. Test webhook signatures, duplicate events, idempotency, retries, delayed events, and user entitlements separately.
- Verify Supabase RLS and user-data isolation. Review privacy policy, terms, and refund/cancellation wording before real users.
- Keep Stripe in test mode until payment, webhook, and access checks pass; document rollback and recovery before launch.