Case study · NRR expansion · 2026

How I grew an account from a one-year renewal into a three-year, expanded-cap contract.

An ANZ enterprise customer in the same book as the save play. The relationship was stable, the contract was renewing, the numbers were green on paper. But the account had stopped growing on its own. This is how I rebuilt the joint roadmap, brought specific products into the conversation that hadn't been pitched, and turned a one-year renewal into a three-year contract with around $100K of expansion in the first six months.

9-slide narrative Problem → Approach → Outcome Customer-identifying details lightly anonymized

  1. 01 Problem · Where it started

    A healthy account that wasn't growing on its own.

    An ANZ enterprise customer in the same book as the save play. The relationship was stable. The contract was renewing. The numbers were green on paper. But the account had stopped adding value on its own. They were using what they had, not seeing reasons to grow into the rest of the platform. The kind of account that doesn't show up on any red dashboard but is quietly capped.

    Healthy on paper · capped in practice · no felt need to expand

  2. 02 Problem · The expansion gap

    Nobody had connected the dots between what they used and what they could have.

    The original deal had brought in a specific set of products against a specific set of business problems. Twelve months later, the customer's business had moved. New initiatives, new compliance pressures, new platform decisions in adjacent teams. The deal hadn't moved with them. The result wasn't churn risk. It was something quieter: an account where the spend wasn't growing because nobody on either side had reframed the relationship against the customer's current business shape.

    Original deal · static · customer business · moved · gap unaddressed

  3. 03 Approach · First move

    Built a multi-quarter joint roadmap. With the customer, not at them.

    Look, the first move was the boring one. I sat down with the customer and we built a multi-quarter joint roadmap. Not a vendor roadmap with their logo on top. A roadmap of what THEIR business was trying to do over the next 12-18 months, mapped against where my platform could help. The exercise itself was the value. Most customers haven't been asked to think this way by their vendor. The roadmap became the document we both worked off for the rest of the engagement.

    Joint multi-quarter roadmap · co-built · customer business as the spine

  4. 04 Approach · Brought new product into the conversation

    Surfaced specific products that hadn't been pitched. With reasons.

    Once the roadmap existed, I could see which platform capabilities the customer hadn't been shown yet. The reality is that most CSMs never bring new products into the conversation because they assume the AE owns that motion. The AE is too busy to drive it from cold. The CSM has the trust and the context. So I drove it. Specific products, against specific problems the joint roadmap had named. Not a feature dump. A 'here's the thing you said you needed, here's what we have.'

    CSM-driven product introductions · grounded in the joint roadmap

  5. 05 Approach · Reframed the contract

    Outcomes, not features. Every conversation.

    The contract value was the same. The way we talked about it changed. Every QBR, every check-in, every escalation, framed in terms of business outcomes the customer was trying to drive, not features the platform happened to ship. This is the same move as the save play, applied at the expansion end of the lifecycle instead of the rescue end. Customers don't expand on a feature pitch. They expand when they believe the platform is in service of where their business is going.

    Outcome framing · every touchpoint · expansion follows belief

  6. 06 Approach · QBR as the forcing function

    Used QBR cadence to keep the roadmap honest.

    Every quarter the joint roadmap got revisited. What landed, what slipped, what changed in the customer's business that should change the roadmap. The QBR wasn't a deliverable I shipped at them. It was the meeting where we both held each other accountable to the roadmap we built together. Same QBR cadence as the save play. Same automation building it. Different customer, different outcome.

    Quarterly accountability · roadmap as living document · automation-built QBRs

  7. 07 Outcome · The numbers

    ~$100K in expansion within six months. One-year renewal became a three-year.

    Approximately $100K of expansion within six months. Cap increases across the products they already had. The one-year renewal that was on the table became a three-year. That last one matters most. A three-year contract isn't just three times the revenue of a one-year. It's a customer who's committed to building on the platform, which means the next conversation is about expanding deeper, not defending the renewal.

    ~$100K expansion · 6 months · 1-year → 3-year · cap increases across in-use products

  8. 08 Outcome · What changed structurally

    Customer requested monthly product sessions. Built into the cadence.

    The structural shift in the relationship: the customer started ASKING for monthly product sessions. They wanted to dive deeper into what was on the platform that they could onboard next. The expansion conversation went from me pulling to them pulling. That's the moment the relationship goes from 'CSM is managing the account' to 'CSM is a strategic resource the customer is using.' Different posture, different next-year math.

    Customer-initiated cadence · monthly product sessions · pull, not push

  9. 09 Takeaways · What another CSM could use

    Spend the time to actually understand the customer. Then deliver on it consistently.

    Look, the lesson is simple. Spending the time to truly understand your customer's problems is important. The other part that's really important is being consistent and doing your best to deliver on value, even when they're struggling to articulate it. This pays off in spades when things get tight, like at renewal. The expansion conversation isn't a separate skill. It's the same patient, deliberate work as the save play, applied earlier in the cycle. Understand the business, deliver consistently, and the expansion shows up on its own.

    Three lessons · Understand the business first · Deliver value consistently · Trust the cadence