Roadmap
Roadmap
Four states, no marketing adjectives. If something is blocked, the thing blocking it is named.
Shipped5
In build4
Planned18
Gated4
The ledger
Every capability, and the state it is actually in
One row per capability, each with its own anchor, so a status badge anywhere on this site lands on the row it refers to.
| Capability | Status | Detail | Blocked by |
|---|---|---|---|
| Availability engine | Shipped | Timezone and DST-aware slot generation, buffers, compound resources. | — |
| Holds and concurrency | Shipped | Atomic Redis holds plus a Postgres exclusion constraint, so a double-booking is refused by the database rather than by application code. | — |
| Public booking flow | Shipped | Catalogue, availability, rate-limited hold, idempotent create, guest manage and cancel. | — |
| Merchant operations workspace | In build | Today, Calendar, booking detail and payment-free status actions, Customers, Services, Setup and guided publication are implemented locally. The current production panel is the earlier read-only dashboard until this release passes promotion. | A production build, seeded portal acceptance pass and operator-approved promotion |
| Tenant isolation | Shipped | Forced row-level security on 105 tables, with separated runtime, authentication and schema-owner database roles. Distinct ALTER TABLE … FORCE ROW LEVEL SECURITY statements in packages/db/prisma/migrations, counted 2026-08-19. | — |
| English and Arabic interface | Shipped | Right-to-left throughout, verified across 12 screenshot cases. | — |
| Deposits and card holds | In build | Policy resolution exists and the deposit amount is written to the booking record. Charge capture against the merchant's own Stripe account is being written. | Stripe platform approval for the UAE rail |
| In build | The official Meta Cloud API adapter is in the codebase and disabled by default. | Meta business verification and a WhatsApp Business account | |
| Booking pages and embeds | In build | The hosted booking page runs today on the public flow. The embed script and custom booking domains are not built. | — |
| Email confirmations and reminders | Planned | Will include calendar attachments and reminders derived from the booking rather than queued once. | — |
| Microsoft calendar sync | Planned | Two-way sync with Teams links generated by the calendar itself. | — |
| Google calendar sync | Planned | Two-way sync with Meet links generated by the calendar itself. | Google OAuth verification review for calendar scopes |
| Team scheduling | Planned | Pooled and collective availability against each host's own working hours and timezone. | — |
| Routing rules | Planned | Territory, segment, language, deal size and account ownership, evaluated in order. | — |
| Weighted distribution and fairness ledger | Planned | Auditable assignment written under a row lock inside the booking transaction. | — |
| Planned | Email, web chat and WhatsApp as one thread per customer, with assignment rules and SLA timers. | — | |
| CRM sync | Planned | Two-way contact and meeting sync with HubSpot, Salesforce and Pipedrive. | — |
| Public REST API and webhooks | Planned | Signed, retried, and delivered with a log. | — |
| Single sign-on, SCIM, audit log | Planned | Specified for the top plan. None of it is built. | — |
| Plans and subscription billing | Planned | Three incompatible draft ladders were found and subscription billing does not exist. Pricing stays unpublished until one location-based model is operator-approved and backed by pilot economics. | Operator decision OG-06 on the ladder, payment economics and included usage |
| Reporting and exports | Planned | Booking, no-show, show-rate, speed-to-lead and routing-fairness reporting, and scheduled exports. None of it is built. | — |
| Self-serve data export | Planned | Contacts, conversations, bookings, deposits and message history as CSV and JSON, without asking us. No export path exists in the codebase today. | — |
| Migration and import | Planned | A self-serve importer for an existing scheduling tool, and assisted migration above it. | — |
| Support tiers | Planned | Response targets per plan are specified. There is no support desk running, because there are no customers and one operator answers every email. | — |
| Badge removal and white-labelling | Planned | Removing the Bookesto badge from public surfaces is an entitlement, and entitlements are not built. | — |
| EU data residency and DPA | Planned | Part of the data-protection pack, together with EU-region hosting for EU tenants. | An Article 27 representative, a DPA with standard contractual clauses, and counsel review |
| EU, EEA and UK signups | Gated | Waitlisted. We will not take the data until the pack above is in place. | The data-protection pack above |
| Saudi Arabia deposits | Gated | Stripe has no presence in the market, so there is no rail to settle a deposit on. | A second payment-rail decision by the operator |
| AI agent on chat and WhatsApp | Gated | Not built, not enabled, not sold, and not marketed anywhere on this site. | A commercial model API runtime, a signed data-processing agreement, and an approved monthly budget cap. None of the three is approved |
| Uptime SLA and public status page | Gated | Production is live, but there is no contractual SLA or public status page and not enough operating history to promise one. | Off-box monitoring, backup/restore evidence, sustained operating history and an operator SLA decision |
| SOC 2 | Planned | Not started. There is no report and there is no badge for one on this site. | Begins after the first 100 paying merchants |
Status checked against the build on 2026-08-19 · Shipped means running in production and reproducible by the verification suite; local release candidates remain In build
Switched off
About the AI capability
It would be easy to put an AI agent in the hero of this website. Everybody else does. It is not there because it does not exist, and because turning it on requires three approvals we have not obtained: a commercial model API runtime, a signed data-processing agreement covering customer conversation data, and a monthly budget cap. Internal development tooling is not a customer-facing runtime and we will not blur the two.
When it is turned on, it will disclose that it is automated in the first message of every conversation, because European law has required that since 2 August 2026 and because you should know.
The changelog is the roadmap keeping its promises.
No card. Merchant access is invite-only — you get the build log and first access.