// playbooks

How to validate your startup idea in 3 days as a solo founder

Most solo founders do "validation" by thinking harder. That is not validation. Validation is getting a stranger to take an action that costs them something. Time. Attention. Money.

This 3-day plan is a fast, honest test. You will build one page. Run one small traffic push. Then talk to real people. At the end, you will either:

• Double down with a clear next iteration.
• Or kill the idea before it steals a month.

If you want the longer path from idea to launch, start at /journey. If you want the tools we use for this workflow, see /bots.

The rule for all 3 days

One idea per test. One audience. One clear action.

If you add three value props, you learn nothing. If you target "everyone", you learn nothing. If your CTA is vague, you learn nothing.

Your goal is not compliments. Your goal is a measurable behavior.

Day 1: Build a fake-door landing page

A fake-door page is a promise. It sells the outcome. It does not build the product.

In one day, you will ship a page that answers:

1. Who is this for?
2. What problem does it solve?
3. What is the promised outcome?
4. What action should the reader take?

Step 1: Pick one buyer and one painful moment

Write this sentence: "This is for [role] who [painful situation] and want [outcome]."

Examples:

• "This is for Shopify store owners who spend 6 hours/week on support and want to cut it to 1 hour."
• "This is for indie app makers who cannot get the first 50 users and want a repeatable outreach routine."

If you cannot write this, pause. You are not ready to test.

Step 2: Write one value proposition

A value proposition is not features. It is a before/after.

Use this format: "Get [outcome] in [time] without [common tradeoff]."

Keep it concrete. "Save 2 hours/week" beats "improve productivity".

Step 3: One CTA (call to action)

Pick one primary CTA:

• "Join the waitlist" (email capture)
• "Request early access" (email + a short form)
• "Pre-order" (payment)

For a 3-day test, email capture is the default. Pre-order is stronger, but harder.

Step 4: Page structure (copy that works)

Your page can be simple:

• H1: Outcome statement
• Subhead: Who it is for and what it replaces
• 3 bullets: proof-shaped benefits (not features)
• Social proof (optional): credible signals, even if small
• CTA section: email field + button + one sentence about what happens next
• FAQ (optional on Day 1): 3 questions that reduce friction

Do not add a pricing table. Do not add a full product tour. Do not add a long founder story.

Step 5: Track the basics

You need two numbers:

• Page visitors
• Email signups

You do not need a full analytics stack. A simple page analytics counter plus form submissions is enough.

Also track:

• Where each click came from (one tag per channel)
• The date and time of your push

You want clean attribution.

Day 1 deliverable

By the end of Day 1, you should have:

• A live landing page.
• One headline.
• One CTA.
• A form that stores emails.
• A way to count visits.

That is validation infrastructure.

Day 2: Drive 50-200 clicks from a niche community

Day 2 is about distribution. Not broad reach. Not branding. Just one controlled test.

Your target is 50 to 200 clicks. That range is large because communities vary. The point is that the sample is big enough to avoid one lucky signup.

Step 1: Choose one niche with intent

Pick a place where your buyer already talks about the pain. Examples:

• A focused subreddit.
• A Slack or Discord community.
• A niche forum.
• A private Facebook group.
• A newsletter community.

Avoid general audiences. Avoid "startup" as a niche.

You want people who already pay attention to the problem.

Step 2: Write the post as a problem statement

Most founders post a pitch. That gets ignored.

Write it like this:

• 2 sentences about the pain (specific)
• 1 sentence about what you tried and why it failed
• 1 question asking for feedback
• 1 link to the page for people who want to be early users

Example structure: "I run [role]. [pain with a number]. I tried [common solution] and it did not work because [reason]. I am testing a small tool to [outcome]. If you want to see it first, I made a 1-page link: [URL]. What would make this a must-have for you?"

This does two jobs. It invites replies. It also filters for intent.

Step 3: Use 2-3 small distribution pushes

Do not spam ten places. You will not know what worked.

Pick 2 or 3 pushes. Examples:

• One post in a niche community.
• One DM batch to 10-20 people who match the buyer.
• One comment thread where the pain is already being discussed.

