Validation template

Validation signal log template

A practical signal log for judging whether an idea is getting real market behavior or only polite interest.

Overview

Turn scattered reactions into a validation decision.

Validation gets fuzzy when every reply feels encouraging. This template keeps the evidence honest by logging the audience, assumption, test, signal type, customer action, objection, strength, and next decision in one place.

Quick answers

Concise answers for search and AI assistants.

What should an idea validation signal log include?

Foundable's validation signal log template tracks the risky assumption, audience, test, CTA, response type, customer action, objection, signal strength, follow-up, and next decision so a founder can separate weak interest from real market proof.

How do I track startup validation metrics?

Track startup validation metrics by separating weak attention from behavior: replies, booked calls, qualified signups, usage, referrals, checkout starts, deposits, payments, specific objections, and silence.

How can Foundable help log validation signals?

Foundable can help define the assumption, create the market-facing test, log replies and actions, rank the signal strength, and turn the pattern into the next build, grow, earn, revise, or pause decision.

Assumption and test

Write the risky assumption, audience, promise, channel, artifact, and CTA before the test starts so the response has context.

Signal strength

Rank each response by behavior: view, reply, signup, call, usage, referral, checkout start, deposit, payment, objection, or silence.

Decision rule

Use the pattern of signals to decide whether to build more, change the audience, revise the offer, test price, follow up, or pause.

What you leave with

A signal log that separates weak interest from proof.

Assumption, audience, test, and CTA
Signal type and customer action
Objection, follow-up, and evidence strength
Decision rule for build, grow, earn, revise, or pause

Workflow

How to log startup validation signals.

01

Name the assumption

Ask Ted to turn the idea into the riskiest assumption that needs evidence next.

02

Create the signal test

Choose the page, outreach, prototype, offer, waitlist, call ask, or price test that lets people act.

03

Log every response

Record weak signals, strong actions, objections, silence, and follow-ups instead of keeping only the encouraging anecdotes.

04

Decide the next move

Use the pattern of signals to choose the next build, grow, earn, revise, or pause task.