Finding a pricing model that's just right

Not the author, posting on Katie's behalf!

We've struggled a lot around pricing. Our product is an incident response tool built on Slack, so there's a few things that make it difficult:

- Our product encourages communication across the entire organisation, not within a single department or team (ie, engineering) and that's where we believe the real value is

- Even so, we want people to be able to adopt the product before committing for their entire workspace, so they can get a good sense of how it works for them

- And we don't want to put any barriers in the way of adoption, or have someone be unable to respond in an incident because "there aren't anymore seats!"

After a few revisions we've settled on a model we believe best aligns the value customers get from our product with what they'd end up paying us.

It's probably only 70% right, but feels a lot better than what we had before.

We wrote this article in case others are going through a similar process, and wanted a view into how we evolved our model over the last year.