Pricing for Enterprise Software — A Story Over Coffee

Everything in this primer is drawn from three books by Winning by Design — Revenue Architecture (Jacco van der Kooij), The SaaS Sales Method, and SaaS Customer Conversations. Rather than list the concepts, it walks you through a single enterprise deal the way a friend would: you are a sales leader at Northwind, a business-to-business software company doing about $60 million a year in annual recurring revenue, and you keep losing enterprise deals on price. Your friend Marcus — a veteran revenue leader who now advises software companies — has a whiteboard, a marker, and a folder of charts. The deal on the table is Meridian Freight, a logistics company. Read it start to finish; the concepts are explained as they come up. A map of which idea comes from which book is at the very end.

Act One — The Map: Why You Keep Losing on Price

You slide your closed laptop across the coffee table and lean back with a sigh.

"I'm losing every enterprise deal on price, Marcus. Meridian Freight was lined up. A hundred and eighty thousand a year in annual contract value, just sitting there. Our impact analysis showed we'd save them almost eight hundred thousand a year in demurrage and detention fees on a single new retail contract, and we still got undercut. Told them one eighty and they asked us to drop to one-thirty-five."

Marcus uncaps a marker and doesn't answer right away. He just looks at the whiteboard for a moment, then turns back to you.

"That's not a price problem," he says. "That's an architecture problem. And you're solving it backward."

He draws a horizontal line across the board.

"Price isn't a knob you turn. I know that sounds backward when a customer's squeezing you. But listen: the revenue model — how you get paid, when you get paid, what triggers payment — is a fundamental architectural choice. Not a sales tactic. And every decision you make above that choice has to align with it, or nothing works. You're losing the deals because the deal itself is built wrong from the ground up."

He slides a folder across the table. "There's a framework in Revenue Architecture that maps this out. But let me show you how deep this goes first."

He draws six layers stacked on top of each other.

"Your business sits in layers. The foundation — Layer One — is the revenue model. That's the monetization strategy. Above that is the data model, the mathematical model — your growth equations — the operating model, and the go-to-market model. And here's the critical part: if you get the revenue model wrong, every single layer above it compounds that error. A mistake in the revenue layer costs you a little time to fix today. In the go-to-market layer? Years. And millions of dollars. Because by then the mistake is baked into your entire operating system."

He taps the bottom layer with the marker.

"Meridian is an annual subscription, right? Not a perpetual license. Not consumption-based. Annual. That one choice — one choice — determines which sales motion you use, which win rate you budget for, what your customer acquisition cost should be, whether they churn in year two, and ultimately whether eighteen months from now the deal is profitable or whether you've been quietly subsidizing it."

You nod slowly. Marcus continues.

"There's a line in Revenue Architecture that hit me hard when I first read it. They quote Price Intelligently — a company that does nothing but study pricing — and the line is: 'A well-oiled pricing strategy is seven and a half times more effective at generating growth than acquisition strategies alone. Yet monetization is too often an afterthought.' Seven and a half times. And yet here you are trying to win by dropping price. You're trying to out-hustle a model that isn't architected for the deal you're chasing."

He draws three points along his horizontal line.

"The spectrum goes from Ownership on the left, to Subscription in the middle, to Consumption on the right. Ownership is where the buyer pays upfront — perpetual software licenses, on-premises hardware, hardware plus support. You promise value, and the buyer realizes the impact on their own dime. Subscription — monthly, annual, multi-year — the buyer pays recurring fees for access. And consumption: pay-per-use, pay-per-action, pay-per-outcome. 'No cure, no pay.' That's where the seller bears the risk and only gets paid if impact actually happens."

He slides another chart across. "This is the responsibility matrix. Watch what shifts as you move along the arc."

"In ownership," Marcus says, "the buyer owns the infrastructure. They install it, they maintain it, they troubleshoot it. The seller's job ends after delivery. In subscription — which is where Meridian lives — you're promising that it works continuously. They don't maintain it. They don't deploy it. You do. And in consumption, you're not just operating it, you're responsible for whether it delivers the outcome."

He leans back. "Here's the kicker: best practices don't transfer across those boundaries. You can't run an ownership sales motion and a subscription sales motion with the same playbook. An ownership deal focuses on feature checklists and technical proof — because the buyer is going to operate it. A subscription deal has to prove the customer's use case and the outcome — because you operate it."

He draws the arc again, this time with more detail.

