4 ms·
yearly pricing seems more appealing than monthly, because there may be no months with vacations scheduled, and it might appear that you're paying "for nothing",
by mgkimsal 11y ago
yearly pricing seems more appealing than monthly, because there may be no months with vacations scheduled, and it might appear that you're paying "for nothing", but there will very likely not be an entire year with no vacations.
$15 feels sort of like the upper end of the price range, unless there's some integration with a payroll service.
I'd encourage considering a flat rate for small companies - $99/year for up to 12 employees, or something like that.
- rtpg 11y agoI agree with the bundling. It's essentially per-user pricing, but it's an easier pill to swallow. The pitch becomes something like "Simple pricing that doesn't break your budget". My reasoning for the $15 was that that's a fully loaded hour at a bit more than minimum wage. I think it's a good reference point for thinking about how much a company might save with the tool. Though for just vacations you're maybe saving less than an hour.
- mgkimsal 11y agoreally depends on your definition of 'small team'. Companies small enough that you might be targeting probably aren't thinking about loaded labor cost per hour on folks taking vacations and such. Also, the issue is how much impact is this going to have on the person arranging vacation time, vs the person taking it.