Skip to content
YibudYibud

Before polite yes becomes a build

Willingness-to-Pay Test — Get Money Evidence Before You Build

“I would pay for that” is manners. A deposit, a pre-order, a paid concierge week, or a priced checkout is evidence. A willingness-to-pay test is the tripwire you write before outreach so Sunday cannot stretch compliments into a factory. Scores do not pick a price. Money moving against a bar you named in advance does.

Last updated: September 30, 2026

Direct answer

What is a willingness-to-pay test?

A willingness-to-pay (WTP) test is a pre-written money tripwire: an observable signal, a threshold, a calendar window, and a named action. The signal is money moving — a deposit, a pre-order, a paid concierge, or a priced checkout — not a survey answer. Rob Fitzpatrick’s The Mom Test is blunt: do not ask “would you pay?” Ask what they already spend and which workarounds they already run. Compliments are not data. Peter van Westendorp’s 1976 Price Sensitivity Meter asks four stated-threshold questions (too cheap, cheap, expensive, too expensive). Those answers are a stated method. They are weaker than a card that actually charged. Alberto Savoia’s Pretotype It separates a pretotype (behavioral evidence, Your Own Data — YODA) from a prototype (building it right). Eric Ries’s public Lean Startup principles treat validated learning as the point of a smoke test versus a build. Steve Blank’s Customer Development treats payment as field evidence you leave the building to collect. This page writes the priced tripwire those methods can later read.

Key takeaways

What to remember

  • WTP is a four-field tripwire: signal + threshold + window + action. The signal is money moving, not “I would pay.”
  • Compliments, stated prices, and uncharged clicks sit below a deposit, a pre-order, a paid concierge, or a priced checkout.
  • Write the tripwire before outreach. A price invented after warmth is a recap, not a test.
  • Run WTP first when price or unit economics is the expensive unknown. Run smoke, fake-door, concierge, or Wizard of Oz first when reach or delivery is still the expensive unknown.
  • Fill your own N. This page does not publish conversion rates, overestimate multiples, or a “usual” pass bar.

Why it matters

Polite yes does not pay rent

I have watched founders treat a week of “I’d definitely pay” as a green light to open the repo. The card never came out. The build did. 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. Unit economics that cannot hold, and a product nobody will pay for, are priced problems. They do not show up in compliments. This page does not invent other percentages, and it does not claim a WTP test predicts survival.

Vocabulary

Four terms this page uses on purpose

These match how the rest of Yibud talks. If a sentence here uses one of these words, it means this.

Willingness to pay

Whether a named person will trade real money for a named offer, in a real transaction. Only money tests money. Interviews and surveys measure talk.

WTP tripwire

A pre-written contract: observable money signal + threshold + calendar window + named action. A risk list without a dated price bar is not a tripwire.

Money-moving signal

A deposit, a pre-order, a paid concierge, or a priced checkout that a stranger could log. “I would pay,” a waitlist email, and an uncharged click are not money-moving signals.

Stated WTP

A number someone says they would pay — including van Westendorp’s four stated-threshold questions. Useful as a stated method. Weaker than money that actually moved. This page does not invent how much stated WTP overestimates behavior.

The ladder

Money-signal ladder: talk is not a rung that pays

Rank the evidence you already have. Do not skip a rung by renaming it. The counts you later write are yours. They are not a benchmark copied from this page.

Rung 1 — “I would pay” and compliments

Polite interest. Fitzpatrick’s rule: compliments are not data. Ask last week’s spend and last week’s workaround. If this is all you have, you do not have a WTP test yet. You have manners.

Rung 2 — Stated thresholds (van Westendorp)

Four questions from 1976: at what price is it too cheap to trust, a bargain, starting to feel expensive, and too expensive to consider. A stated method. Weaker than a charge. Do not treat the answers as a price you can ship.

Rung 3 — Uncharged reach (smoke / fake-door)

A landing-page CTA or an in-product button with no charge. Measures demand and reach. Usually uncharged. A click is not a price. Use the smoke-test and fake-door pages for that work.

Rung 4 — Deposit, pre-order, or priced checkout

Money moves before the factory exists — or a checkout exists and someone completes it. This is the first rung that can fire a WTP tripwire. Refunds and “I need to ask my partner” still count as the card coming out; write how you will treat them before the window opens.

Rung 5 — Paid concierge

