Enterprise Mono-platform pricing as a startup

Oct 20 (edited) in Packaging

Hi everyone, since I feel like tiered pricing usually gets most of the attention I'm seeking clarity for mono-platform pricing on a few points:

1. Our offering includes both a service component (content maintenance and delivery) and a SaaS platform. In a mono-platform model, how should we structure these elements? Should the service be an add-on, or part of the core platform?

Currently, we have:

- A core platform flat fee

- One-time setup payments per new device

- Usage-based pricing above 10,000 monthly knowledge calls

2. How would one go about creating a pricing ladder? Or does that not apply for this pricing model. It seems to me like it’s most applicable to tiers.

For context: our solution targets enterprises and aims to prevent customer support requests for physical devices and technical issues.

Any insights or examples of successful mono-platform pricing strategies in the enterprise space would be greatly appreciated. Thank you!

5 comments