Usable with a quick edit9 of 11 checks passed
The output is well-structured and evidence-based; the only flaw is a missing explicit tie of Physitrack to the churn goal, which a PM could fix with a one-sentence edit without redoing any reasoning.
Output
Tidewell Booking: Roadmap, Q4 2026 to Q1 2027
For: Dana Okafor (CPO), Squad Leads · Shared with: Sales, Design
The short version
We have two goals: cut no-shows, and cut multi-site churn. The evidence points clearly to one fix for each.
- No-shows: Clinics that text patients the day before see 6% no-shows against 11% overall. SMS reminders are the fix.
- Multi-site churn: Multi-site clinics churn at 2.9% a month against 1.3% for single-site, and they are 38% of ARR. 23 of 31 who left cited "can't see all our locations in one place." The multi-site dashboard is the fix.
Everything else is either groundwork for these two, or waits.
Capacity
Each squad has 10 squad-weeks of roadmap work a quarter, so 20 in total. If the calendar sync fix ships in Q4, it frees about 3 squad-weeks from Q1 onward, giving roughly 23.
Q4 2026 (20 of 20 squad-weeks)
| Squad | Work | Weeks | Why |
|---|---|---|---|
| A | Multi-site dashboard | 10 | Goal 2. Top exit reason. FitPhysio's must-have. |
| B | Calendar sync fix | 5 | 38% of support tickets. Frees about 3 weeks a quarter from Q1. |
| B | Messaging service (part 1) | 5 | Foundation for reminders. |
Risk: The dashboard takes all of Squad A's quarter, so it lands late December. Any slip pushes it into January. We will cut scope before we miss the date, for example by shipping bookings first and utilisation second.
Q1 2027 (17 of about 23 squad-weeks)
| Squad | Work | Weeks | Why |
|---|---|---|---|
| B | Messaging service (part 2) | 3 | Finishes the foundation. |
| B | SMS reminders with confirm/cancel | 6 | Goal 1. Target launch mid-March. |
| A | Physitrack integration | 8 | Commitment to FitPhysio (see below). |
| Buffer | ~6 | These are first estimates on new work. Covers slippage, then early waitlist work. |
What success looks like
- No-shows: Clinics using reminders move toward the 6% seen by self-texting clinics. We'll measure from launch.
- Multi-site churn: Monthly churn falls from 2.9% toward the single-site rate. Exit-survey mentions of "one place" drop.
- Support load: Calendar sync tickets fall by most of their current 38% share.
FitPhysio and Physitrack: a date change is needed
Jordan told FitPhysio that Physitrack would be live by Christmas. We can't deliver that without dropping either the dashboard or reminders, and those are the CEO's two goals.
FitPhysio's own evaluation notes list the dashboard as their must-have and Physitrack as nice-to-have. The plan above gives them the thing they said they need by year-end, with Physitrack following in Q1.
Ask for Jordan: Please reset the Physitrack date with FitPhysio to Q1 2027, leading with the dashboard landing in December. I'm happy to join that call.
Going forward, please check dates with product before they go to customers. That way Sales can commit with confidence.
What we're not doing, and why
Booking page redesign (9 weeks): not planned. - 64% of visits already end in a booking. - Across 18 customer interviews this quarter, nobody raised it. - It doesn't serve either goal.
Design: we'd value your help on the dashboard and on the reminder messages patients receive. Those are where design effort changes outcomes this half. We'll revisit the redesign if conversion drops or customers start asking for it.
Waitlist auto-fill (7 weeks): after Q1. - It only fills slots cancelled with notice, and today patients rarely cancel. They just don't turn up. - Reminders with a cancel button should change that. Once reminders are live, waitlist becomes worth building. It is first in line for the Q1 buffer or for Q2.
Deposits at booking (14 weeks): not before Q2, and not yet committed. - The payments contract can't be signed before mid-February 2027, so building can't start this half. - It also adds friction for patients. We'll decide after we see what reminders do to no-shows. If reminders get us close to 6%, deposits may not be needed.
After Q1 2027 (indicative)
- Waitlist auto-fill: Builds on reminders and the messaging service.
- Deposits decision: Based on reminder results and the signed contract.
- Multi-site follow-ons: Based on dashboard usage and churn data, such as cross-site reporting and permissions.
- Booking page: Only if the data changes.
Decisions needed
- Dana: Approve the plan, and the Physitrack date reset with FitPhysio.
- Jordan: Own the FitPhysio conversation this week.
- Squad leads: Confirm estimates, and the dashboard scope-cut plan in case of slippage.
Check by check
Got wrong · 1
- Every commitment serves the goalsPhysitrack integration is committed in Q1 but is not tied to either CEO goal (no-shows or multi-site churn) or to freeing capacity, and the criterion requires such items to be deferred with a reason.
Mixed · 1
- Fits the stated capacityCommitted work sums to 37 squad-weeks (20 in Q4, 17 in Q1) against 40-43 available, with a buffer, and it names what was cut or deferred.The two graders disagreed on this one.
Got right · 9
- Uses the supplied evidence correctlyEvery statement about the current situation is directly from the brief or follows from arithmetic, with no invented facts.
- Addresses the actual decisionThe output commits to a clear two-quarter plan, addresses the Physitrack promise, and says what is not being done and why, framed for the named readers.
- Respects explicit constraintsThe output is under 800 words, addresses the required readers, and says what is not being done and why, respecting all stated constraints.
- Identifies material uncertaintyIt names risks (dashboard slip, estimate uncertainty), uses a buffer, and ties later decisions (deposits, waitlist, booking page) to results from earlier work.
- Avoids unsupported claimsForecasts and interpretations are clearly labeled as such (e.g., 'should change that'), and no unsupported facts are presented as established.
- Produces the required deliverableThe roadmap is complete, in the right form, under 800 words, and usable by Dana, squad leads, Sales, and Design with minimal edits.
- Handles the Sales promise with evidenceIt uses FitPhysio's own notes to show the dashboard is the must-have, gives Sales a clear line to reset the Physitrack date to Q1, and asks Jordan to own the conversation.
- Outcomes, with certainty that falls with distanceEvery item names its outcome or problem, near-term items are specific, and later items (after Q1) are deliberately looser and indicative.
- Sequences around dependenciesMessaging service is built before SMS reminders, calendar sync fix precedes the freed capacity, deposits are not in the half, and waitlist is after reminders.
Grades and run details
Decision model 77 · LLM judge 11 of 12 checks
Decision model checks
- passUses the supplied evidence correctly55%
- passAddresses the actual decision92%
- partialRespects explicit constraints13%
- passIdentifies material uncertainty79%
- partialAvoids unsupported claims46%
- passProduces the required deliverable64%
- partialEvery commitment serves the goals59%
- passHandles the Sales promise with evidence99%
- passOutcomes, with certainty that falls with distance85%
- failFits the stated capacity18%
- passSequences around dependencies68%
Run
- Run
- #1
- Time to output
- 47 s
- Submitted
- 30 Sept 2026