The founder delivers the outcome by hand and charges. Delivery plus money. The concierge page owns the manual job. This page owns the charge as a WTP instrument. A free concierge is delivery practice, not a WTP test.

Not the same page

WTP test vs smoke, cheapest-method, delivery, interviews, and decision contracts

Several Yibud pages sit next to this one. Mixing them up turns a waitlist into “they will pay,” or a paid concierge into “we already built it.”

Smoke test and fake-door — demand and reach, usually uncharged

A smoke test puts the whole concept on one page and watches a CTA. A fake-door puts a feature-level button inside something people already use. Both measure whether anyone reaches. They are usually uncharged. This page starts when the expensive unknown is price, not reach.

Cheapest validation test — which method to pick

That page compares pre-order, MVP, concierge, and fake-door and helps you pick which to run first. This page is WTP depth: how to write the priced tripwire once money is the expensive unknown. Do not use this page as a method picker.

Cheapest validation test (which method first) →

Concierge and Wizard of Oz — delivery

Those pages own how you deliver the outcome by hand, or behind a curtain. A paid concierge is one WTP instrument on this page. An unpaid concierge or a Wizard of Oz week answers “can we produce the result?” — not “will they pay this price?”

Mom Test script — interview filter

That page is the conversation filter: past spend, past workarounds, last week’s incident. This page is the money tripwire you attach after the filter. “Would you pay $X?” is a Mom Test fail and a WTP fail.

Mom Test interview script →

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 priced evidence those contracts can later read. It is not a Stop / Pivot / Continue sitting.

Design partner — scarce co-dev, not money

That page’s signal is staff time, data, workflow access, and weekly use as Customer Validation evidence. This page’s signal is money moving. A design partner is not a deposit. A checkout is not co-development. Use both tripwires when both unknowns are expensive; do not relabel one as the other.

Design partner validation →

A mid-band monetization score is a flashlight, not a price. It can point at a weak paid assumption. It does not name the charge. What a validation score actually means →

The sitting

How to write a WTP tripwire in one sitting

Do this after interviews have named a weekly incident and a workaround — not after you have already spent the week explaining the vision. 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. 1

    Write the priced bet as one sentence

    Person + job + offer + price + instrument. “A $39/month Sunday meal plan for night-shift nurses, sold as a $39 checkout after a 20-minute intake.” If price still says “TBD” or “value-based,” you do not have a WTP bet yet.

  2. 2

    Name whether price is the expensive unknown

    If you still cannot find the person, run smoke or fake-door first. If you still cannot deliver the outcome by hand, run concierge or Wizard of Oz first. If the person and the job are real and the unknown is “will they pay this,” stay on this page.

  3. 3

    Pick one money instrument

    Deposit, pre-order, paid concierge, or priced checkout. One instrument per window. A waitlist plus “we’ll charge later” is still rung 3. Savoia’s pretotype is the posture: get Your Own Data on behavior before you prototype the factory.

  4. 4

    Write the signal a stranger could log

    “Completed a $39 checkout.” “Paid a $20 refundable deposit.” “Paid $150 for a two-week concierge.” Not “showed interest.” Fitzpatrick’s filter still applies in the follow-up: ask what they already pay for the workaround, not whether the idea sounds fair.

  5. 5

    Write a threshold, a window, and the action

    Threshold: “fewer than N of M qualified people complete the charge by day D.” Window: start date and end date. Fourteen days from first priced ask is a window. “Give it the summer” is not. Action: Stop, rewrite the price or offer, or Continue to the next cheapest test. Fill N and M yourself.

  6. 6

    Date the page, then leave the building

    Same sitting. Sign it. Blank’s Customer Development is the posture after the page exists: the cheapest next move is a field ask, not a new repo. 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 WTP Contract (copy this)

If the sitting produced a mood, you did not finish. The page should have one filled tripwire and one instrument you would actually run. Fill the brackets. Leave nothing as “users,” “soon,” or “fair price.”

The tripwire

Priced bet: [person] will pay [amount] via [deposit / pre-order / paid concierge / priced checkout] for [offer]. Signal: [money-moving event a stranger can log]. Threshold: [N of M qualified]. Window: [start]–[end]. Action if miss: [Stop / rewrite price or offer / run a named cheaper test].

If any bracket still says “people,” “traction,” or “later,” the contract is not written. Qualified means they already do the job. Compliments do not count toward N.

What does not count as the signal