"This shows you what moves together as you slide along that arc. Watch."

You study the numbers. The win rates look strange.

"I know what you're thinking," Marcus says. "Shouldn't lower price mean higher win rate? An easier sale? Let me explain that ratio notation carefully, because it trips everyone up."

He points to the win rate column. "A win rate written as a ratio — one in three, one in five — tells you how many qualified opportunities you convert. 'One in three' means you win one out of every three qualified deals. That's a thirty-three percent win rate. 'One in five'? That's twenty percent. So a bigger second number is a lower win rate, not a higher one. One in one hundred is the worst on the board."

He circles the perpetual license row and the freemium row.

"Now here's the part I want you to get exactly right, because most people remember it wrong. As you move from ownership toward freemium — top to bottom of that table — your win rate does not rise and then fall. It declines steadily, and then it collapses at freemium. Perpetual license is one in three. Annual subscription is one in five. Freemium is one in a hundred. Straight down, then off a cliff."

"But why?" you ask. "Lower risk for the buyer should mean easier closes."

"It should," Marcus agrees. "That's the paradox. Lower buyer commitment does two things to you. One, it invites more competitors — a free or cancel-anytime offer is trivial for anyone to copy, so more vendors pile into every deal. Two, it floods the top of your funnel with tire-kickers. When signing up is free, a thousand people click 'yes' and nine hundred and ninety-nine of them were never going to pay. Revenue Architecture calls freemium's one-in-a-hundred the 'high friction of monetizing a free user base.' So a low win rate isn't a sign you're bad at selling. It's a measurement of how hard it is to convert an opportunity as buyer commitment falls away."

He taps Northwind on the folder.

"Your company lives in the annual and multi-year subscription zone. One in five qualified deals — maybe one in four if you're sharp on the use case. Now here's the mistake that quietly kills companies, and Revenue Architecture literally calls it 'Mistake number one': applying the wrong model's win rate to your pipeline."

He draws a pipeline column.

"A perpetual license deal at one in three needs a three-times pipeline. But a twenty-four-thousand-dollar annual subscription has a win rate closer to one in five — call it a 1.5 ratio — and needs a five-times pipeline. If you budget your pipeline on the ownership number, you are systematically underfunding it. So when you lose, you blame price. It's not price. It's that you never had enough qualified deals flowing in to begin with — and you can't make it up on volume the way a freemium product does. You have to win on impact. Hold that thought; it's the whole back half of this conversation."

"That's..." you start, then stop. "That's not wrong."

"It's not," Marcus says. "One more piece before we get to Meridian. You've got to know the difference between recurring and re-occurring revenue. Recurring revenue is predictable, on a fixed schedule — your annual contract billed on the same date every year. The market pays a premium valuation for that, because it's reliable cash flow. Re-occurring revenue happens again and again but unpredictably — support contracts at irregular intervals, sporadic usage, advertising insertion orders. The market punishes companies that get caught classifying re-occurring revenue as recurring. So if Meridian's contract is truly annual — same amount, same date, contracted renewal — that's a genuine recurring-revenue asset, and it's worth defending."

He caps the marker.

"That's the map. But you're probably wondering how the one-hundred-and-eighty-thousand number on the Meridian quote even got picked — and why I'll fight you before you knock twenty-five percent off it. Pour another cup. That's the next part."

Act Two — The Math: How the Number Gets Set, and Why You Defend It

Marcus sets down his coffee. The whiteboard still shows the win-rate ladder.

"Okay. Before you ever quoted Meridian one hundred and eighty thousand a year, let's talk about how that number even gets set. And more importantly, how you defend it when Dana Okafor's team comes back saying, 'we can build the same visibility in-house for eighty thousand.'"

He pulls out a worn chart.

"Here's the brutal truth from Revenue Architecture: pricing and packaging is the first revenue breakpoint every company hits on the growth curve. Before you're founder-led. Before your sales process scales. Before any of it. And most companies treat it like an afterthought."

He draws a box labeled "PRICING & PACKAGING."

"In the early days, everyone dabbles. A little upfront equipment fee. Some re-occurring training support. Maybe a meter on usage. That's fine at five hundred thousand in annual recurring revenue — you're experimenting. But here's what happens: you carry that mix all the way up, and suddenly you've got monthly subscribers and annual contracts and multi-year deals and a freemium tier from years ago nobody wants to kill. Sales gets confused. Finance can't forecast. Customers see three pricing pages and don't know which one is for them. Revenue Architecture is blunt about it: you do not want to carry a 'let them try it monthly for a couple of months' structure all the way to a hundred million in annual recurring revenue."

