I Make $250K/Month From 20 Apps

The app we’re building (so the prompts stay coherent)

Name: BlueprintOS
What it does: A web app that helps a solo founder run John’s workflow end-to-end:

  • Capture “pain” ideas

  • Validate via “signal posts” + comments/interest

  • Generate a waitlist landing page

  • Collect signups (goal: 100)

  • Send a 90% presale offer email

  • Take payments (goal: 5 sales)

  • Track “manual delivery” iterations until users are happy

  • Convert to MVP tasks, optional “co-maker” handoff

  • Add cross-promo widgets linking products together

Stack (recommended): Next.js (App Router) + Tailwind + Supabase (Auth/DB) + Stripe + Resend (emails) + PostHog (analytics)

Cursor prompts (copy/paste in order)

Prompt 1 — Create the repo + baseline

You are my senior full-stack engineer. Create a Next.js 14+ app (App Router) with TypeScript and Tailwind.

Requirements:

  • Use Supabase for auth + database

  • Use Stripe for payments (presales)

  • Use Resend for transactional emails

  • Use PostHog for product analytics (optional but scaffold it)

  • Add ESLint + Prettier

  • Add env var validation (zod)

  • Create a clean folder structure and explain where each feature will live.

Output:

  1. exact terminal commands

  2. file tree

  3. .env.example with all required vars

  4. any setup steps for Supabase/Stripe/Resend

Run the commands Cursor gives you, then continue.

Prompt 2 — Data model for “John’s blueprint”

Design the database schema in Supabase (SQL + RLS policies) for this product:

Core entities:

  • users

  • ideas (a “pain” statement + notes)

  • signals (posts/links + engagement metrics)

  • waitlists (each idea can have a waitlist page)

  • waitlist_signups

  • presales (offer configuration + discount)

  • orders (Stripe checkout sessions + status)

  • manual_deliveries (log of “manual fulfillment” iterations)

  • feedback (satisfaction score + notes)

  • mvp_tasks (when we decide to build)

  • co_makers (people + skills + deal terms)

  • launches (twitter/x launch checklist + links)

  • cross_promos (links/widgets to other products)

Rules:

  • An idea is “validated” if waitlist_signups >= 100 AND paid_orders >= 5

  • An idea is “ready_for_mvp” if feedback shows satisfaction >= 4/5 from at least 3 paying users

Deliver:

  • SQL migrations for all tables

  • indexes

  • RLS policies so users only access their own data

  • a short explanation of each table and how the workflow moves across them

Prompt 3 — Implement auth + app shell

Implement Supabase Auth in Next.js App Router:

  • Email/password + magic link

  • Protected routes under /app

  • Public marketing pages under /

  • A dashboard layout with sidebar nav:
    Dashboard, Ideas, Validation, Waitlists, Presales, Manual Delivery, MVP, Co-maker, Launch, Cross-promo, Settings

Include:

  • middleware or server-side checks for protected routes

  • a reusable if needed

  • clean UI using Tailwind (simple, minimal, fast)

Show the code changes file-by-file.

Prompt 4 — Ideas module (capture the “pain”)

Build the Ideas feature.

Pages:

  • /app/ideas (list + search + filters: stage = draft/signaled/waitlist/presale/manual/mvp/launched)

  • /app/ideas/new (create)

  • /app/ideas/[id] (detail)

Idea fields:

  • title

  • pain_statement (required)

  • target_user

  • existing_solutions_notes

  • stage

  • tags

  • created_at

UX:

  • quick “Add pain” input on the list page

  • on detail page show a “Next step” panel that pushes the user through the workflow:

    1. Add signal

    2. Generate waitlist

    3. Send presale

    4. Track manual delivery

    5. Plan MVP

Deliver code + any server actions / route handlers needed.

Prompt 5 — Signals (talk about the pain on the internet)

Build the Signals feature attached to an idea:

  • Add signal links (X/Twitter post URL, LinkedIn post URL, Reddit thread, etc.)

  • Store engagement fields: views, likes, replies, bookmarks, notes

  • Allow manual entry (we won’t scrape APIs yet)

  • Provide a “Signal score” (simple heuristic) and show it on idea detail

UI:

  • A table of signals per idea

  • A button “I’m seeing resonance → Generate waitlist”

Also add a lightweight “Signal checklist” component explaining what counts as resonance.

Prompt 6 — Waitlist landing page generator

Build a Waitlist generator:

Flow:

  • From an Idea detail page, click "Generate waitlist"

  • Create a public page at /w/[slug]

  • The page includes:

    • headline

    • pain -> promise copy

    • 3 bullets of outcomes

    • email capture

    • optional: “How it works” section

    • privacy note

  • Store page content in DB so the user can edit it in-app

Admin UI:

  • /app/waitlists (list)

  • /app/waitlists/[id] (edit copy + view signups)

