A renewal forecast narrative is the story that sits on top of the installed base. The number tells leadership how much contracted revenue is up for renewal next period. The narrative tells them how much of it is actually at risk, which accounts are driving the exposure, and what customer success and account management are doing to close it. Done right, the renewal narrative gives the board a clean read on retention, surfaces expansion that offsets churn, and gives the CS and AM leaders room to run the save plays before the quarter closes. This guide shows CS and AM leaders how to build the narrative in one pass, align exec sign off, and ship it to leadership inside forty eight hours of the quarterly renewal review.
Time: 2-4 hours per quarter
The opening paragraph is the only one leadership is guaranteed to read, so it has to carry the headline. Open with total ARR up for renewal in the period, total dollars currently flagged at risk, the implied gross retention rate, and the expansion offset that lands the net retention number. Keep it to three or four sentences and avoid caveats. A board member who reads only the first paragraph should know whether net retention is holding, expanding, or contracting, and whether the exposure in the quarter is concentrated or spread. If the opener needs a chart to be understood, the opener is doing too much work. The chart belongs in the appendix. The number belongs in the first paragraph.
After the headline, give leadership one sentence per reporting segment. Use the same shape for every line: segment name, ARR up for renewal in the segment, percentage flagged at risk, direction of movement against the prior quarter, and the single thing that moved it. The point is to make the section scannable in under a minute. Readers who care about mix will spot concentration or decay without asking a single follow up question. If a segment hides a materially different story inside its roll up, flag it on the same line. A segment that looks healthy because one anchor account is renewing clean is a segment that needs its own line in the risks section later.
The named accounts section is where the narrative earns credibility. Pick the accounts that drive most of the at risk ARR for the period rather than the full exception list. For each account, write one line on the exposure in dollars, one line on the specific risk driver (product fit, sponsor change, usage decline, pricing pushback, competitive displacement), and one line on the save play already in motion with a named owner and the next milestone date. Leadership penalizes CS leaders who surface risks without a save plan far more than they penalize leaders who surface risks with plays already in flight. If a save plan has not been scoped yet, say so explicitly and name the date by which it will be. Vagueness here is the single biggest reason renewal narratives lose the room.
A renewal narrative that only reports exposure tells half the story. Leadership also needs to see the expansion motion that will offset gross churn and carry net retention. Report expansion pipeline tied to the same renewal book, broken down by motion (upsell on seats, cross sell to a second product, usage true up, tier upgrade), each with the probability weighted dollar value and the owning AM. Then name the enablers that are driving the expansion signal: a product release that opened a new tier, a motion change that put the AM in the room earlier, a pricing update that unlocked seat expansion. Avoid vanity expansion. One large upsell is a result, not a pattern. A reproducible motion inside a segment is an enabler because it tells leadership where to invest.
For each named at risk account, show the close plan in a compressed, repeatable shape. The plan should name the save play (executive sponsor meeting, usage review, pricing revisit, success plan reset, product gap workaround), the exec sponsor from the Strkr side, the counterpart on the customer side, the milestone date, and the fallback if the primary play misses. Leadership does not need the full project plan. They need to see that every at risk account has an owned play, a measurable next step, and a date on the calendar. Close plans that read as generic (one line: 'EBR scheduled') are a signal that the account team has not yet done the work. Close plans that are specific are the single strongest credibility signal in the narrative.
The renewal narrative is a cross functional artifact even when the CS leader writes it. The CRO owns the connection between renewal exposure and the revenue plan. The CFO owns the connection between retention and cash. The CEO owns the strategic framing that will reach the board. Before the narrative ships, run a thirty minute alignment session with CS, AM, Finance, the CRO, and the CEO on three things: the headline (total at risk and net retention), the named accounts list, and the expansion offset. Do not spend the session rewriting prose. The point is to make sure the CS leader is not calling a different story than the CEO will call in the room. A narrative that contradicts the CEO's framing damages the CS leader's credibility more than any single churn ever will.
The renewal narrative is most useful while the review is still fresh. Send the signed off recap within forty eight hours of the quarterly renewal review, before the full board deck is finalized. Format it as one page of narrative plus a short appendix with the segment table, the named accounts list, the expansion pipeline view, and the gross to net retention bridge. Lead the email with the same headline paragraph that opens the narrative, so a director reading on a phone sees the number first. Make it easy for a director to reply with a question. Narratives that create a short asynchronous question loop before the board meeting shorten the meeting itself and surface the hard questions in writing, where the CS leader can answer with evidence rather than from memory.
A narrative archived cleanly is worth more than one that ships well and disappears. Save the signed off version, the pre meeting draft, the exec sign off notes, and the leadership reply thread as one artifact per quarter inside Strkr. At the end of the period, run a short retro that compares what the narrative said would happen with what actually happened: did the at risk accounts churn, were the save plays executed on time, did the expansion offset land, and did net retention come in where the narrative called it. Over four cycles, the archive turns into the single best coaching tool for the CS leader. At risk patterns that keep repeating point to structural work that was never done, and expansion enablers that fail to compound point to motions that were misread.
A renewal playbook is the operational artifact the CS and AM teams run against during the quarter. It describes the plays, the triggers, the owners, and the escalation paths for every account motion. The renewal forecast narrative is the executive artifact that reports what the playbook produced and what is still at risk. The playbook runs the work; the narrative tells leadership how the work is landing.
The sales forecast narrative covers new logo and expansion ARR flowing in through the sales motion. The renewal forecast narrative covers contracted ARR flowing out of (or holding inside) the installed base through the CS and AM motion. The two narratives share the same shape and the same board audience, but they call different numbers and name different accounts. Most companies produce both, and leadership reads them side by side.
The head of customer success or the CS and AM leader owns the first draft because the narrative is a point of view on retention, not a report on it. CS operations supplies the data and the appendix, Finance validates the gross to net bridge, and the CRO and CEO sign off on the framing. One voice writes it; three functions review it.
Name the accounts that drive most of the at risk ARR for the period, typically five to ten depending on the shape of the book. The goal is to show leadership where the dollar exposure actually sits, not to produce a full exception list. Accounts below the materiality line belong in the operating cadence, not in the board narrative.
Both, and in that order. Lead with ARR at risk and gross retention so the raw installed base signal is visible, then add the expansion offset and the net retention call so leadership can see the full retention picture. Reporting only net retention hides churn behind expansion, and reporting only gross retention understates the net story the board is tracking against the plan.
Inside forty eight hours of the quarterly renewal review is the right target. The narrative is most useful while the review is still the live context for every director, and shipping it fast gives leadership room to ask asynchronous questions before the formal board meeting. CS leaders who wait a full week find the narrative arrives as commentary on a view the board has already formed.
Lock the renewal book, score confidence by segment, and pull named at risk accounts and expansion pipeline from the same system your CS and AM teams work in. Strkr turns renewal inspection into a one page board narrative your exec team can sign off on in a single alignment session.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
