Spotlight: LeaveVia — leave tracking that shows its work
Most small teams manage leave the same way: a shared spreadsheet, a Slack message when someone's out, and a manager doing mental math on how many vacation days are left. It works until it doesn't, usually right around the point someone gets approved for leave that overlaps with two other people already out.
LeaveVia is built for that exact gap. It's not trying to be an HR platform. It says so directly on the site: no payroll, no full HR suite, just requests, balances, and who's away when. Employees submit leave requests (including half days) from the browser. Managers see the request next to the person's remaining balance and, notably, next to a coverage warning if approving it would drop team availability below a set minimum. That last part is the detail that makes this feel like it was built by someone who has actually managed a small team through a leave request pileup, rather than someone designing a generic "HR module."
The smart decision here is the ledger. Instead of showing a single balance number that nobody trusts, LeaveVia records entitlement, accrual, carry-over, expiry, and manual adjustments as individual ledger entries. That sounds like a small technical choice, but it's the difference between a balance you have to take on faith and one you can actually trace back to why it is what it is. Anyone who has had an employee dispute a leave balance and had no good way to explain it will get why that matters.
The other sensible bet is scope discipline. The feature list is short on purpose: requests and approvals, balances and policies, availability and coverage, calendar sync with Google and Outlook, role-based visibility so leave data is shared where it's useful and private where it isn't. There's no attempt to bolt on payroll, performance reviews, or onboarding flows. For a small team, that's usually the right call, since most of them don't want another sprawling HR system they only use 10% of.
Who should try this: small businesses and small teams (the pricing tiers and "team" language suggest this is aimed well below enterprise HR territory) who currently track leave in a spreadsheet or over email and are feeling the friction of it, especially teams where coverage actually matters, like ops, support, or retail-style shift work where knowing "who's away" affects whether the day runs smoothly. If your current process is a shared Google Sheet and a lot of asking around, this is a plausible upgrade with a 30-day free trial and no card required to start.
Who should skip it: anyone who needs leave management as part of a broader HR or payroll system will hit the ceiling fast, since LeaveVia explicitly doesn't do that. Larger companies with complex multi-country policies, union rules, or deep integration needs into existing HRIS platforms will probably outgrow it too. And if your team is small enough that a shared calendar and a Slack channel genuinely still work fine, you don't need this yet, no matter how clean it looks.
Where this goes next, as I read it: the coverage and location views suggest the founder has multi-team or multi-location businesses in mind, which is a reasonable expansion path without breaking the "just leave management" promise. The more interesting test will be whether they hold the line on scope as customers inevitably ask for payroll exports, Slack notifications, or deeper reporting. The pitch right now is refreshingly narrow: everything leave management needs, and nothing you don't. Keeping that promise as the product grows is the real challenge from here.
Try LeaveVia: leavevia.com
See the launch: LeaveVia on welaunch.sh