Include:

  • server action to create waitlist from idea

  • slug generation

  • basic spam protection (honeypot + rate limiting suggestion)

  • success redirect with “invite friends” CTA

Show all code changes.

Prompt 7 — Waitlist signup tracking + “goal 100”

Implement waitlist signup tracking:

  • Save signups (email + referrer + utm params if present)

  • Show a progress bar to 100 signups

  • Add an "Export CSV" button

  • Add an "Email all signups" action placeholder (we'll wire Resend next)

Also add a computed field: idea.stage automatically becomes "waitlist" once waitlist exists, and "validated_waitlist" once signups >= 100.

Prompt 8 — Presale offer + 90% discount email (Resend)

Implement presale emailing via Resend:

  • A presale offer belongs to an idea

  • Default offer: "Founding customer — 90% off" (editable)

  • Button in waitlist admin: "Send presale offer"

  • Send a transactional email to all waitlist signups with a unique link to checkout

Requirements:

  • Use Resend API

  • Use a signed token in the link (expires in 7 days)

  • Track email send status in DB (sent_at, bounced, opened if available; otherwise just sent)

Deliver:

  • email template (clean HTML + text)

  • route handler/server action to send

  • minimal UI states (sending, success, failures)

Prompt 9 — Stripe checkout + “goal 5 sales”

Implement Stripe payments for presales:

  • Create a Stripe Checkout session when user clicks “Claim 90% off”

  • On success, redirect to a thank-you page that asks 3 onboarding questions

  • Use Stripe webhooks to record orders in DB (paid, failed, refunded)

Rules:

  • Once paid_orders >= 5 for an idea, set idea.stage = "presale_validated"

Include:

  • local webhook testing instructions

  • webhook signature verification

  • idempotency

Prompt 10 — Manual delivery tracker (no product yet)

Build the Manual Delivery module:

Goal: help the founder deliver the solution manually and iterate quickly before writing code.

Features:

  • For each paying customer, create a “manual delivery” record

  • Track:

    • customer email

    • promised outcome

    • delivery steps (log entries)

    • status (pending/in_progress/delivered)

    • time spent (estimate)

  • After each delivery, collect feedback:

    • satisfaction score 1–5

    • notes

    • “what should we change?”

UI:

  • Kanban board by status

  • A “What did we learn?” summary panel that lists repeated complaints/praises

Add logic:

  • If >= 3 paying customers have satisfaction >=4, set idea.stage = "ready_for_mvp"

Prompt 11 — MVP planning + tasks

Implement MVP planning:

  • A checklist that turns validated manual delivery into MVP tasks

  • Task fields: title, description, priority, status, estimate

  • Auto-generate initial tasks using the collected feedback themes (simple rule-based, not AI yet)

Pages:

  • /app/mvp (list by idea)

  • /app/ideas/[id] shows “MVP tasks” tab

Also add a “Build scope guardrails” section:

  • Must-have outcomes

  • Non-goals

  • Success metrics

Keep the UI minimal but sharp.

Prompt 12 — Co-maker module (50/50 partner handoff)

Implement a Co-maker CRM module:

  • Store co-maker profiles (name, email, skills, notes, links)

  • Attach co-makers to an idea with fields:

    • ownership_split (default 50/50)

    • responsibilities (founder ops vs co-maker coding/support)

    • start_date

    • status

Include:

  • a “Pitch packet” generator page that summarizes:

    • validation proof (100 signups, 5 sales)

    • what was manually delivered

    • customer quotes

    • MVP task list

Export pitch packet as a printable page (no PDF needed).

Prompt 13 — Launch checklist + cross-promo widgets

Implement Launch + Cross-promo:

Launch:

  • checklist items (announce on X, post demo, Product Hunt prep, etc.)

  • store launch links

Cross-promo:

  • allow founder to create cross-promo blocks that can be embedded on public pages

  • types:

    1. simple link list (“Try my other tools”)

    2. “Boost domain rating” style CTA that deep-links between products

  • show cross-promo blocks on /w/[slug] and on post-checkout thank-you page

Deliver full code.

Prompt 14 — Polish pass (make it feel like a real product)

Do a full product polish pass:

  • Consistent typography + spacing

  • Empty states everywhere

  • Loading skeletons

  • Toast notifications

  • Basic settings page (branding, email sender name, default price)

  • Add analytics events for key steps (idea_created, waitlist_created, presale_sent, checkout_started, paid, feedback_submitted)

Also add a README:

  • setup

  • env vars

  • Supabase + Stripe + Resend configuration

  • deployment notes

If you want it to match the video even tighter

Two optional “extra prompts” you can run after MVP:

  1. SEO growth mode: programmatic pages + sitemap + blog generator

  2. Directory submissions: “Listing bot lite” (track directory outreach)

Say the word and I’ll add those prompts too.

Quick check: do you want BlueprintOS to be single-tenant (just you) or multi-tenant SaaS (others can sign up and use it)? I can tweak the prompts accordingly.