Usable with a quick edit11 of 11 checks passed
A PM could use this roadmap with light edits because the commitments, capacity, dependencies, deferrals, and Sales message are clear. The main gap is that Q1 reserved capacity is not yet sized into specific follow-up work.
Output
Tidewell booking roadmap: Q4 2026–Q1 2027
For Dana Okafor, CPO; squad leads; Sales and Design
Direction
Prioritise fewer no-shows and lower multi-site churn, not a broader feature catalogue.
- No-shows average 11%. The 40 clinics sending their own reminders average 6%: promising evidence for reminders, but not proof of causation.
- Multi-site clinics represent 38% of ARR. Their monthly logo churn is 2.9%, versus 1.3% for single-site clinics. Of 31 multi-site exits, 23 cited the lack of an all-location view.
These findings support two primary investments: multi-site visibility and SMS reminders. Fixing calendar sync makes both more sustainable by reducing support demand.
Q4 2026: retain multi-site clinics and build the reminder foundation
| Squad | Roadmap allocation | Deliverable |
|---|---|---|
| --- | ---: | --- |
| A | Calendar sync fix — 5 squad-weeks | Ship first; address failures responsible for 38% of support tickets. |
| A | Messaging service — 5 of 8 squad-weeks | Begin provider integration, consent records and templates. Not a customer-facing launch. |
| B | Multi-site dashboard — 10 squad-weeks | Deliver bookings and utilisation across locations in one view. |
Total: 20 squad-weeks, matching available roadmap capacity. Messaging carries three weeks into Q1.
Pilot the dashboard with multi-site operators, including FitPhysio if they agree, before broad release. Design should prioritise cross-location workflows and dashboard usability rather than a booking-page refresh.
Calendar sync is a capacity investment as well as a reliability fix. Engineering forecasts three additional squad-weeks per quarter from Q1; we will verify that reduction rather than spend it in advance.
Q1 2027: launch reminders and prove outcomes
| Squad | Roadmap allocation | Deliverable |
|---|---|---|
| --- | ---: | --- |
| A | Finish messaging — 3 squad-weeks | Complete the prerequisite service. |
| A | SMS reminders with confirm/cancel — 6 squad-weeks | Pilot, then expand based on results and consent readiness. |
| A | 1 squad-week reserved | Launch hardening and fixes. |
| B | 10 squad-weeks reserved | Dashboard adoption and retention improvements, reminder rollout support, and evidence-led follow-up work. |
Committed feature build: nine squad-weeks; baseline capacity: 20. The remaining capacity is an explicit investment envelope, not an estimate for unspecified features. Squad leads will size follow-up work after dashboard feedback and reminder pilot results. Any recovered support capacity is additional headroom.
Do not fill this envelope with lower-priority commitments merely to reach full utilisation.
Success measures
- Reminders: compare no-show rates for pilot clinics with their baseline and a comparable holdout where practical. Track delivery, confirmations, cancellations and cancellation notice. Set rollout thresholds before launch; do not promise the observed 6% rate.
- Dashboard: track active multi-site usage, ability to complete cross-location tasks, and location-visibility complaints.
- Retention: monitor multi-site monthly logo churn against the 2.9% baseline. Expect adoption signals before a reliable churn verdict.
- Calendar sync: track sync-related tickets and actual support time recovered.
Not committed—and why
- Physitrack integration (8 weeks): not on the Christmas roadmap. FitPhysio’s documented must-have is the dashboard; Physitrack is a nice-to-have. Jordan and Product must promptly correct the promise, confirm the buying criteria with FitPhysio, and offer a dashboard-led evaluation. Do not replace an unsupported date with another.
- Booking page redesign (9 weeks): 64% conversion alone does not establish a problem, and none of 18 interviews raised it. Revisit with funnel evidence or usability findings.
- Deposits (14 weeks): the partner contract cannot be signed before mid-February 2027. Too large and dependency-constrained for a credible Q1 commitment.
- Waitlist auto-fill (7 weeks): today, cancellations with notice are rare. First establish whether reminders create enough recoverable slots. Consider Q1 only if evidence and remaining delivery time support it.
After Q1
Prioritise waitlist auto-fill if timely cancellations increase; otherwise improve reminder effectiveness and dashboard adoption. Reassess deposits after the contract and an operational/business case are ready. Reconsider Physitrack against verified demand and opportunity cost. No dates beyond Q1 until outcome evidence and estimates justify them.
Check by check
Got right · 11
- Uses the supplied evidence correctlyThe output’s current-situation facts, figures, customer statements, estimates, dates, and capacity numbers all come from the supplied context or follow directly from it.
- Addresses the actual decisionIt commits to a clear two-quarter roadmap and named deferrals, and states the evidence or conditions that would change later choices.
- Respects explicit constraintsIt is addressed to the named readers, stays under 800 words, covers Q4/Q1 and after, says what is not being done and why, and its allocations fit the stated capacity.
- Identifies material uncertaintyIt names material unknowns such as reminder causation, recovered support time, dashboard adoption, timely cancellations, and Physitrack demand, and says how they would be resolved.
- Avoids unsupported claimsInterpretations and forecasts are labelled as evidence, assumptions, or verification items rather than presented as established facts.
- Produces the required deliverableIt is a usable roadmap for the CPO, squad leads, Sales, and Design, with near-term commitments, success measures, deferrals, and post-Q1 direction.
- Every commitment serves the goalsEvery committed item serves no-show reduction, multi-site churn reduction, or capacity freed for those goals, and non-serving items are deferred with reasons.
- Handles the Sales promise with evidenceIt uses FitPhysio’s own must-have/nice-to-have notes to tell Sales to correct the Physitrack promise and lead with the dashboard.
- Outcomes, with certainty that falls with distanceItems are framed by outcomes, near-term work is specific, and later work is deliberately looser pending evidence.
- Fits the stated capacityThe committed work totals 29 squad-weeks against 40 available, with checkable quarter sums and explicit slack/reserved capacity.
- Sequences around dependenciesMessaging precedes reminders, deposits are deferred until after the contract, and the dashboard is committed before Physitrack is reconsidered.
Grades and run details
Decision model 100 · LLM judge 12 of 12 checks
Decision model checks
- passUses the supplied evidence correctly78%
- passAddresses the actual decision98%
- passRespects explicit constraints27%
- passIdentifies material uncertainty97%
- passAvoids unsupported claims55%
- passProduces the required deliverable68%
- passEvery commitment serves the goals96%
- passHandles the Sales promise with evidence100%
- passOutcomes, with certainty that falls with distance83%
- passFits the stated capacity70%
- passSequences around dependencies69%
Run
- Run
- #1
- API response time
- 40 s
- Submitted
- 30 Sept 2026