Humanity’s Last PRD
Latest drop: Gemini 3.8 Flash · 1 Oct
Tasks / Define

Build a roadmap

Can the model sequence bets against capacity and dependencies, and explain the order?

Measures the modelTask v1.0 · 2 casesDifficulty

What AI gets right here, and what you’ll still have to catch

From 14 graded outputs by 7 models. 36% were usable with at most a quick edit.

Reliably right

  1. Outcomes, with certainty that falls with distance95% pass
    Every item names the outcome or problem it serves; near-term items have specific targets (mid-December, January) while later items are looser (trigger-based, contract-dependent).
    Sonnet 5.5 · API · Two squads, eight asks, one half
  2. Sequences around dependencies89% pass
    Messaging service is built before SMS reminders and waitlist auto-fill, reminders before waitlist, and deposits are placed after the contract can be signed; the key dependencies are named.
    Sonnet 5.5 · API · Two squads, eight asks, one half
  3. Plans on the squads we actually have89% pass
    It explicitly excludes the two new squads from committed critical-path work and treats their capacity as upside after observed ramp.
    GPT-6 Astra · ChatGPT · A year of spend management, with a hard deadline

Where it slips

  1. Makes the call on procurement50% pass
    It correctly challenges the $6M claim but proposes only time-bounded validation without a threshold that would justify the full procurement build.
    GPT-6 Luna · API · A year of spend management, with a hard deadline
  2. Produces the required deliverable50% pass
    The roadmap and case are present, but the case is too long and the roadmap has capacity conflicts that would require major rework.
    GPT-6.1 Sol · API · A year of spend management, with a hard deadline
  3. Uses the supplied evidence correctly61% pass
    Most numbers and quotes are correct, but the output presents 'undermines booking reliability' as a current fact when the supplied context only says calendar sync failures cause 38% of support tickets.
    GPT-6 Astra · ChatGPT · Two squads, eight asks, one half

Case viewer

Read the brief, then put up to three outputs side by side, each with the LLM judge’s verdict on every check. Highlights mark what a PM had to fix.

The brief

You're the PM for Tidewell's booking product. Write the roadmap for the next two quarters (Q4 2026 and Q1 2027) and what comes after, for Dana Okafor, our CPO, and the two squad leads. It will also be shared with Sales and Design, so it needs to say what we're not doing and why. Keep it under 800 words. Everything we know is below.

What the model was given7 items: About Tidewell, Goals for the next two quarters (set by the CEO), Data, Capacity, Candidate work (estimates in squad-weeks, from the squad leads), Sales note, FitPhysio's evaluation notes (shared by their operations director)
About TidewellOnline booking and scheduling for independent physiotherapy clinics. 1,450 clinics, $3.9M ARR.
Goals for the next two quarters (set by the CEO)1. Cut no-shows for our clinics: it's the main thing we promise them. 2. Cut churn among multi-site clinics.
DataNo-shows average 11% of appointments across all clinics. The 40 clinics that text their own patients a reminder the day before average 6%. Multi-site clinics are 16% of clinics and 38% of ARR; their monthly logo churn is 2.9%, against 1.3% for single-site clinics. In exit surveys, 23 of the 31 multi-site clinics that left in the last year cited 'can't see all our locations in one place'. Booking page: 64% of visits end in a booking. In 18 customer interviews this quarter, nobody mentioned the booking page.
CapacityTwo squads. Each has 13 weeks a quarter, but about a quarter of each squad's time goes on support and bugs, so we plan on 10 squad-weeks of roadmap work per squad per quarter.
Candidate work (estimates in squad-weeks, from the squad leads)1. Calendar sync fix, 5. Calendar sync failures cause 38% of support tickets; engineering expects fixing them to free about 3 squad-weeks a quarter of support time, starting the quarter after it ships. 2. Messaging service (SMS provider, patient consent records, templates), 8. Nothing patient-facing on its own. 3. SMS reminders with confirm or cancel, 6. Needs the messaging service. 4. Multi-site dashboard (every location's bookings and utilisation in one view), 10. 5. Waitlist auto-fill: texts waitlisted patients when a slot frees up, 7. Needs the messaging service. It only fills slots cancelled with some notice, which is rare today: patients don't cancel, they just don't turn up. 6. Deposits at booking, 14. Needs a payments partner contract; Legal says the earliest it can be signed is mid-February 2027. 7. Booking page redesign, 9. Requested by the Head of Design. 8. Physitrack integration (sends patients' exercise plans to the Physitrack app), 8. See the Sales note.
Sales noteFrom Jordan, Head of Sales: “FitPhysio Group (30 sites, $64,800 ARR) is our biggest deal this year. I told them Physitrack would be live by Christmas. It's what closes the deal.”
FitPhysio's evaluation notes (shared by their operations director)“Must have: see all 30 sites' bookings and utilisation in one place. Nice to have: Physitrack integration.”
What a strong answer doesThe answer key the graders mark against

