TL;DR
Validate by talking to 10–20 target customers, testing willingness to pay, and running a cheap smoke test before you quit. Compliments are not revenue. Build only what the riskiest assumption requires.
Introduction
Side projects die from untested hope. Validation flips the order: evidence first, resignation later. Here is a sequence you can run nights and weekends without cosplay metrics.
Write the Hypothesis
One page: customer, problem, offer, why now, riskiest assumption. If you cannot name what would kill the idea, you are not ready to build.
Run Interviews Like a Pro
Ask how they handle the problem today, what is annoying, what they tried, cost of inaction, and whether they would pay for a better path. Do not pitch for 15 minutes. Tag notes for pain, budget owner, urgency.
Sources: intros, niche communities, adjacent customers, personal outreach. "Cool idea" from friends does not count as in-segment.
Score Honestly
After ~10 talks, look for repeated acute pain, clear buyers, unprompted next-step asks, and intros to peers. Polite interest without urgency means wrong segment or problem.
Smoke-Test Demand
One page: headline, audience, outcome, CTA. Strongest CTAs: paid pre-order, paid pilot booking, serious application. Email-only is weak alone. Drive traffic from networks and focused posts first.
Force the Money Conversation
Say the price. Offer a limited pilot. Collect deposits where honest about timelines. If they will not pay for a manual version, software will not save you.
Decide With a Memo
Persist, pivot, or pause — written down with evidence. Keep your job until pre-written criteria and runway are met.
Mistakes
Pitching over listening; friends-only samples; building for months to demo; AI personas as "research"; quitting after one good chat.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:0 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:1 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:2 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:3 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:4 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:5 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:6 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:7 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:8 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:9 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:10 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:11 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:12 -->Key Takeaways
- Hypothesis → interviews → smoke test → payment signal → decide.
- Costly actions validate; compliments do not.
- Build for the riskiest assumption only.
- Quit against criteria, not vibes.

