Selling AI to people who have been burned by AI

The market has a memory. After three years of vendor promises that collapsed on contact with reality, automations that broke under edge cases, "AI copilots" that required a junior engineer babysitting them full-time, pilots that lit up in demos and died in production, buyers have developed something that most sales teams treat as an obstacle. I think it is one of the most valuable raw materials in enterprise GTM right now: genuine, hard-won skepticism.

I run revenue at Devlyn, an AI-native engineering company. We sell technical delivery: senior engineers who work with AI tooling the way a craftsman works with a better set of tools, faster, yes, but with the same judgment and accountability. When I stepped into the CRO seat, the dominant wisdom in our space was to lead with AI's transformative potential. Speak to the board-level pressure. Promise acceleration. Show a demo. Close.

I tried a version of that posture for about six weeks. It produced a lot of second meetings and almost no signed contracts. When I actually listened to what prospects were saying, not the polite version they gave our AEs, but the unfiltered version that came out in the third conversation when trust had built up, the pattern was unmistakable. They had been burned. Not once. Repeatedly. And they had gotten good at sniffing out the same story being repackaged with a newer model name in the headline.

The instinct for most revenue leaders facing skepticism is to sharpen the pitch. Better slides. Stronger case studies. A more compelling ROI calculator. I went the other direction. I started leading with what we would not claim. That pivot changed everything.

Why demos lie by omission

The standard enterprise software demo is a controlled environment, a curated data set, a pre-seeded workflow, a deliberate avoidance of the edge cases that will make up forty percent of your buyer's actual use. AI demos amplify this problem by an order of magnitude. The model performs beautifully on the representative input. It hallucinates, drifts, or refuses on the inputs that reflect the buyer's real messy world. The buyer in the room doesn't see the messy world. They see the clean one. They sign. Three months later, they are that company, the one that burned the next buyer.

This is not malice in most cases. It is incentive structure. The person building the demo is optimizing for the meeting. The person who will own the implementation is not in the room. The gap between those two realities is where trust dies.

When I redesigned our sales motion, I insisted that every technical discovery call include the engineers who would actually work the account, not a solutions engineer performing delivery, but the people who would be in the code. This costs more in labor per deal. It closes at a significantly higher rate, compresses the post-close surprise curve, and produces clients who refer us without being asked. The math works.

The burned buyer's actual objections

Burned buyers rarely tell you directly that they don't trust you. They tell you adjacent things. "We're moving slowly on this." "We need more stakeholder alignment." "Can you send over references from clients in our exact vertical?" These are not bureaucratic speed bumps. They are diagnostic signals. The buyer is asking: Are you going to be the fourth vendor who overpromised?

When I trained our team to hear skepticism as a question rather than resistance, the entire conversation changed. Instead of overcoming objections, we started answering the real question underneath them. The real question is almost always some version of: "How do I know this will actually work in our environment, with our data, under our constraints, for our team that doesn't have the bandwidth to manage a vendor relationship that breaks?"

That question deserves a direct answer, not a case study. The case study is about someone else's environment. The direct answer is about yours. So we started saying: "We don't know yet. Here's the scoped pilot that tells us both."

A scoped pilot with defined success criteria is not a concession to a difficult buyer. It is the correct product. It forces specificity on both sides. It surfaces integration complexity early, when it is cheap to address. It builds the reference relationship that every subsequent deal in that vertical depends on. The pilot is not a trial period for the buyer to evaluate you. It is the period in which you both learn whether the engagement makes sense.

Lead with what you will not claim

Our go-to-market copy, our AE scripts, and our executive conversations now all open with constraints rather than promises. Verbatim: We won't oversell AI. We won't promise fantasy timelines. We won't trade quality for speed.

The first time I put that language in front of a skeptical CTO, he stopped me mid-sentence and asked me to repeat it. Not because it was unusual language in a vendor conversation, it was unusual because it sounded like something he would say to us rather than something we would say to him. That moment of alignment, when the buyer hears their own internal voice coming back at them from the vendor, is the beginning of a real commercial relationship.

This posture creates a specific kind of disqualification, and that disqualification is a feature. Buyers who need a vendor to validate a fantasy timeline, because they've already sold the board on an unrealistic schedule and need someone to co-sign the fiction, will not choose us. That is correct. We cannot deliver on a fantasy timeline without doing what every other vendor has done: overpromise, underdeliver, and add to the market's skepticism that then makes the next sale harder for everyone. The deals we turn away by being honest about scope protect the deals we keep by being honest about scope.

This is laid out in more depth in Selling AI to the Burned: Points of View, Volume I, which collects a year's worth of practitioner observations from revenue leaders navigating this exact posture shift. The through-line across all of them: constraint is a credibility signal when the market has been oversold.

Senior engineers only, and why that sentence closes deals

One of the cleanest differentiators in our pitch is also the simplest: Senior engineers only. No juniors hidden behind AI. We say this plainly, early, and we explain what it means in practice.

The AI hype cycle produced a specific pattern of vendor behavior: hire large numbers of junior engineers, buy them access to code generation tools, and present the output as senior-caliber AI-assisted work. The speed metrics can be impressive. The quality metrics, over time, are not. Burned buyers know this. They can often describe, specifically, the version of this pattern that failed them, the code that shipped fast and then required six weeks of remediation, the architecture decisions that got made at speed and then became the technical debt that blocked the next year's roadmap.

When we say senior engineers only, we are not just describing a hiring standard. We are making a claim about judgment. AI tooling amplifies whatever judgment it is attached to. A senior engineer using AI becomes faster without becoming less careful. A junior engineer using AI can produce volume that masks the absence of the underlying judgment. The client pays for speed in the short run and quality problems in the medium run.

