Operators take on the work that never scaled.

The CISO rarely joins your calls. They appear as a gate other people describe: reaching it, waiting on it, failing it. They don’t fund the deal, but they can stop a deployment, a data path, an AI use case or the signature itself. And saying no costs them almost nothing.

Recommendation: treat security as a sequence, not a meeting. Arrive with the full packet before it’s asked for, and keep the AI review to the smallest surface possible.

How receptive they are depends on which part of their work you walk into.

~15 open deals where the CISO is in play right now, matched to the situation you’re walking into and the play for it.

What starts deals instead: contract renewals and expiries, price rises, end-of-life notices, migration deadlines.

Buyers won’t buy a platform because of AI, but they will walk away from one that fails the AI question. Demand generation built on AI messaging will underperform; an unanswered AI question in a deal started by something else will quietly lose it.

Recommendation: move AI out of campaigns and into the evaluation. Lead demand generation with the events that actually start deals.

~30 open deals where one of the five findings is live right now, each with the move it calls for.

Buyers are widening from content people read to content machines read. The evidence supports the direction, not a date. So build what serves both: structure, approval controls and reach into other systems are what today’s customers already buy, and exactly what machine readers need.

Recommendation: run one roadmap, not two. Commit in stages: seven assumptions, each with a cheap test and a tripwire, re-checked every quarter.

Grouped by what buyers want from AI, not by industry or size.

In five of six, what serves today’s job also makes the buyer AI-ready. The exception is the largest group: most show no AI interest at all, and it’s where deals are being lost on the editor.

Once leadership approves the archetypes, every other operator works from them.

Customers describe your value in three ways: faster releases, better quality and control, and lower running costs. Each comes with a before and an after number in their own words, so a value claim never rests on a vendor estimate.

Recommendation: lead discovery with the value drivers, not the numbers. Probe for the prospect’s current baselines, then use the after benchmarks to size the room for improvement, working it through with your champion.

Every after number was observed by customers in production. Test failures uses an industry benchmark for the before.

~20 open deals where discovery is still thin: no baselines, pains from similar wins not yet explored, or outcomes not tied to what the economic buyer cares about.

Most of the value is cost: retiring custom release scripts is worth $250–350K on its own. Faster releases and better quality add the rest. Every line uses the low end of what customers report.

Recommendation: before the CFO meeting, confirm the four benchmarks with Kestrel’s platform lead. Incidents and audits move the number most.

Every benchmark behind the unit gains traces to customer calls in the domain metrics.

Filled from Kestrel’s own calls where they’ve said it, and from your customer benchmarks where they haven’t. The buyer confirms every benchmark for their own situation.

Buyers aren’t asking for a more capable platform. They’re asking you to finish what you already ship: the connector that drops formatted text, the agent that skips linked content, the bulk publish that stops at one page. Seven of the eight themes are requests to remove a step someone does by hand today.

Recommendation: sequence by the revenue at stake, not by volume. The most severe fixes are small, specific and already scoped by customers.

Ranked on three things combined: how often it comes up, how many accounts raise it, and the pipeline and revenue riding on it. Trend is the last 90 days against the year.

~35 open deals, renewals and lost deals that asked for one of these fixes, each with an owner to tell.

Since these deals were lost, you’ve addressed the weaknesses buyers pointed out against Tessel: fewer steps in everyday CPQ flows, and small-team pricing. Your recent wins against Tessel show why teams leave it: dependency errors in production and failed releases they can’t roll back. Twelve lost accounts raised at least one of these during their evaluation, either a weakness you’ve since fixed or a worry about Tessel that recent switchers share, and all are within six months of an estimated Tessel renewal.

Recommendation: approve the 12 and start with the nearest renewals. Open each with the worry about Tessel they raised, then what’s improved about you.

From the competitive intelligence manager operator: your campaign brief, plus 9 recent wins and winbacks against Tessel.

Drivers come from what was said during each evaluation. Each approved account goes to its account executive with a playbook.