He taps the board. "So, decision one: keep pricing simple. Decision two: pick whether the business runs on monthly recurring revenue or annual recurring revenue. That's independent of the contract term — you can sell annual contracts and still recognize the revenue monthly for accounting — but you need one anchor."

He slides another chart across.

"Decision three: refund policy. Write it down. What happens if a customer wants out five months into a twelve-month contract? Sixty days? Never? It sounds cynical, but transparency builds trust, and most companies don't have it written down — which means every renewal becomes a negotiation instead of a rule."

He sips his coffee.

"Decision four: multi-year revenue recognition. If Meridian signs a three-year deal, do you book the whole thing up front, or recognize it annually? It changes your financial reporting and how fast you look on a growth chart. We'll come back to it, because Meridian is going to push for a multi-year at a discount — and you need to know what you're doing before they do."

He draws a table.

"This might be the most important table in Revenue Architecture, because it's not just price — it's the motion that earns that price. The book puts it perfectly: treating a hundred-dollar deal like a hundred-thousand-dollar deal burns money, and treating a hundred-thousand-dollar deal like a hundred-dollar deal loses the deal. Meridian at one hundred and eighty thousand sits squarely in Dedicated Touch. Which means a consultative, impact-led process — the real conversation with Priya and Dana — not a price war."

He leans forward.

"And here's how people wreck this: they understand the table intellectually, then run the same motion across all five tiers. Self-serve customers get white-glove onboarding; enterprise deals get pointed at a community forum. It doesn't work economically. One product can span small business to enterprise — but each segment needs its own motion and its own pricing and packaging."

He slides his cup aside and pulls the next chart.

"Now the economics. This is the whiteboard that lets you defend one hundred and eighty thousand when Dana pushes back."

He draws a long horizontal flow, like a factory line with multiplication signs between the stages.

"This is the growth formula. Think of a go-to-market motion as a recurring-revenue factory. Inputs on the left — visitors, leads, qualified opportunities — run through conversion gates. Each gate multiplies the flow. The output is annual recurring revenue. Here's a real worked example from the book."

253 visitors × 0.12 × 0.15 × 0.845 × 0.26 × 0.767 × $24,000 list price = $18,408 in annual recurring revenue

"Two hundred fifty-three visitors. Twelve percent become leads. Fifteen percent of those get interested. It funnels down through qualification and a roughly twenty-six percent win rate, the price gets cut by a twenty-three percent discount — that's the 0.767 — and you land at eighteen thousand four hundred and eight dollars from that slice of the motion."

He circles the whole equation.

"Here's the insight: this is a product, not a sum. Everything multiplies. So a five percent drop across all of those conversion rates doesn't cut revenue five percent. In the book's scenario it cuts it forty-one percent — from eighteen thousand four hundred down to ten thousand seven hundred and fifty-nine. The math is nonlinear; one bottleneck cascades through the whole system. And it cuts both ways — small improvements compound just as hard."

He taps the page.

"And this is the punchline for your Meridian negotiation. See that list price? In the formula you multiply it by the discount term — one minus the discount. A ten percent discount means you multiply by 0.9; twenty percent means 0.8. Because it sits right next to list price in the multiplication, cutting price is mathematically identical to cutting win rate or throughput. A discount isn't a one-deal margin nick. It's a cascade. Which means you can test a discount on the whiteboard before you ever offer it — the book does exactly this, asking what would have to be true to drop a twenty-three percent discount and keep the same revenue. You quantify the trade instead of guessing."

He turns to a fresh page.

"Now, why I fight so hard before accepting a discount. From the book: a customer acquired at eighteen thousand four hundred in annual recurring revenue generates a five-year lifetime value of one hundred and six thousand nine hundred and nine dollars. Sounds great. But only seventeen percent of that — the first eighteen thousand four hundred — lands in year one. The other eighty-three percent depends entirely on retaining and growing them over five years. So when you discount at signing, you're not giving away one year of margin. You're compounding that discount against a five-year base. And if they churn in year two instead of staying five years, that discount just tipped the whole thing unsustainable."

He draws three diverging lines, labeled Ownership, Flat Subscription, and Subscription with a 10% annual increase.

