Start Here / first artifact scorecard

Are the buyer, offer, and stack specific enough?

Use this scorecard after the first three Start Here sessions. This checks specificity only before manual validation. It does not prove demand, revenue, or launch readiness.

No form · no data collection · no launch approval
DAY 01 / BUYER MAP

Buyer map check

Names one specific buyer type, not everyone.
0–2
Names one painful workflow the buyer repeats.
0–2
Explains why the pain matters now.
0–2
Lists one safe way to learn more without scraping, spamming, or claiming proof.
0–2
DAY 02 / OFFER

Offer one-liner check

Says who the offer helps.
0–2
Says what changes after the offer.
0–2
Names what is included and what is not included.
0–2
Avoids guaranteed income, fake proof, legal/tax/financial claims, and vague AI hype.
0–2
DAY 03 / SMALLEST STACK

Smallest stack check

Has only the tools needed for catch, talk, sell, do, and remember.
0–2
Defers paid tools until the workflow needs them.
0–2
Keeps accounts, checkout, capture, analytics, integrations, and automations unconnected until approved.
0–2
Names one review-only AI job instead of giving AI broad authority.
0–2
READINESS RESULT

Use the score to choose the next safe move.

18–24 pointsClear enough for Tim-approved manual validation review.
10–17 pointsRevise the weakest buyer, offer, or stack artifact before review.
0–9 pointsReturn to the manual router and restart with the clearest stuck point.

Approval lock

Clarity is not public permission.

AI may draft, organize, summarize, score, route, remind, compare, and create local files. Humans approve publishing, sending, contacting, buying, deploying, account creation, terms acceptance, checkout, email capture, analytics, marketplace listings, proof claims, customer-facing messages, external-system changes, and private payment/tax/legal/KYC/identity details.