Scheduling should show when you're actually free
Most scheduling tools work by dividing your calendar into a grid of identical slots. That assumption breaks down fast for anyone with a real, busy calendar.
A meeting that ends at 9:45am blocks the entire 9:00 and 9:30 slots — even though there's a valid 30-minute window from 9:45 to 10:15 that guests could book. That availability is hidden completely.
Skedvio fixes this at the root. Instead of pre-generatingfixed slots, it computes actual free windows after subtracting all busy time — calendar events, buffers, existing bookings, holidays. Guests see any start time where their chosen duration genuinely fits.
Every booking is also re-validated live at confirm time so double-bookings are caught even if the calendar changed while someone was on the page.
Scheduling that works the way time actually works.
Congrats on shipping, em_asad. The free-window computation is the right instinct, most tools do get this wrong. The claim I would want tested before trusting it live: the re-validation at confirm time. That only proves itself under real race conditions, two people trying to book the same freed-up slot within seconds of each other, a calendar sync lagging behind, a guest in a different timezone hitting a boundary right at a buffer edge. Those are the cases that quietly break scheduling tools after launch, not before.
I do product testing and walkthrough videos for early tools like this. I would want to run concurrent booking attempts and a few timezone and buffer edge cases against it directly, then document where the re-validation actually holds versus where it assumes. Happy to talk through it if useful.
I like that you're questioning the assumption behind scheduling instead of adding more scheduling features.
Most tools optimize around predefined slots. You're optimizing around actual availability. That sounds subtle, but it changes what the product is fundamentally trying to represent.