Not a signal: “I would pay,” a waitlist email, an uncharged smoke/fake-door click, a van Westendorp number, a compliment, a score. Stated method (if used): van Westendorp’s four questions only as talk — then still run a money instrument in the same window.

You may collect stated thresholds. You may not let them fire the tripwire. Money fires the tripwire.

Example tripwires (templates — fill your own N)

Checkout: if fewer than N of 12 qualified nurses complete a $39 checkout by day 14 → rewrite price or offer the same day. Deposit: if fewer than N of 10 pay a $20 refundable deposit by day 14 → Stop this sentence. Paid concierge: if fewer than N of 5 pay $150 for a two-week manual job by day 14 → do not automate.

The counts are blanks for you to fill. They are not conversion rates, not Yibud results, and not a claim about what “usually” happens.

The fork

When WTP is the expensive unknown — and when it is not

The cheapest-method page picks which test family to run. This page decides only whether price is the unknown you should buy evidence for now. Reach and delivery have their own pages. Do not charge a stranger for an offer you cannot name, or for a person you cannot find.

Run WTP first

You can name the person and the weekly job. Interviews already show unprompted pain and a workaround they already pay time or money for. The expensive unknown is whether they will pay this price. Write the tripwire. Use one money instrument.

Run smoke or fake-door first

You cannot yet find qualified people, or you do not know whether anyone reaches for the concept. An uncharged demand test is cheaper than a priced ask with no audience. Charge later, in a new window, once reach is no longer the unknown.

Run concierge or Wizard of Oz first

You still cannot describe the happy path without improvising every time. Delivery is the expensive unknown. A free or cheap manual week can teach the steps. A paid concierge is WTP plus delivery — only if you already named the price bar.

When WTP is the expensive unknown

The person is named. The job happened last week without you prompting it. A workaround already costs time or money. You can deliver a thin version by hand. You do not know whether the planned price moves a card. That is this page. A weak monetization score on a Yibud report sits near this fork — as a flashlight, not as a price.

When WTP is the wrong next test

You cannot name the buyer. The channel is silent. The outcome still takes you three hours of invention per customer. Or you are asking “would you pay?” instead of charging. Run the interview filter, the reach test, or the delivery test first. A priced ask with no qualified person is theater.

Worked example

One WTP contract you can copy (illustrative)

The week below is illustrative — names, prices, 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 priced bet, written before outreach

“A $39/month Sunday meal plan for night-shift nurses, sold as a $39 checkout after a 20-minute intake, reached through one Facebook group.” The tempting next step is a recipe app. The current bet assumes the nurse is the person, Sunday prep is the job, $39 is the price, and checkout is the instrument.

The tripwire, written the same sitting

Signal: completed $39 checkout (not “I would pay,” not a waitlist). Threshold: fewer than 3 of 12 qualified night-shift nurses complete checkout by day 14. Qualified means: they prepped food last Sunday or paid for a workaround last month. Window: first priced ask through day 14. Action if miss: rewrite to a $15 one-Sunday job or Stop this sentence. Compliments do not count.

What a miss looks like on day 14

Illustrative close: eight nurses compliment the idea; four join a waitlist; one starts checkout and abandons; zero complete the $39 charge. That is a WTP miss you already named — rewrite the offer or Stop. It is not a reason to start the recipe app “because people were warm.” A smoke-test waitlist in the same week would have looked busier. That waitlist is reach, not WTP.

What must not happen in the window

Do not ask “would you pay $39?” and count yeses. Do not treat van Westendorp answers as checkouts. Do not extend day 14 because the twelfth nurse has not replied — silence is a no on this ask. Do not invent a cheaper price on day 13 unless that rewrite was the action you wrote. If you cannot find twelve qualified people in fourteen days, you may have a reach problem — that is a smoke-test or channel tripwire, not a reason to fake a WTP pass.

Write the tripwire before the first DM. If day 14 arrives and money did not move, honor the action. If money moved against the bar you wrote, Continue to the next cheapest test — not to 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 WTP 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 monetization dimension and a critical assumption, then a Day-7 Continue / Refine / Re-test / Stop signal. WTP sits next to a weak paid assumption — write the priced tripwire, do not hope a mid-band score means “charge 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 WTP contract

Asking “would you pay?”

That question invites a compliment. Fitzpatrick’s Mom Test is the filter: last week’s spend, last week’s workaround. If the only evidence is a hypothetical yes, you have talk. You do not have a tripwire firing.