"This is the wealth engine — and it's why Jacco van der Kooij, the author of Revenue Architecture, built a career around price escalation. Ownership is a one-time two-thousand-dollar sale: flat, no growth. Flat subscription at two thousand a year: linear — each year adds another two thousand. But subscription with a ten percent annual increase? That's exponential. By year five the exponential curve has separated so far from the linear line it's not close — about ninety percent more revenue than the flat subscription. Recurring revenue plus price escalation is the ultimate wealth-building model — but only if customers stay and value keeps growing."

He taps the board.

"Netflix from 2007 to 2023 is the real proof. Those price hikes everyone grumbled about weren't random — they were tiering plus gradual increases plus new monetization, like advertising in 2022. It looks scattered. It's actually an exponential price architecture. That's why Northwind built a roughly ten percent annual escalator into the Meridian contract. Defend the list price, and the escalator does the compounding."

He pulls one more chart.

"And this is the sustainability math — the Chief-Financial-Officer-grade argument for discipline, the one that wins Dana over."

"A go-to-market motion is sustainable when total cost stays at or below twenty percent of cumulative revenue over a defined horizon — five years for platforms like Northwind, three for applications, twelve months for plug-ins. In the book's example, amortized over a five-year lifetime value of three and a third million dollars, total cost is fourteen point three percent. Sustainable. But watch — if that customer churns in year two, the denominator shrinks and the ratio jumps to twenty-six point six percent. Unsustainable. The rule of thumb: under twenty percent is sustainable; twenty to fifty percent needs a path back; over fifty percent is bleeding. So a deep discount is never 'just one deal' — because acquisition cost is high and value is deferred, it can tip the entire motion past the line."

"One last metric so you don't fool yourself," he adds. "Gross retention rate versus net revenue retention. Gross retention rate excludes expansion — it's the true durability signal, and targets run from about eighty percent for No Touch up to ninety-eight percent for Dedicated Touch. Net revenue retention is gross retention multiplied by expansion, and it can be inflated by price increases even while real retention rots underneath. So watch gross retention to know whether customers actually value the product, independent of your price hikes."

He gathers the charts back.

"Quick tour of how companies blow all this. One: applying the wrong model's metrics — the pipeline mistake from before. Two: changing the monetization strategy mid-flight — monthly to annual, product-led to enterprise, adding a subscription beside a hardware business. Those are 'phase shifts,' and they take years. Adobe's perpetual-license-to-subscription transition took more than three years, and subscription revenue only passed license revenue in 2014; executive turnover mid-transition is devastating. Three: running too many models at once — annual plus monthly-trial plus metering plus on-premises — defensible only during a time-boxed transition, never forever. Four: confusing recurring with re-occurring revenue, which inflates valuation until the market discovers it and craters you."

He slides the folder back to you.

"You know the map and the math now. You can price a discount before you offer it, you know one hundred and eighty thousand isn't arbitrary, and you know the escalator is doing real work. Let me show you how the Meridian deal should actually run — from the very first conversation with Priya."

Act Three — The Deal: Running Meridian from the First Call

Marcus draws a vertical line down the middle of a fresh sheet.

"This is where most deals die. You've got Priya excited; you know she feels the pain. Now you have to run the whole thing properly — from the first real call. And that means SPICED."

He writes it vertically: S / P / I / CE / D.

"Situation. Pain. Impact. Critical Event. Decision. In that order. It's not a checklist — it's causal. Situation and Pain are the causes. Impact is the effect. And Impact is what drives the Decision. Miss any piece and the deal collapses."

The first call with Priya.

"What do I ask her first?" you say.

"Two or three Situation questions. Background. You're peeling an onion — outer layer first. What does Meridian move, how many lanes, what are they using today, tell me about the retail account that just came online. Don't dump product on her. Listen. Take notes."

"Priya tells you: about five hundred shipments a week across North America, spreadsheets and phone calls plus one old point solution from the incumbent, and yes — they just landed a major retailer whose contract runs through peak season with brutal penalties for late delivery."

He leans back. "Now you shift to one or two Pain questions. Not 'do you have a problem' — you know she does. You ask, what happens when a shipment is late? And you really listen. She says something like, 'we get dinged, the retailer withholds payment, sometimes we reroute at cost.' That's surface pain. So you go deeper — how often, and what does it cost you? The book says it can take as many as seven questions to reach the real impact. You're peeling, looking for the number."

