A new CRO at a 45,000-person building services company builds her 90-day plan for the CEO, checking her predecessor's story against the data, with any AI chat her company allows.
A welcome email from the CEO that already contains the explanation, three lines from her predecessor's deck, and four short notes from sales ops, customer success, HR and finance. The story is tidy. The data underneath it is not.
Here the AI helps you plan when someone has already explained the problem. The prompt tells it to treat that explanation as claims to check.
Use the AI tool your company approves: ChatGPT, Claude, Gemini or Copilot.
Copy the prompt and the five fictional inputs from the appendix into one message.
Put the CEO's announcement date next to the payroll deadline. Then decide which first moves the CEO needs to see.
I've just joined an industrial building services company as Chief Revenue Officer. The sales organisation has missed plan two years running, and the CEO wants my 90-day plan by Friday, January 22. I started on Monday, January 11, and today is Wednesday, January 13. Our fiscal year runs April to March. Below are the CEO's email, my predecessor's turnaround deck, and notes from sales operations, customer success, HR and finance.
Please give me:
Treat everything my predecessor wrote as a claim to check, not a fact, and give the evidence for every first move. Don't swap one unsupported explanation for another. Check the arithmetic and the dates. Don't add facts that aren't in the inputs; if you assume something, say so.
Exactly as it came back, not edited. Read it the way Amara did: check each point against the source it cites.
Assumption about the year: the inputs don't state one. Kevin's deck is dated September 2026 and FY28 starts April 1, so I've taken "now" to be January 2027. On that basis every date in the inputs falls on the weekday given: Mon Jan 11, Wed Jan 13, Fri Jan 22, Fri Feb 26, Mon Mar 15, Wed Mar 31, Thu Apr 1. Counting Jan 11 as day 1, day 30 is Tue Feb 9 and day 90 is Sat Apr 10.
| Claim (source) | What the data shows | Verdict |
|---|---|---|
| "Pipeline is fine at $2.4B, three times the $800M target" (CEO [1], deck [2]) | The total of $2.4B is correct, and $2.4B is 3.0 times $800M. But $520M is stale (older than 18 months, no activity in 6 months) and $310M is duplicated renewals. Sales ops says the two don't overlap [3]. Removing both takes out $830M, 34.6%, which leaves $1.57B, or 1.96 times $800M. | Doesn't hold. Coverage is about 2x on the export's own numbers, not 3x. found |
| Same pipeline counted toward FY28 | The export is "total open pipeline". It doesn't say how much is due to close in FY27 Q4 (January to March), which is "usually our biggest bookings quarter" [5]. Whatever closes before March 31 counts toward FY27, not FY28. It also doesn't say whether the $800M includes renewals, which make up part of the pipeline. | Unknown. FY28 coverage could be below 1.96x. |
| "Pipeline is healthy, so this is execution" (CEO [1]) | This conclusion rests on the 3x figure, which doesn't hold. | Doesn't hold as reasoned. Execution may still be part of the problem, but the data doesn't show it. found |
| "Service contract churn is up" (deck [2]) | FY26 was 6.1% over 12 months. FY27 to date is 412 of 5,150, which is 8.0% (checked), over 9 months. FY27 has already passed the whole of FY26 with a quarter still to go. Caveat: I don't know whether 5,150 means contracts due for renewal or the whole contract base, or whether FY26 used the same base. | Holds, provided both years use the same denominator (customer success to confirm). found |
| "…because of SightLine product issues" (deck [2], CEO [1]) | SightLine is the reason in 21 of 160 recorded exits (13.1%) and 21 of 412 non-renewals overall (5.1%). The recorded reasons are price 61 (38%), response time 48 (30%), competitor bundle 30 (19%) and SightLine 21 (13%). Those add up to 160. 252 of 412 (61%) have no reason recorded. | Doesn't hold on recorded data. Price isn't proven to be the cause either: 61% of exits have no reason, so the cause is unknown. found |
| "Sales attrition has stabilised at 12%" (deck [2]) | 12% was the FY26 figure. In FY27 to date, 58 of 310 sellers have left, which is 18.7% in 9 months. The base isn't defined (start, average or current headcount), but 58 leavers would only be 12% of a base of 483 or more, far above 310. | Doesn't hold. Attrition is higher than FY26, and the year isn't over. found |
Other things I noticed:
Items 1 to 3 are ordered by deadline: they feed the February 26 comp deadline and protect Q4.
What FY28 coverage really is.
The Feb 26 comp and quota deadline: what's already in motion.
What Q4 bookings need to be protected. found
Why sellers are leaving.
Why customers aren't renewing.
Who owns renewals in the CRM.
| Date | Decision | Checked against |
|---|---|---|
| Fri Feb 12 (day 33) | What scope of territory change for FY28: full redesign, targeted changes (for example, vacant territories), or current territories with clean data. | Has to come two weeks before Feb 26 so finance can set quotas by territory. A full redesign may not be possible in this window. A: decide the default |
| By Fri Feb 19 (day 40) | Whether $800M stays as the FY28 target, based on the cleaned FY28 coverage from item 1. This is a decision for me, the CEO and the CFO. | Quotas are set from the target, so this has to come before Feb 26. |
| Fri Feb 26 (day 47) | Final FY28 comp plan and quotas by territory [5]. | A fixed payroll deadline. This is the real territory deadline, not March 15. found |
| Early to mid-March (date to be set with HR) | When and how sellers hear their FY28 territory and quota. This needs care with Q4 deals in flight, for example deciding who gets credit for deals that change hands. | Territories must be set by Feb 26 anyway. Announcing during the biggest quarter, with attrition already at 18.7%, carries a risk (my judgment, not a finding) of distraction or more departures. Seller notice periods are unknown: confirm with HR. |
| By Wed Mar 31 (day 80) | Pipeline rules live for FY28: stale-deal rules and single ownership of renewals. | Stops the FY28 pipeline starting with the same $830M problem. |
| By Wed Mar 31 | First churn actions, only where the reasons now known support them. They may involve service response time, pricing or product, and each needs its owner's agreement. | Depends on item 5. If reasons are still missing for most exits, the decision is to keep investigating, not to act. |
| Thu Apr 1 (day 81) | FY28 starts. | |
| Fri Apr 9 (day 89, the last working day before day 90) | Review with the CEO: FY27 actual against forecast, FY28 coverage, churn reasons and attrition trend. | Day 90 is Saturday Apr 10. |
Subject: 90-day plan: outline and one change to the timing
Daniel,
Thank you for the welcome. You'll have the full plan by Friday, January 22. Here is the shape of it, plus one change I'd like to make to your request.
What I've found so far, from the January exports: - Pipeline: $520M is stale and $310M is duplicated renewals. Excluding both leaves $1.57B, about 2x the $800M target, not 3x. Some of that will close this quarter and count toward FY27, so FY28 coverage may be lower still. Sales ops and I are confirming the cleaned figure by early February. - Churn: it is up, from 6.1% in FY26 to 8.0% in the first nine months of FY27 (confirming the bases match). SightLine is the reason in 21 of the 160 exits with a recorded reason, but 252 of 412 have no reason at all. I won't name a cause until we have one. - Seller attrition: 58 of 310 sellers have left since April, 18.7%, against 12% last year. It hasn't stabilised.
The change I'd suggest: the FY28 comp plan, including quotas by territory, has to be final by Friday, February 26 for payroll. That means territories have to be decided by then, not announced on March 15. I'd decide the scope of territory change by February 12, set quotas by February 26, and agree with HR when sellers hear, in a way that protects Q4 deals.
One question for you and finance: if cleaned coverage confirms about 2x, I'd like to review the $800M with you before quotas lock on February 26. B: show, don't ask
Days 1 to 30: clean the pipeline, protect Q4, understand seller departures and the unexplained churn, and fix renewal ownership in the CRM.
Amara
Arithmetic I checked:
What I didn't do: I didn't annualise churn or attrition. Renewal and departure timing within a year isn't given, so a full-year projection would be an assumption.
Claude found every planted problem and refused to swap one explanation for another. Amara's edits are about what a new CRO commits to, what she asks for in week one, and what the CEO needs to see.
Use it whenever you step into a role and an explanation of the problem is already waiting for you: a new region, a turnaround, an acquired business, a function that missed its goals.
I've just joined [the company or function] as [your role]. [What went wrong], and [who] wants my [length]-day plan by [date]. I started on [date], and today is [date]. Below are [their brief, my predecessor's material, and the data and deadlines].
Please give me: 1. What I've inherited: each claim, with what the data shows: holds, doesn't hold, or unknown. 2. Days 1 to 30: what I need to find out first, with the evidence that makes each item a priority. 3. Days 31 to [end]: the decisions and their dates, checked against [the deadlines]. 4. What I won't commit to yet, and what would let me. 5. A short note to [who] covering the plan and anything in their request I'd change.
Treat everything my predecessor wrote as a claim to check, not a fact, and give the evidence for every first move. Don't swap one unsupported explanation for another. Check the arithmetic and the dates. Don't add facts that aren't in the inputs; if you assume something, say so.
Copy the prompt, then all five inputs, into one message in a new chat. Everything here is fictional and safe to paste.
I've just joined an industrial building services company as Chief Revenue Officer. The sales organisation has missed plan two years running, and the CEO wants my 90-day plan by Friday, January 22. I started on Monday, January 11, and today is Wednesday, January 13. Our fiscal year runs April to March. Below are the CEO's email, my predecessor's turnaround deck, and notes from sales operations, customer success, HR and finance. Please give me: 1. What I've inherited: each claim in the CEO's email and the deck, with what the data shows: holds, doesn't hold, or unknown. 2. Days 1 to 30: what I need to find out first, with the evidence that makes each item a priority. 3. Days 31 to 90: the decisions and their dates, checked against our fiscal year-end and any other deadlines in the inputs. 4. What I won't commit to yet, and what would let me. 5. A short note to the CEO covering the plan and anything in his request I'd change. Treat everything my predecessor wrote as a claim to check, not a fact, and give the evidence for every first move. Don't swap one unsupported explanation for another. Check the arithmetic and the dates. Don't add facts that aren't in the inputs; if you assume something, say so. [1] Email from Daniel Hart, CEO Amara, welcome. We've missed plan two years running. Kevin's view was that churn is a product problem with SightLine, our connected monitoring service, and the pipeline is fine at $2.4B, three times next year's $800M target, so this is execution. I'd like your 90-day plan by Friday, January 22, including a territory redesign announced by March 15 so FY28 starts clean on April 1. [2] From the previous CRO's turnaround deck (Kevin Marsh, September 2026) - "Service contract churn is up because of SightLine product issues." - "Pipeline: $2.4B, 3x coverage of FY28 target. Healthy." - "Sales attrition has stabilised at 12%." [3] Sales operations: pipeline export (January 8) - Total open pipeline: $2.4B. - $520M is in opportunities older than 18 months with no activity in the last 6 months. - $310M is duplicated: 214 service renewals were entered once by the service team and again by sales. The stale and duplicate amounts don't overlap. [4] Customer success: service contract churn (January 7) - FY26 (12 months): 6.1% of service contracts not renewed. - FY27 to date (April to December): 412 of 5,150 contracts not renewed, 8.0%. - Exit reason recorded for 160 of the 412: price 61, response time 48, moved to a competitor's bundle 30, SightLine issues 21. No reason recorded for the other 252. [5] HR and finance notes - Sales attrition: 12% in FY26. In FY27 to date (April to December), 58 of 310 sellers have left. - The FY28 sales compensation plan, including quotas by territory, must be final by Friday, February 26 for payroll set-up. - FY27 closes Wednesday, March 31. Q4 (January to March) is usually our biggest bookings quarter.I've just joined an industrial building services company as Chief Revenue Officer. The sales organisation has missed plan two years running, and the CEO wants my 90-day plan by Friday, January 22. I started on Monday, January 11, and today is Wednesday, January 13. Our fiscal year runs April to March. Below are the CEO's email, my predecessor's turnaround deck, and notes from sales operations, customer success, HR and finance.
Please give me:
Treat everything my predecessor wrote as a claim to check, not a fact, and give the evidence for every first move. Don't swap one unsupported explanation for another. Check the arithmetic and the dates. Don't add facts that aren't in the inputs; if you assume something, say so.
Amara, welcome. We've missed plan two years running. Kevin's view was that churn is a product problem with SightLine, our connected monitoring service, and the pipeline is fine at $2.4B, three times next year's $800M target, so this is execution. I'd like your 90-day plan by Friday, January 22, including a territory redesign announced by March 15 so FY28 starts clean on April 1.