Your most expensive plan is for a team of 40-100 people. For the sake of simplicity, you are talking about a team that is costing a company a minimum of say $1,200,000 a year (assuming $15/hr FTE's) and you are asking them to pay you $300 a year for a tool they are supposed to use throughout the day.
Why have you built such a low value tool?
Take your prices and multiply by 10 and you are probably at a more correct pricing strategy if you are selling to businesses.
1) Daily stand-ups are adequate to communicate what I'm working on each day. Updates more often than that become noise.
2) The issue/task tracking system will let me see who, if anyone, is working on a particular issue. I more often care about who is working on issue X (if X is blocking me, for example) than I care about what Joe is working on right now.
The "realtime" aspect of it is less important than it seems at first. Our team, for example, updates 3-4 times a day on average, sometimes a bit more if we're just jumping from project to project to cleanup bugs or do general maintenance.
The fact that we've positioned this as a status board just reinforces that perception - that seems to be a common sentiment, and something we're going to have to consider again.
Thanks for the feedback.
But $15/mo seems insane for a 13 person team. It makes me think you guys won't be around in a few months, and makes me reluctant to commit.
Baremetrics charges $250/mo! You should charge at least $50, but probably $150.
The other aspect of this is that we have other features coming that we expect to be able to charge more for. Complicating the pricing matrix was something we're concerned about, but we were thinking something like Github's two-tier pricing model when we got those features out.
But, like I said, the way you explained it was not a perspective I had considered. Thanks for the feedback, was helpful.
was in response to:
>multiply your prices by 10