A two-quarter roadmap that fits about 40 squad-weeks (10 per squad per quarter), with items framed as the outcome they serve. Puts the calendar sync fix first because it frees capacity for Q1, builds the messaging service before reminders and the waitlist, and sequences reminders before the waitlist since slots only free up once patients can cancel. Commits the multi-site dashboard in the half: it serves the churn goal and is FitPhysio's own must-have, so it tells Sales to lead with the dashboard rather than promising Physitrack by Christmas. Leaves deposits for after the contract (it can't be built in the half once signing is mid-February) and doesn't commit the booking page redesign without evidence. A committed plan of about 36 squad-weeks (sync 5, messaging 8, dashboard 10, reminders 6, waitlist 7) leaves a little slack; Physitrack only fits if something else goes. Near-term items are specific, later ones looser, and it names what's not being done and why.

Critical failures (cap the score at 40)
  • Schedules an item before something it depends on: SMS reminders or waitlist auto-fill before the messaging service, or deposits shipping in the half
  • Commits clearly more than about 40 squad-weeks of work to the two quarters
Case

Mid-level · v1.1 · synthetic · B2B SaaS, healthcare, capacity, sales promise

The outputs

7 setups answered this brief. Pick up to three to read side by side.

Sonnet 5.5API100Usable with a quick editGPT-6.1 SolAPI100Usable with a quick editOpus 5.5Claude88Usable with a quick editGPT-6 AstraChatGPT83Needs more workGPT-6 LunaAPI83Needs more workGemini 3.8 FlashAPI63Needs more workGemini 3.5 Flash-LiteGemini23Critical failure
Gemini 3.5 Flash-LiteGemini
Critical failure: Commits clearly more than about 40 squad-weeks of work to the two quarters. Score capped at 40.

Needs more than a quick edit2 of 11 checks passed

A PM would need to rework the capacity math and decide whether Physitrack is committed or deferred. The evidence and sequencing reasoning also need correction before it can be used.

Output

To: Dana Okafor (CPO), Squad Leads, Sales, Design From: PM, Tidewell Booking Subject: Booking Product Roadmap: Q4 2026 – Q1 2027 & Beyond

At $3.9M ARR across 1,450 independent physio clinics, our immediate focus is clear: ruthlessly align our capacity with the CEO's goals of cutting no-shows and reducing multi-site churn.

With two squads and 10 productive weeks per squad-quarter (20 total squad-weeks per quarter), here is our execution plan.

---

Q4 2026: Foundation & The Multi-Site Anchor

Goal Alignment: Multi-site churn, Support capacity.

  • Multi-Site Dashboard (10 squad-weeks – Squad A): A single view of every location’s bookings and utilization.
  • Why: Multi-site clinics drive 38% of our ARR ($1.48M) but churn at 2.9% (vs. 1.3% single-site). "Can't see all locations in one place" was cited in 74% of multi-site exit surveys. This is also the explicit "Must Have" for FitPhysio Group (30 sites, $64.8K ARR).
  • Messaging Service (8 squad-weeks – Squad B): Infrastructure for SMS provider, consent, and templates.
  • Why: Prerequisite for our Q1 no-show reduction engine.
  • Calendar Sync Fix (5 squad-weeks – Squad B, spilling into Q1): Resolving sync failures that drive 38% of support tickets.
  • Why: Engineering estimates this will permanently reclaim ~3 squad-weeks/quarter of engineering time starting Q1.

---

Q1 2027: Solving No-Shows