Air cover: the ABM team runs ads on what’s improved to the people from each lost evaluation, before the account executive reaches out.

Vireo chose Tessel on ease of use but also worried it couldn’t roll back data with configuration. Their senior administrator raised it on four calls. Since then you’ve cut steps from daily flows, making it easier to use, while rollback has always been your strength. You also have winback accounts like Calloway Insurance that left Tessel over the same rollback concern Vireo voiced during their evaluation. Vireo signed with Tessel in January 2026.

Recommendation: reopen through the Platform team lead. Share what’s improved, ask how rollback has gone on Tessel, and offer to run one of their real releases. Bring the director in once the admins are asking for it.

Timed so a pilot can finish before the estimated renewal.

From recent wins against Tessel, matched to Vireo’s drivers.

The signals your team tracks don’t separate your wins from your losses. A firm deadline, a big dollar figure on the pain, a named approver, an excited champion: each shows up just as often on the deals you lost. MEDDPICC is a general checklist. What decides your deals is specific to how release teams buy and where your product fits them: pain tied to a release or contract date that arrives anyway, doubts resolved in the buyer’s own setup, and a number someone has the budget to fund. Your team can act on each of these in every deal.

Recommendation: put the five deciding factors below into every deal review, spend technical time proving the buyer’s specific doubt instead of re-demoing what they already believe, and run security, procurement and legal in parallel.

Rebuilt from your buyers’ own words, not your CRM stages. Win rate is for closed deals where the winning pattern was present, against where it wasn’t.

Buyers arrive already believing the core of your product. Deals are almost never lost there, so re-demoing it wastes the meeting. They are won, slowed or lost on a handful of capabilities, and on whether the buyer saw their own doubt resolved in their own org.

Hard limits are for the first technical call. The four movable ones are where most winnable losses sit.

Each tied to the stage it comes from. The sales coach operator applies the same patterns to live deals in its pipeline coaching and deal reviews.

AI review is where deals slow down now, and buyers ask the same questions in almost every one. Up to nine reviewers can each stop a deal, and each wants a written answer they can keep on file, not a reassurance on a call. Six topics cover most of what they ask.

Recommendation: start with the AI governance pack. Every regulated buyer asks for it, and it answers much of what sits behind the next three.

Ranked by how often buyers raise each topic and how many accounts raise it. Trend is the last 90 days against the full 180.

Each brief goes to its owner with the buyer evidence attached. Your team decides whether that means something new or improving what you already have.

Buyers ask the same questions about your AI in almost every evaluation, usually on a call and often weeks in. Answer them on your site in the buyer’s own words, and buyers get answers before they talk to anyone, AI assistants and search engines have something to cite, and evaluations start further along.

Recommendation: one FAQ page in eight sections, ordered by how often buyers ask. Keep each question in the buyer’s phrasing, so it matches what they type into search and AI assistants.

The page goes to the web team with every answer drafted. Your team edits and publishes it, with FAQ markup so search engines and AI assistants can read each answer.

Fastlane isn’t beating you on capability. It wins on price and simplicity, usually before anyone tests sync, governance or testing at scale. Where buyers do test those, you win, and they say why. The problem is the deals that never get that far.

Recommendation: put a value number on the table before Fastlane’s price sets the frame, and qualify every deal on team size, environments and who signs off production changes.

Buyers don’t decide by industry or size. They decide by which part of their release process hurts most. Find that first: it tells the rep whether to attack or defend, and it is the best way to defuse price.

Recommendation: steer every deal toward the six offense battlegrounds. Clear the bar fast on comparison and setup, then move on. On price, reframe to total cost before the number decides.

You win when the conversation moves off price and simplicity and onto governance, sync, testing and scale. Known renewal dates convert best, yet almost none are tracked as close dates.

Recommendation: tag every deal in your CRM with its play and battleground, give each critical and high deal an owner in sales, solutions, value engineering and product marketing, and review them weekly. Log every known Fastlane renewal as a managed close date.

