The pricing meeting nobody is ready for
You have a product that works. A few people are using it. Someone from outside your network says they want to pay for it.
Then comes the question you have been avoiding: how much does it cost?
The honest answer is that you don't know yet. You don't have enough data on willingness to pay, on what the switching cost is, on what the alternative costs, or on how your product actually delivers value to different types of users.
But you have to say a number.
This is the SaaS pricing strategy problem at early stage. It is not a pricing problem at its core. It is a hypothesis problem. You are setting a price before you have the evidence to justify it confidently.
The goal is not to set the right price. The goal is to set a price that does not cripple the business before you collect enough information to set the right one.
The two fatal pricing mistakes at early stage
Pricing too low because it feels safer
The reflex is understandable. Lower price means lower barrier. More signups. Proof of demand.
The problem is that very low pricing attracts a customer profile that is optimising for cost rather than outcome. These customers churn fast when a cheaper alternative appears, generate the most support volume per dollar of revenue, and tell you almost nothing about what real buyers value.
They also make it very difficult to raise prices later without churn and credibility damage.
Pricing too low is not conservative. It is just a different kind of wrong — one that's harder to recover from because you have built expectations into your early customer base.
Pricing based on what feels comfortable to you
What the founder would personally pay for a product is almost never the right reference point.
If you have built something, you understand exactly what it does and how. You see all the code, the effort, the infrastructure. You have a fully formed mental model.
Your customer does not. They are evaluating an unfamiliar tool against their current workflow, their existing spend, and a mental model assembled from your homepage copy and the first 10 minutes of trying it.
What feels expensive to you — because you know every corner of it — might feel exactly right or even cheap to them if the outcome value is clear.
Pricing from your own discomfort with the number is the fastest way to undercharge at scale.
The information you can actually get before launch
You cannot get clean willingness-to-pay data before you have paying customers. But you can get useful signals.
Observe what comparable tools charge. Not competitors exactly — the same problem solved differently, the same category, adjacent categories. If tools solving a less specific version of your problem charge $49/month and you solve the specific version better, that is a reference point.
Run the Amos Tversky pricing question. Ask 5 to 10 potential buyers: "At what price would this product feel too cheap to be credible? At what price would it feel too expensive to consider? At what price does it feel like good value?" The overlapping range gives you a working zone to start from.
Price discovery in early conversations. When a prospect says "I love this, how much is it?" and you give a number, their reaction is data. A quick "that's fair" is different from a long pause. A "can you do a discount?" is different from "can I pay annually upfront?" These are imperfect signals. They are still signals.
Check job postings. If companies are hiring people to do manually what your product automates, the salary plus overhead for that role is the upper ceiling of what the right buyer could justify spending on automation.
The framing that helps most
Pricing is not permanent. That is the most important thing to internalise before setting the first number.
Early pricing is public hypothesis testing. You set a number, put it in front of people, watch what happens, and adjust.
The founders who agonise over getting it perfect before launch delay a data collection process that can only start when pricing is live and someone is either buying or declining to buy.
Set a number you can defend intellectually. Make it easy to adjust. Then start collecting real evidence.
A simple framework for the early price
If you are genuinely starting from scratch with no comparable tools and no market data, this structure produces a reasonable starting point:
Identify the value unit. What are customers actually buying an outcome of? More leads, more time, fewer errors, less staff time required? Quantify a conservative version of that outcome in their terms.
Find the cost of the alternative. If they do not use your product, what do they do instead? Hire someone part-time? Use a less specific tool that doesn't quite fit? Do it manually? Estimate the cost of that alternative.
Price below the alternative, above the price point that signals toy. If the alternative costs $800/month in person-hours and a comparable but less specific tool costs $39/month, a $79 to $149/month range for something that does the job better has a defensible logic.
This is not sophisticated pricing research. It is enough to start.
The monthly-versus-annual decision at early stage
Offer annual billing from the start, even if most people choose monthly.
The reasons are practical:
Annual customers churn at dramatically lower rates. They have committed for 12 months. They are financially incentivised to use the product enough to justify renewal. The relationship has a different quality.
A 15 to 20% discount for annual versus monthly is enough of an incentive to get the customers most committed to the outcome onto the annual plan early.
Early annual customers also give you a cleaner MRR signal. Monthly churn distorts the picture. Annual customers let you see what your base actually looks like when people are using the product seriously.
The free tier decision
Do not default to a free tier because every other SaaS seems to have one.
Free tiers are expensive. They generate support load. They attract customers who will never pay. They create a floor expectation that can complicate conversion.
A free tier makes sense when the product creates network effects (more users make it more valuable for all users), or when the product has a genuine land-and-expand dynamic where free users become the product's own distribution mechanism.
If neither of those is true, a free trial period (14 days, no credit card) is more honest. It signals that the product is worth paying for. It gives real buyers enough time to evaluate. It filters out people who are only there because it's free.
The difference in quality between free trial signups and freemium signups is significant for most vertical SaaS products.
What to do when you are clearly underpriced
The signal is usually this: close rate is high, churn is low, and customers rarely ask about price.
All three of those together suggest the price is not doing enough work to qualify buyers. When nobody pushes back on price, you probably have room to move.
The approach I prefer is gradual: raise the price for new customers first. Watch the close rate for 4 to 6 weeks. If it holds, the market is absorbing the new price. If it drops, you have learned where the elasticity is.
Do not grandfather indefinitely. Existing customers at old pricing should move to new pricing on a timeline, with advance notice. The customers worth keeping will understand that a product that is worth more should cost more.
SuperLaunch at https://superlaunch.in exists partly for exactly this stage — helping founders think through positioning and pricing before launch, and connecting early products with audiences that can provide real validation. Feedback from an actual interested audience is worth more than any pricing framework.
The question worth sitting with
If your product doubled in price today, how many of your current customers would cancel?
If the answer is "almost none," you are almost certainly underpriced. The customers who stay at double the price are telling you what the product is actually worth to them.
If the answer is "most of them," you either have a price elasticity problem (the value is not clear enough yet) or a wrong-customers problem (you have attracted users optimising for price rather than outcome).
Both of those answers are useful information. Neither is available until pricing is live and tested.
Set a number, watch what it tells you, adjust. That is the actual process.
For teams using WhatsApp to close early leads — which is common in founder-led sales for the first 50 customers — having a clear, confident price to state in the conversation is more important than having the objectively correct price. A confident number with a clear rationale converts better than a hedge. AutoChat at https://autochat.in helps teams that are scaling WhatsApp-based sales conversations as the funnel grows.
Image suggestion: a simple 2x2 grid showing four pricing zones based on close rate and churn rate axes, with annotations explaining what each quadrant signals about pricing calibration.
