1Sales Team of One

Chapter 10

Closing Without Pitching

Get the next chapter by email — one email per new chapter, nothing else.

The Moment of Truth

Karen Walsh, the VP of Sales at Regional Home Lending, comes onto the Zoom with a different energy than Marcus has seen from her before. She has decided something and isn't telling him what yet.

"Marcus, I'll be direct. We want to move forward. But I have concerns, and I'm going to lay them out, because if I can't get past them, none of this matters."

"Lay them out."

"My CEO liked you. You know that; you were in the room." She says it as a small concession. "After the meeting, he called me and asked exactly one question. Nothing about your platform. He asked, 'What happens to the loan officers who won't use it?' Because the last two times we bought something like this, that was the story: a year of pain and a quiet mutiny." She keeps going. "IT is certain you'll promise a clean integration and hand us a six-month nightmare. They've earned that opinion. And my officers are tired of tools. Every quarter somebody sells us the future, and every quarter it's one more login they resent." She sits back. "I already believe you understand our business. That was settled a long time ago. What I don't know is whether I can get this through my own building without it becoming the third disaster. So talk to me."

Old Marcus would already be sharing his screen: the ROI calculator, the integration architecture, the slide that proves the concerns wrong. He can feel the reflex, and he lets it pass, because every one of those slides answers a question Karen didn't ask.

"You're right to worry about all three," he says. "Each one is a real way this fails." He lets that sit. "What would it take for you to feel confident recommending this to your CEO?"

Karen pauses. She wasn't expecting that.

"I need to know it won't be the third failure. That you'll still be here during the adoption, not just the signature. That when something breaks, and something breaks, you fix it instead of telling me it's a configuration issue on our end."

"What would that look like, concretely, so I can't wiggle out of it later?"

"A real implementation plan. Training my fifteen-year veterans won't roll their eyes at. And some way to find out this works before I bet my credibility on it."

Marcus nods slowly. He doesn't reach for the screen share.

"Then let's not bet your credibility. What if twenty loan officers ran it for sixty days, against numbers we write down together before we start? If it clears them, we expand. If it doesn't, you've lost sixty days instead of a year and I've lost the right to your business."

Karen's expression shifts.

"If some officers won't use it, you find out with twenty of them, not two hundred," he says. "And nothing touches the core system, so IT has little to object to."

"IT will anyway." She's quiet a moment. "What are the numbers we write down?"

He opens a document, not a deck but a one-page success definition. Three things on one page: how many of the twenty are still using it after thirty days, whether their contact with past clients actually goes up, and whether their client retention rate moves. Targets beside each, open to argument.

"And if we miss them?"

"Then we find out why, or we admit the VaultPath software isn't right for Regional Home Lending. I'll put that in writing too. If we can't agree on what winning looks like before we start, we shouldn't start."

They spend the rest of the hour on timelines, training, and what happens the first week something goes wrong. Marcus asks more than he answers. When they finish, Karen sits back with a look he can't quite place.

"I blocked this hour for a negotiation," she says. "We planned a pilot instead."


Consultation, Not Convincing

After she drops off, Marcus sits with it.

He didn't pitch Karen. He asked what she needed in front of her own CEO and built the answer with her while she watched.


The LISTEN Framework: The Human Move

Buyers are worn out by persuasion. Their inboxes fill with personalized, well-written pitches, many from something that isn't a person, many saying their name four times to prove somebody looked them up. What helps is someone who knows the field and will think through the decision with them.

Tom gave Marcus a framework for this, and it has a name: LISTEN.¹ Each letter is something the machine around you can help with but can't do for you in the room.

Learn their situation before you have any opinion about it. Ask about the history as well as the problem. What have they tried, what worked, who else has a vote, what can't change. "Walk me through what you do now." "What's working that we'd need to protect?" The machine can hand you Karen's org chart and every email she ever sent you. It can't hear that the word she reached for was credibility.

Investigate the root cause, because the problem a buyer states is usually a symptom of something else. "When did this start hurting?" "What happens if you don't fix it?" Don't dig for a reason they need your product. Understand the situation well enough to say something true they hadn't thought of.

Share relevant experience, as perspective rather than proof. "I've watched this fail three ways; here's the one that gets people." This is where the expertise you built in Chapter 4 pays off. This is where the expertise you built in Chapter 4 pays off.

Test alignment before you propose anything. "So the real priorities are these three. Is that right?" Say the problem back until they correct you or nod.

Explain the options, plural, with their real trade-offs, and let the buyer choose. "Faster and riskier, or slower and surer? Which fits how much room you have?"

Navigate to the natural next step instead of forcing one. If the first five letters are done, the buyer will usually tell you the next step. "What makes sense from here?"

Run this way, fewer objections come up. Hidden decision-makers get named early if you ask who else has a vote, and the real need is on the table before anyone talks price. Objections still surface, as Karen's did. When one does, treat it as information about what to build, which is how Marcus treated all three of hers.

The pilot he offered wasn't a discount. It answered Karen's question: how could she try this without risking her credibility?

A machine can pull up every prior conversation with Karen, surface the retention figures, and draft the follow-up. Marcus didn't fill the pause after what would it take for you to feel confident, and what Karen said next is what the pilot was built on.


The Call

A few days later, Karen calls and skips the preamble.

"We're in. The CEO and IT have both approved the pilot, and the officers will try something that doesn't ask them to throw out everything they know at once."

"That's the right way to start," Marcus says.

"Next month. I'll send the contract and the twenty names." A pause. "I figured I'd spend this month fighting you on the contract. Instead I've got a one-pager my CEO read in two minutes and said fine."

He logs it after she hangs up. Closed Won, contract to follow. Forty-five thousand for the pilot, and a path to two hundred thousand a year if the twenty names do what he thinks they'll do.² It is the first deal that isn't a favor or a fluke. Rachel, who funds the company, gave him a second ninety days to land one signature. The contract is still to come, and that time is nearly gone.

He walks over to David's desk.

"Regional Home Lending said yes."

David looks up. "The Karen deal?"

"A yes. The contract comes Friday, with the twenty names."

"Then I'll start on the pilot setup."


Endnotes

  1. The LISTEN framework is a teaching device, not a citation. Its claim is narrow: in a market where the persuasion half of selling has been automated, the diagnostic half is the part that stays human. That means hearing which concern a buyer cares about most, reading what a buyer won't say outright, and working out a decision with them in real time. It is the part worth being expert at.

  2. Karen's deal size, the pilot terms, and the $45,000 and $200,000 figures are invented, and consistent with the rest of Marcus's fictional pipeline: a mid-market win, not an enterprise close. Nothing here is offered as a benchmark.

Chapter alerts

Get the next chapter by email

One email when a new chapter goes up, and one when the book is finished. No drip sequence, no pitch.