The Value Engine

Contents

Preface — Why I Wrote This

I have watched seven-figure deals die — not because the product failed, but because no one on the account team could explain the customer’s cost of delay in one sentence. The demo was flawless. The champion was enthusiastic. The proposal was beautiful. And in the meeting that mattered, when a CFO asked why this had to happen now instead of next fiscal year, the room went quiet. Quiet is how deals die. They almost never die loudly.

I came to sales from the technical side of the table. For years I was the solutions engineer — the one brought in to make the proof actually work, to survive the architecture review, to stand at the whiteboard while the buyer’s skeptics tried to break the story. That seat teaches you something no sales training does: buyers don’t believe claims, they believe evidence, and the deal is won or lost in the quality of the evidence long before anyone talks price.

Then came the stress test. In the economic hardship of the COVID years, DataRobot — like much of the industry — went through waves of workforce reductions, and Latin America took the hit hardest: the BDRs, the ADRs, the sellers — effectively the region’s entire go-to-market — were gone. What remained was me, the pre-sales technical lead, and a book of live contracts that still had to be supported. So I rebuilt the region from the ground up, alone at first: system automations to do the work a team no longer could, a go-to-market strategy sized for one person and maximum leverage, pricing built for the region’s actual economics, and a reseller and partner network that multiplied me across countries I could not physically be in.

As RVP of Latin America I ended up being everything at once — the seller, the partner manager, the forecaster, and the leader responsible for the number — and I ran all of it on the system in this book. Following that method — and it is a method, closer to science than to art — LATAM ARR grew roughly six-fold over the next two years. Every deal ran through the same inspectable machine, and the machine caught the weak ones early enough to fix them. When people ask why I believe systems beat headcount, that is why: I have run the experiment, involuntarily, with the region as the lab.

The pattern I have seen since, again and again, is the same. Sales organizations do not lose because their sellers lack talent or effort. They lose because the things their best sellers do instinctively — quantify the pain, test the champion, get the Economic Buyer conditionally committed before the proof begins — live in nobody’s system. They live in a few people’s heads, and when those people are stretched, promoted, or gone, the organization forgets how to win.

This book is that method, written down for the people who now sit where I sat. It codifies proven enterprise-selling disciplines — rigorous qualification, value engineering, insight-led teaching, proof governance — into one inspectable system: gates a deal must pass, evidence a deal file must contain, scores a leader can read at a glance, and questions to ask out loud in every deal review.

Read it with your pipeline open. Argue with it. Replace my numbers with yours. And the next time someone tells you a deal feels strong, ask them what the customer’s cost of delay is — in one sentence, with a number in it.

— Rudy M. Celekli
Charlotte, North Carolina

Author’s Note — The Case That Runs Through This Book

Every framework in this book is illustrated with a single running case: the pursuit, proof, close, and expansion of a transformational deal at Meridian National Bank — a top-ten U.S. bank by assets, with roughly 62 million retail customers, a Financial Crimes operation of several hundred analysts, and a regulator watching the clock. The vendor in the story, Northstar, sells an AI-powered decisioning and workflow platform. The deal is followed from first research to second-year expansion, with real numbers carried consistently through every chapter — the same discipline this book demands of your sellers.

Meridian, Northstar, and every named individual are fictional composites, assembled from the recurring patterns of real enterprise sales cycles in regulated industries. The texture, however — model-risk review under SR 11-7, third-party risk gauntlets, consent-order pressure, procurement’s final squeeze — is drawn to be indistinguishable from the real thing. That is the point: you should recognize every scene.

Introduction — The Leader’s Mandate

Selling is a transfer of confidence, backed by evidence. Leadership is the system that makes that transfer repeatable — across every seller, every quarter, every deal.

Most sales organizations do not have a selling problem; they have a variance problem. The top decile runs beautiful deals on instinct. Everyone else improvises. The gap between them is not talent — it is the absence of an operating system that makes the top decile’s instincts inspectable, teachable, and mandatory. This book is that operating system, written down.

Read it in two passes. First, read the Meridian case straight through — the ‘In the Field’ sections tell one continuous story, from a cold Value Pyramid built off a 10-K to an $8.9 million three-year agreement and the expansion that followed. Second, read the frameworks and the Leader’s Lens sections with your own pipeline open in another window.

The Cast of the Running Case

The distinction sounds obvious and is violated daily. Feature selling leads with capabilities and demos, wins on checkbox comparisons and price, and creates interest. Value-based selling leads with the customer’s pains and desired outcomes, wins on a quantified business case and differentiated fit, and creates urgency. Interest gets you meetings. Urgency gets you signatures.

A leader’s first inspection question on any deal is simply: which kind of selling is happening here?

Every bad deal I have ever inspected was a feature-selling deal wearing a value costume. The costume comes off in one question: whose number is on the first slide — ours, or theirs?

Two kinds of selling

1.1 The Value-Based Conversation Model

Every deal narrative your team constructs should follow one eight-element structure — the DNA of this entire book and the backbone of every Economic Buyer conversation your sellers will ever run:

1. 1.Before Scenario — the customer's current state, in their language, with the specific friction they live with today.
2. 2.Negative Consequences — the measurable damage of staying there: lost revenue, cost, risk, missed roadmap, reputational exposure.
3. 3.After Scenario — the concrete future state your solution creates.
4. 4.Positive Business Outcomes — the quantified benefits of the After: faster time to value, higher ROI, reduced cost and risk.

5. 5.Required Capabilities — what any solution must have to move the customer from Before to After. This is where decision criteria get shaped.
6. 6.Metrics — how success will be measured and proven, before and after.
7. 7.How We Do It / Better — how your solution delivers each required capability, and why it does so better than the alternatives.
8. 8.Proof Points — customer stories, benchmarks, and references that make the claim credible.

Running vertically through all eight: discovery questions — the questions that uncover which value drivers actually matter to this customer.

The delta (Δ) between Before and After is the value at stake. The entire job is to make that delta vivid, quantified, and attributable to you.

1.2 Value Drivers: Where Conversations Begin

Value drivers are the problems a prospect is proactively trying to solve — top-of-mind business topics that exist whether or not your company does. Good value drivers share five properties: they are revenue, cost, or risk related; they exist independently of your product; they could cause a buyer to reallocate discretionary funds (the real test of urgency); they are mutually exclusive and collectively exhaustive as a set; and each maps to specific buyer personas who own that problem.

Most companies can express their value through three universal driver archetypes: getting high-value initiatives live (time to value), driving repeatability and scale across teams (avoiding one-off heroics), and maintaining quality in production as requirements, data, and markets change (protecting realized value). Adapt the language to your category; the architecture holds.

1.3 Differentiators and Trap-Setting

Differentiators influence a technical buyer’s decision criteria through Required Capabilities. Every differentiator your team claims should be documented with four elements: a description, its customer value in revenue, cost, and risk, its defensibility from the customer’s point of view, and its trap-setting questions.

There are three types: unique (capabilities only you provide), comparative (superior attributes versus other vendors), and holistic (attributes that make a customer feel safe doing business with you — delivery track record, expert services, financial durability).

A trap is a topic you raise deliberately because honest exploration of it leads the buyer to your differentiation — and away from competitors who cannot follow. Never lie, never disparage; simply make the buyer confront requirements only you satisfy.

Every trap has three moves: set the topic neutrally as a common client challenge; open the trap by probing the current process, its costs, and its failure modes; close the trap by inviting the buyer to describe the impact of the differentiated capability. The buyer articulates your value in their own words — the most powerful form of persuasion that exists.

In the Field: The First Conversation at Meridian

Meridian National Bank · Month 1

The setup. Meridian’s Financial Crimes Operations group runs 340 analysts adjudicating roughly 4.1 million AML and fraud alerts a year — about 22 minutes per alert, with a false-positive rate north of 90%. Six months earlier, the OCC issued a Matter Requiring Attention citing alert-backlog aging, with a remediation deadline of March 31. Dana Whitfield, the SVP who owns the function, has been asked by her COO for a plan twice. Northstar’s AE, Alex Osei, gets thirty minutes with her through a former colleague.

The feature-selling version of this call — the one Alex’s competitor ran two weeks earlier — opened with a platform demo and a slide titled ‘Our AI Advantage.’ Dana gave them the second fifteen minutes to her deputy.

Alex’s version opened on the value driver Dana already owned: “Most financial-crimes leaders we work with are caught between two clocks right now — alert volume compounding at fifteen to twenty percent a year, and a regulator’s calendar that doesn’t care. Where does that sit for you?”

Twenty-two of the thirty minutes were Dana talking. Alex asked four questions, wrote down three verbatim quotes, and never opened a slide. The trap he set — neutrally — was Meridian’s model-governance process: “When teams here have tried to automate adjudication before, what happened when the model hit Model Risk Management review?” Dana’s answer (“It died there. Fourteen months, then dead”) handed Northstar its differentiation battlefield: explainability and audit-ready decisioning, the one requirement the incumbent point solutions could not survive.

What made the delta vivid was one sentence Alex constructed from Dana’s own numbers before the call ended: “So the current process consumes roughly one and a half million analyst hours a year to find the four percent of alerts that matter — and the backlog it creates is now a regulatory finding.”

Dana’s reply went straight into the deal file: “That’s the sentence I’ve been trying to get my leadership to hear for two years.”

The Leader’s Lens — What to Inspect

The failure smell: deal reviews where the seller can recite the product story but not the customer’s Before Scenario in the customer’s vocabulary. If the first three minutes of a deal review are about your platform, stop the review.

Questions to ask out loud: “Say the Before Scenario in the customer’s words — what quote do you have?” · “Which value driver did we anchor to, and who owns it?” · “What trap have we set, and what decision criterion did it produce in writing?” · “If I called the champion right now, could they tell me the delta in one sentence?”

The coaching move: require one verbatim stakeholder quote in the CRM before any deal advances past discovery. Quotes are currency in the Economic Buyer conversation; a deal file without them is a deal built on paraphrase.