He circles the Pain box. "And the number lands: about forty thousand a month in demurrage and detention, plus twenty-five thousand a month in at-risk contract revenue, because if they miss windows the retailer applies holdbacks or walks. Sixty-five thousand a month. Seven hundred and eighty thousand a year."

The summary, and the platform.

"Now a moment that changes everything: you summarize back. So Meridian runs five hundred shipments a week on spreadsheets and old software, you just landed the retail account with penalties on missed windows, and right now you're bleeding forty grand a month in demurrage plus twenty-five in at-risk revenue. Did I get that right?"

"Priya confirms. But you don't pitch yet — you empathize. I hear this a lot; you're not alone. Then you tell a story — the 'man in the hole' arc. A similar customer, call them Apex Freight: part one, their situation, just like Meridian's. Part two, what happened when they did nothing — penalties mounted, the relationship strained. Part three, after they got visibility live before peak season — penalties stopped, revenue protected. The story isn't about you. It's about them, and it anchors Priya to the idea that this is solvable and that it matters."

The Critical Event.

"Now the move that separates winners from the field. You ask, when do you need this live? And Priya has to answer: before peak season — the first quarter is here, we need it live in about six weeks. Then you ask the second question: what happens if you don't have it by then? And she says, penalties start day one; the retailer doesn't care if we're ready; we could lose the account."

He taps the board. "That's your Critical Event. You didn't create it — you discovered it. It flips her priority from nice-to-have to must-have-by-a-date."

"Meridian just moved from Level 4 to Level 2. Priority is a function of impact over time — and a deal that 'goes dark' usually hasn't lost its budget, it's lost its priority. A critical event brings it back. That changes deal velocity, the buying center's attention, and yes, the price conversation."

The Critical Event Timeline.

"Before you leave that call, you build the Critical Event Timeline — working backward from the moment she gets impact, not from your signature date."

"A handful of tasks, anchored to her success. You send a short email after the call: here's what I heard, here's when you need to be live, here's the critical path — does this match your thinking? You're not imposing a timeline, you're confirming one. And if dates slip later, you pull out that email and everyone realigns."

The buying center: who decides what.

"Meridian isn't just Priya. The book says enterprise decisions run through as many as nine roles — Initiator, User, Champion, Decider, Gatekeeper, Influencer, Executive Buyer, Approver, Purchaser — and in a smaller company one person wears several hats. Here's your cast."

"Here's what kills deals: you sell Impact and the business case to Priya and Dana, then let Tom run the close on price alone. Tom doesn't care about the twenty-five thousand a month in at-risk revenue — his job is to squeeze your price. So he says, 'twenty-five percent off or we walk,' and you cave. But Tom doesn't have the full picture. Dana does. So instead of letting Tom negotiate in a vacuum, you arm Priya to sell internally. The book even gives you the buyer's own words for the close: 'help me sell this internally and make a trade-off to match my budget.'"

The decision-criteria reframe.

"This is the killer move." He sketches a table. "The traditional way: the buyer stack-ranks criteria — price, performance, integration, support — and optimizes on price, because it's the biggest, scariest number."

"Now you flip it. You quantify the business impact of each criterion and re-rank by that."

"Performance rises to the top. Price sinks to the bottom. Why? Because a few hundred dollars a month in cost is trivial against thousands a month in new and protected revenue. Revenue Architecture studied more than fifty thousand deals and found that reps who positioned against the customer's Impact sold fifty-three percent more on average. That's not opinion — that's data. The salesperson who demonstrates impact across these criteria a dozen-plus times a week becomes the expert who shapes the decision. That's you, educating Dana on why Performance matters more than Price."

Arming the champion, and the emotional thread.

"So you pull Priya aside and give her the language: this isn't about spending one hundred and eighty thousand a year — it's about protecting sixty-five thousand a month you're bleeding right now, before penalties start on day one. The negotiation isn't the price; it's the speed. Now when Tom says 'twenty-five percent off,' Priya can tell Dana: 'this is a sixty-five-thousand-a-month impact — the cost isn't the issue, getting live by May 28 is.'"

