Should an MVP be free or paid?

Paid, for almost any B2B SaaS product. Free MVP users provide engagement data but not revenue validation. The most important thing to validate in a B2B MVP is whether the market will pay for the solution. A free tier that attracts non-paying users tells you the product is useful; it does not tell you whether it is a business. Charge from the first customer, even if the amount is lower than the eventual price.

How do you set a price for an MVP when you do not know the market price?

Start with the minimum price that would make the business economically viable per customer, and test whether customers accept it. If customers accept it without negotiation, you may be priced too low. If all customers push back, you may be priced too high. The right price in an early market is the one where roughly half of qualified prospects convert without significant price objection. This is a different standard than a mature market where pricing is benchmarked against competitors.

What pricing model works best for an MVP?

A simple, flat monthly or annual subscription is the best starting model for most B2B MVPs. Usage-based pricing is compelling in theory but requires infrastructure to meter usage and creates unpredictable revenue for both the company and the customer. A flat fee that covers all MVP features for a defined number of users or seats is easier to sell, easier to administer, and easier to compare against a budget line. Complexity can be added when the simpler model is validated.

What is a founder discount and is it a good idea?

A founder discount is a lifetime discount offered to the first cohort of customers in exchange for early adoption. It creates urgency and rewards risk-taking from early customers. The risk is that discounted customers become a permanent segment that the business cannot remove from. A better approach is a time-limited discounted rate with a clear expiry (at version 1.0 launch, at month six, or when a specific feature set is reached) so the discount does not become permanent.

When should an MVP offer a free trial?

A free trial is appropriate when the product has a clear value delivery moment that the customer can reach within the trial period, and when the conversion path from trial to paid is well-defined. A seven to fourteen day free trial works for SaaS products where the customer can see meaningful value in that time. For complex products where value takes weeks to realize, a trial creates an expectation that the product delivers value immediately, which may not match reality.

MVP Development and Startup BuildsMay 23, 20266 min read

MVP Pricing Models: How to Charge for Something That Is Not Done Yet

MVP pricing is the decision about what to charge for a product that is not yet complete, with limited features, and an unproven track record. The pricing decision for an MVP serves two purposes: it validates whether target customers will pay at all (proof of willingness to pay), and it establishes a pricing baseline that is easier to adjust upward as the product improves than to rebuild from a free tier that trained customers not to expect to pay.

Written by Yashveer Singh, founder of Yashveer Labs.

What you need to know

Free MVP tiers validate engagement but not the most important hypothesis: willingness to pay. Charge from the first customer.
Starting with a price that is too low is a business model problem. Customers who were acquired at low prices are difficult to move to higher prices. Starting at a justifiable rate and discounting for early adopters is better than starting free and trying to charge later.
Simple, flat-rate subscription pricing is the easiest to sell, explain, and administer for an MVP. Add complexity only after the simple model is validated.
The right MVP price is one where qualified prospects convert without significant price objection but where the conversion rate is not 100 percent. A price that every prospect accepts without hesitation is probably too low.
Pricing is part of the MVP's hypothesis. The specific price should be a deliberate decision based on business economics and willingness-to-pay testing, not a random number chosen to feel accessible.

The core argument

The founder instinct to make the MVP free is understandable. The product is not finished, there will be bugs, the feature set is limited, and charging for it feels presumptuous when the product is not yet ready to be presented with confidence. This instinct is wrong for B2B SaaS products. The willingness-to-pay validation is the most important signal the MVP can generate, and a free tier does not test it. A customer who uses a free product to manage a small part of their workflow has told you the product is useful. A customer who pulls out a credit card has told you the product is valuable enough to be worth a budget decision.

The pricing model for an MVP should match the simplest version of the pricing model you expect the full product to use. If the full product will be seat-based, price the MVP per seat. If the full product will be workspace-based, price the MVP per workspace. This alignment matters because pricing expectations set early are difficult to change. An MVP priced on seats creates the expectation that additional seats are the mechanism of growth. An MVP priced as a flat all-in fee creates the expectation that the price is fixed regardless of team size.

The amount matters less than the fact of charging. In my experience working with early-stage founders on their first pricing decisions, the specific number within a reasonable range (50 to 200 dollars per month for most B2B SaaS) has less impact on conversion than whether the founder presents the price with confidence. Founders who apologize for the price, immediately offer discounts, or add excessive caveats about the MVP being incomplete lose deals not because the price is wrong but because the lack of confidence signals that the price is arbitrary. Decide the price based on business economics, present it without apology, and treat pushback as negotiation data rather than a reason to immediately reduce it.

Common mistakes

Starting with a free tier because it feels more appropriate for an MVP. Free users validate interest, not value. Charge from the first customer, even at a reduced introductory rate with a clear expiry date.

Setting the price based on what competitors charge without knowing if those prices work for your economics. If a competitor charges 20 dollars per month and your cost of service is 15 dollars per month, you do not have a business at 20 dollars. Price based on economics and willingness to pay, not competitor benchmarking.

Offering permanent discounts to early customers. An early adopter who receives a 50 percent lifetime discount has established a pricing expectation that the customer relationship will continue to reflect. Offer time-limited discounts with clear expiry dates.

Not testing price sensitivity before committing to the MVP price. Present the MVP to ten qualified prospects and ask what they would pay. The distribution of answers reveals the willingness-to-pay range and lets you set a price with actual market data.

Conflating price acceptance with product validation. A customer who buys the MVP at the MVP price has validated that the product is worth the current price to them. It does not validate that the product is worth the eventual target price. Test price sensitivity at the target price range, not just at the MVP price.

Where to start

Calculate the minimum viable price based on your business economics. What customer acquisition cost, hosting cost, and support cost must the subscription cover to make each customer profitable? That number is the floor for your MVP pricing.

Present the price to ten qualified prospects before finalizing it. In your next ten prospect conversations, propose the price and observe the response. How many accept without negotiation? How many push back? The responses tell you whether the price is in the right range.

Write the pricing page copy before making the first sale. The discipline of writing the value proposition that justifies the price often reveals whether the price is defensible. If you cannot write the value proposition confidently, either the price or the value proposition needs work.

Frequently asked

Author

The engineer behind this page

This was written by Yashveer Singh. Full stack developer, founder of Yashveer Labs, currently in Class 12 in New Delhi, shipping production systems while most of my peers are still writing their first console app. I am pointing the work, on purpose, at machine learning, AI engineering, and cybersecurity. If you are reading this because you want to hire someone who will not waste your time or your money, that is the role I am built for.

Start the conversation See the work DM on Instagram

MVP Pricing Models: How to Charge for Something That Is Not Done Yet

What you need to know

The core argument

Common mistakes

Where to start

Related reading

Frequently asked

The engineer behind this page

Technical Co-Founder vs Hired Developer: The Decision That Decides Your Startup

The Complete Startup App Development Process from Idea to Launch

How to Avoid the Mini Salesforce Trap as a First Time Founder

How to Budget for an MVP Without Knowing Software Costs