Counting a waitlist or a smoke-test click as WTP

Uncharged reach is a different page. A click measures whether anyone reached. It does not measure a price. Run the money instrument in its own window, or you will automate a waitlist.

Treating van Westendorp as a charge

The four stated-threshold questions are a stated method. They are not a deposit. This page does not invent an overestimate multiple. If you use the questions, still run a money instrument before you treat the price as real.

Using the score as a price

A low monetization score does not pick $39. A high score does not prove anyone will pay. The score ranks relative risk in the inputs you typed. A dated threshold on a named charge is what decides the week.

Charging before you can name the person — or automating after a miss

A priced ask with no qualified buyer is theater. A miss you already named, followed by a new repo, is how the bar moves. Honor Stop or rewrite the offer. Keep the notes.

Sources

Where these ideas come from

  • 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 WTP 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.
  • Rob Fitzpatrick, The Mom Test (2013) — Used as the interview filter: do not ask “would you pay?” Ask past spend and workarounds. Compliments are not data. This page does not treat the book as a conversion benchmark.
  • Eric Ries, The Lean Startup — public methodology at theleanstartup.com/principles — Used for validated learning and the fork between a smoke test and a build. A smoke test can stay uncharged. This page is the charged tripwire you write when price is the unknown. This page does not invent success rates.
  • Alberto Savoia, Pretotype It — pretotyping.org — Used for pretotype versus prototype, and for YODA (Your Own Data): trust behavioral evidence you collected, not opinions in Thoughtland. Linked to the verified public site. This page does not invent pretotype success rates.
  • Peter van Westendorp, Price Sensitivity Meter (1976) — Cited as a stated method: four threshold questions (too cheap, cheap, expensive, too expensive). Stated WTP is weaker than money-moving behavior. No public canonical URL is linked here. This page does not invent overestimate multiples or accuracy percentages.
  • Steve Blank, Customer Development — Used for payment as field evidence: leave the building and collect a real transaction. Blank is not the source of the tripwire fields, and this page does not treat Customer Development as a sample-size rule.

In one paragraph

Summary you can quote

A willingness-to-pay test is a pre-written money tripwire: an observable signal, a threshold, a calendar window, and a named action. The signal is money moving — a deposit, a pre-order, a paid concierge, or a priced checkout — not “I would pay,” a waitlist, or an uncharged smoke or fake-door click. Rob Fitzpatrick’s The Mom Test filters interviews: ask past spend and workarounds; compliments are not data. van Westendorp’s 1976 Price Sensitivity Meter is a stated method and weaker than a charge. Alberto Savoia’s pretotype collects Your Own Data on behavior before you prototype. Eric Ries treats validated learning as the point of a smoke test versus a build. Steve Blank treats payment as field evidence. Run WTP first when price is the expensive unknown. Run smoke, fake-door, concierge, or Wizard of Oz first when reach or delivery is still the expensive unknown. Kill, pivot, pre-mortem, critical-assumption, and validation-decision pages are decision contracts; this page is the priced evidence they can later read. Scores do not decide prices. A Yibud report can point at a weak paid assumption. The tripwire still has to be written by the founder.

FAQ

Questions founders actually ask

Is “I would pay” enough to start building?

No. That sentence is manners. A WTP tripwire needs a money-moving signal — deposit, pre-order, paid concierge, or priced checkout — plus a threshold, a window, and an action you wrote before outreach.

Can a Yibud score tell me the price?

No. The score is a structured read of the inputs you typed. It does not charge anyone. A failed priced threshold you named before the window is what rewrites the offer. A report’s weak monetization line is a flashlight. The contract is still yours.

When should I run a smoke test or fake-door instead?

When reach is still the expensive unknown — you cannot find qualified people, or you do not know whether anyone reaches for the concept. Those tests are usually uncharged. Charge in a new window once the person is findable.

Is van Westendorp a willingness-to-pay test?

It is a stated method: four threshold questions from 1976. It is not a money-moving test. Use it as talk if you want. Do not let it fire the tripwire. This page does not invent how much stated answers overestimate behavior.

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 paid 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 WTP tripwire before the next sprint

Yibud scores weak paid assumptions with a deterministic engine. You write signal, threshold, window, and the money instrument while you are still honest — then WTP is a tripwire, not a polite yes.

Generate a Yibud report →