Construction / Trades · Cold Call
The Construction / Trades Cold Call Script for Selling to VPs of Operations and General Superintendents
The person you're about to call is standing in a gravel lot with wind on the mic, or they're three tabs deep in a WIP schedule trying to work out why a job that was bid at nine points is now showing six. They are a VP of Operations, a Director of Field Operations, a General Superintendent, or the Owner of a 90-man mechanical contractor who still drives the truck. They did not download anything. They do not know your name. And the last software rep who got through pitched them a "connected jobsite ecosystem" for four minutes before mentioning what it actually did.
Your advantage on this call is not your product. It's that you can describe, in their words, the T&M tag sitting face-down on the dash of a foreman's truck since Tuesday, and what that tag is worth by the time the owner's rep says "first I'm hearing of it" on Friday. If the first thirty seconds of your call sound like a WIP review and not a webinar, you get thirty more. If they sound like marketing, you get "we're all set" and a dial tone.
This script is built for the cold dial specifically: no referral, no trigger email, no prior touch. The goal is not to explain the platform, run discovery, or handle six objections. The goal is one calendar hold, confirmed while they're still on the phone, framed around a number they already get measured on — days from field work performed to COR submitted, unapproved change orders as a percentage of contract value, or gross margin fade in points from bid to as-built.
The cold call script
Say it in your own words. The structure is the part that matters.
- 1
Before you dial — 90 seconds, out loud
Answer these to yourself before the phone rings. If you can't, don't dial yet. 1. WHO: Exact title and what they own. A Director of Field Operations owns supers and crews. A Project Executive owns a portfolio's margin. A CFO/Controller owns DSO and retainage. Same product, three different first sentences. 2. WHAT THEY DO: Self-perform or broker it out? Electrical, mechanical, concrete, drywall? Public work or private GMP? "Self-perform electrical on healthcare" gets you a different problem than "site concrete for a national homebuilder." 3. THE ONE PROBLEM: Written down, one only. For ops titles: T&M tags not reaching the office same day. For finance titles: unapproved change orders sitting in a folder as unbillable cash. 4. THE ASK: 20 minutes, two specific slots that respect their day — before the 6:30 huddle, or after 4 when the crews are off. Have the follow-up email drafted in a window before you dial.
- 2
Opener — name, honest frame, permission, pause
"Mark — it's Dan Reyes at Fieldline. We haven't spoken, this is a cold call. Give me thirty seconds to tell you why I rang and then tell me to get lost?" Then STOP. Two full seconds. Do not fill it. Tonality: slower than feels right. "Thirty seconds" lands with a downward inflection, not a question mark. If he answers flat and clipped — and he will, he's on a jobsite — come in one notch under him, not above. Variant if he sounds like he's mid-stride: "Mark, Dan Reyes, Fieldline. You don't know me. Are you walking somewhere?" — half of them say "depends what it's about," which is permission.
- 3
The reason — problem, not product (max two sentences)
For VP of Operations / Director of Field Operations / General Superintendent: "We work with self-perform trade contractors doing forty to a couple hundred million. The thing that keeps coming up with ops guys is the T&M tag — foreman does the extra work Tuesday, writes it on a tag, and the tag lives on the dash until Friday or never gets to the office at all. By the time the PM writes the COR the owner's rep says 'first I'm hearing of it' and it gets negotiated down or eaten. Is that anywhere near your world, or have you got that locked down?" For Project Executive / Senior Project Manager: "Most of the PXs I talk to can tell me a job's bid margin and its current margin, but not where the fade happened — real labor hours against unbilled scope, a GC backcharge, rework, and no field-level record to point at when the postmortem starts. Sound familiar or is your documentation tighter than that?" For Owner / President or CFO / Controller: "I'll be blunt about why I called. Every unapproved change order sitting in a folder is cash you can't bill, and it's sitting on top of ten percent retainage while payroll runs every Friday. The number I'd want to know if I were you is unapproved COs as a percentage of contract value across the book. Do you have that number, or is it a WIP-meeting surprise?" No product name yet. None.
- 4
Earning the next 60 seconds — two questions, maximum
Narrow and factual. Not "walk me through your process." • "Honestly — how many days from the extra work happening in the field to a COR in front of the owner's rep? Ballpark." • "Is that a person chasing it or a system? Like, is somebody driving to jobs on Friday collecting tags?" • "How many foremen are writing tags on a given week?" • "Is that on someone's list this year or is it just the cost of doing business?" Listen for the admission: "yeah, it's a mess," "we've talked about it," "our WIP is always a fight." The second you hear it, stop asking and close.
- 5
The ask — small, specific, two options
"Here's what I'd suggest. Twenty minutes, not a demo. I'll walk you through what the gap between work performed and COR submitted looks like in dollars on a job your size, and you tell me if it's worth a second conversation. If it's not relevant you say so on the call and I'll leave you alone. I've got Tuesday at 6:45 before your huddle, or Thursday at 4:30 once the crews are off. Which is less bad?" The moment he picks: "Sending the invite now — it's coming from dan@... Can you tell me it landed before we hang up?" Do not hang up before he confirms it. A verbally-agreed meeting calendared later no-shows at a dramatically higher rate.
- 6
Gatekeeper / dispatch screen
"It's about their T&M tags and change order paperwork — Dan Reyes at Fieldline, he won't know me. Is he on a job today or in the office?" Short, calm, specific. Never claim a prior relationship, never say "it's personal," never be cute. Asking whether he's on a job gets you the callback window for free.
- 7
The soft no — get a date and a fact
"No problem. Last thing and I'll let you go — is this a timing thing or a 'this isn't a priority' thing?" … then … "Got it. When do you close out the fall jobs and look at next year's overhead? … October. Fine, I'll come back to you the second week of October. I'll send one email so you've got my name in your phone." A cold call that produces a dated callback and one real fact — 'unbilled change work is an every-job problem, not a two-job problem' — is not a failure. 'Send me an email' with nothing else is.
- 8
Voicemail — under 20 seconds, no ask
"Mark, Dan Reyes at Fieldline — you don't know me. Calling about T&M tags getting from the truck to the office same day, and what that does to days-to-COR. It's a thing we see a lot with self-perform contractors your size. I'll try you again Thursday morning. 555-0148." No ask. The voicemail's job is name recognition for attempt two and the email, not a callback.
- 9
Immediately after — five minutes, no exceptions
• Send the email within five minutes. Subject: "Our call just now — T&M tags and days-to-COR." • Log his exact words. If he said "the tags come in when they come in," that sentence goes in the email and opens the discovery call. • Log a real disposition: "booked Thurs 4:30, self-perform electrical, 14 foremen, killed a Procore rollout in 2023" — not "interested."
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Mark — it's Dan Reyes at Fieldline. We haven't spoken, this is a cold call. Give me thirty seconds to tell you why I rang and you can tell me to get lost?
Buyer
I'm walking a punch list right now, so make it fast.
Rep
Fast is fine. We work with self-perform trade contractors doing forty to a couple hundred a year. The thing that keeps coming up with ops guys is the T&M tag — foreman does the extra work Tuesday, writes it on a tag, tag lives on the dash till Friday or never makes it in at all. By the time the PM writes the COR the owner's rep says 'first I'm hearing of it' and it gets negotiated down. Anywhere near your world, or have you got that locked down?
Buyer
Look, everybody calls me with the same speech. We run Procore on the GC's side and everything hits Vista on our side. It's all in the system.
Rep
It's in there eventually — I don't doubt that. What I'd want to know if I were you is when. Honestly, ballpark: from the extra work happening in the field to a COR sitting in front of the owner's rep, how many days?
Buyer
Depends on the job. Some of them same week. Some of them, I'll be straight with you, we find them at the WIP meeting.
Rep
That's the part I hear most. And the WIP-meeting ones are the ones that get argued down, because you're negotiating from memory instead of from a tag with a date and a photo on it.
Buyer
Sure. But I'll save you some time — my foremen won't use another app. We rolled something out two years ago, spent real money on it, and it was dead inside a quarter. I've got guys in their fifties running my best crews and I'm not fighting them over a phone.
Rep
Fair, and I'd bet the rollout was a login and a training deck. Genuine question — what did they stop doing first, the daily report or the change tickets?
Buyer
Daily reports lasted about six weeks. The change tickets they never really started.
Rep
Then that's the one that matters, because that's the one with money attached. So I wouldn't roll anything out to anybody. Pick two foremen — one who's fine with a phone and one who's your loudest holdout — one job, three weeks. If the holdout can't do a tag in under a minute with gloves on in the rain, you've learned something cheap and you're out.
Buyer
Our margins are single digits, Dan. Software is a luxury line item around here.
Rep
Agreed — which is why I'd rather talk about the unbilled work than the subscription. Best guess: change work performed last year that never got billed or got negotiated down because the paperwork was late. What's the number?
Buyer
I couldn't tell you. My PMs would say it's small. I don't believe them.
Rep
That gap right there is the whole reason I called. Your PMs will optimize for their own jobs; you're the one looking at fade across the whole book. Twenty minutes, not a demo — I'll show you what days-to-COR and unapproved COs as a percent of contract value look like in dollars on a job your size, and you tell me if it's worth a second conversation. Tuesday 6:45 before your huddle, or Thursday 4:30 once the crews are off?
Buyer
Thursday. But I'm telling you now, we're booked through next year and I'm not implementing anything in Q4.
Rep
Understood, and busy is exactly when the tags stay in the truck. I'm not asking for an implementation — one job, one foreman. Sending the invite now, it's coming from dan@fieldline.co. Can you tell me it landed before I let you get back to your punch walk?
Buyer
Yeah, it's here. Thursday, 4:30.
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, we've learned something cheap. The test isn't whether they like it, it's whether the T&M tag gets to the office same day." |
| “"Margins are single digit. Software is 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 done last year that never got billed or got negotiated down because the paperwork was late? Most guys your size land somewhere between $200K and $500K. If it's a tenth of that, this pays for itself on one job — and you cancel it if it doesn't." |
| “"We already bought a platform. Nobody uses it. I'm 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 be talking about whether this is even a software problem or whether your supers were never held to it." |
| “"Talk to my PMs, they handle the field paperwork."” | "Happy to, and I will. But your PMs will optimize for their 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." |
| “"Our backlog is booked through next year. We're too busy to implement anything right now."” | "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 too busy, and I'll call you when the fall jobs close out." |
| “"We do this in the accounting system already. 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 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 for 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." |
| “"Just send me some information."” | "Happy to, but the generic deck goes in the bin and we both waste the effort. Give me two things — do you self-perform or sub most of it out, and roughly how many foremen are writing T&M tags in a week — and I'll send you something that's actually about your business instead of somebody else's." |
Questions reps ask about this call
- What's the best opening line for a construction cold call?
Name, honest frame, permission, then a two-second pause: "Mark — Dan Reyes at Fieldline. We haven't spoken, this is a cold call. Give me thirty seconds and you can tell me to get lost?" Naming it as a cold call collapses the suspicion loop faster than any clever hook. Skip "how are you today" and "did I catch you at a bad time" — the first outs you as a script-reader, the second hands a General Superintendent a scripted no while he's standing in a lift.
- When should I call a VP of Operations or General Superintendent?
Ops and field titles answer around the edges of the crew day — before the 6:00–6:30 huddle, or after 4:00 once crews are released. Mid-morning is when they're walking jobs or on the phone with the GC. Project Executives and Senior PMs are more reachable late morning and after 3. CFOs and Controllers are worst in the last week of the month and the first week of the next — that's pay app and WIP season. Use it: if you catch a Controller in WIP week, the margin fade opener lands harder than any other time of year.
- Which pain should I lead with on a construction / trades cold call?
One only, matched to the title. Ops titles: T&M tags that don't reach the office the same day. Project Executives and Senior PMs: margin fade they can't explain until the WIP meeting, and no field-level record to point at during the postmortem. Owners and CFOs: unapproved change orders as a percentage of contract value, and cash stuck behind retainage and rejected pay apps while payroll runs every Friday. Leading with three pains reads as a pitch; leading with one reads as "how do they know that about us?"
- How do I handle "my foremen won't use another app" without arguing?
Don't defend the software — shrink the test. Agree that a company-wide rollout is exactly what failed last time, then propose two foremen on one job for three weeks, including the loudest holdout. Then ask the diagnostic question: what did they stop doing first on the last platform, the daily report or the change tickets? The answer tells you whether you're selling into a tooling problem or an accountability problem, and it's the single most useful piece of intelligence you'll get on the call.
- What metrics should actually appear in the script?
The ones they get measured on and can't fake: days from field work performed to COR submitted, unapproved change orders as a percentage of contract value, gross margin fade in points from bid to as-built, DSO and retainage outstanding, and over/under billings on the WIP. Use them as questions, not claims — "how many days from the work happening to a COR in front of the owner's rep?" beats any statistic you could quote, because you're asking about their number, not asserting an industry average.
- What counts as a successful cold call if they won't book?
A dated callback plus one real fact. "Call me back after the fall jobs close out in October, and yes, unbilled change work is an every-job problem" is a live pipeline entry. "Send me an email" with nothing attached is a polite hang-up that produces an unopened message. Before you let a soft no go, ask whether it's a timing thing or a priority thing, get the month they look at next year's overhead, and log their exact words about the problem — those words open your next call.