If you do DM, lead with the pain. Ask one question. Then share the page.

Step 4: Measure email signup conversion

Conversion rate is: Signups / Visitors

For a cold audience, here are rough interpretation bands:

• Under 2%: weak promise or wrong audience.
• 2-5%: some pull, needs iteration.
• 5-10%: strong pull for a cold test.
• Over 10%: unusually strong, often indicates a sharp pain.

These are not laws. They are a starting point. The real signal is what people say when you follow up.

Step 5: Capture qualitative data

Track:

• The words people use to describe the pain.
• The alternatives they currently use.
• The reasons they hesitate.

Copy their language. Do not translate it into founder jargon.

Day 2 deliverable

By the end of Day 2, you should have:

• 50-200 visitors.
• A conversion rate number.
• 5-20 replies, comments, or DMs with real language.

If you have zero replies, your post was a pitch. Rewrite it.

Day 3: Follow up, ask for pre-order, decide to iterate or kill

Day 3 turns interest into commitment. Emails are cheap. A conversation is expensive. Payment is more expensive.

Your goal is to learn:

• Is this a real pain?
• Is your promise the right promise?
• Would anyone pay?
• What would they pay instead of?

Step 1: Message every signup within 24 hours

Speed matters. When someone signs up, they are in the moment.

Send a short message:

• Thank them.
• Ask one question.
• Offer a 10-minute call or a short reply.

Template: "Thanks for signing up. What are you using today to handle [problem]? If you reply with 2-3 sentences, I will send back a concrete recommendation. If you prefer, I can do a 10-minute call this week."

This is not a sales call. It is a diagnostic.

Step 2: Ask for a pre-order (or a stronger commitment)

If the conversation shows real pain, test a paid commitment.

Two options:

1. Pre-order with a refund promise.
2. Paid pilot for a defined outcome.

Keep it simple. Offer one tier. A small number is fine.

Example: "I am building this with 10 early users. It will deliver [outcome] in [time]. I am asking for [$X] to join. If it does not deliver, I refund. Do you want one of the 10 spots?"

If you are not ready to take payment, ask for a stronger action:

• A calendar booking.
• A short onboarding survey.
• A "yes" to being a test user next week.

Step 3: Make the decision using a simple scorecard

Do not debate yourself for weeks. Use a scorecard.

Score 0-2 for each:

1. Conversion rate on the page.
2. Quality of replies.
3. Strength of alternatives.
4. Willingness to pay.

Interpretation:

• 0-4 total: kill or change audience.
• 5-6 total: iterate the promise and rerun Day 2.
• 7-8 total: build the smallest deliverable and sell it.

The point is not precision. The point is momentum with guardrails.

What "kill" means (and why it is a win)

Killing an idea is not failure. It is buying back time.

Write down:

• What audience you tested.
• What promise you made.
• What you learned.

Then reuse the learnings on the next test.

Day 3 deliverable

By the end of Day 3, you should have:

• 10-20 follow-up conversations started.
• 3-10 clear problem statements in the buyer's words.
• At least one attempt to collect money or a strong commitment.
• A decision: iterate or kill.

FAQ

What if I cannot get 50 clicks?

Your distribution channel is wrong, or your post is a pitch. Go narrower. Find a place where the pain is already being discussed. Then write as a participant, not a marketer.

What should I build if the test is strong?

Build the smallest deliverable that creates the promised outcome. Not the full product. A concierge version is valid. If you can deliver the outcome manually, you can learn pricing faster.

How much should I charge on a pre-order?

Start with a number that is meaningful but not scary. If the problem saves 5 hours/month, a $49-$99 test is reasonable. If the outcome is revenue, you can charge more. The point is to test willingness to pay, not maximize it.

Should I use ads?

Not on the first 3-day test. Communities and DMs give you language and objections. Ads give you numbers without context. Use ads later, after you have a message that converts.

Where does this fit in the bigger Boteam workflow?

This is the first gate. If you pass it, move to a tighter build plan and a simple launch. Use /journey as the map, and /bots as the toolkit.