Just start with comps. With comparables.
Software is very expensive to build, but for the most part, costs almost nothing to ship. It might cost you $0.10 a month in hosting charges per user for an app that isn’t server or storage intensive.
So why is one app $5 a month and another $150 a month? The answer is value provided, yes (that’s why Salesforce and Workday can charge so much) … and also, comparables.
- If your app is about as valuable as Box, then price it like Box.
- If your app is about as valuable as Twilio, then price it like Twilio.
- etc., etc., etc.
At this point, every company has bought between 1 and 200 SaaS apps. You’re not the first. They are used to it, and used to certain organic price points.
Your prospects and customers are now veterans for the most part, and they “know” what an app should cost — based on the value they think it provides relative to other apps they pay for.
Imagine opening a new restaurant. If it looks like McDonalds, and tastes like McDonalds, it probably needs to be priced close to McDonalds. A $4-$5 hamburger, max. If it looks like a standard brasserie, maybe a $20 steak frite is OK. And maybe if it looks like French Laundry, and tastes like French Laundry, a $200 steak is maybe OK.
I may be taking the new restaurant metaphor too far, but the point is, give the customers context. If pricing feels consistent with similar apps, then it will seem fair and correct, and pricing won’t be a huge issue.
Later, you can raise prices and optimize.
