Hashoff - Kill the leave spreadsheet. Time off, handled in Slack.

Hey Product Hunt 👋 I'm Dharani. Every company I've worked at tracked leave the same way: a spreadsheet, then a spreadsheet plus a Slack message, then a spreadsheet plus a Slack message plus somebody's memory. By the time anyone needs an actual answer — is she off next Thursday? how many days do I have left? — nobody fully trusts the sheet. So we built Hashoff to kill it. What it does: • Request leave from Slack or the web. Managers get a Slack message with Approve and Deny. One tap, done — no new login for anyone. • A monthly timeline of who's away, pending requests included, plus a morning Slack message to approvers listing who's off today. It stays quiet on days when nobody is. • Balances that actually add up. Accrual is a real policy here, not a label: weekly, fortnightly, monthly or quarterly, pro-rated so a March joiner doesn't get January's days, and it back-fills correctly if you switch it on in June. • The fiddly things the sheet always got wrong: half days at either end, carry-over, leave years that span New Year, public holidays for 152 countries applied per team, per-person allowances. • Rules it can't break: no double-booking, no going over allowance, no quietly cancelling leave already taken. • Install it in Slack and your roster imports itself. People who leave get deactivated, not deleted, so their history survives. • And since it already knows the team: birthday and work-anniversary digests. Both ship switched off — they read dates that often arrive from a spreadsheet, and the first thing a wrong row does is announce someone's birthday on the wrong day. An admin has to look and turn them on. What it doesn't do: payroll, performance reviews, or the other eleven modules in an HR suite. One job. Free for the first 30 days, no card. I'm here all day — tell me how your team tracks leave right now, and be hard on us. The broken edge cases are the ones I most want to hear about. — Dharani