"And there's one more person: Marisol, who'll actually use it every day. Priya feels the business impact and Dana evaluates the financial case, but emotional impact is just as powerful. The book splits it: rational impact benefits the corporation — revenue up, cost down, risk down — and emotional impact benefits the individual — ease of use, less stress, confidence she won't miss a date. So early on you get Marisol in a demo and you show her workflow, not your product: the single dashboard, the alert twenty-four hours before a delivery slips, the phone app from the warehouse floor. And here's the quiet magic — emotional impact follows the laws of habit formation. Once Marisol relies on seeing everything in one place, it gets harder to leave the longer she uses it. That's a switching cost. And a switching cost is also a price justification — people don't abandon software they love, even when it costs a little more."

Marcus leans back with a knowing smile.

"So you've run discovery, uncovered the sixty-five-thousand-a-month impact, told the story, mapped the timeline backward from May 28, armed Priya, won over Marisol, and worked integration with Raj. Dana's nodding. You're three weeks in. Then an email lands."

He mimes reading his phone: "Appreciate the proposal. Great product. But we can't land one hundred and eighty thousand without a discount. Can you do twenty-five percent off? Otherwise we move to the alternative vendor — they're at one thirty-five and already in our stack. Let me know by Friday. — Tom."

He puts the phone down and grins. "And that's where most people cave."

He leans forward. "Here's where you don't."

Act Four — The Close, and the Back Half: Trade, Don't Discount

You read Tom's email and look up at Marcus, who is grinning — actually grinning.

"This," he says, tapping the marker, "is where you do not cave."

"But twenty-five percent off is—"

"A demand. So treat it like a trade instead." He starts fresh. "From The SaaS Sales Method: reframe negotiation as trading — both sides give up something of value so both are better off. The data is striking — sellers who trade instead of haggling on price alone take average discounts from above twenty percent down to below ten. You protect margin, and you walk away with things worth far more than the percentage."

He draws a box.

"Step one of the trade framework: know the person. Tom is procurement — measured on savings, not on whether the software works. Dana, the Chief Financial Officer, is the actual decider; she cares about the seven hundred and eighty thousand a year of impact at stake. Step two: understand their situation, impact, and critical event — Meridian must be live before the first-quarter peak season, the incumbent auto-renews in six weeks, and the software protects sixty-five thousand a month. That desperation is your leverage, not a reason to cut price. Step three: prepare your trade items and the value of each before the call — and notice every item on that chart has a real number attached, not a wish."

He keeps writing.

Step 4 — CLARIFY every element of the offer.
Step 5 — SET all negotiable items on the table at once: price, term, setup fee.

Step 6 — REPEAT / ASK:
  "So if I've got it right, you want a better annual number, the option
   to expand to freight forwarding later, and confidence there's no
   downtime during peak. Anything else?"

Step 7 — PRIORITIZE:
  "What matters most — the price, or locking it in for two years?"

Step 8 — CONFIRM AUTHORITY (before you offer):
  "If we agree on price, term, and expansion, can you and Dana decide
   by end of day Friday?"

Step 9 — MAKE THE OFFER, then LISTEN and REPEAT the counter back.

"Step eight matters more than people think: never give your best price to someone who can't say yes. You've already confirmed with Priya that if you and Dana agree, Dana can sign before quarter-end. Good. Now you make the offer once, clearly."

THE OFFER
  • Eighteen thousand off year one — a real, genuine concession (not 25%)
  • Two-year term, with the ten percent annual escalator intact
  • Public case study with Meridian's name and metrics
  • Marisol commits to one reference call for your next enterprise deal
  • At month nine, Meridian pilots the software in freight forwarding

  Effective discount across the whole deal: about 8%.
  You save forty-plus thousand a month in detention. You're protected
  at renewal. We're locked in together for two years. Everyone wins.

"You don't negotiate down from twenty-five percent. You change the conversation. Tom wants price; Dana wants certainty; Priya wants the expansion unlocked; you want the case study and reference because they turn one deal into a revenue multiplier. You trade across all of it at once."

"And you do not grind extra rounds. Remember the math from Revenue Architecture: win rate is an inverse exponential of meeting count — the per-meeting conversion rate raised to the power of the number of meetings. An enterprise deal runs about twelve meetings at roughly ninety percent conversion each. When average meeting counts rose from twelve to sixteen in early 2023, win rates collapsed from thirty percent to eighteen. Every extra round erodes conviction — fear-of-messing-up beats fear-of-missing-out, and the deal decays instead of progressing. So: all items on the table, confirm authority, make the offer once, then listen and repeat the counter back. Two rounds, maybe three if Dana has to brief her board. Not six. The critical event — peak season, the incumbent auto-renewal — is your time border. Don't let the deal drift."

