Needs more than a quick edit9 of 11 checks passed
The roadmap is strong and usable, but the unsupported 'undermines booking reliability' claim and the slightly confusing Q1 '20/20' allocation that includes uncommitted ceiling work need a quick correction before it is fully reliable.
Output
Tidewell booking roadmap: Q4 2026–Q1 2027
For Dana Okafor, CPO; both squad leads; Sales and Design
Strategy and trade-offs
Prioritise fewer missed appointments and better multi-site retention, not a broader feature set.
- No-shows average 11%. Clinics sending their own reminders average 6%—a promising signal, not proof that reminders alone cause the difference.
- Multi-site clinics represent 38% of ARR and churn at 2.9% monthly, versus 1.3% for single-site clinics. Of 31 multi-site departures, 23 cited the lack of a consolidated view.
- Fix calendar sync early: it causes 38% of support tickets, undermines booking reliability, and could release capacity for subsequent work.
Q4 2026: retain multi-site clinics and establish the reminder foundation
| Squad | Committed work | Squad-weeks |
|---|---|---|
| --- | --- | ---: |
| A | Ship multi-site dashboard: bookings and utilisation across locations | 10 |
| B | Ship calendar sync fix | 5 |
| B | Begin messaging service: provider, consent records and templates | 5 of 8 |
| Total | 20 / 20 |
Sequencing: Squad B tackles calendar sync first, then messaging. Messaging remains unfinished at quarter-end; we are not promising patient-facing SMS in Q4.
Dashboard rollout: Validate workflows with multi-site operators, including FitPhysio, before broad release. Track activation, repeated cross-location use and whether operators can answer their core bookings/utilisation questions without separate location views.
Calendar acceptance: Confirm failures and related tickets decline. Engineering’s expected three squad-weeks of quarterly savings are a forecast, not guaranteed capacity.
Q1 2027: launch reminders and validate outcomes
| Squad | Planned work | Squad-weeks |
|---|---|---|
| --- | --- | ---: |
| B | Complete messaging service | 3 |
| B | Build and roll out SMS reminders with confirm/cancel | 6 |
| A | Dashboard adoption, measured follow-up improvements and outcome evaluation | Up to 10 |
| B | Reminder rollout contingency | 1 |
| Total baseline allocation | 20 / 20 |
Squad A’s allocation is a budget ceiling, not ten weeks of pre-approved features. Dana and the leads will approve specific improvements from dashboard usage and customer evidence; unused capacity stays uncommitted rather than funding lower-priority scope.
The calendar fix could increase Q1 capacity to 23 squad-weeks across both squads. Confirm actual support savings before allocating the extra three weeks; use them first for rollout risks and demonstrated retention blockers.
Reminder sequencing: Finish messaging before reminder implementation. With nine squad-weeks on this dependency chain, plan for a late-Q1 rollout, not a January launch.
Measurement: - Pilot reminders with a comparison group where practical. Measure no-shows, advance cancellations, delivery failures and opt-outs; do not promise the observational 6% result. - Track multi-site dashboard adoption and monthly churn against the 2.9% baseline. Review churn reasons and rolling trends; the small population makes short-term attribution uncertain. - Establish baselines and experiment design before rollout. Expect fuller reminder-impact evidence in Q2.
Not doing in these two quarters
- Physitrack integration: Not committed. FitPhysio calls it nice to have; the dashboard is its must-have. Dana and Jordan should immediately correct the Christmas promise with FitPhysio, confirm whether its buying criteria have changed, and offer the dashboard delivery plan. An integration commitment requires an explicit roadmap trade-off—not hidden extra work.
- Waitlist auto-fill: Defer until reminders demonstrably create cancellations with enough notice to refill. Today, its prerequisite behaviour is rare.
- Deposits: No Q1 delivery promise. The contract cannot be signed before mid-February, and the 14-week build is a substantial commitment before testing the simpler reminder intervention.
- Booking page redesign: Defer. The 64% conversion rate alone does not establish a problem, and none of 18 interviews raised it. Design should support dashboard and reminder usability first.
What comes after
Q2 2027 onward: Scale effective reminders and address remaining multi-site retention gaps. Prioritise waitlist auto-fill if advance cancellations create sufficient refill opportunities. Reassess deposits if no-shows remain high and the partner contract is ready. Revisit Physitrack and booking redesign only with stronger customer or commercial evidence.
Claims the judge couldn’t find in the brief
- Calendar sync failures undermine booking reliability.
Grades and run details
Decision model 100 · LLM judge 9 of 12 checks
Decision model checks
- passUses the supplied evidence correctly85%
- passAddresses the actual decision96%
- passRespects explicit constraints56%
- passIdentifies material uncertainty97%
- passAvoids unsupported claims75%
- passProduces the required deliverable34%
- passEvery commitment serves the goals97%
- passHandles the Sales promise with evidence100%
- passOutcomes, with certainty that falls with distance78%
- passFits the stated capacity47%
- passSequences around dependencies93%
Run
- Run
- #1
- Time to output
- 47 s
- Submitted
- 1 Oct 2026