mvp

Pricing test for an MVP: methods, limits, and when to stop

AA
Aurum Avis Labs Author
7 min read

Pricing test for an MVP

A pricing test for an MVP checks whether strangers accept a specific price and terms for the outcome your minimum product promises, before you freeze scope or scale the build. You show the number, the currency, what is included, and what is not, then you measure behaviour: checkout started, invoice paid, pilot signed, or a deliberate step you defined in advance. The test is not a poll about “what would you pay”. It is evidence about whether the price you need can survive contact with buyers who do not owe you a favour.

This is for founders and innovation leads in Switzerland who already have a believable problem and a narrow MVP definition. For the full validation menu, see how to validate a startup idea. A smoke test landing page checks demand on a message; a fake door test can include price on the page. Here the focus stays on the price itself and what you are allowed to conclude.

How to run a pricing test for an MVP

Keep one segment, one packaging story, and one primary price in the first run. Multiple tiers often tell you which layout won, not which price the market tolerates.

  1. Anchor the test to the MVP outcome

    Write what the buyer gets in the first usable version: scope, channel, support, and timeline. If the MVP is a concierge service, price the service. If it is software, price access to that software, not a roadmap deck.

  2. Pick a price test that matches your risk

    Strongest: payment or a signed order at the stated price. Next: refundable deposit or paid pilot with credit rules in writing. Lighter: a pricing page with checkout or invoice request, or a fake door where the click leads to price and terms before any “success” message.

  3. Show terms before enthusiasm

    Renewal, minimum term, refunds, and exclusions belong on the same screen or PDF as the price. Hidden fees after interest are negotiations, not a test.

  4. Send traffic you can explain

    Organic posts mix audiences. A small paid campaign on one channel, stable targeting, and UTM labels make it easier to tie clicks to the price shown.

  5. Write the falsifier first

    Example: “If fewer than three of twenty targeted firms start checkout at CHF 89 per month, we change the segment before we add features.” Without a written stop rule, you will reinterpret silence as “not yet”.

What a pricing test can show, and what it cannot

A clean pricing test answers a narrow question: at this price and these terms, do enough of the right people move toward payment or pay? It can justify changing the headline, the segment, the packaging, or the number itself.

Counts as price signal

  • Completed payment or invoice at the test price from a buyer you did not coach through every objection
  • Checkout or order flow started after the full price and terms were visible
  • Paid pilot at the stated fee, with scope exclusions written down

Does not count alone

  • Survey bands or “too expensive” without a behavioural step
  • Clicks on “pricing” with no view of the actual number
  • Discount-only purchases that nobody would repeat at list price

What a pricing test does not prove

Even a successful run shows that some buyers accepted your offer under the terms you set. It does not prove you can acquire customers profitably, retain them, or defend the idea in court: ideas as such cannot be protected (IGE overview on ideas). It does not replace tax, contract, or regulatory advice when you invoice in Switzerland.

On client projects we sometimes ship an MVP without payments in the first release so the team can test listings, chat, and demand before adding billing complexity. That is a scoping choice, not proof that price does not matter. When price is the riskiest assumption, leave payments in scope or run a separate priced pilot alongside the build.

A made-up example: two prices on one MVP page

A made-up example: a founder in Bern tests software that turns spoken site notes into structured inspection reports for small property managers. Problem interviews are done; the MVP is a web form, PDF export, and email delivery, not integrations. They publish one page with two monthly prices, CHF 49 and CHF 89, same features, different support response time stated in writing. The primary button opens a Stripe checkout for a refundable CHF 1 deposit that converts to the first month if the buyer stays after week two. Over fourteen days they run a modest Google Ads budget on German keywords in Switzerland, with the price visible above the fold. Analytics show 310 sessions, 41 scrolls past the price block, nine deposit attempts, four completed deposits from domains they do not recognise, and five abandonments on the card step. Session recordings show several visitors compare the two tiers and leave on the support paragraph. The founder keeps CHF 89, drops the cheaper tier from the next test, and does not claim revenue or channel economics. They only claim that some cold visitors accepted a visible price enough to start payment.

Who should run a pricing test now, and who should wait

If you still need to learn whether the problem is real or frequent, run problem work and sharper interviews before you optimise price. If procurement must approve every purchase, test with one department and document who signed. If you already have paying users, your question is packaging or churn, not whether anyone will ever pay.

For online payment in Switzerland, card and TWINT through a provider such as Stripe is a practical path when you need checkout without building billing first (Stripe TWINT). Choose mechanics after the offer is clear; the test is the commitment at the stated price.

Common questions

Is a pricing test the same as testing willingness to pay?

Overlapping, but not identical. Willingness to pay is the wider question of whether anyone puts money or a binding order on the table. A pricing test for an MVP asks whether a specific number and package for your first product version holds up. You can run both in sequence.

Should the MVP include real billing?

Include billing when price or payment flow is what you fear most. If fulfilment or habit is riskier, a manual pilot at a written price can come first. Do not pretend a free waitlist answered the price question.

When the Product Validation Package fits

The Product Validation Package fits when price must be read against real product behaviour: deployed software, analytics, paid acquisition, and measured conversion through a funnel you can inspect. Weeks 1 to 4 put a working MVP live; later weeks compare drop-off and cost per lead with the price you assumed. If you still need the first priced commitment without a build, stay with pilots, fake doors, and the broader validation guide before you book a build conversation on the contact page.

mvp pricing startup validation fake door pre-sales
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.