Construction / Trades · Warm Call
The Warm Call Script for Construction / Trades That Survives the First Ninety Seconds
You've got a name. A VP of Operations at a mechanical contractor downloaded something, or a Project Executive you closed last spring told his buddy at the sheet metal shop across town "you should call these guys." Now you're dialing a General Superintendent at 6:40 in the morning while he's standing in a parking structure with a punch walk starting in twenty minutes. He'll pick up. He picked up because of the other guy. That's the whole gift, and it's worth about ninety seconds.
Here's what goes wrong. The rep spends the first three minutes on "so how do you know Mike?", then gives a company overview, then transplants Mike's problem onto a contractor with a completely different self-perform mix — and by minute four the super is saying "send me something" with his thumb already over the red button. Warm turned into cold, except now the prospect feels slightly awkward about it, which is worse than cold. Warmth is a loan. Every sentence that could have been said to anyone burns ten seconds of it.
This script does one job: convert somebody else's credibility into one specific, testable reason you're relevant to this contractor — the days between a foreman doing extra work Tuesday and a COR landing in front of the owner's rep, the points of gross margin fade nobody can explain until the WIP meeting — and get out with a diary slot that has a name and a date on it. Three questions, not eleven. No demo. No deck. And you close the loop with the referrer the same day, or you never get a second name out of him.
The warm call script
Say it in your own words. The structure is the part that matters.
- 1
1. Pre-call: write the provenance line before you dial
One sentence, out loud, checkable, small: "[Referrer] mentioned you because [specific reason]." Good: "Mike Delgado pulled down our thing on T&M tags last month and said you two were comparing notes on backcharges from the same GC." Dead: "Mike thought you'd be interested in what we do." Three things to pre-decide: - **Exactly what the referrer said.** If Mike said "you should call Ray," you say "Mike suggested I call." You do not say "Mike said you'd be really interested." These guys sit on the same association board and bid the same work. Getting caught embellishing costs you two relationships in one move. - **Your relevance hypothesis about *their* shop, not the referrer's.** Pull the trigger from something real: they just picked up a $22M hospital fit-out, they're hiring a second Senior Project Manager, they went from 40% self-perform to 70% on the last two jobs, they just added a Controller. - **Assume the intro email was never read.** Have a fifteen-second re-brief ready in field language, with no product in it.
- 2
2. The open — name, referrer, provenance, permission (25 seconds)
"Ray — Dani Kroll, from Fieldline. Mike Delgado suggested I call you. He grabbed something we wrote about T&M tags sitting on a dashboard till Friday and said you'd taken over field ops for all four crews when Terry retired. He may have been overselling my usefulness. Have you got three minutes for me to find out whether any of that's true, or should I call back after the punch walk?" If they say **"yeah, Mike said you'd call"** — that's your entire warmth budget handed over. Five words of acknowledgement, then move: "Good, he said he'd flag it. Then I'll be quick." Do **not** ask how they know Mike. It costs three minutes and returns nothing.
- 3
3. If they don't remember the referrer
Happens constantly. Don't argue them into remembering. "No reason you would — it was a two-line email on a Friday afternoon. Short version: we do the T&M tag and the daily report off a phone in under a minute, so the ticket's in the office the same day instead of Friday. Mike's shop was losing change work to late paperwork. Worth three minutes or not really?" No company history. No "we were founded in." No platform. Field language only.
- 4
4. The relevance bridge — name why you might be irrelevant
This is the beat the call lives or dies on. Referrer's world → the specific difference → a question that hands them control. "What Mike was dealing with was six foremen self-performing underground on GMP work, tags coming in on Friday, and his fade running two, three points off bid by month four. That's his shop. You're mostly hard-bid, you're subbing out more than he does, and you've got a Controller who actually chases the pay apps — so honestly I don't know if this lands the same way. When your foreman does extra work on a Tuesday, what's the actual path that ticket takes to get in front of the owner's rep?" Naming a reason you might be irrelevant is the fastest credibility move available on a warm call. It reads as honest and it kills the "here comes the pitch" brace. Never say: "Mike was drowning in unbilled change orders, so I imagine you are too."
- 5
5. Discovery — three questions, four at the outside
This is not a booked discovery meeting. Do not run eleven questions on a man standing in a stairwell. **1. Mechanical current state.** "Who physically touches that ticket — foreman writes it, super signs it, PM writes the COR? And where does it sit in between?" **2. Cost in their numbers.** "From the work getting performed in the field to a COR in front of the owner's rep — honestly, how many days? And what's your unapproved change orders sitting at as a percentage of contract value right now on the big job?" Or, if you're talking to a CFO / Controller or Project Executive: "When you look at bid margin versus as-built on last year's closed jobs, how many points of fade are you eating, and can anybody tell you where it went?" **3. Priority test — the one that saves you a wasted follow-up.** "Is that a this-quarter problem or a live-with-it problem?" **Optional fourth:** "Besides you, who'd care about this — your Controller, or the Project Executive on that job?" Write down their exact phrasing. "It's not the tags, it's that my supers were never held to it" goes verbatim into the follow-up email and the second meeting agenda.
- 6
6. Reading the cool-off
Warmth withdraws politely. The tells: - Answers shorten. "Yeah. Yeah, makes sense." - They narrate logistics: "Can you send something over?" - They ask what it costs before you've established a problem — that's a disqualification in a polite jacket. - They invoke the referrer as an exit: "Well, if Mike rates you." Stop talking and name it: "I'm getting the sense this isn't the thing keeping you up right now — which is fine, Mike was guessing. Is it not the problem, or not the moment?" A clean "not the problem" is a good outcome. It protects the referral source and stops you burning a quarter chasing a ghost.
- 7
7. The close — a date, a length, their words, and a name
The number one failure on a warm call is a pleasant conversation that ends in "send me some info." "Then here's what I'd do. You said the tag hits the office Friday and the COR goes in a week and a half later, and you're arguing from memory by then. Give me thirty minutes and I'll show you what one contractor did to get that to same-day on a single job — and I'd want your Controller on it, because the piece that mattered to them was the backup getting attached to the pay app so it stopped bouncing. Thursday at 6:30 before crews roll, or Monday at lunch?" Must contain: a date, a length, a reason built from their own words, and who else should be there. If they genuinely can't commit, take the smaller real commitment: "I'll send you one page — two paragraphs and a photo of a tag. Tell me Thursday whether it's worth thirty minutes." Then put Thursday in *your* calendar, not theirs.
- 8
8. Close the loop with the referrer — same day, two lines
"Mike — spoke to Ray, thanks for that. His issue's a bit different to yours, it's less the tags and more that the backup never makes it onto the pay app. Meeting him and his Controller Thursday. Appreciate the intro." This thanks them, tells you whether you can use their name again, and is the only reliable way one referral turns into two. Sources who never hear back stop referring.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Ray — Dani Kroll from Fieldline. Mike Delgado suggested I call you. He picked up something we wrote about T&M tags sitting on a dash till Friday and said you'd taken the whole field ops seat when Terry retired. He may have been overselling my usefulness. Three minutes, or should I catch you after the punch walk?
Buyer
Mike mentioned something. I'm on the fourth floor of a parking structure and I've got an inspector at seven. What is this — is this software?
Rep
It is, and I'll be quick about it. Short version: T&M tag and daily report off a phone in under a minute, so the ticket's in the office the same day instead of Friday. What Mike was dealing with was six self-perform crews on GMP work and his fade running a couple points off bid by month four. That's his shop — you're mostly hard-bid and you sub out a lot more than he does, so I genuinely don't know if this lands. When one of your foremen does extra work on a Tuesday, what actually happens to that ticket?
Buyer
Half our jobs, the GC makes us live in their system anyway. I'm not running two platforms. My guys already double-enter into a notebook.
Rep
You're running two either way, though — their system is their record, not yours. It's not going to be on your side the day the GC hands you a backcharge for the ceiling grid and you're trying to prove your guys were on site and productive. Whose number wins that argument today?
Buyer
What's it cost? Just tell me the number, because our margins are single digit and I'm not adding a line item.
Rep
I'll tell you, but you'll hate the number until we know if there's anything to fix. So let me ask the one that matters — from a foreman doing the extra work in the field to a COR in front of the owner's rep, honestly, how many days?
Buyer
Depends on the PM. Week? Week and a half. On the hospital job there's stuff from March we're still fighting about at closeout.
Rep
So on the March stuff you're negotiating from memory against a guy with a schedule and a stack of RFIs. What's your unapproved change orders sitting at as a percentage of contract value on that job right now?
Buyer
That's not my number, that's Karen's. Look — you should talk to my PMs. They handle the field paperwork, I don't chase tags.
Rep
Happy to, and I will. But your PMs will optimize for their own jobs. You're the one looking at fade across the whole book. The question I'd want answered before you hand me off is whether unbilled change work is a two-job problem or an every-job problem — your PMs won't tell you that. The WIP will, and Karen's got it.
Buyer
We bought a platform two years ago. Full rollout, training day, the whole thing. Nobody used it. I'm not doing that to my supers again.
Rep
Fair. What did they stop doing first — the daily reports or the change tickets?
Buyer
Dailies lasted maybe five weeks. Change tickets never happened at all. And my two best foremen — guys in their fifties who run flawless crews — never opened it once. I'm not fighting those guys over an app.
Rep
Then don't. That's the honest answer. If the change tickets never happened at all, that might not even be a software problem — that might be that nobody ever held the supers to it. Is that a this-quarter problem for you, or a live-with-it problem?
Buyer
It's a live-with-it problem because we're slammed. Backlog's booked through next October. I don't have a week to implement anything.
Rep
Busy is exactly when the tags stay in the truck — that's when it costs you the most. I'm not asking for an implementation. One job, two foremen: the one who's fine with a phone and the loudest holdout you've got. Three weeks. If the holdout can't do it with gloves on in under a minute, we've learned something cheap and you're out.
Buyer
...The parking structure's got eight more months on it. Denny would be the holdout. He'd tell you exactly what he thinks, too.
Rep
Denny's the one I want. Here's what I'd suggest: thirty minutes, and bring Karen — because the piece that mattered at the last contractor I worked with wasn't the tags, it was the backup getting attached to the pay app so it stopped bouncing and the retainage conversation started earlier. Thursday 6:30 before crews roll, or Monday at lunch?
Buyer
Thursday, but 6:45, and don't send me a deck. One page. If it's longer than a page I won't read it.
Rep
One page, two paragraphs and a photo of a tag. Thursday 6:45, you and Karen, thirty minutes, and the thing we're answering is whether the March change work would've been billable if the ticket had hit the office that Tuesday. I'll let Mike know I got you.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “My foremen won't use another app. Half of them hate smartphones.” | Then don't roll it out to all of them. Pick two — one who's fine with a phone and one who's your loudest holdout — and run it on one job for three weeks. If the holdout can't do it in under a minute with gloves on in the rain, we've learned something cheap. And the test isn't whether he likes it. The test is whether the T&M tag gets to the office the same day. |
| “Margins are single digit. Software's a luxury line item.” | Agreed, which is why I'd rather talk about the unbilled work than the subscription. What's your best guess on change work performed last year that never got billed, or got negotiated down because the paperwork was late? Most contractors your size land somewhere between $200K and $500K. If yours is a tenth of that, it pays for itself on one job and you cancel it if it doesn't. |
| “We already bought a platform. Nobody uses it. Not doing that again.” | Fair — and I'd bet the rollout was 'here's the login, here's a training deck.' What specifically did they stop doing first, the daily report or the change tickets? I want to know, because if the answer is 'both, in about five weeks,' we should talk about whether this is even a software problem or whether your supers were never held to it in the first place. |
| “Talk to my PMs, they handle the field paperwork.” | Happy to, and I will. But your PMs will optimize for their own jobs, and you're the one looking at fade across the whole book. The question I'd want answered before you hand me off is whether unbilled change work is a two-job problem or an every-job problem. Your PMs won't tell you that — the WIP will. |
| “Backlog's booked through next year. We're too busy to implement anything.” | That's exactly when the leaks are worst — busy is when the tags stay in the truck. I'm not asking for an implementation. I'm asking for one job and one foreman. If you're too busy for that, then you're genuinely too busy, and I'll call you when the fall jobs close out. |
| “We already do this in the accounting system. It's all in there.” | It's in there eventually — the question is when. If the change ticket hits accounting Friday instead of Tuesday, you're billing three days late and arguing from memory. How long, honestly, from the extra work happening in the field to a COR in front of the owner's rep? If it's more than a week, you're negotiating from a weak position every single time. |
| “The GC makes us use their system on that job. I'm not running two.” | You'll run two either way — their system is their record, not yours. Your guys are already double-entering into a spiral notebook. The version I care about is the one that documents your labor hours when there's a backcharge fight at closeout, because their platform will not be on your side that day. |
Questions reps ask about this call
- How is a warm call to a contractor different from a cold call?
The referral buys you exactly three things: the pickup, about ninety seconds of suspended disbelief, and permission to ask a direct question without earning it first. It does not buy you interest, budget, or a problem. A General Superintendent who took the call because his buddy at another shop said to is still a stranger to your product. Cash the referral in the first twenty-five seconds — name, referrer, why they thought of you, permission with a time box — then get to one specific question about their jobs. Two generic sentences and you've converted a warm call into a cold call the prospect now feels awkward about.
- When should I actually dial a VP of Operations or General Superintendent?
Early or late, not mid-morning. Before crews roll — 6:15 to 7:00 — you'll often catch a super in a truck, and Project Executives and Directors of Field Operations are frequently at a desk by 6:30. After 4:30 is the second window, once the punch walk and the inspector are done. Avoid Monday morning entirely; that's look-ahead and manpower scramble. If you get a CFO or Controller, the last week of the month is bad and the WIP review week is worse — though the week after a bad WIP meeting is the single best time to be talking about margin fade.
- What do I say if the prospect doesn't remember who referred them?
Don't argue them into remembering — it was a two-line email skimmed on a phone. Say so: 'No reason you would, it was a two-line intro on a Friday.' Then give a fifteen-second re-brief in field language with no product in it: 'Short version — T&M tags and dailies off a phone in under a minute so the ticket's in the office the same day instead of Friday.' Then ask for three minutes. Never open with 'as per the email below' or 'following on from Mike's note.'
- How many discovery questions should I ask on a warm construction call?
Three, four at the outside. This is not a booked meeting and running eleven questions at a superintendent standing in a stairwell reads as an abuse of the referral. Ask one mechanical question (who physically touches the T&M tag, and where does it sit), one cost question in their numbers (days from field work performed to COR submitted, or points of gross margin fade between bid and as-built), and one priority test ('this-quarter problem or live-with-it problem?'). The priority test saves you more wasted follow-ups than anything else on the call.
- Should I try to get the CFO or Controller on the call too?
Not on the first call, but name them in the close. Field ops leaders own the T&M tags and the look-ahead; the CFO or Controller owns DSO, retainage outstanding, and the over/under billings on the WIP. Those are two different arguments for the same fix. Ask 'besides you, who'd care about this — your Controller, or the Project Executive on that job?' Warm calls have an unusually high hit rate on that question because you're already a known quantity by association. Then make the Controller part of the reason for the second meeting.
- What counts as a successful outcome if they won't commit to a meeting?
Two things. First, a smaller real commitment with a date on it: 'I'll send one page — two paragraphs and a photo of a tag. Tell me Thursday whether it's worth thirty minutes,' with Thursday in your calendar, not theirs. Second — and this genuinely counts — a clean 'this isn't the problem.' If they self-perform almost nothing and their change work is all owner-directed on GMP contracts with a contingency, say so out loud and get off the phone. It protects the referral source, and sources whose intros don't get abused give you second names. Either way, email the referrer the same day.