buyer-validation

Files (1)

• SKILL.md

SKILL.md (first lines)

# Buyer Validation Skill

Input:

```text
$ARGUMENTS
```

## Mission

Answer the question: **Will anyone buy this?**

## Required output

Produce a validation plan with:

1. **ICP** — ideal customer profile.
2. **Economic buyer** — the person who can approve spend.
3. **User** — the person who feels the pain day to day.
4. **Pain statement** — in buyer language, not builder language.
5. **Current workaround** — what they do today.
6. **Existing spend** — tools, contractors, analysts, wasted labor, lost revenue, risk.
7. **Trigger event** — when the buyer becomes actively receptive.
8. **Buying objection map** — price, trust, implementation, data access, switching cost, accuracy, compliance.
9. **10 validation questions** — non-leading, pain-first.
10. **5 outreach messages** — concise, specific, no hype.
11. **3 fake-door tests** — landing page, waitlist, paid pilot, diagnostic audit.
12. **Concierge MVP** — what can be done manually before software.
13. **Kill criteria** — what evidence would make us stop.

## Rule

Do not treat verbal interest as validation. Validation means at least one of:

- payment
- calendar commitment with a decision-maker
- access to real data/workflow
- signed pilot
- buyer introduces you to other buyers

## Durable output

If working in a repo, create or update:

```text
docs/profit/buyer-validation.md
```

From az9713/idea-to-capital, MIT.

More from az9713/idea-to-capital