The call, and the buyer's words.

"You call Dana directly — not Tom — and you run it with discipline the book calls TALKER: Tone, Ask, Listen, Keep notes, Elaborate, Repeat. Open-ended questions. Listen for what matters emotionally and rationally. Repeat the counter back so nothing's misheard — that one habit is how you avoid conceding to a demand you didn't actually hear. The book frames the close from both sides: the seller's view is 'the discussions as the customer prepares to commit'; the buyer's view is 'help me sell this internally and make a trade-off to match my budget.' Dana is literally telling you she expects a trade, not a giveaway."

"So you ask her what matters most — the annual cost, or certainty the platform won't go down at peak. She says, honestly, both: price matters to her board, but they cannot afford a failure during peak season. Boom. That's your opening. You build a package that addresses both — the two-year term for cost predictability, an uptime commitment for peak, the month-nine expansion if it delivers, and the public case study because that story helps other logistics companies. Tom, listening in, hears you offering a solution, not a discount. He gets something; Dana looks good to the board; Priya looks good to her team."

The close, and the flip.

"The call happens the next morning. You lay out the package — eighteen thousand off year one, two-year term, case study, reference, month-nine expansion pilot — an effective discount of about eight percent once you model the escalator and the two-year economics. Dana asks one question: can you guarantee uptime? You say: ninety-nine point five percent on your platform tier, plus a dedicated infrastructure engineer through peak season starting in December — because your critical event is peak season, and we're building the contract around you winning it. Tom winces; he wanted more. Dana leans in: 'if we sign by Friday, that's the deal?' Yes. She nods at Tom. Tom, grudgingly, nods back."

"You call Priya: closed at eight percent effective, not twenty-five, with the freight-forwarding expansion teed up for month nine. She says, 'that's the margin we need — when does setup start?'"

"And here is where it flips. The instant the contract is signed, the relationship moves from across the table to the same side of the table. That's not a feeling — it's operational. The book calls it Handoff, Redo, Kick-off."

HANDOFF (first week)
  Sales stays involved — "continue through the ball, don't swing at it."
  Short, frequent updates. You don't vanish after signature.

REDO (week one or two)
  Revisit ALL the deal details with the buyer — not just impact and
  critical event. Set up a three-on-three:
    Your team:  Account Executive (you), Solutions Engineer,
                Customer Success Manager
    Their team: Priya (Vice President of Operations),
                Raj (Information Technology director),
                Marisol (Operations Manager)
  Re-confirm what was promised, how you'll measure it, and what
  success looks like at month three, six, and nine.

KICK-OFF (week three)
  A welcome (maybe the t-shirts). Build the impact-journey timeline:
    Month 1  — live with the first workflows
    Month 3  — measure impact: has detention dropped?
    Month 6  — prepare for peak season
    Month 9  — expand into freight forwarding
    Month 18 — renew early and extend the term
  Set the cadence: weekly operations sync, a MONTHLY impact report,
  a quarterly business review with Priya and Dana.
  Set alerts for risks (a support spike) and opportunities
  (detention falling, the retailer extending its contract).

"If the Redo doesn't happen — if you treat signature as 'hand it off and disappear' — the customer feels abandoned and the expansion dies. You stay involved and re-confirm the impact that justified the price you agreed to."

The back half — where the real money is.

"Now the part most people miss. At scale, the vast majority of a company's revenue is in the installed base. Meridian is just the start. There are three growth engines: acquisition — winning Meridian — renewal, and expansion. Watch what expansion does."

"A business starting at two million in annual recurring revenue, with full renewals, doubles on acquisition alone. But add just twenty percent net expansion from the base and the math jumps — year two becomes six point four million, year three thirteen point seven million: two hundred twenty percent growth, then a hundred fourteen percent. That's what compounds a company from two million toward hundreds of millions. Not discounts. The installed base. As the book puts it: customer success is not a cost center; it is a revenue engine."

He draws the quadrant.

"Every customer lives in this two-by-two. For Meridian: Renew — same benefactor, same impact — owned by Customer Success. You renew early, at month eighteen of a two-year deal, extend the term to three or four years, and apply the ten percent increase — and you do it on impact achieved, not usage. Your monthly impact report keeps the score: 'this month you prevented nine hundred twenty thousand dollars in detention; the industry benchmark is eight hundred thousand — you're above it.' That's proof, not a feature list, and it's why the renewal isn't a renegotiation."