Severity is how close the buyer is to choosing Fastlane and what’s at stake, not deal size.

About 18,000 compromised accounts reset in one week, and about $500K in takeover losses avoided. At that rate, the platform paid for itself within weeks.

Recommendation: use it with security and fraud buyers who have to justify spend in dollars, and where value has to be proven before they buy. Lead with losses avoided, then precision: catching fraud without blocking good customers.

~25 open deals whose situation matches Larkspur’s: the same problem, the same decision criteria, at a point where a peer’s story can move the deal forward.

Buyers have stopped arguing about price. Over the year, the three loudest objections were about affordability. In the last 90 days all three fell out of the top eight, replaced by architecture fit, security and packaging limits. These don’t get negotiated: they go to a reviewer you never meet, or they end the evaluation before value comes up. The constraint has moved from willingness to pay to permission to proceed.

Recommendation: five moves across four teams, none touching list price. An architecture gate in first-call discovery, an integration reference library, a reviewer-ready security pack, a review of which tier limits block revenue, and billing options offered as product rather than conceded under pressure.

~45 open deals stuck at one of the three blockers right now, each routed to the team that clears it.

Buyers don’t open by naming a product category. They open with brands they can’t govern, a content model they’ve outgrown, a legal translation requirement, or marketers stuck in a developer queue. Five asks account for most of what they say, and each maps to something you do well.

Recommendation: qualify on the tell, lead with the pillar it points to, and run that pillar’s play: what to ask, say, show and avoid. Name the setup effort early; buyers trust it more than finding out in week three.

Why it matters to buyers: their growth now outpaces what page-built systems can carry. Every new brand, market or channel becomes another rebuild, another translation project, another developer queue.

Where you fit: the structured, governed content layer under all of it. The five pillars are how buyers experience that, one problem at a time.

~40 open deals where a pillar’s tell is live on their calls right now, each matched to the play to run next.

This book is won on proof in the buyer’s own environment. The risk sits in three places: the nearest close has the thinnest call coverage, the largest expansion rides on reliability that isn’t proven yet, and the biggest new logo has no executive in it.

Recommendation: confirm Meridian Bank’s real stage with the rep this week. Put a fix-and-prove plan on Fenwick Pharma, and an executive sponsor on Ardent Systems. Then win the trial at Osprey Logistics and clear the data-residency review blocking the trial at Corvane Health.

Next quarter’s pipeline covers the target 1.8 times, against the 3 times this team usually needs. That leaves a gap of about $700K. The pipeline strategist operator has two campaigns ready for this territory.

Deals whose stage looks like progress but whose calls tell a thinner story. Each deal owner gets the play, and the manager gets the flag.

Winnable. The technical case is strong; the commercial case hasn’t been built. A capable analyst champion and real pain with Halyard, but no executive in the deal, no date tied to the Halyard renewal, and no side-by-side proof yet.

Recommendation: do what your wins against Halyard did. Pin a date to their renewal, turn the champion’s offered leadership call into an executive sponsor, run the side-by-side test the buyer proposed, and land a price at or below Halyard spend 90 days before it expires.

Graded on the dimensions of MEDDPICC, plus compelling event, commercials and technical fit. Three reds, all on the selling side. Pain, criteria and technical fit are the deal’s strongest assets.

Your wins against Halyard followed one sequence. The deal owner gets each step as a play, with who and when, tied to the gap it closes.

The product is embedded across teams. The open question is whether it still delivers: leaders questioned it after a run of service issues, new leaders have since arrived, and no substantial call has been recorded in five months.

Recommendation: get in front of the executives and new leaders this month with a recovery plan and a dated upgrade, and put the order form with procurement by early January.

Live across teams, but reliability slipped last winter, a required upgrade hasn't started, and no value figure is stated.

The grade is a judgement, not a formula. It weighs this account's own history against what came before full and lost renewals in your past deals.

The three gaps that most separate full renewals from lost ones, open at Acme right now. The account team gets each as a play, with who and when.