Validation template
Validation signal log template
A practical signal log for judging whether an idea is getting real market behavior or only polite interest.
Updated · Published by Foundable
Overview
Turn scattered reactions into a validation decision.
Validation gets fuzzy when every reply feels encouraging. This editable template keeps the evidence honest by logging the assumption, audience, test and CTA, observed action, objection, evidence strength, follow-up, and next decision. Entries stay in the browser tab unless you copy or download them.
Editable template
Log what people do, not only what they say.
Add one row for each response or observed behavior. Keep the test context attached to the evidence so a promising anecdote does not become a false pattern.
Private by default: entries stay in this browser tab. Foundable does not save or send what you type here. Reloading clears the log; copy and CSV export happen only when you choose them and are created on this device.
Each card is one observed response or behavior. Use separate rows when the audience, test, or action changes. This tab supports up to 50 rows; export before reloading to begin another batch.
Field definitions
Keep each row auditable.
- Date
- When the response or behavior happened, not when you remembered it.
- Assumption
- One belief this test could support or disprove.
- Audience
- The specific segment and role that produced the response.
- Test + CTA
- What the person saw and the exact action you asked them to take.
- Observed action
- What actually happened, including counts and time windows when known.
- Objection / exact words
- The person's language, a concrete objection, or an explicit note that there was no response.
- Evidence strength
- A behavior-based rating using the rubric below, not a confidence score.
- Follow-up
- The next evidence-gathering action, owner, or date.
- Next decision
- Build, revise, change audience, test price, grow, earn, follow up, or pause.
Evidence-strength rubric
Costlier behavior usually carries more weight.
This is a directional sorting aid, not a validated scoring model. Do not add or average ratings across different audiences or tests; strength does not replace sample size, source quality, or counterevidence.
- 0: No supporting evidenceNo response, an accidental action, an irrelevant response, or a clear rejection. Keep it in the log so silence and negative evidence are not erased.
- 1: AttentionA view, open, like, or other low-cost action. Useful for message testing, but not proof that the problem or offer matters.
- 2: Stated intentA relevant reply, booked call, qualified signup, or specific problem confirmation. Stronger than attention, but still a promise rather than costly behavior.
- 3: Costly actionThe person invests meaningful time, effort, reputation, data, or purchase intent without paying yet: a substantive first use, referral, data transfer, setup work, or checkout start.
- 4: Paid or repeated behaviorA deposit, payment, renewal, or repetition of the same meaningful use or referral by the intended audience. Check that the behavior matches the assumption before treating it as proof.
Before you interpret the log
Check whether your traction signals cover the full path.
The startup traction calculator maps problem, behavior, repetition, source, and money-or-referral signals. Use it to spot the next gap; keep this log as the underlying evidence trail.
Quick answers
Practical answers for the next decision.
What should an idea validation signal log include?
Foundable's validation signal log has nine fields: Date, Assumption, Audience, Test + CTA, Observed action, Objection / exact words, Evidence strength, Follow-up, and Next decision. Its behavior-based rubric helps compare weak attention with stronger observed behavior; it is a directional sorting aid, not proof of demand or a validated scoring model.
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 one falsifiable assumption, the audience, and the exact test and CTA before the test starts so each response has context.
Signal strength
Rank what happened from no evidence through attention, stated intent, costly action, and paid or repeated behavior. Record objections and silence too.
Decision rule
Read patterns across comparable tests, not one flattering response, then choose whether to build, revise, change audience, test price, follow up, grow, earn, or pause.
Template payload
Start Foundable with the structure from this page.
Starter prompt
I found the "Validation signal log template" page on foundable.com. Help me turn this into a concrete Foundable project. Context: Use a free, editable validation signal log to track assumptions, customer actions, objections, evidence strength, follow-ups, and next decisions.
Fields Foundable should fill
- Assumption and test
- Signal strength
- Decision rule
What you leave with
A signal log that separates weak attention from stronger observed behavior.
Workflow
How to log startup validation signals.
Name the assumption
Write one belief that a real customer action could support or disprove.
Create the signal test
Choose the page, outreach, prototype, offer, waitlist, call ask, or price test that lets people act.
Log every response
Record weak signals, strong actions, objections, silence, and follow-ups in the editable log instead of keeping only encouraging anecdotes.
Decide the next move
Use the pattern of signals to choose the next build, grow, earn, revise, or pause task.