How do I validate a startup idea before spending money building it?

Validating a startup idea before investing capital is the most effective way to avoid building something nobody wants. The goal is to prove there is a genuine problem, not just that you have a "good idea."

Here is a straightforward approach to validation:

1. Define the Problem

Don’t start with your solution; start with the pain point.

• Identify the audience: Who specifically is struggling with this problem?
• Articulate the pain: Can you describe the issue in one sentence? If you can't, the problem might not be clear enough.

2. Conduct "Customer Discovery" Interviews

Talk to at least 15–20 people who experience this problem. Do not pitch your product. Instead, ask questions that reveal their current behavior:

• "Tell me about the last time you dealt with [problem]."
• "How are you currently solving this?" (If they aren't trying to solve it, it might not be a high-priority pain.)
• "What is the most frustrating part of that process?"

3. Build a "Smoke Test" or Landing Page

You don't need a product to see if people are interested.

• Create a simple landing page that describes the value proposition.
• Include a call-to-action (CTA), such as "Join the Waitlist" or "Request Early Access."
• If people are willing to give you their email address—or better yet, pre-order—you have initial validation.

4. Create a "Concierge" Prototype

Before writing code or manufacturing, do the work manually to see if it provides value. If you want to build an automated meal-planning app, offer to manually create meal plans for five people for a week. This "manual MVP" helps you learn the nuances of the service and confirms if users find it helpful enough to pay for.

5. Seek "Skin in the Game"

The ultimate form of validation is a financial commitment.

• Ask potential users if they would be willing to pay a deposit for a lifetime membership or a discounted annual fee if you build the product.
• If they are hesitant to commit money, they might be being polite during your interview. Money is the only honest signal.

What to avoid:

• Asking friends and family: They will likely be too supportive and give you biased feedback.
• Building in a vacuum: Don't spend months developing software or hardware before you have confirmed that at least 10–20 strangers are willing to use your solution.
• Over-relying on surveys: People often tell you what they think you want to hear. Real-world behavior (time or money spent) is more valuable than survey responses.

If you find that people aren't interested, you haven't lost money—you've simply saved yourself from building the wrong thing. You can then pivot to a different problem or a different audience based on what you learned.