Before outreach counts as evidence
Earlyvangelist Validation — Who Qualifies Before You Treat Them as Proof
A compliment is manners. A waitlist is reach. An earlyvangelist is a named person who has the problem, knows it, is already searching on a timetable, has cobbled together a workaround, and can get budget — then buys the 18–36 month vision while you deliver the minimum feature set. Write the tripwire before the first intro so Sunday cannot promote a polite yes into “we have earlyvangelists.”
Last updated: October 2, 2026
Direct answer
What is an earlyvangelist?
Steve Blank coined Earlyvangelist as Early Adopter plus Internal Evangelist: a special customer who can see a product’s potential to solve a critical, immediate problem and who has the budget to buy it. In “Perfection By Subtraction – The Minimum Feature Set” (4 March 2010) he lists exactly five characteristics — no sixth. They have a problem. They understand they have a problem. They are actively searching for a solution and have a timetable for finding it. The problem is painful enough that they have cobbled together an interim solution. They have, or can quickly acquire, dollars to purchase a product that solves it. Those people are first buying the vision, then the product. Blank’s line is the one this page keeps: you are selling the vision and delivering the minimum feature set to visionaries, not everyone. Most customers will hate a minimal feature set. Earlyvangelists need an 18–36 month product vision past that minimum, and they understand the vision can change. This page is the who-filter written as a tripwire — observable signal, threshold, calendar window, named action — before outreach treats a warm conversation as validation evidence. Fill your own N. Do not invent a typical count.
Key takeaways
What to remember
- An earlyvangelist tripwire is four fields: who-signal + threshold + calendar window + named action. A compliment is not the signal.
- Blank’s five characteristics are the only checklist. Problem, awareness, search plus timetable, cobbled workaround, budget. Three out of five is not an earlyvangelist.
- You sell the vision and deliver the minimum feature set to earlyvangelists, not everyone. Most customers will hate the thin first version.
- Write the tripwire before outreach. A who-list invented after warmth is a recap, not a test.
- Scores do not count earlyvangelists. Matching Blank’s signals against a bar you wrote in advance does. Fill your own N. This page publishes no conversion rate.
Why it matters
Most people will hate the minimum feature set
I have watched founders treat eight “this is interesting” calls as a pipeline of earlyvangelists. Nobody had a workaround last Tuesday. Nobody named a date they needed the mess solved. Nobody could point at a budget. The build still opened — and the first thin version was shown to people Blank said would hate it. In the 2010 post, the minimum feature set is a tactic: less wasted engineering, and a first version in the hands of visionary customers soonest. It is not a product you can sell to a general audience. Earlyvangelists stay through bugs, bad performance, and pricing arguments because they bought the longer vision. CB Insights’ 2026 analysis of 431 VC-backed companies that shut down since 2023 is useful here as a warning about symptoms versus roots — not as a personal forecast. “Ran out of capital” leads their list at 70 percent, and they are explicit that this is often the final cause of death. Among the 385 companies with identifiable reasons, more telling patterns include poor product-market fit (43 percent), bad timing (29 percent), and unsustainable unit economics (19 percent). Many shutdowns cited more than one reason, so those shares can add to more than 100 percent. Building a thin product for people who never had the pain, the timetable, or the budget is a fit problem. It does not show up in compliments. This page does not invent other percentages, and it does not claim an earlyvangelist predicts survival.
Vocabulary
Blank’s five characteristics, written as checkable signals
Earlyvangelist means Early Adopter plus Internal Evangelist — Blank’s 2010 definition, not a synonym for “anyone who likes the demo.” The five cards below are the only characteristics this page uses. Each one needs a log a stranger could read. A sixth invented trait, or a 3-of-5 pass, is how a cheerleader becomes “our earlyvangelist.”
1. They have a problem
A recent incident in their life or job, not a hypothetical. Log the last time it happened, in their words. “Companies like ours struggle with X” is a category. It is not this signal.
2. They understand they have a problem
They can name the cost without you prompting the punchline. If you have to explain why last Tuesday was bad, they are not problem-aware. Blank’s second characteristic is awareness, not your pitch landing.
3. They are actively searching, with a timetable
They have already looked, asked, or shopped — and they can name a date or event by which they need a better answer. “Sometime this year” is not a timetable. A vendor shortlist, an RFP window, a compliance deadline, or “before the next quarter close” is.
4. They have cobbled together an interim solution
Pain high enough that they already built a messy workaround: a spreadsheet, a contractor, a weekend script, a stack of tools taped together. If they have not spent time on an interim fix, the pain is still a story.
5. They have, or can quickly acquire, budget
Dollars, or a named path to dollars, to buy a solution. Blank’s wording is purchase, not “would love to try it free.” A person who cannot name a budget owner, a card, or a procurement path fails this characteristic even if the first four are loud.
The tripwire
Signal, threshold, window, action — written before the first intro
The five characteristics tell you who. The tripwire tells you what happens if you cannot find that who in time. Do not skip a field. The counts you later write are yours. They are not a benchmark copied from this page.
Field 1 — Observable who-signal
A stranger could log that a named person matched all five characteristics. Notes from last week’s incident, the workaround they already run, the date they need it solved, and the budget path. “Seemed excited” is not a signal.
Field 2 — Threshold
N of M qualified conversations produce a person who matches all five. Qualified means they already do the job you named. Fill N and M yourself. This page does not publish a usual pass bar or a typical earlyvangelist count.
Field 3 — Calendar window
Start date and end date. Twenty-one days from the first who-ask is a window. “Give discovery the quarter” is not. Silence inside the window is a no on this filter.
Field 4 — Named action
Stop treating the current ICP as earlyvangelist-rich, rewrite the who-sentence, or Continue to the next cheapest test (design-partner ask, money tripwire, or a thinner discovery pass). Hope is not an action.
Field 0 — Written before outreach
If the four fields appear after the first compliment, you wrote a recap. Date the page in the same sitting you name the who-bet. A kinder bar later is a new page with a reason — not an edit after warmth.
Not the same page
Earlyvangelist vs design partner, WTP, beta, discovery, smoke, delivery, and decision contracts
Several Yibud pages sit next to this one. Mixing them up turns a polite yes into “we found our earlyvangelist,” or a usage tester into a vision buyer with budget.
Design partner — scarce co-dev, not the who-filter
That page’s signal is staff time, data, workflow access, and weekly use as Customer Validation evidence. This page is who qualifies before or alongside that commitment. An earlyvangelist can later become a design partner. A signed partner who never matched the five characteristics is a custom, not a who-pass.
Design partner validation →Willingness-to-pay — money moving
That page’s signal is a deposit, pre-order, paid concierge, or priced checkout. Blank’s fifth characteristic is that they have or can acquire budget — a path to purchase, not a charge that already moved. Do not count an earlyvangelist as WTP, and do not count a checkout as the who-filter.
Willingness-to-pay test →Beta testers — usage testers, not vision buyers
That page is how to find people who will run the unfinished product and tell you what broke. A beta tester can be quiet, unpaid, and still useful. An earlyvangelist buys the vision first, has a pain timetable, and can get budget. Do not recruit twenty testers and call two of them earlyvangelists.
How to find beta testers →Customer discovery and the Mom Test — how you ask
Those pages are the interview method: find who has the problem, ask about last week’s life, refuse a polite yes. This page is the who-filter those notes must pass before you treat the person as validation evidence. “Would you be our earlyvangelist?” is a Mom Test fail if it is the whole conversation.
Smoke test and fake-door — uncharged reach
Those pages measure whether anyone reaches. They are usually uncharged. A click is not an earlyvangelist. Use them when you still cannot find the person. This page starts when the expensive unknown is whether a named person matches Blank’s five.
Concierge and Wizard of Oz — delivery
Those pages own how you produce the outcome by hand, or behind a curtain. An earlyvangelist can sit on a concierge week. Delivery answers “can we produce the result?” This page answers “is this person the visionary you should sell the 18–36 month picture to?”
Kill, pivot, pre-mortem, assumption, decision — contracts
Kill and pivot pages write Stop or rewrite tripwires. A pre-mortem ranks failure modes. Critical-assumption names one claim. The validation-decision page reads a week of evidence you already have. This page supplies who-evidence those contracts can later read. It is not a Stop / Pivot / Continue sitting.
A mid-band customer, founder-fit, or monetization score is a flashlight, not an earlyvangelist. It can point at a weak “someone with budget and a timetable exists” assumption. It does not match Blank’s five. What a validation score actually means →
The sitting
How to write an earlyvangelist tripwire in one sitting
Do this before the week of intros, not after you have already spent it pitching the minimum feature set to everyone who would take a call. Set a timer. Leave the build closed. If you have a co-founder, each of you writes a draft alone, then you keep the stricter bar.
- 1
Write the who-bet as one sentence
Person + job + last week’s incident + the workaround they already run. “An AP manager at a mid-size manufacturer who chased three past-due invoices last week on a shared spreadsheet.” If the sentence still says “early adopters” or “visionaries,” you do not have a bet yet.
- 2
Turn Blank’s five into log fields
For each characteristic, write what you will accept as evidence. Incident date. Cost they named without a prompt. Search already in motion plus a date they need it solved. The interim tool they already use. The budget owner or card. Five fields. Not six. A 3-of-5 score is a miss.
- 3
Name whether who is the expensive unknown
If you still cannot find anyone in the job, run discovery, smoke, or fake-door first. If you only need usage testers, recruit beta. If the person is named and the unknown is scarce access, write a design-partner tripwire. If the unknown is price, write a WTP tripwire. If the unknown is “will anyone match all five,” stay on this page.
- 4
Write the signal a stranger could log
“Named person matches all five, with quotes and dates in the note.” Not “loved the vision.” Blank’s earlyvangelists buy the vision first — that is why you still owe them an 18–36 month picture. Vision-buy without the five logged characteristics is a pitch that landed, not a who-pass.
- 5
Write a threshold, a window, and the action
Threshold: “fewer than N of M qualified conversations produce a five-characteristic match by day D.” Window: start date and end date. Twenty-one days from first who-ask is a window. Action: Stop this ICP, rewrite the who-sentence, or Continue to the next cheapest test. Fill N and M yourself.
- 6
Date the page, then leave the building
Same sitting. Sign it. Take the five log fields into the conversation. Do not lead with “would you be our earlyvangelist?” Ask about last week, the workaround, the timetable, and who holds the budget. If you later want a kinder bar, that is a new page with a reason — not an edit after the first compliment.
What you leave with
The Earlyvangelist Contract (copy this)
If the sitting produced a mood, you did not finish. The page should have one filled tripwire and five log fields you would actually use. Fill the brackets. Leave nothing as “users,” “visionaries,” or “soon.”
The tripwire
Who-bet: [person / job] who [last incident] and already runs [workaround]. Signal: named person matches all five Blank characteristics (problem, awareness, search + timetable, interim solution, budget path). Threshold: [N of M qualified]. Window: [start]–[end]. Action if miss: [Stop / rewrite who-sentence / run a named cheaper test].
If any bracket still says “early adopters,” “traction,” or “later,” the contract is not written. Qualified means they already do the job. Compliments do not count toward N. Three of five is a miss.
What does not count as the signal
Not a signal: a compliment, a waitlist, a smoke/fake-door click, a beta signup, a discovery call with no workaround, “I’d use that,” a demo they sat through, a Yibud score. Optional later: a design-partner ask or a money tripwire is a different page, written on its own.
You may still run interviews. You may not let them fire the tripwire. All five characteristics fire the tripwire. The 18–36 month vision is what you sell after someone qualifies — it is not a sixth characteristic.
Example tripwires (templates — fill your own N)
Who: if fewer than N of 8 qualified AP managers match all five by day 21 → rewrite the who-sentence the same day. Timetable: if they cannot name a date they need the invoice mess solved → do not count them. Budget: if they cannot name a card or a budget owner → characteristic 5 fails, even if the spreadsheet workaround is ugly.
The counts are blanks for you to fill. They are not conversion rates, not Yibud results, and not a claim about what “usually” happens. There is no typical N on this page.
The fork
When the who-filter is the expensive unknown — and when it is not
This page decides only whether “a named person matches Blank’s five” is the unknown you should buy evidence for now. Scarce commitment, money, reach, interviews, and usage testers have their own pages. Do not ask a stranger to buy a vision you cannot describe, or a person you cannot find.
Run the who-filter first
You can name the job and last week’s incident. The expensive unknown is whether anyone in that job is problem-aware, already searching on a timetable, running a workaround, and able to get budget. Write the tripwire. Take the five log fields into the next conversation.
Run design-partner or WTP first
The person already matches all five. The unknown is whether they will put time, data, and workflow at risk — or whether they will pay this price. Use the design-partner page or the WTP page. Do not relabel a who-pass as scarce commitment or as money.
Run discovery or beta first
You cannot yet name the job, or you only need people who will use an unfinished build and report breakage. Interviews and beta recruitment are cheaper than a who-tripwire with no person behind it. Come back here once the job is findable and “do they match all five?” is the unknown.
When an earlyvangelist tripwire is the expensive unknown
The job is named. A weekly incident exists without you prompting it. You can describe a thin first version and an 18–36 month picture. You do not know whether anyone has the workaround, the timetable, and the budget. That is this page. A weak customer or founder-fit line on a Yibud report sits near this fork — as a flashlight, not as an earlyvangelist count.
When an earlyvangelist tripwire is the wrong next test
You cannot name the job. The channel is silent. You are still asking “would you be our earlyvangelist?” in the same breath as the pitch. Or you only needed a usage tester, a scarce-commitment partner, or a charge. Run the interview filter, the reach test, the beta playbook, the design-partner ask, or the money tripwire first. A who-filter with no qualified job is theater.
Worked example
One earlyvangelist contract you can copy (illustrative)
The week below is illustrative — names, firms, and counts are invented so you can see the setup. It is not a conversion benchmark and not a Yibud report. Copy the method, not the numbers.
The who-bet, written before outreach
“An accounts-payable manager at a mid-size manufacturer who chased at least three past-due invoices last week on a shared spreadsheet, and who already has a date they need that chase to stop.” The tempting next step is to automate collections. The current bet assumes the AP manager is the person, last week’s chase is the job, and all five Blank characteristics are the instrument. Illustrative names: founder Priya Shah at Ledgerlane; candidate Jordan Hale at Westfield Parts.
The tripwire, written the same sitting
Signal: named AP manager matches all five — last week’s chase in their words, they named the cost without a prompt, they are already looking and have a date (quarter close, audit, new ERP freeze), they already run a spreadsheet or a contractor, and they can name a card or a budget owner. Threshold: fewer than 2 of 8 qualified AP managers match all five by day 21. Qualified means they personally chase invoices, not that they “work in finance.” Window: first who-ask through day 21. Action if miss: rewrite to a narrower who (plants with an existing ERP export and a named AP lead) or Stop this sentence. Compliments do not count.
What a miss looks like on day 21
Illustrative close: six AP managers compliment the vision; four join a waitlist; two describe a messy spreadsheet; one has a timetable; zero can name a budget owner. That is an earlyvangelist miss you already named — rewrite the who-sentence or Stop. It is not a reason to start the collections engine “because people were warm.” A beta signup list in the same week would have looked busier. That list is usage interest, not a vision buyer with budget.
What must not happen in the window
Do not count a compliment as characteristic 2. Do not skip characteristic 5 because the workaround is ugly — Blank’s fifth is dollars, not pain intensity. Do not add a sixth trait (“they have a large LinkedIn following”) to rescue a miss. Do not stretch day 21 because the eighth manager has not replied — silence is a no on this filter. If you cannot find eight qualified AP managers in twenty-one days, you may have a reach problem — that is a discovery or smoke-test tripwire, not a reason to fake a who-pass. After someone matches, still sell the 18–36 month vision and deliver the minimum feature set to that person, not to everyone who sat through the demo.
Write the tripwire before the first intro. If day 21 arrives and no named person matched all five, honor the action. If it moved against the bar you wrote, Continue to the next cheapest test — a design-partner ask or a money tripwire, not a factory. The method is the dated page, not the story you tell after.
Where Yibud fits
Use the free validator as a flashlight, then write the who-contract yourself
Yibud is a free, no-signup startup idea validator. Scores come from a deterministic rule engine, not from a language model guessing success. Optional AI text, when it is used, only polishes prose. It does not invent the number. A Startup MRI report can name a weak customer, founder-fit, or monetization assumption, then a Day-7 Continue / Refine / Re-test / Stop signal. Earlyvangelist work sits next to a weak “someone with budget and a timetable exists” assumption — write the who-tripwire, do not hope a mid-band score means “earlyvangelists later.” If you already have a report, start the contract with the named assumption — not with the overall score. Then run the window yourself. The method stands alone if you never open the analyzer.
Analyze my idea →Common mistakes
What usually wastes the earlyvangelist contract
Counting a compliment or a waitlist as an earlyvangelist
Blank’s earlyvangelists buy the vision because the five characteristics are already true. “This is interesting” is manners. A waitlist is reach. If the only evidence is warmth, you have talk. You do not have a tripwire firing.
Passing on 3 of 5, or inventing a sixth characteristic
The 2010 list is five. Skipping budget because the spreadsheet is ugly, or adding “influencer” or “design-partner logo” as a sixth, is how a cheerleader gets promoted. All five, logged, or it is a miss.
Selling the minimum feature set to everyone
Blank is blunt: most customers will hate a minimal feature set. You sell the 18–36 month vision and deliver the thin first version to earlyvangelists, not to a general audience. Showing the thin product to people who fail the who-filter is how you collect “not enough features” as if it were market truth.
Relabeling a beta tester or a design partner as the who-filter
A usage tester reports breakage. A design partner puts scarce resources at risk. Neither page replaces Blank’s five. You can have testers and partners who never matched. Do not use a logo or a signup list to skip the who-contract.
Writing the bar after outreach — or using a score as the count
A who-list invented after warmth is a recap. A miss you already named, followed by a new repo, is how the bar moves. Honor Stop or rewrite the who-sentence. A Yibud score does not match Blank’s five. Fill N yourself.
Sources
Where these ideas come from
- Steve Blank, “Perfection By Subtraction – The Minimum Feature Set” (March 4, 2010) — Used for the Earlyvangelist definition (Early Adopter + Internal Evangelist), the five characteristics (problem; understands they have it; actively searching with a timetable; cobbled-together interim solution; dollars to purchase), selling the vision and delivering the minimum feature set to visionaries not everyone, the 18–36 month product vision past the minimum, and the claim that most customers will hate a minimal feature set. This page does not invent a sixth characteristic or a sample size from the post.
- CB Insights, “The top 9 reasons startups fail” (report analyzing 431 VC-backed shutdowns since 2023; updated March 5, 2026) — Used as a warning about why fit and unit economics matter, not as a personal success forecast. CB Insights reports “ran out of capital” at 70 percent and calls it often the final cause of death. Among the 385 companies with identifiable reasons, more telling patterns include poor product-market fit (43 percent), bad timing (29 percent), and unsustainable unit economics (19 percent). Many companies cited more than one reason. This page does not invent other percentages.
- Steve Blank, Customer Development category — Used as light primary context for the Customer Development posture after the who-page exists: leave the building, talk to people who have the job. This page does not invent quotes from the category archive.
In one paragraph
Summary you can quote
An earlyvangelist test is a pre-written who-filter tripwire: an observable signal, a threshold, a calendar window, and a named action. The signal is a named person matching Steve Blank’s five characteristics from the 4 March 2010 post “Perfection By Subtraction – The Minimum Feature Set” — they have a problem, they understand they have it, they are actively searching on a timetable, they have cobbled together an interim solution, and they have or can quickly acquire dollars to buy a product that solves it. Earlyvangelist means Early Adopter plus Internal Evangelist. You sell the vision and deliver the minimum feature set to those visionaries, not everyone; most customers will hate a minimal feature set, and earlyvangelists need an 18–36 month picture past it. Design-partner pages own scarce co-dev; WTP owns money moving; beta pages own usage testers; Mom Test and discovery own how you ask; smoke and fake-door own uncharged reach; concierge and Wizard of Oz own delivery; kill, pivot, pre-mortem, critical-assumption, and validation-decision pages are decision contracts. This page supplies who-evidence those contracts can later read. Scores do not count earlyvangelists. A Yibud report can point at a weak customer or founder-fit assumption. The tripwire still has to be written by the founder.
FAQ
Questions founders actually ask
What is an earlyvangelist?
Blank’s 2010 definition: Early Adopter plus Internal Evangelist — a customer who can envision a product solving a critical, immediate problem and who has budget to buy it. They match exactly five characteristics (problem, awareness, search plus timetable, cobbled workaround, dollars). They buy the vision first. You deliver the minimum feature set to them, not to everyone.
Is an earlyvangelist the same as a design partner or a beta tester?
No. A beta tester uses the unfinished product and reports what broke. A design partner puts scarce resources at risk and co-develops. An earlyvangelist is the who-filter: vision buyer with pain, timetable, workaround, and budget. The same person can later become a partner or a tester. The labels are not interchangeable.
How many earlyvangelists do I need?
Fill your own N. This page does not publish a typical count, a conversion rate, or a “usual” pass bar. Write N of M qualified conversations inside a dated window before outreach. A miss you already named is a miss.
Do they have to pay now?
Not on this page. Blank’s fifth characteristic is that they have, or can quickly acquire, dollars to purchase a solution — a path to budget, not a charge that already moved. If money moving is the expensive unknown, write a WTP tripwire. Characteristic 5 can be true before a card is charged.
Do I need an account, and where does Yibud fit?
You do not need an account. The method on this page stands alone. Run the free analyzer if you want a flashlight on a weak customer or founder-fit assumption before you write the contract. The engine is deterministic. Optional language-model text only polishes prose. Bring the named assumption back here and fill the brackets.
Write the who-tripwire before the next sprint
Yibud scores weak customer and founder-fit assumptions with a deterministic engine. You write signal, threshold, window, and the five log fields while you are still honest — then an earlyvangelist is evidence, not a polite yes.
Generate a Yibud report →