Failure patterns

Reframe it as a hypothesis · start againPresent matching friction as the hypothesis the research suggests, not a proven diagnosis, and stage the spending so the board learns before it commits the full £1.2m.

Reframe it as a hypothesis · substantial reworkPresent the cause of the 7-hour delay as a hypothesis, and measure where the time goes (queueing, triage, lookup, staffing) before designing around it.

Reframe it as a hypothesis · quick editFrame the range up front as illustrative full-capture scenarios, with actual capture still unmeasured, so it isn't read as a forecast.

Verify or remove the claim · start againRemove the 75% routing baseline and the 900,000 interaction pairs: neither is in the brief. Measure the baseline before setting targets against it.

Verify or remove the claim · targeted repairThe brief says training is on Friday, not 'next Friday'. Don't turn an ambiguous date into a blocker, or build an October schedule around it.

Verify or remove the claim · targeted repairTreat £1.2m as a funding ceiling, not a spending commitment. Assuming one-hour lessons, reaching 6,000 monthly bookings adds only £12k–18k in monthly commission revenue before costs. That target alone does not justify the investment. Cost the 90-day matching pilot first; release further funding only if incremental completed bookings, repeat behaviour and service costs support a credible path to covering the investment within our financing horizon. Assess that path against actual cash burn and remaining runway before scaling.

Redo the arithmetic · start againRead each step against the one before: 92% of trial starters do a first workout, and 40% of those reach three. That second drop is the leak. Add a test plan and success metrics.

Redo the arithmetic · targeted repairRecount without Call 4, which is about a failed tool switch, not close time. It's five of eight.

Redo the arithmetic · quick editDescribe 1.4pp as the lower end of the interval, not the largest possible loss, and qualify the one-day cost assumption.

Tighten the test · substantial reworkTest the reason the memo gives: whether agencies without a BD person can turn AI-sent cold email into deals. Demand for a different product doesn't settle that.

Tighten the test · targeted repairAn agent’s explicit “Approve and send” action authorises only the exact response displayed, including their edits. Regeneration or any subsequent change requires fresh approval. Enforce this in the send service and prevent duplicate sends on retries. If drafting fails, agents can compose and send manually. AI-generated drafts must use approved noncommittal refund wording; agents may add refund commitments under existing policy and explicitly approve the final response.

Tighten the test · quick editSay which tickets count towards the 90%, and how unavailable drafts and abstentions are reported, so the gate can't be met by drafting only the easy tickets. Say how the confidence intervals affect passing.

Restore the constraint · start againBuild the list of possible owners from who actually joined, not who was invited, and enforce it in code on generated owners, manual edits and sending. A model-set is_verified_attendee flag can't guarantee it.

Restore the constraint · targeted repairApply the roster check to organiser edits and the final send as well, not only to the model's output.

Restore the constraint · quick editCut the dashboard and the finance-approval step, and the confusing Cancel after saving. The brief asks only to capture, correct and save.

Surface the contradiction · substantial reworkFlag that a 21-day test can't have complete day-30 outcomes, and ask when the readout was produced before leaning on the retention figure.

Surface the contradiction · targeted repairAccount for the onboarding-to-trial step: 71% finish onboarding but 52% start the trial, so about a quarter stop at the card-up-front paywall. That bears directly on the team's paywall plan.

Surface the contradiction · quick editAsk how a 21-day test reports day-30 retention before relying on the figure.

Make the call · targeted repairGive Commercial something to plan around: say whether the four clean regions can go by 9 November, set a threshold for pausing a region, and give Scotland a Christmas fallback.

Make the call · targeted repairMake the argument rather than hedging it: the point estimate breaches the guardrail and most of the interval is past it. The refund question can be settled from the numbers given, so settle it.

Make the call · quick editAnswer Lena's question more directly: mobile's 5.2% drop with no navigation change points away from the navigation as the main cause. Tighten the SSO hedge.

Fix it · targeted repairThese assumptions produce an illustrative $4.5M–$10M envelope, not a validated revenue range. They assume customer adoption translates proportionally into invoice volume and the modelled payments route through Pay. Rebuild by segment: accessible invoice value × volume-weighted adoption × routing share × payment-method economics, excluding contracted volume.

Fix it · quick editInstrument alongside fix 1 rather than before it, and merge fixes 1 and 4, which both land the user on an auto-drawn chart.

Fix it · targeted repairWeigh the risk of a small activation loss, not only the one day of engineering, and say what result would justify the extra four weeks.

Fix the artefact · quick editMark fully booked days in the day picker, so patients don't have to tap each day to find out.

Fix the artefact · quick editFix the jump from a fully booked day: it suggests the wrong next available date. Everything else is ready to test.

Fix the artefact · quick editWord the warning as 'Please check this amount' rather than revealing the correct figure, or the review step tests nothing.