[benzible]

The issue is: if you have pricing that works for solo devs / small teams, you'll leave a lot of money on the table with respect to enterprises, who are willing to spend silly amounts of money but also don't want to feel like they're being ripped off. One "solution" is non-transparent pricing but your low-end pricing may leak. Of course you can charge for enterprise features but the signal you send via low end pricing will set expectations for enterprises as well.

[tcistull]

You've hit the nail on the head with this. One big reason we don't show our pricing is that we're still a young company, and we're figuring things out. We don't yet have enough data to know the real value we bring or who our ideal customer is. If we price too low, we might shortchange ourselves, but if we go too high, we could scare people away.

[tcistull]

For now (until we are bigger and have more devs), I go off of a per company basis and see the needs/amounts for them. Then I see our costs and shoot over a price to start the discussion