Scope before you build (the one-page spec)
30 minutes of scoping saves 8 hours of regenerating.
Why scoping matters
Prompting 'build me a SaaS for X' produces vague code, vague features, and a vague product. The single biggest predictor of vibe-coding success is whether you wrote a one-page spec first. The spec is for YOU, not the AI — it forces you to think before generating.
The one-page spec template
Three sections: 1) What the user does, step by step. Example: 'A pet owner visits my site, picks a dog-walking time slot, enters their email and address, gets a confirmation.' 2) The data the app stores. Example: bookings (date, time, address, email). 3) What's explicitly out of scope. Example: NOT building payment processing, NOT building login, NOT building a mobile app.
How specific to get
Specific enough that someone else reading it could build the same thing. Vague: 'a booking system'. Specific: 'a 7-day calendar grid, user clicks an empty slot, fills name/email/notes, gets a confirmation email'. The more specific the spec, the cleaner the AI's first output.
1. What's the most common scope mistake beginners make?
Write a one-page spec
Pick something simple you'd actually use — a personal habit tracker, a recipe organizer, a custom landing page. Open a text editor. Write the 3 sections (user steps, data stored, out of scope). Spend 15-30 minutes. Don't open the vibe-coding tool yet.
Your spec fits on one page. The 'out of scope' section is not empty.
Write a 3-section spec before opening any tool — saves multiples of your build time later.
Get the next course before anyone else
Subscribers get new courses a week early and a monthly rate-change report on the catalog.