Hi everyone — thanks for being here on launch day. What inspired Slotix We were tired of scheduling tools that either felt like a consumer toy or a enterprise maze. We wanted something that treats booking as a product surface: clean public pages, predictable slots, and a model that scales when you are not one person with one calendar — but many spaces, each with its own branding, rules, and bookings. The problem we set out to solve Scheduling breaks in boring ways: availability drifts from the real calendar, exceptions are painful, and multi-brand or multi-client setups turn into account hacks and forwarded invites. Slotix focuses on accurate slot computation from weekly availability, exceptions, and existing bookings, then makes the outcome visible through a simple booking flow and admin tools teams can actually run day to day. How the approach evolved We started from the domain, not the UI trend of the week: tenants as spaces, meeting types with duration and buffers, and explicit rules vs exceptions so “why is this day blocked?” has an answer in the data model. As we got closer to launch, the product pushed us toward integrations that match how meetings really happen — CalDAV for calendar truth and KMeet for a real join link — and toward localization (en / fr / de) because booking is inherently local for guests. Along the way we also invested in the unglamorous parts that matter when you ship for real: platform administration, deployment discipline, and privacy-minded operational defaults — because scheduling touches personal data by definition. We would love your take: what is the #1 scheduling pain you still hit in 2026 — availability accuracy, multi-tenant setup, calendar sync, or something else entirely?

Slotix

Online calendar booking

Online calendar booking