Ask HN: How do you price a SaaS prodcut?

1 points by santy-gegen ↗ HN
Hi Hacker News!

Santy again here. I'm learning a lot in this community and am thankful for that.

Today my question has to do on how do you pick a price point for a SaaS product?

One heuristic I came up with is how much would I pay for sth like what I'm building, but I'm not sure it's the best one.

I studied economics in college and remember we talked about demand curves and so on, and always wondered what would the optimal price be to maximize profits. It's a theoric exercise but it seems it's not how it's done in real life (though it definitely would be cool if we could do that).

Anyway, I appreciate any answers and thanks for the help.

Santy

4 comments

[ 3.1 ms ] story [ 16.7 ms ] thread
Figure out your costs…how much will it cost to develop? How much will it cost to run? Do the operational costs increase or decrease over time? Do they increase or decrease as you add more customers? How much will maintenance cost over time? How much will adding new features cost over time?

Don't forget the vig that the app stores and payment processors take (anywhere from 2-5% depending on the whims and fancies of the companies involved as well as the credit card the consumer used, if you take credit cards).

Don't forget compliance costs, e.g. if your service has to access another service's data in the cloud they may demand SOC 2 certification or some other certification.

No, you're not going to be able to accurately identify each and every cent / yen / euro of cost but you need to identify as much as possible and then set your price as some multiple so that you can eat moderate fluctuations in costs or revenue or items you missed and hopefully have a decent profit.

I think too many SaaS's underestimate the basket of costs involved in providing their probably perfect useful, viable service and attract a decent customer set (or they use investor funds to subsidize the cost of service). Then when they actually have a sense of how much money they're losing per month or per transaction they radically change the cost structure with too short a timeframe for customers to adapt. The larger the customer, the longer it will take to absorb a change to expenses. Doesn’t matter whether they can afford it or not, what matters is how the increased usage fee intersects with the customers annual or biannual budgeting process.

Just my opinion, I mostly walk a dog now.

Thx for the very detailed response. I think the main wisdom for me lies in understanding how it is important to take into account the budgeting process of big companies & to also use a margin of safety technique when deciding the price.

Thank you very much!

I used to work for a large F100 company where I had to know no later than June 30th what my expected expenses would be for the next fiscal year (January-December). Any increase in expenses or acquisition of a new product required going through an extraordinary escalation process. Smaller companies may be more flexible but also may not be able to absorb price increases.

For what it’s worth, the same F100 company was notorious for taking anywhere from 90 to 180 days to pay invoices…because it could. If your price is above a couple hundred (US) per month you may not be able to just use credit cards/paypal/etc and need to learn the ins and outs of procurement systems.

wow, it sounds extremely bureaucratic but then again there must be some reason why bureaucracies come up with size. it's a great warning and very kind of you to share this info with me. I'll do my best to avoid these pitfalls when selling to big co's. Also, it seems pricing your product under 100 bucks might do the trick