Pressure-test a business or side-hustle idea before you sink money and months into it — find the real demand, the risky assumptions, and the cheapest way to test them. Use when asked to validate my business idea, is this a good business idea, test my side hustle, or should I start this. Produces a read on the core assumptions the idea depends on, who the customer really is and whether the pain is real, the cheapest experiments to test demand before building, a rough viability check (market, c...
Scanned 9/3/2026
Install to Claude Code
npx -y skills add mohitagw15856/pm-claude-skills --skill business-idea-validator --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Business Idea Validator?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mohitagw15856-business-idea-validator)More formats (shields.io, HTML) on the badges page.
---
name: business-idea-validator
description: "Pressure-test a business or side-hustle idea before you sink money and months into it — find the real demand, the risky assumptions, and the cheapest way to test them. Use when asked to validate my business idea, is this a good business idea, test my side hustle, or should I start this. Produces a read on the core assumptions the idea depends on, who the customer really is and whether the pain is real, the cheapest experiments to test demand before building, a rough viability check (market, competition, economics), and a go/refine/rethink call — honest, not a cheerleader."
homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/business-idea-validator.html
metadata:
{
"openclaw": { "emoji": "🧠" }
}
---
# Business-Idea Validator
Most business ideas fail not from bad execution but from building something nobody wanted — a problem you can catch *before* spending the money. This pressure-tests your idea: it surfaces the assumptions it secretly depends on, checks whether the customer and pain are real, and designs the cheapest experiments to find out — so you validate demand before you build, and get an honest call, not applause.
## What This Skill Produces
- **The core assumptions** — what has to be true for this to work (the customer exists, the pain is real, they'll pay, you can reach them, the economics work)
- **A customer & pain check** — who the real buyer is and whether the problem is painful enough to pay to solve
- **Cheap validation experiments** — the fastest, lowest-cost ways to test demand *before* building (conversations, a landing page, pre-sales, a manual/concierge version)
- **A viability read** — rough market size, competition, and whether the unit economics could work
- **A go / refine / rethink call** — honest, based on the evidence and the riskiest assumptions
- **The riskiest assumption to test first** — where to point your first experiment
## Required Inputs
Ask for these if not provided:
- **The idea** — what it is, who it's for, and the problem it solves
- **The customer** — who you think will pay, and why
- **Your evidence** — any real signal so far (interest, sales, competitors)
- **Your stake** — time/money you'd commit, and your risk tolerance
- **Your goal** — a side hustle, a real business, or just testing the water
## Framework: Test The Assumptions, Cheaply, First
1. **Surface the hidden assumptions.** Every idea rests on beliefs — that a specific customer has a painful problem, will pay, and can be reached affordably. Name them.
2. **Interrogate the customer and pain.** Is the buyer specific and real, and is the pain strong enough that they'll pay? "Nice to have" ideas die here.
3. **Design cheap experiments.** Before building anything, test demand the fast way: talk to real potential buyers, put up a landing page, attempt pre-sales, or run a manual "concierge" version.
4. **Sanity-check viability.** Rough market size, existing competition (its presence can validate demand), and whether the numbers could plausibly work.
5. **Test the riskiest assumption first.** Point the first, cheapest experiment at the thing most likely to kill the idea — don't validate the easy parts.
6. **Give an honest call.** Go, refine (pivot the weak assumption), or rethink — based on evidence, not enthusiasm. Be a critic, not a cheerleader.
## Output Format
### Idea validation: [idea] · for [customer] · stake [x]
**Core assumptions:** [customer exists · pain is real · they'll pay · reachable · economics work].
**Customer & pain:** [who really pays] · pain level: [must-have / nice-to-have].
**Cheapest tests (before building):** [customer conversations · landing page · pre-sale · concierge version].
**Viability:** market [rough] · competition [signal] · economics [plausible?].
**Riskiest assumption to test first:** [x].
**Call:** [go / refine / rethink] — because [evidence].
## Quality Checks
- [ ] Surfaces the idea's hidden assumptions
- [ ] Interrogates whether the customer and pain are real/payable
- [ ] Prescribes cheap experiments before building
- [ ] Includes a rough viability read (market, competition, economics)
- [ ] Identifies the riskiest assumption to test first
- [ ] Gives an honest go/refine/rethink call, not cheerleading
## Anti-Patterns
- **Cheerleading** the idea instead of stress-testing it.
- **Jumping to build** before testing demand.
- **Vague "big market"** with no real customer/pain.
- **Testing the easy assumptions** and ignoring the killer one.
- **Confusing personal excitement** with market demand.
## Example Trigger Phrases
- "Is this a good business idea? Help me validate it."
- "I want to start a side hustle doing X — is there demand?"
- "How do I test my business idea cheaply before committing?"
- "Pressure-test my startup idea honestly."
- "Should I actually start this, or am I kidding myself?"
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!