Getting started · Schedule.software
There is no sign-up form on this page. That is deliberate.
Self-serve tenant onboarding is one of the things we are still building. We could put a form here and mail you afterwards, but a form that does not provision an account is a form that lies about what it does. So: a conversation first, and an honest account of what runs today.
The engines are built and running — dispatch, routing, the multi-resource constraint gate, the self-healing reschedule proposer, the eligibility gate, and all eight K-12 booking surfaces. What is opening is the standalone product surface around them.
What actually happens
Four steps, and you can stop after any of them.
✓1 — Tell us the shape of the problem
Write to [email protected] with what you are scheduling, roughly how much of it, and what breaks today. One paragraph is plenty. If you already know which surface you need — conferences, facilities, crew dispatch — say so and we will skip the tour.
✓2 — A walkthrough of what is built, not a pitch deck
We show the surfaces that exist and name the ones that do not. Where something is module-dark or in development, you will hear the word before you see the screen. You should leave the call able to repeat back what is real.
✓3 — A scoped pilot on one surface
Almost nobody should start on eight surfaces. Pick the one that hurts — usually conference booking or crew dispatch — and run it for one cycle. The correctness guarantees (no double-booking at the database, capacity counted under a lock, the consent chokepoint) are the same on one surface as on all of them.
✓4 — Widen only when the first one is boring
The surfaces share one calendar substrate and one eligibility engine, so adding the second is a module toggle rather than a second procurement. That is the whole argument for the product, and it is worth nothing until the first surface is dull and reliable.
Three conversations, depending on who you are
Education, Professional, Enterprise.
Education. We walk the eight K-12 booking surfaces, the correctness guarantees, and the consent posture — the roster chokepoint, the family wall, the calendar feed that carries no names — and what a school or district rollout actually looks like term by term.
Professional. We show the dispatch and routing engine, the multi-resource booking flow, and the hard-constraint eligibility gate, including the consumer-booking-through-to-dispatch path.
Enterprise and white-label. We discuss the licensing model, the module toggle layer, and what a self-hosted or managed deployment looks like in your context.
What starting does not involve
No card, no charge, no contract signed on a web page.
There is no live checkout on this site. Reserving early access does not create a payment, does not store a card, and does not commit you to anything — the pricing published on the home page is the planned launch tier, not a price you can be billed at today. A booking fee inside the product is a computed, reserved ledger line and is not charged; the payment seam exists and Stripe is not enabled.
Reminders are opt-in and currently send nothing at all. Self-serve onboarding, two-way calendar sync, the CalDAV server, public booking pages as a standalone consumer surface, and the full workforce layer are in development. We would rather you hear that here than discover it in week two.