A voting ring is when people get friends to upvote their post. This is against the rules. We want stories to be on HN because they're good, not because they were promoted.
All: Please don't do this; just take your chances with HN's randomness. If a post is solid and hasn't gotten any attention yet, a couple of reposts is ok. Be careful not to abuse that, though, since accounts that repost too much eventually lose submission privileges. Send any questions to hn@ycombinator.com.
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.
The only reason I can see for us to NOT use it, is because we already use rollbar[1] (for tracking js errors) and rollout[2] (for feature flags). The name 'Rollcall' will create way too much confusion for us. Sounds silly, I know, but it does have an impact.
[1] https://rollbar.com/ [2] https://github.com/FetLife/rollout
and, the naming conundrum - we just stuck with what we called it when it was an internal tool. I can respect the confusion angle, though. Still, you should give it a try :)
Many small operations carve out services and say 'You two work on X, Y, and Z services'. At which point, no one else cares until you hit a point/prod release.
Maybe that is just me tho.
Thanks for the feedback, though - it would be good to hear if others have similar thoughts.
My team uses an issue tracker right now (YouTrack, from JetBrains) as a central hub for our activity. Telling people what you're working on is as easy as changing the status of a ticket to "In Progress".
Is there something about this system that reduces the friction of that process (simply selecting an item from a dropdown)? It seems like having to actually go type out what you're working on would be more work (not to mention that if someone wants more detail about the ticket you're working on, they have to look it up themselves instead of clicking on it).
I thought it was a cool idea then, and it's cool to see someone re-examining the status-communicating problem today.
Maybe it would be too duplicative since pivotal is supposed to show what is being worked on at a glance, but this integration was the one thing I was hoping to try out in the free plan after viewing the landing page...
