Hacker News new | past | comments | ask | show | jobs | submit login

I'm a dev, so don't know the exact details. We make a niche B2B application that is essential for the daily operation of businesses in our niche, with several hundreds of businesses as our customers.

Our pricing is in general based on a "fixed" monthly per-module price plus max-simultaneous-users price, and then a usage based per-transaction price element in addition.

The "fixed" cost can be somewhat different, typically it's a bit lower for smaller customers which also takes into account smaller customers typically have fewer custom integration needs (ie less custom maintenance/support).

The transaction pricing has a volume discount "ladder" with many steps. So smaller customers pays a lot more per transaction than larger customers. The transaction-based "price ladder" is otherwise quite fixed between customers.

This transaction-based element allows us to have reasonable overall prices for small as well as large, as it scales with our customers' activity. If they have a good month they pay more but also have more income.

This model is used for all our customers, from single-employee shops to the largest ones we have (many hundreds of simultaneous users). Our CEO has been clear he doesn't want to be cheapest, but deliver a superior product that justifies the price.

In the 10 years I've been here we've gone from #5 of a group of vendors to a dominating position. I think our pricing model has been one of the factors that has facilitated this.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: