Pricing Tests Can Inform Your Price, Not Prove Demand

Listen Labs announced that Gabor-Granger pricing tests were live on September 23, 2026. Its announcement describes recruiting, moderation and analysis in one place, supported by career researchers. Its October 2 pricing-tests page also explicitly covers monthly and annual willingness to pay for subscriptions and software. I give Listen Labs credit for bringing a structured pricing method into its research workflow. Making that work easier to organise is useful.

A pricing test can help you choose a price to try, but a stated willingness to pay does not prove that customers will buy.

That is the boundary I want to keep visible. The supplied pages establish what Listen Labs offers and how it positions the feature. They do not independently establish how accurately the method predicts sales. I would use the result to narrow a decision, then check it against behaviour involving a real offer and real money.

What a pricing response tells you

In a Gabor-Granger study, people are asked whether they would buy a described offer at specified prices. Those responses can help you examine how stated demand changes across the prices tested.

That is more disciplined than asking people to name a price with no structure. You can compare responses to a consistent offer rather than collect a pile of numbers that may mean different things.

But the word “would” still carries a lot of weight.

Someone answering your survey can sincerely like the product and accept the price, then decide against buying when rent is due or their current product still works. For software, the person responding might want the tool but lack purchasing authority. An annual subscription can sound reasonable until the full payment appears at checkout.

I understand the temptation to turn a neat chart into a forecast. I want research to resolve uncertainty too. But I would push back on treating the strongest price in a survey as an established selling price. It is a candidate, under the conditions you described, among the people you asked.

The offer before the price

Before testing prices, write the offer as your customer would encounter it.

For a physical product, that means specifying what is included and the costs or conditions that affect the purchase. Is delivery included? Is this a single order or a recurring one? Can the customer return it?

For software, specify the plan and its relevant limits. A response about an unspecified “team plan” leaves too much room for people to imagine different products.

Keep that description consistent across the prices you want to compare. If a higher price also comes with better support or more product, you are changing the offer as well as the price. That may be a useful study, but it answers a different question.

I would also avoid dressing up the description with claims such as “incredible value” or “essential for busy teams.” Give people enough information to judge the offer without telling them what their judgement should be.

If participants cannot explain what they would receive, fix the description before paying to ask more people about it.

The audience that could actually buy

A price response belongs to an audience. Existing customers, people considering their first purchase and people who rarely buy the category can give you very different answers.

Choose the audience based on the decision you face. If you are setting an acquisition price, surveying only loyal customers leaves a gap. They already know whether your product works for them. A new buyer does not have that experience.

Screen for relevant behaviour rather than enthusiasm alone. Depending on the offer, you might ask when someone last bought from the category, what they currently use, or whether they take part in purchasing decisions. Avoid a screener that makes the desired answer obvious, such as asking whether they love discovering premium products.

Recruitment cannot repair a fuzzy audience definition. A panel can help you reach eligible participants, but you still have to define eligibility and decide whose answers belong together.

These are study-design recommendations, not reported findings about Listen Labs’ participants or results.

The billing period on the page

The subscription use case deserves care because a monthly amount and an annual commitment can describe quite different decisions.

If you show an annual subscription as a monthly equivalent, show the total charged and when payment happens. Also make the commitment and cancellation terms clear. Otherwise, someone may answer about a flexible monthly plan while you think they have accepted an upfront annual payment.

I would test the terms a customer will actually see. If you want to compare monthly and annual offers, treat billing terms as part of that comparison rather than assuming that dividing the annual price gives you an interchangeable offer.

Ask a plain comprehension question before interpreting the price response. For example, ask participants to describe what they would be charged today. If their understanding differs from your offer, you have found a problem that a willingness-to-pay chart alone could hide.

The decision before the results

Write down what you will do differently after the study, before you see the answers.

Perhaps you need to choose which of two prices to take into a live test. Perhaps you need to decide whether a proposed increase deserves further investigation. “Find our perfect price” is too broad to guide a small study.

A one-page research decision brief can hold the audience, offer and intended decision in one place. Include what the study cannot settle. For a pricing survey, I would explicitly leave actual conversion and renewal behaviour unresolved.

Then decide how you will handle an inconclusive result. If the responses do not clearly separate your options, you should be able to say so. A chart does not oblige you to declare a winner.

At Probe, we support survey and interview studies for exploring these questions. Own-audience studies are free up to 10 questions and 25 responses. If we recruit participants, they come from our recruitment partner’s vetted panel, with one all-in study price shown before launch. That can support work on offer comprehension and purchase objections; it should not be read as a claim that we offer an equivalent Gabor-Granger feature.

Evidence after the survey

Before launching the research, choose the behaviour that would make you more confident in its result.

A completed purchase at the proposed price gives you stronger evidence of willingness to pay than a survey answer. A clearly disclosed paid pilot may be useful for software. A real preorder may help for a product that is not yet available, provided the delivery and refund terms are explicit.

An email signup or a click on a pricing page can tell you something, but I would not count either as payment evidence. People can take those steps without accepting the financial commitment.

Even purchase evidence needs context. A discounted launch to existing fans does not establish what unfamiliar customers will pay at full price. An initial subscription payment leaves renewal unresolved. Keep the audience and terms visible when you compare the research with the behaviour that follows.

Before your next pricing study, finish this sentence in your brief: “If respondents accept this price, our next test will ask eligible customers to…” Make the ending a concrete action with clear terms. If you cannot finish it yet, keep working on that before you collect the price responses.