Day 01 clarity / SP-BUYER-MAP

Make the buyer map too clear to dodge.

A no-form companion sheet for the first Start Here worksheet. It helps a beginner replace vague audience language with one buyer, one painful workflow, and one reason the problem matters now.

Use the clarity promptsOpen Markdown sheet
StatusLocal no-form sheet
PurposeFix vague buyers
Used beforeOffer + stack
Live systemsNone connected

Command brief

Day 01 is the cheapest place to be honest.

Most beginner AI-business ideas fail before the tool stack because the buyer is too broad. This sheet forces the first useful constraint: name one type of person, one repeated task, and one reason the task is painful enough to discuss.

10-year-old mode

Pick one person with one annoying chore.

Do not say “businesses.” Say “a solo lawn-care owner who loses receipts after supply runs.” If a kid can picture the person and the chore, you can build the next worksheet.

Buyer-map formula

Use three boxes, not a brainstorm cloud.

1 / BuyerOne specific role, situation, or business owner. Avoid “everyone,” “small businesses,” “creators,” or “people who need AI.”
2 / Painful workflowOne repeated task that wastes time, causes missed money, creates anxiety, or blocks a decision.
3 / Why nowThe pressure that makes the workflow worth fixing this month: deadline, mess, lost follow-up, confusion, growth, or compliance risk.
Buyer sentenceI help [specific person] who struggles with [repeated workflow] because [current pressure].
First evidenceI have seen/heard/read this problem from [source], or I am labeling it as a hypothesis until Tim manually validates it.
Not yetI am not building tools, agents, content, checkout, or outreach until this buyer map survives a plain-language review.

Weak vs strong examples

Specific beats impressive.

Weak

“I help small businesses use AI to grow.”

Stronger

“I help solo home-service owners turn one messy month of receipts and payments into a clean owner report before they lose another weekend.”

Weak

“I help realtors automate follow-up.”

Stronger

“I help busy agents review last week’s conversations and draft follow-up notes they approve manually before promising anything to a buyer or seller.”

Weak

“I build AI systems for creators.”

Stronger

“I help solo course creators turn one finished lesson into a reviewed email, post, and lead-magnet outline without inventing testimonials or results.”

Stop rules

Do not move to Day 02 until the buyer passes these checks.

Too broad

Anyone could fit.

If the buyer phrase can include half the internet, rewrite it smaller.

Too abstract

No workflow appears.

If the pain is “growth” or “productivity,” name the actual task that goes wrong.

Ready

A normal person can picture it.

You can imagine the buyer, the annoying task, and why they might talk about it now.

Hermes-safe help

AI may prepare the map.

  • Brainstorm narrow buyer examples.
  • Rewrite vague ideas into concrete workflow sentences.
  • Flag broad language and missing evidence.
  • Create local files and checklist notes.

Human approval lock

AI may not test the market alone.

  • No publishing, sending, outreach, DMs, ads, capture, checkout, analytics, accounts, or deployment.
  • No fake proof, testimonials, revenue, screenshots, logos, or customer claims.
  • No private customer, payment, tax, legal, KYC, identity, CRM, MLS, or employer data.

Next click

Once Day 01 is clear, move to the offer — not automation.

Open Guide 01 if the buyer still feels fuzzy. Open Guide 02 only after the buyer sentence can be explained in one breath.

Open Guide 01Next: Guide 02Back to Start Here