Win themes when you're the incumbent defending a contract
Defending a contract is a different proposal than winning one. The win themes that worked four years ago will lose you the renewal. Here's what changes when you're already inside.
I have watched more incumbents lose renewal bids than I can count. Most of them lost the same way, for the same reason: they wrote the same win themes in the renewal that they wrote in the original bid four years ago. The themes worked the first time because the buyer had no incumbent. The themes lost the renewal because the buyer now has an incumbent, and the incumbent is you.
If you are defending a contract you currently hold, your win themes need to be a different shape than a challenger’s themes. This is the post I find myself writing — in capture-plan form — every time I work with an incumbent team going into a recompete.
What the challenger gets to do
A challenger’s themes are about promise. They get to argue from clean slate: their architecture is more modern, their team has more relevant experience, their pricing is better, their methodology has been refined since the last cycle, their reference customers are more recent and more impressive. The challenger has the easier job of the two. They can frame everything they’ve ever done as the natural evolution of what the buyer needs next.
A challenger does not have to defend any specific decision their company made on the buyer’s account. They have no scars on this account. They can argue forward.
You don’t have that option. You have a paper trail.
What the incumbent has to do
Three things, in order of how often they get fudged.
1. Acknowledge the scars
Every long-running contract has incidents, escalations, missed milestones, billing disputes, and at least one moment when the buyer was unhappy enough to consider leaving. The buyer remembers all of them. If your renewal proposal does not reference any of them, the buyer reads that as either ignorance or arrogance — neither of which they want to renew.
The strongest incumbent themes lead with acknowledged history. Not generic “we’ve been on a journey together” prose. Specific references to specific events, with what was learned and what changed. “After the Q3 2024 outage, we shifted our maintenance window to a four-hour buffer and have run 22 consecutive months at 99.95% measured uptime — including the regional event in March.” That is a theme that a challenger cannot match because it speaks to a history the challenger doesn’t share.
The mistake most incumbents make is to either leave the scars out (it reads as evasive) or to recite them as “challenges we overcame” without specifics (it reads as marketing). The third path — acknowledge with detail, demonstrate the specific change, link the change to a measurable result — is the one that wins. It is also the one that requires the capture lead to have read the account history honestly, which is itself a discipline most teams skip.
2. Convert tenure into compounding evidence
Tenure on its own is not a theme. “We’ve been your trusted partner for four years” is the kind of phrase the PropLibrary swap test catches in the first scan — swap your name for any incumbent and the sentence still works, which means it is doing no work.
Tenure becomes a theme when you frame it as compounded knowledge that a challenger cannot have. The exact configuration of the buyer’s environment, the cross-system data flows, the integration patterns with their other vendors, the names of their internal champions, the unwritten priorities of their procurement lead. None of these are the kind of thing the challenger can claim. Many of them are the kind of thing the challenger has to discover painfully in the first six months of a transition — which is exactly the cost the buyer is weighing against the discount the challenger is offering.
The wording that converts tenure into theme is operational. Not “we know your business.” Specifically: “Our team carries the post-2024 schema migration in their working memory. The four engineers on your account have shipped a combined 87 changes against your environment in the last 18 months. None of those changes required your team to re-test integrations; the regression suite was already aware of your specific edge cases.” That is a theme that can only come from inside.
3. Pre-empt the cost-of-switching argument the buyer is having internally
The buyer’s evaluation panel includes someone whose job is to argue that the contract should go to a challenger. That person is making one of three arguments, sometimes all three: the incumbent is complacent, the incumbent’s pricing has crept up over time, the incumbent’s roadmap has gotten lazy.
A defending proposal should structure win themes to refute each of those arguments specifically, by name, with evidence. Not with vague rebuttal. With the kind of concrete proof that closes a thread.
- Against complacency: a list of investments made during the contract that benefit the buyer and weren’t part of the original SOW. The change-volume number from above. A roadmap-from-feedback narrative — “five of the seven major releases over the contract were directly informed by feedback from your team.”
- Against price creep: an explicit price comparison vs. CPI, vs. industry benchmarks, vs. the original contract. If your effective per-unit price has fallen, say it with numbers. If it hasn’t, address why and what value that price now reflects.
- Against roadmap stagnation: the next 18 months of roadmap, with the specific items that respond to the buyer’s stated priorities (which you have, because you have been in the room for four years).
The buyer’s evaluation panel does not need to be told you are a good vendor. They are paying you. They need ammunition to win the internal argument against switching, and the proposal is where you give it to them.
The themes you should retire
A few patterns that work for challengers and consistently lose for incumbents.
“We’ve grown alongside you.” This is dangerous because it can read as “we got bigger and you became a smaller fraction of our revenue, which means our attention is divided.” Even when that’s not true, the phrase suggests it. Better: name the specific people on the buyer’s account who have not changed.
“Our solution has matured.” Maturity is good for buyers who don’t have one yet. For an incumbent, “maturity” can read as “we haven’t shipped anything new lately.” Replace with a specific roadmap claim and the past performance to back it up.
“We continue to be your trusted partner.” Trust is past-tense by the time it gets to the proposal. If the buyer trusts you, you don’t need to say it. If they don’t, saying it doesn’t help. Cut.
“Best practices.” This phrase is acid for any proposal but especially for an incumbent’s. The challenger gets to claim best practices because they don’t have a body of evidence to be measured against. The incumbent’s themes need to be specific to the buyer’s environment, not industry-generic. “Best practices for environments like yours” is the same evasion in fewer syllables.
The capture-plan move
In the capture plan for an incumbent defense, I add a section that is not in the standard Shipley template. It is called Switching Cost Realism and it states, in writing, the buyer’s actual cost of moving away. Specific months, specific integrations, specific data migrations, specific re-training on the buyer’s side. This section is not in the proposal — it informs the proposal.
The reason it is not in the proposal is that telling the buyer their switching cost would be bad form and would read as a threat. The reason it is in the capture plan is that the win themes need to be calibrated against what the buyer would actually have to give up. If the switching cost is low (the contract is mostly commodity work, the data is portable, the training is light), your themes need to do more work on differentiation than on tenure. If the switching cost is high (deep integrations, custom workflows, multi-team training), your themes can lean harder on continuity — but only if you have the operational evidence to back it up.
A team that doesn’t write down the buyer’s switching cost ends up calibrating its themes against the team’s own preferences instead of the buyer’s actual decision economics. That mistake costs renewals.
What good looks like
In the renewal proposals I have seen win, the themes have a recognizable shape:
- One acknowledgment theme. Specific scar, specific change, specific measurable result.
- One compounding-knowledge theme. Tenure converted into operational evidence that a challenger structurally cannot have.
- One forward-investment theme. Specific roadmap commitment tied to a buyer-stated priority, with the evidence that the priority was understood from inside the relationship.
- One commercial theme. Pricing-and-terms framing that addresses the cost-of-switching argument head-on, with numbers.
Three or four themes. Specific, evidence-backed, written from inside the relationship. Anything more dilutes; anything fewer leaves the door open to a challenger theme nobody refuted.
The renewal proposal is not a sequel to the original proposal. It is a different document, on a different argumentative footing, against a buyer who has lived with you for four years. Treat it as a different document, write it from inside, and the themes will write themselves.