Meeting-Seeking

Why this page exists

Most sellers get a prospect on the phone, try to do the whole sales job right there, and wonder why nothing happens. Or they fire off an email, get a one-line reply, and call it "in dialogue." Meanwhile the real relationship — the one that actually becomes an account — is being built by the seller who said "I need to come see you."

Meeting-seeking is its own skill. It's the discipline of knowing when the phone won't cut it, and having the posture to actually ask for the in-person time. Most sellers are too apologetic about asking. That's why they stay where they are.

"I'm not going to have that conversation on this phone call. I need to meet with them. We know that we're going to do better face-to-face. So I'm not going to 'well, what would you ask me about?' I'm like, dude, that's what I got to do over a sandwich. I got to look you in the eye when you answer. You got to look me in the eye when I ask."

Industry terms this page covers

Why the phone and email don't cut it

Two reasons. One is the communication math: on the phone you've lost body language, on email you've lost everything. You're trying to do real work with one arm tied behind your back. (See Communication Pie and Tonality.)

The other reason is deeper:

"It's a vibe thing. I got to be face-to-face. We don't do business over the phone."

Construction and ready-mix are in-person industries. Your customers are on jobsites. Their whole relationship with their current supplier was built at a trailer, over a tailgate, across a counter. If you're trying to displace that relationship over the phone, you're bringing a fork to a knife fight. Go where they are.

Plus: sitting across from someone changes what they're willing to say. Things leak out in person that never come out on a call. (See Listening for Leaks.) Every moment you're with them is a moment the relationship can thicken.

The ask — make it directive, not tentative

Here's where most sellers blow it. They ask for meetings like they're apologizing for existing.

Weak: "Hey, I just wanted to see if maybe sometime you might have a few minutes to possibly grab a coffee or something?"

Strong: "I need to see you. I'm going to be in the area Thursday. Do you have 20 minutes at 9 or 10?"

"Make it stronger. 'Oh, I need to talk to you. Do you have time next week? I'm going to be in the area on this day. I probably need half an hour of time.' Make it a little bit more direct. Make it imperative that we meet. Make it seem important rather than 'hey, just thought I'd stop by and just see how things are going and check in.'"

The difference is posture. Weak ask says "I hope you'll take pity on me." Strong ask says "I respect your time enough to be direct about needing some of it." Customers feel the difference. Strong ask gets the meeting. Weak ask gets "yeah, maybe, send me something."

The "worst case you get a free meal" escape hatch

For prospects who've never met you — or have met you and are cold — give them an out they can't refuse.

"I gave them an out. Meet with me. I'll pay for the coffee or the sandwich. Worst case, you get a free meal. And if you tell me to leave you alone, I don't call you. If I could ask you some questions, spend a few minutes with you — I just feel like there's possibly something that I might be able to do better for you. And if I can't, send me on my way. I'd hate for you to go another 10 years without knowing what's good. What if it's better? If it's not, you kick me out of the curb, whatever — lunch is on me. But if it's better, it could be the best decision you ever make. I won't know unless we sit down and talk."

Three moves happening inside that ask:

1. The free meal. Literally zero downside for them. Lunch on you.
2. The kill switch. "If I can't, send me on my way. I won't call you again." That disarms the fear that agreeing to lunch = agreeing to a lifetime of sales calls.
3. The "what if it's better" frame. Not a pitch. Just a question they can't quite un-hear.

It's almost impossible to say no to that ask cleanly. Which is the point.

Why owners are worth asking to meet

When you're dealing with a company where you know the estimator but have never met the owner — ask for the owner meeting specifically. Not to go around the estimator, but to go above them for a different conversation.

"Hey Janice, it's Steve over at Impact. I've never met you. And what I've been noticing lately is when I call on owners of the companies that we work with, I start hearing their needs and their wishes and their dreams and what's going on and some of the problems they run into that I didn't have any exposure to when I just worked with their estimating staff. Is there a time that you might be able to meet with me? I'm happy to bring a coffee if it's in the morning. I'd love to ask you a bunch of questions for a half an hour and get to know where you're coming from — just to make sure I'm a good supplier."