The depth behind this distinction, what separates the CRO's read of the market from the CTO's, is something I have spent a lot of time thinking through in Revenue, Re-Engineered: What a CRO sees that a CTO can't. The short version: the CTO optimizes for technical excellence. The CRO has to optimize for the client's ability to trust, absorb, and advocate for the work. Those are not the same optimization target. Senior engineers help align them.

Ownership over hours. Outcomes over velocity.

The dominant pricing and value narrative in technical services for the past decade has been hours. Utilization. Time-and-materials. Even retainer structures are often mental-modeled as "how many hours am I buying." AI should be disrupting this entirely, and largely hasn't yet, because vendors found it easier to charge the same way and just produce more hours of output per engineer.

We price on outcomes. That is not a novel concept, but it is a genuinely rare practice because it requires the vendor to be willing to absorb scope risk, and it requires the client to be willing to define, specifically, what success looks like. Both sides find this uncomfortable. The vendor has been trained to protect margin through scope limitation. The client has been trained to protect scope through contract language. The result is contracts that are long on process and short on accountability for results.

The posture we take: Ownership over hours. Outcomes over velocity. We want to own something, a product function, a system, a transformation, and we want to be measured on whether it works. This is only possible when the senior engineer relationship runs deep enough that we actually understand the client's definition of working. Surface-level engagements cannot do this. They do not have the context.

The burned buyer, specifically, has often been burned on velocity. They were sold speed and got chaos. When we reframe value around ownership and outcomes, we are directly addressing the wound. We are saying: the thing that failed you was not that the previous vendor moved too slowly. It was that they moved fast in the wrong direction and nobody took ownership of the direction being right.

Building a repeatable playbook for the skeptical market

Here is what the CRO playbook actually looks like when you operationalize this posture, step by step, in a real sales process.

First conversation: No demo. Discovery only. The goal is to understand where the buyer has been burned and what their internal definition of "this actually worked" looks like. Most vendors skip this because demos are compelling and discovery is vulnerable, it requires admitting you don't know the answer yet. Skip the demo. Do the discovery. You will close more and lose less post-close.

Second conversation: Bring the technical lead. Not a pre-sales engineer, the actual engineer who would own the work. Let the buyer's technical team run the conversation. What comes out of that conversation is more valuable than any slide deck: you learn the real constraints, the political landmines, the prior failures that are still in the room emotionally. Your pitch in the third conversation is entirely shaped by what you learn here.

Pilot design: Define success in writing before work begins. Not vague success ("the system performs well") but specific and measurable ("the extraction accuracy exceeds ninety-two percent on the validation set we have both agreed on, within eight weeks"). Commit to it publicly. If you cannot hit it, say so before the pilot starts, not after. The burned buyer has heard "we'll get there" too many times. Written, specific, pre-agreed success criteria are the closest thing to trust in an early-stage vendor relationship.

Evals over promises: Where the work is AI-specific, build evaluations into the engagement from day one. Not as a QA layer at the end, as a continuous signal that the model is performing, that the outputs are in range, that the thing you promised is the thing being delivered. Evals are the AI-native equivalent of tests. They are also the antidote to the demo problem: the demo shows you the clean world, the eval shows you the messy one. Share them with the client. Transparency here is a competitive advantage because most vendors do not offer it.

Reference architecture: After a successful pilot, codify what worked into a reference architecture the client team can maintain and extend without you. This sounds like it reduces future revenue. It actually expands it, because the client trusts you with larger, more complex work when they know you are not creating dependency by hoarding knowledge. The burned buyer has often been burned by this too, by vendors who built complexity they could not explain, creating lock-in through obscurity rather than value.

The hype cycle analysis in First Principles for a Hype Cycle makes this case from a structural angle: markets that overshoot on claims always mean-revert to proof, and the vendors who are already operating at proof when the mean-reversion happens capture disproportionate share. We are in that mean-reversion now. The buyers who were burned are now the market. Selling to them honestly is not a moral posture, though it is that too. It is a correct reading of where the market is and where it is going.

The long-term structural advantage

There is a compounding dynamic that takes twelve to eighteen months to show up clearly but is decisive when it does. Honest vendors, operating on proof rather than promise, build a reference base of clients who were not oversold. Those clients become the most powerful sales asset in the market: they can describe, specifically, what worked and why, without qualification or asterisk. They can take a skeptical peer's call and say not "it was transformative" but "here is exactly what we measured before and after, here is the pilot structure we used, here is what broke and how they fixed it."

That kind of reference is not available to vendors who oversold and then heroically salvaged something. The heroic salvage story contains an acknowledgment of the original failure. The skeptical buyer hears the failure more than the recovery. The clean reference, from a buyer who was accurately sold, accurately delivered to, and never had to absorb a crisis, is the cleanest asset in enterprise sales. It is built only one way: by not overselling in the first place.

I have watched three years of the AI hype cycle from multiple seats, engineering leadership, operations, and now revenue. The pattern is consistent: companies that sold the fantasy got the early deals and are now managing a reputation problem. Companies that sold the proof got fewer early deals and are now managing a referral engine. The market is sorting. If you are reading this as a revenue leader trying to figure out whether to sharpen the pitch or to constrain it, the answer, in this market, in this moment, is to constrain it. The buyer who has been burned has a very sensitive instrument for detecting when they are about to be burned again. That instrument is not your enemy. It is the most honest feedback loop your sales process has access to. Trust it. Sell to it. Build a business that deserves to survive the hype cycle.

The burned buyer is not a hard buyer. The burned buyer is a buyer who knows what they actually need. Meet them there.