Goal Alignment: No-show reduction.

  • Calendar Sync Fix completion (0 extra weeks, Squad B finishing up).
  • SMS Reminders with Confirm/Cancel (6 squad-weeks – Squad B): Leveraging the Q4 Messaging Service.
  • Why: Our data proves this works: clinics manually texting reminders drop no-shows from 11% to 6%. Automated confirm/cancel turns passive ghosting into active rescheduling, opening slots early.
  • Physitrack Integration (8 squad-weeks – Squad A): Sends exercise plans directly to the Physitrack app.
  • Why: Sales commitment to close FitPhysio Group by Christmas. (Note: While FitPhysio listed this as "nice-to-have" vs. the dashboard's "must-have," it is a commercial blocker per Sales).
  • Waitlist Auto-Fill (7 squad-weeks – Squad A, utilizing reclaimed support capacity): Texts waitlisted patients when slots free up.
  • Why: Directly targets no-shows, but depends on SMS reminders and cancellations working first.

---

What Comes After (Q2 2027 & Beyond)

  • Deposits at Booking (14 squad-weeks): Paused until Legal secures the payments partner contract (earliest mid-February 2027). This will be our primary Q2/Q3 bet to further crush no-shows once infrastructure is live.

---

What We Are NOT Doing & Why

1. Booking Page Redesign (9 squad-weeks): * Why Not: 64% of visits already convert to bookings, and 18 customer interviews this quarter yielded zero mentions of the booking page. Spending design capacity here is a distraction from our retention and no-show crises. 2. Deposits in Q4/Q1: * Why Not: Blocked by external legal/contract timelines until mid-Q1 at best. 3. Prioritizing Physitrack over Multi-Site in Q4: * Why Not: While Sales needs Physitrack for FitPhysio, FitPhysio’s actual operational blocker is the Multi-Site Dashboard. Building the dashboard first secures our largest pipeline deal and addresses the core churn driver for our highest-value segment.

Claims the judge couldn’t find in the brief

  • Fixing calendar sync will permanently reclaim about 3 squad-weeks per quarter of engineering time starting Q1.
  • Clinics manually texting reminders drop no-shows from 11% to 6%.

Grades and run details

Decision model 32 · LLM judge 2 of 12 checks
Decision model checks
  • failUses the supplied evidence correctly13%
  • partialAddresses the actual decision30%
  • failRespects explicit constraints44%
  • failIdentifies material uncertainty25%
  • partialAvoids unsupported claims43%
  • failProduces the required deliverable27%
  • partialEvery commitment serves the goals44%
  • failHandles the Sales promise with evidence23%
  • passOutcomes, with certainty that falls with distance34%
  • failFits the stated capacity57%
  • passSequences around dependencies38%
Run
Run
#1
Time to output
4 s
Submitted
1 Oct 2026
GPT-6 AstraChatGPT

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

SquadCommitted workSquad-weeks
---------:
AShip multi-site dashboard: bookings and utilisation across locations10
BShip calendar sync fix5
BBegin messaging service: provider, consent records and templates5 of 8
Total20 / 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

SquadPlanned workSquad-weeks
---------:
BComplete messaging service3
BBuild and roll out SMS reminders with confirm/cancel6
ADashboard adoption, measured follow-up improvements and outcome evaluationUp to 10
BReminder rollout contingency1
Total baseline allocation20 / 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
GPT-6 LunaAPI

Needs more than a quick edit9 of 11 checks passed

A PM could use most of it, but the Q1 calendar sync placement undermines the capacity logic and would need resequencing before it is fully decision-ready.

Output

Tidewell Booking Roadmap | Q4 2026–Q1 2027

For: Dana Okafor, CPO; squad leads; Sales and Design North star: Reduce clinic no-shows and multi-site churn. We have 20 roadmap squad-weeks per quarter across two squads; support and bugs are planned separately.

Q4 2026 — Build the multi-site view and messaging foundation

  • Multi-site dashboard — 10 squad-weeks. Show bookings and utilisation across every location in one view. This directly addresses the most-cited multi-site exit reason (23 of 31 surveyed departures) and FitPhysio’s stated must-have.
  • Messaging service — 8 squad-weeks. Build the SMS provider, patient consent records and templates needed for reminders. This is foundational work, not a patient-facing launch; reminders follow in Q1.

Capacity: One squad takes the dashboard; the other builds messaging, with two squad-weeks uncommitted.

Sales: Jordan’s Christmas commitment for Physitrack is not in this roadmap. FitPhysio called it “nice to have,” while the multi-site view is a must-have. Please correct the commitment with FitPhysio now; do not sell a Christmas delivery date.

Q1 2027 — Launch reminders and fix calendar sync

  • SMS reminders with confirm/cancel — 6 squad-weeks. Launch using the Q4 messaging foundation, with rollout and measurement. Forty clinics that send their own day-before texts average 6% no-shows versus 11% overall. That’s a promising signal, not proof of causation; measure results against a comparison group and track cancellations as well as no-shows.
  • Calendar sync fix — 5 squad-weeks. Address a cause of 38% of support tickets. Engineering expects it to free about three squad-weeks of support time per quarter, starting Q2.

The remaining Q1 roadmap capacity is reserved for rollout learning and iteration rather than adding another large commitment.

Success measures: No-show rate for reminder-enabled appointments versus comparison; reminder delivery, confirmations and cancellations; dashboard adoption across multi-site locations; and multi-site support and churn trends.

After Q1 — Reassess before committing

  • Waitlist auto-fill: Revisit once reminders give patients a way to cancel and we know whether cancellations happen with enough notice. Today, patients mostly don’t cancel, so auto-fill has few openings to act on.
  • Deposits: Reassess after the payments contract can be signed (earliest mid-February) and we have evidence on reminder impact and clinic appetite. The 14-week estimate and partner dependency make it unsuitable for this committed plan.
  • Physitrack: Reassess against customer evidence and capacity; it is not committed for Q4 or Q1.
  • Booking page redesign: Revisit if research identifies a meaningful problem. Booking-page conversion is 64%, and nobody in 18 recent interviews raised it; it is not the best use of capacity against current goals.

Explicitly not doing now

We are not building the booking redesign, waitlist auto-fill, deposits or Physitrack in these two quarters. This is a focus decision: prioritize the evidenced churn driver and test the clearest no-show intervention before investing in lower-evidence or dependency-heavy work.

Grades and run details

Decision model 91 · LLM judge 10 of 12 checks
Decision model checks
  • passUses the supplied evidence correctly27%
  • passAddresses the actual decision81%
  • failRespects explicit constraints11%
  • passIdentifies material uncertainty80%
  • passAvoids unsupported claims53%
  • passProduces the required deliverable15%
  • passEvery commitment serves the goals91%
  • passHandles the Sales promise with evidence100%
  • passOutcomes, with certainty that falls with distance85%
  • passFits the stated capacity32%
  • passSequences around dependencies81%
Run
Run
#1
API response time
31 s
Submitted
1 Oct 2026

Check by check

Where the outputs differ comes first. Open a check to read the judge’s reasons. “Mixed” means the two graders disagreed.

Where they differ 9

Uses the supplied evidence correctlyWrongMixedRight
Gemini 3.5 Flash-Lite · Gemini

It treats correlation as causation for SMS reminders and adds unsupported 'permanently reclaim' language about calendar sync capacity.

GPT-6 Astra · ChatGPT

Most numbers and quotes are correct, but the output presents 'undermines booking reliability' as a current fact when the supplied context only says calendar sync failures cause 38% of support tickets.

GPT-6 Luna · API

The output uses the supplied numbers, dates, customer statements, and capacity facts correctly, and its few inferences follow from the context.

Addresses the actual decisionWrongRightRight
Gemini 3.5 Flash-Lite · Gemini

It commits to a roadmap but does not clearly state what condition would change the answer, especially around the Physitrack commitment and capacity trade-off.

GPT-6 Astra · ChatGPT

It commits early to prioritising no-show reduction and multi-site retention, with a clear two-quarter plan and explicit deferrals, and states conditions that would change later choices.

GPT-6 Luna · API

It commits to a clear two-quarter roadmap for the named readers and states conditions that would change later decisions, though it could be stronger on what would change the committed plan itself.

Respects explicit constraintsWrongRightMixed
Gemini 3.5 Flash-Lite · Gemini

It violates the stated capacity constraint by committing 44 squad-weeks to two quarters despite saying capacity is 40.

GPT-6 Astra · ChatGPT

It is addressed to the named readers, stays under 800 words, includes what is not being done and why, and respects the capacity and dependency constraints in its proposed plan.

GPT-6 Luna · API

It is under 800 words, addressed to the named readers, includes what is not being done and why, and respects the stated capacity and dependencies.

Identifies material uncertaintyWrongRightRight
Gemini 3.5 Flash-Lite · Gemini

It does not name the material unknowns that could change the roadmap, such as whether FitPhysio will accept the dashboard or whether reclaimed support capacity will materialise.

GPT-6 Astra · ChatGPT

It names material unknowns such as whether reminders cause the 6% result, whether calendar savings materialise, dashboard adoption, churn attribution, and FitPhysio's buying criteria, and says how they would be checked.

GPT-6 Luna · API

It names material unknowns such as reminder causation, cancellation notice, contract timing, and booking-page evidence, and says how they would be resolved.

Avoids unsupported claimsWrongMixedRight
Gemini 3.5 Flash-Lite · Gemini

It presents unestablished causal and capacity claims as fact, including that texting 'drops' no-shows and that sync fixes 'permanently' reclaim engineering time.

GPT-6 Astra · ChatGPT

It labels many hypotheses carefully, but still asserts that calendar sync failures undermine booking reliability without supplied evidence.

GPT-6 Luna · API

It labels the 6% versus 11% signal as not proof of causation and frames later items as reassessments rather than committed facts.

Produces the required deliverableWrongRightRight
Gemini 3.5 Flash-Lite · Gemini

Although it is a roadmap memo under 800 words, it is not usable as-is because the plan exceeds capacity and leaves the Physitrack trade-off unresolved.

GPT-6 Astra · ChatGPT

The roadmap is present for Q4 2026, Q1 2027, and after, with squad-week tables, deferrals, and measurement notes that the CPO and squad leads could act on.

GPT-6 Luna · API

It is a usable roadmap for the CPO, squad leads, Sales, and Design, with committed work, deferred work, success measures, and a sales message.

Every commitment serves the goalsWrongRightMixed
Gemini 3.5 Flash-Lite · Gemini

Physitrack is committed on its own without being tied to the two CEO goals or to freeing capacity, and the dashboard is not clearly positioned as the substitute for the Sales promise.

GPT-6 Astra · ChatGPT

Committed items serve no-show reduction, multi-site churn, or capacity release; Physitrack, waitlist, deposits, and booking redesign are deferred with reasons.

GPT-6 Luna · API

The calendar sync fix is committed in Q1 but only frees support capacity starting Q2, so it does not serve the two-quarter goals or free capacity within the half as required.

Handles the Sales promise with evidenceWrongRightRight
Gemini 3.5 Flash-Lite · Gemini

It notes FitPhysio's must-have is the dashboard but does not give Sales a clear line on Physitrack, such as later or only if something else is cut.

GPT-6 Astra · ChatGPT

It uses FitPhysio's own must-have/nice-to-have notes, commits the dashboard, and tells Sales to correct the Christmas Physitrack promise rather than hide extra work.

GPT-6 Luna · API

It uses FitPhysio's own must-have/nice-to-have notes to tell Sales to correct the Christmas Physitrack promise and lead with the committed dashboard.

Fits the stated capacityWrongRightRight
Gemini 3.5 Flash-Lite · Gemini

The committed items sum to 44 squad-weeks against 40 available, and the claimed reclaimed capacity does not make the plan fit.

GPT-6 Astra · ChatGPT

The quarter tables sum to 20 squad-weeks each, the known committed work is within capacity, and it names deferred items and uncommitted slack.

GPT-6 Luna · API

The committed work totals 29 squad-weeks against 40 available, with explicit slack and deferrals to make it fit.

All got right 2

Outcomes, with certainty that falls with distanceRightRightRight
Gemini 3.5 Flash-Lite · Gemini

Each item names an outcome or problem, and later items are looser than near-term items.

GPT-6 Astra · ChatGPT

Items are framed by outcomes, near-term work is specific, and later work is deliberately looser and conditional.

GPT-6 Luna · API

Each item names the problem or outcome it serves, and later items are deliberately looser than near-term commitments.

Sequences around dependenciesRightRightRight
Gemini 3.5 Flash-Lite · Gemini

Messaging is scheduled before SMS reminders and waitlist, and deposits are deferred until after the contract date.

GPT-6 Astra · ChatGPT

Messaging is sequenced before reminders, waitlist is deferred until reminders create cancellations, deposits are deferred past the contract date, and Physitrack is not committed.

GPT-6 Luna · API

It places reminders after the messaging service, defers waitlist until reminders create cancellations, and defers deposits until the contract can be signed.

Results

Every setup we’ve tested on this task, across all cases and repeats, graded on the current checklist. Calibrated: the graders match our PM on 89% of checks.

#Model · HarnessTask scoreDecision modelLLM judgeRunsCritical failures
1Sonnet 5.5API89.6100.02None
2GPT-6 AstraChatGPT91.787.52None
3GPT-6.1 SolAPI91.784.62None
4GPT-6 LunaAPI85.076.32None
5Opus 5.5Claude80.565.12None
6Gemini 3.8 FlashAPI70.151.92None
7Gemini 3.5 Flash-LiteGemini28.48.322 capped

The PM job

Turning strategy into a sequenced plan.

Why it matters

A roadmap is where strategy meets capacity. Dated feature lists turn guesses into promises.

What good looks like

  • Items are problems or outcomes, not just features
  • Sequencing reflects dependencies
  • Explicit trade-offs
  • Commitment falls with distance

Deliberately not measured

  • Gantt formatting
Capability tested

Sequencing under constraints

The failure we’re looking for

A dated wishlist sorted by excitement

Grading

Decision model and LLM judge, calibrated against a blind PM review