validate-idea

Diagnose customer problems and payment willingness for business ideas.

Updated Jun 29, 2025
One-click install
npx skills add https://github.com/YHWriteCode/EconRAGent --skill validate-idea-yhwritecode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-idea
Source: https://github.com/YHWriteCode/EconRAGent/tree/main/skills/validate-idea
Command: npx skills add https://github.com/YHWriteCode/EconRAGent --skill validate-idea-yhwritecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many founders build products before confirming there is a paying market, wasting time and money on solutions users don't want. This Skill helps quickly determine whether a business idea addresses a real, painful problem and whether customers will pay for a manual, minimal version of the solution.

Core Features & Use Cases

  • Customer-focused diagnosis: Clarify the specific target customer, current workarounds, and the true pain level to reveal real demand.
  • Manual-first validation workflow: Guide creation of a "processized" manual offering you can deliver today to test value before engineering.
  • Payment and interview-based proof: Provide interview scripts, outreach plans, and criteria for counting paid commitments or strong purchase intent.
  • Use Case: A solo founder with an invoicing bottleneck can use this Skill to identify 10 freelance designers, run manual invoicing for a week, and secure 3 paid commitments before building software.

Quick Start

Help me validate a business idea by identifying the target customer, outlining a manual service I can deliver this week, drafting a script for ten customer interviews, and defining the payment test to confirm at least three paying users.

Frequently Asked Questions about validate-idea

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate my business idea before building a product?

Idea validation requires diagnosing target customer problems and testing willingness to pay through manual service delivery and customer interviews. You draft an interview script, define a manual deliverable, contact ten prospects, and collect payments to confirm real demand.

What is a manual service MVP and how does it test willingness to pay?

A manual service MVP tests willingness to pay by having you deliver a processized manual offering directly to customers before building software. You collect explicit purchase commitments or payments to prove real demand without writing code.

Can I use customer interviews to confirm market demand for an MVP?

Yes, customer interviews confirm market demand by clarifying the specific target customer, current workarounds, and true pain level. You must contact at least ten prospects using a drafted interview script to reveal real demand and secure paid commitments.

Best way to test if customers will pay for a solution before developing software?

The best way to test if customers will pay before developing software is running a payment test with a manual service. You define a manual deliverable, contact at least ten prospects, and collect explicit purchase commitments or payments from multiple customers.

How many customers do I need to validate an idea and what are the criteria?

To validate an idea you need to contact at least ten prospects and collect explicit purchase commitments or payments from multiple customers. The criteria require securing at least three paying users who confirm the problem is painful enough to pay for a manual solution.