The owner says things the estimator doesn't. The estimator is telling you about specs and prices. The owner is telling you about vision, frustration, goals, growth plans. Different altitude, different information. Both conversations matter. Most sellers only have one.

The "this project is too big for a quote" ask

Specific application — when an RFQ lands that's meaningfully bigger than your normal:

"It seems like you're really busy right now. Listen — this is 45,000 yards. This is a big project. I'm going to need to sit down with you for a half an hour. So when should we book that? I want to ask some really good questions to make sure logistically this thing's going to work out. Before I quote and start getting all my guys together to figure this out, can we sit down and really break down this project? This isn't a 1,500 yard thing. I want to make sure it's a real good fit."

The move: use the size of the project itself as the reason the meeting is non-negotiable. You're not asking for the meeting because you want face time. You're asking because "I can't responsibly quote this without understanding it better." That's a reason the customer actually respects.

Same move works for complex jobs, big-name projects, or anything with unusual schedule/spec/safety requirements. "I like the plane to land as well, not just get off the ground."

The "look at the next few months" ask — for existing customers

Different meeting, different reason. When you've got a customer you're already serving but you want to deepen:

"I don't know if you eat lunch or anything, but I'd love to sit down with you and maybe look out at the next three, four months worth of work. Get a feeling for which ones are closest to us, which ones I could help make it so we're doing a good job for you. Do you have some time on the calendar this coming week? I just want to look at the jobs, because it feels like I'm kind of reactionary to you — and if I knew what the next three months looked like, I could start putting together some sweet service packages where I understand your flow and provide better service."

Why this works: you're offering to do more work on their behalf, not ask for more work from them. You're not "checking in." You're "getting ahead of it so I can serve you better." Huge posture difference. (See Proactive vs. Reactive.)

When they stall — don't try to do the meeting on the call

This is the trap. You ask for the meeting. They go "well, what did you want to ask me about?" — and now you're tempted to start doing the meeting right there on the phone.

Don't.

"I'm not going to have that conversation on this phone call. What are you talking about? I got to do it over a sandwich. I got to look you in the eye."

The answer to "what did you want to ask me about?" is not "well, first — how's your backlog looking?" It's something like:

"A bunch of stuff. Some about your business, some about how we could fit in, some stuff I want to show you. Honestly, it's half an hour of conversation, not a phone call. When's a good time this week — Tuesday or Wednesday?"

You just pivoted right back to the meeting ask. Stay disciplined. The meeting is the win. Doing the meeting badly on the phone is a loss disguised as a win.

Always book the next meeting before you leave the current one

This is the discipline that compounds:

"Every event should have the next event."

Before you pull out of their parking lot, you should know when the next meeting is. Ideally on their calendar. At minimum on yours. If it's not scheduled, it won't happen — you'll drift, they'll drift, and next time you reach out it'll feel cold again.

Closing moves:

• "Let me put something on the calendar for two weeks from now. What's good — morning or afternoon?"
• "Okay, I'll check in Friday and if we need to get together next week, we'll book it then."
• "Before I go, let me throw Tuesday at 10 on your calendar — we'll regroup after you've talked to your brother."

Leave with the next touch already set. Every time.

Homework — the meeting-ask audit

This week:

1. Pick three prospects you've been talking to "via phone and email." For each, draft the exact directive meeting ask you'd send. Make it imperative, not apologetic.
2. Send all three. Report back on how many said yes vs. the usual drift.
3. For one big existing customer, ask for the "next three months look-ahead" meeting. See how that conversation differs from your normal touch-point.
4. At your next meeting (any customer), book the next one before you leave the room.

Where to go next

• Proactive vs. Reactive — meeting-seeking is inherently proactive work
• Listening for Leaks — the reason in-person beats phone: more leaks
• Tonality — why phone and email lose so much information
• Gatekeeper as Key Master — how to get past the gate when asking for the meeting
• Infiltrate Strategy — meeting-seeking is one of the main infiltration moves

Source: drawn from 9 canonical moments across the live-coaching corpus — including the "I'll pay for the sandwich, worst case you get a free meal" ask, the "I won't know unless we sit down" frame, the "owner meetings surface different information" posture, the "this 45,000-yard job deserves a sit-down" reason-to-meet move, and the "make it directive, not tentative" correction. Voice preserved.