TFT: You're Talking Your Way Out of Deals

The engineer wanted one number. We took 45 minutes of his time. I never got back in front of him again.

Early in my career I was an account manager in the Rockies, riding along with a more experienced rep to learn a product line from someone who'd sold it for years. An engineer reached out looking for pricing — a rough budgetary number to drop into a project proposal. That was all he wanted. One rough number.

Five minutes in, I could tell we were wasting his time. The rep, who was supposed to be training me, kept going anyway — through features, capabilities, everything the product could do, other problems he'd solved with it. The engineer barely talked, and the rep took that silence and filled it with more information each time. We talked about 80% of that call. I followed up afterward more times than I can count. I never got another meeting with that engineer. He moved forward with another company.

If you're a founder running your own discovery calls, you know where this comes from. You built the product. You know the pain of the problem personally. When a buyer opens the door even a crack, everything you know wants to come out at once. But every minute you spend talking is a minute you aren't learning whether this person has a problem you can solve — or is ready to solve it.

This week I'm digging into the opposite of that story: a rep I hired who listened his way into what became one of our largest accounts. We'll also look at why the pitch-first instinct quietly kills deals, and the count-to-ten habit I still use on my own calls.

Listening is the skill that sells, not talking

There was an account we wanted to win. They did a lot of work with our competitors, and we wanted some of it. I had room to add headcount, so I hired a rep and handed him that account. Today it's one of our largest.

The way it became one of our biggest isn't exciting. He spent a lot of time driving out to that customer and sitting in their offices with their engineers. When he was in the room, he asked questions. The one that mattered most was simple:

"What's the hardest part about using this equipment, whether it's ours or anyone else's?"

It took time to build trust, but because he kept showing up, they started to trust him. Eventually the engineers told him: their biggest frustration was the commercial terms. They wanted the vendors — us — to have more skin in the game. He brought that feedback back, and we built a two-tiered approach around what they said. The first tier covered the initial installs, when operations are hardest and the most can go wrong, so the structure kept our risk in check. The second tier was pay-for-performance: once the installs were stable, we earned our keep by keeping the equipment running longer. Nobody else was offering that, and it came straight out of conversations where the engineers did most of the talking.

My rep listened about 80% of the time and talked about 20%. Because those engineers felt heard, they told him what frustrated them and how we could make their jobs easier. One rep talked his way out of a relationship. The other listened his way into one of our biggest accounts.

Confirm the problem before you pitch anything

Doctors learn it early: never prescribe before you diagnose. Sales runs on the same rule. When you jump straight into the pitch, you skip the questions that decide whether there's a deal at all:

Does this person have the problem you solve? Do they want it solved now? Is there money to solve it now?

If you can't answer those from what they told you, you're guessing — and a pitch built on a guess turns into a list of features, because features are all you have to offer. That's what happened in the Rockies. Five minutes of listening would have told us the engineer had a project, no approved budget, and a proposal to finish. The right move was a rough number and a follow-up once it got funded. Instead we gave him a product tour and wasted 45 minutes.

The right path changes with what you hear. If it's a fit and the timing's right, you sell. If someone in your network solves it better, you refer them. If the budget gets approved in six months, you follow up in six months. Every one of those meets the customer where they are today.

Out in the market, be an evangelist for the problem — talk about it everywhere. Once you're on the call, confirm the problem, then stop talking about it. Make the person across from you the most important person in the room. Let them talk 80% of the time. Once you go past 20%, you risk drifting into features, and the call loses its one job: showing them you understand the problem and can deliver the outcome.

Count to ten, then talk

I'd love to tell you I have this figured out, but I don't. On my own discovery calls, I catch myself wanting to jump in. A founder starts describing the problem and I can already see ways to help. That eagerness is part of why I write this newsletter and work with founders — and it's also the thing most likely to turn me into that rep in the Rockies.

So I gave myself a rule: count to ten. While they're talking, I keep my attention on what they're saying. When they stop, I count to ten before I respond. Ten seconds feels like forever on a call, but it gives me space to process what I heard and answer in a way that helps. Most calls, I end up listening more than I planned to — which is exactly the point.

The listening doesn't stop when the call ends. I record my calls with Notion's AI Meeting Notes, then reread the transcript and have AI help me pull out the challenges this person is facing and where I could help. That second pass, once the urge to jump in has worn off, makes it much easier to help clients.

Listening drives the first driver

The Customer Engagement driver is the first engine in the Revenue Flywheel, and it runs on listening. "Never prescribe before you diagnose" is how that driver works in practice: you can't solve a problem you haven't heard. Look at what one rep's listening set in motion:

Engineers talk → frustration surfaces → offer reshaped in their language → trust earned → one of our largest accounts.

Every driver after this one depends on that first conversation. Skip the listening and the flywheel has no momentum to turn.

Action step

• This week: record your next discovery call. Afterward, check your talk time. If you're over 20%, find the moment you started pitching.
• Before your next proposal goes out: write down the problem, why they want it solved now, and how it gets funded — all in their words. If you can't fill in every piece, you're prescribing before you diagnose.
• On your next call: count to ten after they stop talking. Skip it, and you'll keep hearing the answer you expected instead of the one they gave you.

Not sure where you're talking when you should be listening? The Revenue Flywheel Diagnostic will show you where your engagement is leaking.

Recommended reading

• TFT: Engage With Insight — the Diagnose → Prescribe step that kicks off the Customer Engagement engine.
• TFT: Win the Problem Before You Talk Price — what happens downstream when you confirm the problem first.
• TFT: Diagnose Before You Prescribe — the original post behind this week's rule.

Sales is just problem solving with another human.

This article was originally published on the ENG Sales newsletter.