Construction / Trades · Renewal Call
Construction / Trades Renewal Call Script: Saving an Account After a Year of Dead Adoption
You are six weeks from the end of the term with a specialty trade contractor, and you already know how this went. You sold twenty-two licenses. Two foremen on the hospital central plant job used it, one of them because he liked it and one because the Senior PM stood over him. The rest of the field never got past the login email. Then Q2 hit — school shutdown season, everybody's busiest ten weeks — and three of their tickets sat while your support queue was underwater. Now a competitor rep has been emailing their Controller a number that's 20-30% lower, and the VP of Operations took this meeting mostly so he could say all of that out loud to your face.
This Construction / Trades renewal call script is built on one rule: the order form is the last five minutes, not the first five. If you open with "so what would it take to get this done," you confirm the thing they already believe — that you show up when money is due and not when a T&M tag is sitting on a dashboard. If you open with ticket 41-882, the date it went nine days without a response, the fact that Ops adoption peaked at 34% in March and never moved, and what actually broke on your side, the same VP will start negotiating with you instead of against you.
What makes this industry different is what you're really defending. It isn't the subscription line item — on single-digit gross margin they will cut that without blinking. It's whether the change ticket gets from the field to a COR in front of the owner's rep in two days instead of nine, whether there's a labor record when the GC comes with a backcharge at closeout, and whether the Controller can attach backup to the pay app so it doesn't come back rejected. Talk about that. Then talk about price.
The renewal call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: the renewal autopsy (do this before you dial)
Do not walk in without these on one page: — Every ticket from the last 12 months: ID, open date, first response, resolution, who touched it. Flag anything over 48 hours to first touch. Know your three worst by number and by date. Ours are 41-882 (opened June 11, nine days to first response, during their school shutdown push), 42-107, and 43-556. — Usage by role, month over month. Not "adoption is 60%." It's: "Accounting is at 92% weekly active — Angela in the office runs the pay app backup out of it. Field peaked at 34% in March — that's 7 of 22 licenses — and has been flat since." — Your own turnover. If they've had three CSMs in eighteen months, that's your fault and you name it before the VP of Ops does. — Every QBR commitment you didn't deliver. The Sage integration. The two toolbox-talk training sessions that got rescheduled and then quietly dropped. — Their org changes. Did the Project Executive who bought this get moved to the new distribution center job? Is the General Superintendent who hated it now reporting to a different VP? Is the CFO the one actually holding the pen this time? Before you dial, get written internal confirmation on what you can commit: named support engineer, response SLA, onsite training days, seat reduction authority. Do not improvise a remedy on the call. A second broken promise ends this account and it gets attributed to you by name. Know your walk-away on price, term and seat count before the phone rings.
- 2
Opening: go first, name it with numbers
"Ray, thanks for the half hour. I know the contract's up March 31. I'm not here to talk about the renewal yet — I want to talk about this year first, because from where I'm sitting it wasn't the year we sold you. Here's what I can see on my side. Ticket 41-882 — your general super opened it June 11 when the T&M tags weren't syncing off the hospital job — went nine days before anyone from us responded. That was the middle of your school shutdown season. You had two CSM changes, Dana in February and then me in August, and nobody handed off the training plan for your Ops group. And the adoption number is the one that matters: you're paying for twenty-two field licenses and we've never had more than seven weekly active. That peaked in March and it's been flat since. That's what I've got. What am I missing, and what did it actually cost you?" [Then stop talking. Whatever the silence is, let it run. This is where the meeting is won.]
- 3
Listening: let it be worse than you thought
Budget half the call here. Fifteen minutes minimum on a thirty-minute call. No "but." No "to be fair." Do not defend a single ticket, including the one where their super never opened the app. Probes to use, in their language: "When the tags weren't syncing in June — what did your guys go back to? Paper?" "Which job took the worst of it? Was that the one that faded?" "Who did you have to explain this to? Did it come up in front of your CFO at the WIP review?" "Your general super — I want to hear it straight. What does he say about it in the truck when I'm not on the phone?" Follow the emotional word. If he says "we were writing tickets on the back of a submittal log for two weeks," that's the thread: "Tell me about those two weeks." Write it down visibly and read it back: "So: the June sync failure and the nine days of silence, the Ops training that got promised twice and never ran, and the fact that on the hospital job your guys ended up running our thing plus the GC's platform plus a spiral notebook. Anything else?" Ask "anything else" twice.
- 4
The apology: once, specific, no hedge
"The Q2 response times were a failure on our side. We reorganized support in April and small and mid-market queues got stacked behind enterprise escalations. That's an explanation, not an excuse — you bought a 24-hour first response and we missed it eleven times, and we missed it in the worst ten weeks of your year. The training that never happened is on me differently. Dana committed to two sessions for your foremen in the January QBR and when she moved off the account nobody picked it up. Your guys didn't fail to adopt it. We never showed up to roll it out." One apology. Then move. Do not repeat it later in the call — repeating it turns it into a technique.
- 5
Proof of change: show, don't promise
Only three things carry weight. Use their own data, never a company-wide stat. 1. Structural change with a date. "We split the support queue by segment on September 1 and staffed it. Your median first response since then is 3.2 hours across nine tickets — I'll send you the list with the ticket numbers so you can check it against your own inbox." 2. Something already done, unasked. "I had the team clear the three open items in your queue last week — the pay app export formatting one and the two login resets for the guys at the distribution center. Those should have closed Thursday." 3. Evidence from a contractor like them. "There's a mechanical contractor out of Columbus, about your size, self-perform heavy, who had the exact same dead rollout in year one — the office used it, the field didn't. Their VP of Ops will take a fifteen-minute call with you and tell you what they did differently the second time. Want me to set it up?" If nothing has genuinely changed, say that and change what you control instead: your own coverage, a named escalation path, an exec sponsor. Do not manufacture progress. They will check.
- 6
Rebuild on what works: find the person, not the feature
"You said the one thing you'd miss is the pay app backup — the change ticket packets attaching to the G702 without Angela rebuilding them by hand. Tell me about that. Who's actually running it and what did it replace?" Then quantify it in their language, out loud: "So before, every pay app went out and roughly one in four came back because the backup on the change work wasn't attached, and that's two, three weeks added to DSO on that draw. What's it been since?" "If we went away April 1, whose Monday breaks?" That person — usually the Controller or a Senior PM — is your remaining champion, and there's a good chance they weren't invited to this call. Get their name and get them in the room before signature. And say the switching cost plainly: it isn't the license fee, it's rebuilding whatever Angela built and running two versions of your billing backup through a summer.
- 7
Handling the competitor
Surface it yourself. Don't wait. "I'd assume you've had [Competitor] in your inbox — I'd be surprised if you hadn't. What did you like about it?" Then find out how far it's actually gone: "Have they given you pricing in writing? Has anyone scoped the migration — what happens to eighteen months of daily reports and photo documentation on the jobs that aren't closed out yet?" Reframe from price to total switching cost, in their terms: "Here's the part I'd want you to think through. The people who did adopt this are your office — Angela and your two PMs on the hospital job. Switching means retraining the only group that's actually using it, in the same year you're trying to get the field on. And your historical labor records live here. If a backcharge fight comes at closeout on a job that finished last fall, the documentation is in this system, not the new one. And honestly — the risk you're taking is that you inherit somebody else's version of the same support problem, except this time you've got no year of goodwill and no history with the rep." Do not match on price here. Price is the last section.
- 8
The 90-day plan: build it live, four fields per line
"If we do this, I don't want to sell you twelve more months of what you just had. Let me build the first ninety days with you right now, and I'll send it in writing tomorrow. Every line has a name on it — mine and one of yours. Field adoption: we run it on one job, not the whole company. Pick the job — I'd say the distribution center because it's just starting. Two foremen: one who's fine with a phone and one who's your loudest holdout. I fly out and run it onsite in a truck, not on a Zoom. Week of the 14th. Done looks like: T&M tags submitted same day the work happens, and days from field work performed to COR submitted under three on that job by day 60. Support: named escalation contact, direct cell, four-hour response on anything that stops the field. Effective at signature, written into the contract with a credit attached if we miss it. Governance: 30, 60, 90 check-ins with a written usage report by role. First one dated on the calendar today. Your side: I need your general superintendent to own it on that one job — not endorse it, own it, meaning he asks the two foremen about it at the Monday coordination meeting. If he won't, tell me now and we build a different plan. And the thing I can't do: the Sage 300 two-way write-back isn't happening before Q3. It was promised in January and it shouldn't have been. I'm not going to pretend otherwise." Ask what they'd add. A plan where only the vendor has obligations is a wish list — and that's part of why the rollout died last time.
- 9
Only now: the commercial conversation
Earn the transition out loud: "If we can agree that plan is real, can I walk you through what a renewal would actually look like?" Structure before number: "You're paying for twenty-two field licenses and using seven. I'm not going to discount twenty-two — I'm going to cut you to ten and put a fixed price on adding the rest as the jobs come on. That's a smaller invoice and it kills the shelfware argument permanently. On term: I'd rather do a twelve with a break at six months than fight you for thirty-six. If the plan doesn't hit — if we're not at same-day tags on that job by day 60 — you walk at six months and I don't argue. On the bad year: I'm not discounting the renewal as an apology, because a price cut isn't an apology and you'd read it as one. What I am doing is a service credit for the three months in Q2 where we missed the SLA. That's specific, it's finite, and it's for the year we actually broke." Any further discount is traded, never given: for the multi-year, for the reference call with another VP of Ops, for an earlier signature.
- 10
Multi-thread and close
"Before we hang up — walk me through what happens between now and March 31. Who else signs? Does this go through your Controller, and does she already have the other quote in front of her?" Then three things, on the call, not in a follow-up email: 1. "I'd like fifteen minutes with you, Angela, and my VP of Customer Success in the next two weeks to walk the ninety-day plan. She'll say the same things I just said, which is the point." 2. Book the next meeting live. Date and time, on the calendar before you hang up. Never "I'll follow up." 3. The honest temperature check: "On a scale where one is you've already decided to leave — where are we right now, and what moves it?" Take the honest answer over the polite one, and if it's a three, ask what a six looks like. Within 24 hours, send four things: the written ninety-day plan with names and dates, the ticket data you quoted, the intro to the reference contractor, and a one-page summary of what went wrong this year in their words. That last document does more work than any proposal you'll ever send.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Ray, thanks for the half hour. Contract's up March 31 — I'm not here to talk about renewal yet. I want to talk about this year, because from where I'm sitting it wasn't the year we sold you. Ticket 41-882, your general super opened it June 11 when tags weren't syncing off the hospital job — nine days before we responded. Two CSM changes on our side. And you're paying for twenty-two field licenses with never more than seven weekly active. That's what I can see. What am I missing?
Buyer
What you're missing is that June was the middle of our shutdown season. We had four schools going at once, three crews on the central plant, and my super's calling your 800 number from a mechanical room while I'm getting asked by the GC why the three-week look-ahead doesn't match what's actually staffed. Nine days. He came into my office and said, and I quote, throw the tablets in the dumpster.
Rep
Tell me about those nine days. What did the field go back to?
Buyer
What do you think. Paper tags. Same as 1994. And here's the part that actually costs me — two of those tags never made it off a dashboard. We did the work, the owner's rep says first he's hearing of it, and we ate it. So I'm paying you thirty-eight grand a year for a system that put us back on paper during the only ten weeks of the year that matter.
Rep
How much was on those two tags?
Buyer
Between them? Call it twenty-two thousand of self-performed labor. And that's the ones I know about. My controller thinks unapproved change orders ran close to two percent of contract value across the book last year, but honestly nobody can prove it because there's no field record — which is the exact thing I bought this for.
Rep
So the Q2 response times were a failure on our side. We reorganized support in April and your queue got stacked behind enterprise escalations. That's an explanation, not an excuse — you bought a 24-hour first response and we missed it eleven times, in your worst ten weeks. Separately, the two training sessions Dana committed to in the January QBR never ran. Your foremen didn't fail to adopt it. We never showed up. Anything else on the list before I say a word about what's changed?
Buyer
Yeah. The hospital job. The GC mandated their own platform for daily reports. So my PM is entering into theirs, my foreman's entering into yours, and my super's still keeping a spiral notebook because he doesn't trust either one. Three systems. I'm not doing that again, and the guy from [Competitor] is quoting me about eleven grand less a year for something my controller says does the same thing.
Rep
You'll run two either way — the GC's platform is for their record, not yours, and it will not be on your side the day a backcharge shows up at closeout. But I'm not going to argue you out of the quote. Have they put pricing in writing, and has anyone scoped what happens to eighteen months of daily reports and photos on the jobs that aren't closed out yet?
Buyer
Pricing's in writing. Migration, no, we haven't gotten there. Look, I'll be straight with you — the only reason this isn't already done is Angela. She built the pay app backup out of your system and she says if it goes away her draws start coming back rejected again.
Rep
That's the part I'd want on the table. Before, roughly one in four pay apps came back because change work backup wasn't attached — what's it been since she built that?
Buyer
Better. She'd say one in ten, maybe. Our DSO came off seventy-something to the low sixties, though I'm not giving your software all the credit for that.
Rep
I don't want all the credit. Here's what I'd rather do than defend the year. Don't renew twenty-two licenses. Renew ten — the office group that actually uses it, plus two field. Twelve months with a break at six. And in the first ninety days we run one job, the distribution center, with two foremen: one who's fine with a phone, and whoever your loudest holdout is. I come out and set it up in a truck onsite, not on a Zoom. Success by day 60 is same-day tags and days-to-COR under three on that job. If we miss it, you walk at six months and I don't argue.
Buyer
And support? Because if my super calls in August and gets nine days again, none of the rest of it matters.
Rep
Named engineer, direct cell, four-hour response on anything that stops the field, written into the contract with a credit if we miss it. Plus a service credit for the three Q2 months we already missed — that's for the year we broke, not a discount on next year. What I need from you is your general superintendent owning it on that one job. Not endorsing it. Asking those two foremen about it every Monday. If he won't do that, tell me now and we build a different plan or we don't build one.
Buyer
He'll do it if I tell him it's one job and three weeks. He won't do it if it's another company-wide rollout with a training deck.
Rep
One job, two foremen, three weeks. I'll have the plan to you tomorrow with both our names on every line. Two things before I let you go — can we get fifteen minutes with you, Angela, and my VP of Customer Success the week of the 14th? And honestly, on a scale where one is you've already decided to leave, where are we right now?
Buyer
Three weeks ago you were a two. Right now, maybe a five. Get me the plan in writing, get Angela on that call, and don't make me chase you for it — because if I have to send a second email about this, we're back to a two.
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 — and they proved it this year.” | They did, and part of that's on us for never running the training. So don't roll it out to all of them again. Pick two foremen on one job — one who's fine with a phone and one who's your loudest holdout — for three weeks. If the holdout can't do it in under a minute with gloves on at the end of a ten-hour day, we've learned something cheap and you're out at the six-month break. The test isn't whether he likes it. It's whether the T&M tag gets to the office the same day. |
| “Margins are single digit. Software is a luxury line item and we didn't get anything for it last year.” | Agreed on last year, which is why I'd rather talk about the unbilled work than the subscription. You just told me two tags off the hospital job were twenty-two thousand of self-performed labor billed at zero, and your controller thinks unapproved change orders ran near two percent of contract value across the book. I'm not asking you to believe my number. Pull the WIP, pick the two worst faders, and tell me how much of the fade was change work that never got documented. If it's a fraction of what you think it is, this pays for itself on one job. |
| “We already bought this. Nobody used it. I'm not doing that again.” | Fair, and the rollout was a login email and a deck that nobody delivered. What I want to know is what they stopped doing first — the daily report or the change tickets? Because if the answer is both, in about five weeks, then the ninety-day plan has to have your general superintendent's name on it and not just mine. Adoption died last time partly because nobody on your side owned it, and I let that happen without saying it. |
| “The GC makes us use their platform on the hospital job. I'm not running two systems.” | You're already running three — theirs, ours, and your super's notebook. Their system exists for their record. The version I care about is the one that documents your labor hours and your tags when the backcharge fight comes at closeout, because their platform will not be on your side that day. If it helps, let's take the hospital job out of the ninety-day plan entirely and run this on the distribution center, where nobody's mandating anything. |
| “[Competitor] quoted us eleven grand less. Same features, my controller says.” | I'd expect that quote, and I'm not going to talk you out of it on price — matching would just tell you I was overcharging you all along. Two questions instead. Have they scoped what happens to eighteen months of daily reports and photo documentation on the jobs that aren't closed out yet? And who retrains Angela and your two PMs — the only people who actually adopted this — in the same year you're trying to get the field on? The switching cost isn't the license fee. It's her billing backup workflow and six months of not having it. |
| “Backlog's booked through next year. We're too busy to implement anything right now.” | Busy is exactly when the tags stay in the truck — June proved that better than anything I could say. I'm not asking for an implementation. I'm asking for one job, two foremen, three weeks, and me on site. If you're too busy for that, then you're genuinely too busy, and I'd rather you tell me now than sign a twelve and have it die in the spring again. |
| “Talk to my PMs and my controller. They're the ones who actually use it.” | I will, and I want Angela on the plan review specifically. But your PMs will optimize for their own jobs and you're the one looking at margin 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. |
Questions reps ask about this call
- What makes a construction renewal save call different from a normal renewal?
The customer usually isn't leaving over features — they're leaving because the field never adopted it and something broke during their busiest stretch. In this industry that stretch has a name: shutdown season, the summer school work, the winter push before a substantial completion date. Your script has to name that window specifically. "Ticket 41-882 sat nine days in June" lands. "We know Q2 was rough" does not, because it tells them you never actually looked.
- Should I lead with a discount if a competitor has quoted 20-30% lower?
No. A price cut reads as an apology, it reframes a bad service year as a pricing dispute, and it permanently resets your floor. The honest instrument for a bad year is a service credit for the specific months you missed the SLA — finite, dated, tied to the actual failure. If you need to reduce the invoice, reduce seats to real usage instead. Cutting twenty-two field licenses to ten shrinks the number and kills the shelfware objection at the same time.
- How do I handle it when their general superintendent is the one killing adoption?
Don't fight him and don't route around him. Shrink the ask to something he can't reasonably refuse: one job, two foremen, three weeks, with you on site in a truck rather than on a Zoom. Then put his name in the 90-day plan as an owner — not an endorser. The line to use is: "I need him asking those two foremen about it at the Monday coordination meeting. If he won't, tell me now and we build a different plan." A plan where only the vendor has obligations is a wish list, and that's how the first rollout died.
- Which metrics should actually appear in the 90-day plan?
Field-level ones the VP of Operations and the CFO already argue about at the WIP review. The two most useful: days from field work performed to COR submitted (target under three on the pilot job by day 60), and same-day T&M tag submission rate on that job. Behind those sit the ones the CFO cares about — unapproved change orders as a percentage of contract value, DSO and retainage outstanding, and gross margin fade in points from bid to as-built. Tie your success criteria to the first two, because those are the ones your product can actually move in ninety days.
- Who else needs to be on the call besides the VP of Operations?
Whoever built a workflow around the product — usually the Controller doing pay app backup, or a Senior Project Manager running the change ticket log. That person is your remaining champion and is often not invited to the save call. Get them into a plan review inside two weeks. You also need to know whether the Controller or CFO already has the competitor's quote in writing, because most stalled renewals in this industry die in the finance conversation you never got into, not in the operations conversation you did.
- What do I send after the call?
Within 24 hours, four things: the written 90-day plan with a name and a date on every line, the ticket data you quoted so they can check it against their own inbox, the intro to a reference contractor of similar size who survived the same dead rollout, and a one-page summary of what went wrong this year in their words. That last document does more to save the account than any proposal, because it proves the meeting wasn't a technique.