"Upsell — same benefactor, new impact: predictive alerts for the retail customer, a new capability, owned by Sales or Account Management. Resell — new benefactor, same impact: that's the month-nine freight-forwarding expansion, committed at signature. You bring the metrics from the logistics team — 'we saved you forty thousand a month; your freight forwarding team has the same problem' — for about sixty thousand a year. Don't wait for them to ask; you own that pipeline. Cross-sell — new benefactor, new impact: a whole new product line. Lower priority, but it's there."

"And expansion isn't 'you bought fifty seats, buy more.' The book calls it impact-based whitespace: 'you're getting impact A and B — here's how to unlock C.' Map which impacts each customer actually extracts, and sell into the empty spaces. One more time, because it matters: watch gross retention rate, not just net revenue retention, so your price increases never mask churn underneath."

The final napkin.

Marcus pulls a clean napkin from under his cup and sketches.

THE WHOLE ARC, ON ONE NAPKIN

1. ARCHITECT THE PRICE
   Build it on impact (~$780k/year benefit vs ~$180k cost),
   plus an annual escalator to protect long-term margin.

2. DIAGNOSE THE IMPACT
   Find the real number ($65k/month) and the critical event
   (peak season, retail penalties, incumbent auto-renews).

3. FRAME IMPACT AS THE CRITERION
   Not "our price is fair" but "your impact is this big —
   the price is small against it." Price sinks down the list.

4. TRADE, DON'T DISCOUNT
   All items on the table at once. Confirm authority first.
   Trade an ~8% effective concession for a two-year term, a
   case study, a reference, and a committed expansion.

5. EXPAND THE BASE
   Renew on impact, upsell new impact, resell to new units,
   cross-sell new products. Year 1 is $180k; year 3 is far more.
   Acquisition is the beginning. Expansion is the business.

He slides it across.

"Pricing isn't a negotiation," he says. "It's a reflection of the value you create. You got Meridian right because you diagnosed the impact, framed it as the criterion, and protected the price by trading for things worth more than the discount. Now go deliver that impact and expand them relentlessly — because the deal isn't done at signature. It's done at renewal, when Meridian signs again, at a higher price, because the software saved them half a million dollars."

He raises his cup. "Go close it Friday."

Where Every Idea Comes From

So you can go back to the source — all three books are by Winning by Design.

• Pricing is architecture; the six layers; the Ownership → Subscription → Consumption arc; the responsibility matrix; the win-rate ladder and the "declines then collapses" paradox; recurring vs. re-occurring revenue; "Mistake number one" (wrong-model metrics); the mid-flight / too-many-models / misclassification mistakes — Revenue Architecture, Chapter 5 (The Revenue Model, and its Implications & Warnings).
• The "7.5×" pricing quote (from Price Intelligently); Breakpoint 1 — Pricing & Packaging; keep-it-simple, monthly vs. annual recurring revenue, refund policy, multi-year revenue recognition; matching the sales motion to the annual contract value; the growth stages — Revenue Architecture, Chapter 9 (The Growth Model).
• The growth formula; the 5% → 41% non-linearity; the discount-as-multiplier; 83% of lifetime value deferred; price escalation as the exponential wealth engine; the Netflix example — Revenue Architecture, Chapter 7 (Growth Formula & Unit Economics).
• The 20% sustainability rule; the three cost centers; gross retention rate vs. net revenue retention — Revenue Architecture, Chapter 10 (Sustainability in Go-To-Market Motions).
• The SPICED framework (Situation, Pain, Impact, Critical Event, Decision); the 53%-more-impact study; the four priority levels and "priority is a function of impact over time"; the Critical Event Timeline; the nine buying-center roles; the decision-criteria reframe (quantify each criterion's impact so price sinks) — Revenue Architecture, Chapter 8, and The SaaS Sales Method, Chapter 5 (Moments That Matter).
• Trade, don't discount (the nine-step Trade framework; >20% → <10%); the buyer's-view of the Close; the TALKER conversation discipline; Handoff → Redo → Kick-off; the monthly impact report; the Renew / Upsell / Resell / Cross-sell growth quadrant; renew-early-and-extend — The SaaS Sales Method, Chapter 6 (Blueprints).
• The three growth engines and how 20% expansion compounds; impact-based whitespace; win rate as an inverse exponential of meeting count — Revenue Architecture, Chapter 8.3 and the Annex.