I never intended to build a scheduling tool. The market is crowded, right? You have the giants like Calendly, the open-source heroes like Cal.com, and a dozen others.
But then I tried to set up a simple booking flow for my agency team.
The Problem: The "Team Tax"
I wanted a simple workflow:
- Client books a "Discovery Call".
- The system checks anyone on my dev team who is free.
- The booking goes to them.
In industry terms, this is Round Robin scheduling.
In pricing terms, this is usually "$16/user/month" or requires an "Enterprise" plan.
For a small team of 5, I was looking at $1,000/year just to route phone calls. That felt wrong.
The Solution: TimeFlux
I decided to build TimeFlux with one core philosophy: Collaboration shouldn't be a premium feature.
The Stack
- Next.js & React: For a snappy, client-side booking flow.
- Firebase: Real-time availability syncing.
- Google Calendar API: The source of truth for free/busy times.
- AI Integration: (Coming soon) To handle complex queries.
The Hardest Part: Timezones
Everyone warns you about timezones, but you don't realize the pain until you're trying to calculate whether "10 AM Tuesday in Tokyo" overlaps with "8 PM Monday in New York."
Dev Tip: Store everything in UTC. Display everything in Intl.DateTimeFormat().resolvedOptions().timeZone. Never trust the client clock.
Launching on Product Hunt
We just went live!
The response has been validating. It turns out, I wasn't the only one tired of the "Team Tax." Agencies, small dev shops, and consultants are switching because they can finally organize their team without a massive monthly bill.
What's Next?
We are building a "Lead Dashboard" right into the tool—so you don't need a separate CRM just to see who booked you.
Check it out here: https://timeflux.dev
I'm hanging out in the comments if you have questions about the tech stack!
Top comments (0)