Anatomy of a Close · #07 · ~4 min read
Why I Build the Solution Before I Build the Deck
Anatomy of a Close — #07 of an ongoing series.
The big-money B2B e-commerce deals I closed at WEBSE didn't start with a deck. They started with a real answer to a real question about what the buyer actually needed — and the deck, if there ever was one, got built to describe a solution that already existed, not the other way around.
The default order, and why it's backwards
The normal sequence is: build the deck (or the standard package) first, then go find people to fit it. It's efficient to produce and it scales — one deck, many prospects. It also means the thing you're presenting was designed before you'd met the person you're presenting it to. At best it's a close fit. At worst you're stretching a generic template over a specific problem and hoping the seams don't show.
The order I actually use
Ask first. Actually build second. By the time I'm describing a solution, it's not a menu item — it's something assembled specifically around what this buyer told me, in this conversation, about this problem. Sometimes that means the shape of the deal looks different than the last one I closed. That's not a bug in the process. That's the process working.
Why buyers respond to this differently
A generic pitch, however polished, reads as a pitch — something built in advance, delivered regardless of who's in the room. A solution that visibly traces back to something the buyer said ten minutes earlier reads as attention. Buyers can tell which one they're getting, even when they can't articulate why one feels different from the other. That difference in feel is often the entire gap between "let me think about it" and "let's move forward."
What this costs, honestly
This is slower than running a fixed pitch. It takes longer to build a response than to recite one, and it means every deal takes real thinking instead of a rehearsed sequence. That cost is real, and it's also the reason most reps default to the deck-first order — not because it's more effective, but because it's easier to repeat. The custom version wins more often. It also asks more of you every single time.
What "the deck" becomes once the solution already exists
Once the real solution has been built around what the buyer actually said, the deck stops being a sales tool and becomes something closer to a summary — a document that describes a decision that's functionally already been shaped in conversation. It's shorter. It has fewer generic claims and more specific detail, because it's not trying to persuade in the abstract anymore; it's confirming something the buyer already recognizes as theirs. Some of the strongest B2B conversations I've had barely needed a deck at all by the time we got there — the solution had already been talked into shape, and the document just made it official.
How this changes the negotiation itself, not just the pitch
A negotiation over a generic package is a negotiation over discount — the only lever available is the price, because the offering itself is fixed. A negotiation over a custom-built solution has more surface area: scope, sequencing, what's included in phase one versus later, which parts of the problem get solved first. That's a fundamentally different, and usually less adversarial, conversation. Instead of two sides pulling on one number, you're jointly shaping a thing that doesn't fully exist yet — which tends to produce a buyer who feels like a collaborator in the deal rather than an opponent across from it.
The discipline that keeps custom from becoming over-promising
The obvious risk of building solutions on the fly is promising something you can't actually deliver, in the moment, to close the room. The discipline against that is simple to state and harder to hold to: never describe a piece of the solution you haven't actually confirmed is buildable. If I'm not sure something's possible, I say "let me check on that" instead of nodding it into the pitch. Custom-built trust is expensive to earn and cheap to destroy — one overreach discovered later costs more credibility than the deal was worth.
The honest caveat
Building custom doesn't mean building unlimited. Some needs genuinely don't fit what you can deliver, and the honest move there is to say so plainly instead of stretching a solution to close a deal that shouldn't close. The point of this method was never "find a way to say yes to everything." It's "build the real answer to what was actually asked" — and sometimes the real answer is that it's not a fit yet.
Previously: reading the room before the room knows you're reading it
Next: the difference between rapport and performance