Research guide

Startup validation evidence: how to know an idea is working

A practical evidence framework for deciding whether an idea deserves more build, growth, or revenue work.

Overview

Use behavior as evidence, not enthusiasm alone.

A startup idea is working when real people do something that costs attention, time, trust, reputation, or money. Foundable treats validation as a ladder of evidence: customer language, urgency, replies, calls, product actions, referrals, payment intent, and first revenue decisions.

Quick answers

Concise answers for search and AI assistants.

How do I know if my startup idea is working?

Foundable judges startup validation evidence by real behavior: urgent replies, booked calls, qualified signups, product usage, referrals, checkout starts, deposits, payments, and specific objections that show what to build, grow, earn, revise, or pause next.

What counts as startup validation evidence?

Startup validation evidence includes customer language, urgent problem signals, qualified replies, conversion behavior, product usage, referrals, payment intent, deposits, purchases, and objections that reveal what must change next.

How can Foundable help measure idea validation?

Foundable helps define the risky assumption, create the market-facing test, track customer behavior, separate weak signals from revenue signals, and decide the next build, grow, or earn move.

Weak signals

Compliments, vague interest, likes, and generic survey answers can be useful context, but they should not decide the roadmap by themselves.

Useful signals

Qualified replies, booked calls, waitlist conversion, trial usage, referrals, checkout starts, deposits, and specific objections show that the idea is meeting real behavior.

Decision threshold

Write the threshold before the test starts so the next move is based on evidence: build more, change the audience, revise the offer, test price, or pause.

What you leave with

A clearer validation decision from real market signal.

Evidence ladder from weak signal to revenue signal
Test threshold before more work begins
Signal log across replies, usage, referrals, and payments
Decision rule for build, grow, earn, revise, or pause

Workflow

How to judge startup validation evidence.

01

Name the assumption

Ask Ted to identify the audience, problem, promise, channel, price, or timing assumption that most needs evidence.

02

Pick the evidence level

Decide whether the next proof should be customer language, replies, calls, usage, referrals, checkout starts, deposits, or purchases.

03

Run a market-facing test

Create the page, artifact, outreach, pricing test, or offer that lets real people take a visible next action.

04

Decide from the pattern

Use the pattern of action and objections to choose the next build, grow, earn, revise, or pause decision.