As a developer who also manages a team, I got fed up with the email chains and error-prone Excel spreadsheets for tracking annual leave. The process was time consuming. People would email requests, I'd update a spreadsheet, then someone would book time off that conflicted because they were looking at an outdated version. The lack of visibility was the killer - nobody could easily see who was out when. It's just a faff.
Yeah I know there are existing products for this, and big HR and payroll software usually has modules to cover it but I'm a developer and I like building things. So I built Team Toggle as a side project over the past year, just evenings and weekends now and then. It handles leave requests, approvals, shared calendar views, and lets you set custom policies for your team.
Technical side:
I used .NET 8 MVC with MS SQL Server - pretty straightforward stack for a line-of-business application. The actual development was the easy part for me since I've built similar internal tools before. The real challenge has been everything else: marketing, landing page optimisation, figuring out how to get people to actually find and try the tool.
Where I'm at:
The users I do have really like how straightforward it is to use, and I've been able to be very responsive to feature requests. But I'm struggling with the typical developer problem - I can build the thing, but I'm not sure I'm selling it effectively.
What I'm looking for:
I'd love brutal feedback on whether my landing page does a good job explaining the value proposition, whether the product itself seems compelling enough, and any advice on getting traction. I'm particularly interested in hearing from anyone who manages teams or has dealt with PTO and annual leave tracking tools - does this solve a real problem worth paying for?
Feel free to be as blunt as possible. I'd rather get honest feedback now than keep spinning my wheels.
Homepage: https://teamtoggle.com
dev_proximity•10h ago