How to Sell Into Construction and the Trades Without Sounding Like a Software Guy

Every industry has a moment where the buyer decides which bucket you go in. In construction it happens fast, usually inside your first two sentences, and once you are in the wrong bucket you are not getting out on that call.

The bucket is "software guy." It is not a compliment. It means you have never stood in a gravel lot at 6:40 in the morning, you are going to talk about workflows, and whatever you sell is going to end up as another login nobody uses. The buyer is not being unfair. They have been sold this before.

I have built and exited four businesses and sold inside AWS and Dell, and construction is one of the few patches where the product almost never loses on features. It loses on credibility. So this is a guide to not sounding like a software guy — who actually buys, how the money moves, when to pick up the phone, the words that get you taken seriously, and how the trust problem reshapes every stage of the cycle from the first dial to the renewal.

Who actually buys

Start by throwing out the org chart you use for tech companies. There is no Head of Revenue Operations. There is often no CTO. There may be a guy named Dave who set up the email and is also the estimator.

The first thing to understand is that construction companies split into two very different animals, and they buy differently.

General contractors

GCs manage. They win the project, break it into scopes, and hire specialty contractors to actually swing the hammers. Their people are project executives, project managers, superintendents, and a VP of Operations sitting over the top of all of it.

The project executive owns a portfolio of jobs and is measured on whether those jobs hit the margin they were bid at. That is the entire job. They are your economic buyer for anything that touches schedule, cost, or documentation, and they are chronically short on time because they are being escalated to from four directions.

The superintendent runs the physical jobsite. They do not buy anything. They can absolutely kill your deal, because if the super does not use it, the field does not use it, and dead adoption is how these accounts churn. Treat the super as a required champion, not a nice-to-have.

The VP of Operations is where the money and the pain meet. They see every job's numbers, they hear every complaint from the field, and they are usually the person who signed the last three tools that failed. They are also the person most likely to answer their own phone.

Specialty contractors

Electrical, mechanical, plumbing, concrete, roofing, drywall, low voltage. These are the subs. They self-perform the work, they own trucks and tools and crews, and a huge number of them are owner-operated.

In a specialty shop the buyer is very often just the owner, sometimes with an operations manager and a controller. The cycle is shorter. The check is smaller. The scrutiny is higher, because it is the owner's own money and not a line item in an overhead budget. An owner who came up as a journeyman and now runs forty people will make a decision on one call if you give them a reason to, and will also never speak to you again if you waste twenty minutes on discovery theater.

The people who are not the buyer but decide anyway

The office manager or controller controls the calendar, the payables, and often the actual software stack. If you steamroll this person you will find that the contract sits unsigned for six weeks for reasons nobody explains.

The foreman is the last mile. Every tool that survives in construction survived because a foreman decided it made his morning easier. Every tool that died, died because it added a step to his morning.

How the money actually works

This is where most reps out themselves. If you do not understand how a construction company makes money, you cannot connect your product to it, so you fall back on "efficiency" and "visibility," which are the two most meaningless words you can say to someone whose crew is standing around waiting on a material delivery.

Here is the model in plain terms.

Work is won by bid, and the bid contains the margin. The company estimates labor hours, materials, equipment, and overhead, adds a margin, and submits a number. If they win, that number is now the ceiling. Everything that goes wrong from that point comes out of the margin. Construction margins are famously thin relative to the revenue numbers involved — a company can do a very large annual volume and still be one bad job away from a very bad year. That asymmetry is the emotional core of every conversation you will have.

Labor is the variable that moves. Materials are mostly locked at buyout. Equipment is mostly known. Labor hours are the thing that bleed. Rework bleeds hours. Waiting on an RFI answer bleeds hours. Sending a truck back to the shop for a tool that was already on the job bleeds hours. If your product saves hours in the field, say it in hours. If it saves hours in the office, be honest that it is an office benefit, because they can tell.

Change orders are how a job gets healthy or dies. Scope changes constantly. If the change is documented, priced, and signed, it is revenue. If the crew just did the work because the super on site asked them to and nobody wrote it up, it is free work and it comes straight out of margin. Ask a specialty contractor owner about unbilled change orders and watch their face. That is a real wound. Almost every one of them has a story about a job where they did the work and never got paid for it.

Retainage and cash flow. A percentage of every progress payment gets held back until the job closes out, so the company is financing work it has already completed. That is why closeout documentation matters so much and why "we'll get to it later" is expensive. It is also why a controller cares about anything that speeds up billing far more than they care about anything that speeds up planning.

Backlog is the health metric. How much signed work is on the books for the next several quarters. When backlog is fat, they will buy things that make execution easier. When backlog is thin, they will only buy things that help them win work or cut cost. Ask about backlog early. It tells you what kind of pitch you are in.

When to call

The calendar in construction is not the calendar in SaaS.

The field day starts early. Crews are on site before most tech buyers have opened their laptop. Superintendents and VPs of Operations are usually reachable in the window before the day gets away from them — early morning, before the first crew issue lands. I have consistently had better luck dialing in that pre-shift window than at any point during the working day.

Mid-day is dead. Between mid-morning and mid-afternoon your buyer is on a jobsite, in a truck, in a walk-through, or in a meeting with an owner's rep. They will not answer, and if they do answer they are annoyed.

Late afternoon opens back up. The crews are wrapping, the superintendent is doing paperwork, the owner of a specialty shop is back at the yard. That second window is real and most reps never use it because it falls outside the hours they have decided are "prospecting time."

Also pay attention to the week and the season. Monday morning is triage. Friday afternoon in a specialty shop can be surprisingly good because the week's fires are out. Bid day is a black hole — if their estimating team is chasing a deadline nobody in that building is talking to you. And if you sell into a region with real weather, the shoulder seasons change everything: winter in the north is when office staff finally have time to implement something, which makes it the best implementation window and a great reason to close in the fall.

The mechanics of getting a real conversation in those windows — the opener, the pattern interrupt that does not sound like a pattern interrupt, what to do when the super picks up in a truck with the radio on — are worth their own treatment, and I laid the whole thing out in the construction and trades cold call script for VPs of Operations and general superintendents rather than trying to compress it here.

The vocabulary that outs you

You do not need to fake being a tradesperson. Faking it is worse than not knowing. What you need is to use the right nouns for the right things, and to stop using the words that only exist in software.

Words that signal you have done this before. Jobsite, not site. Crew, not team. Field and office, which is the fundamental divide in every one of these companies. Scope. Buyout. Submittal. RFI. Punch list. Closeout. Retainage. Backlog. Self-perform. Prequal. T&M versus lump sum. Mobilization. The yard. The shop. Callback, meaning warranty work you have to go back and fix on your own dime.

Words that end the call. Solution. Platform. Digital transformation. Stakeholders. Alignment. Leverage as a verb. Single source of truth. Seamless. Empower your workforce. Any sentence containing the phrase "in the field" spoken by someone who has clearly never been in one.

The deeper tell is not vocabulary, it is time horizon. Software people talk in quarters and roadmaps. Construction people talk in jobs. A job has a start, a finish, and a number. When you ask a project executive about their goals for next year, you get nothing. When you ask which job on their board is currently underwater and why, you get twenty minutes.

One more: never, ever say you will "put some time on their calendar to align." Say you will call them Tuesday at 6:45. Then call them Tuesday at 6:45.

The trust problem, and what it does to your cycle

Here is the thing nobody tells reps who get handed a construction patch. You are not the first. Your buyer has already bought a piece of software that was supposed to change everything, and it died in the truck.

That is the literal phrase you will hear. The tags are in the truck. The tablets are in the truck. Somebody bought hardware, or an app, or a scanning system, the office was excited, the field ignored it, and eighteen months later there is a box of gear in the back of a pickup and a line item on the P&L that nobody wants to talk about. Whoever signed that deal took the hit internally. Sometimes that person is the one you are talking to.

This single fact reshapes every stage.

It changes discovery

You cannot run a standard pain-funnel discovery on someone who has been burned, because they will give you the pain and then quietly decide you are the same as the last guy. The move is to go at the failure directly and early. What did you try before. Who championed it. What happened in month three. Who stopped using it first, the field or the office. What did that cost you, not in dollars, in credibility.

When a buyer tells you the last rollout failed, that is not an objection, it is the most useful information in the deal, because it tells you exactly what your implementation has to survive. I built a full 25-minute discovery playbook for construction and trades around getting past that "the tags are in the truck" moment instead of politely stepping around it.

It changes the demo

A burned buyer does not watch your demo looking for capability. They watch it looking for the moment where a foreman has to do something extra. That is the only thing they care about. Every screen you show, they are mentally putting it in the hands of the worst-case guy on their worst-case crew at the end of a long day.

So demo the field experience first, and demo it on a phone, held in a hand, the way it will actually be used. Do not open with the dashboard. The dashboard is what the last vendor opened with. Show the two taps the foreman has to do, then show what the office gets as a result. I walk through the whole running order in the demo script for a VP of Operations who has already been burned once, including how to handle the moment they go quiet and cross their arms.

It changes how you close

Pilot on one job or one crew, not company-wide. Construction buyers understand pilots because that is how they think anyway — a job is a contained unit with a start, a finish, and a number. Define what success looks like on that one job before you start, in their language, and put a date on it.

And be careful what you promise about implementation. The office will say they can handle the rollout. The office is understaffed and it is bid season. If you leave enablement to them, you have just built next year's dead account.

It changes renewals

The renewal in this industry is not a formality, it is the moment the buyer finally gets to settle the question of whether you were different. If adoption is soft, they already know. They have known for months. Walking into that call with a usage chart and a positive attitude is how you lose it.

The accounts I have seen saved were saved by a rep who named the problem out loud before the customer did, took responsibility for the part that was theirs, and came with a specific restart plan tied to one crew and one job. That conversation has a shape to it, and I put the shape down in the renewal script for saving a construction account after a year of dead adoption.

What I would do this week

If you just got handed this patch, do not start by learning the product. Start by learning three companies. Pull up a mid-sized specialty contractor near you, read their project pages, figure out what they self-perform and who their typical GC is. Do that twice more. Then write an opener that could only be said to that company, and dial it before seven.

The part that takes longest is not the knowledge, it is the fluency — being able to say "unbilled change orders" without a beat of hesitation, and to handle "we tried something like this and it's sitting in a truck" without your voice going up at the end. That comes from reps, and doing those reps on live buyers is expensive. It is exactly why I built DrillCall: so you can run the early-morning cold call, the burned-buyer demo, and the dead-adoption renewal against a voice that pushes back the way a real VP of Operations does, until the words come out flat and confident. Then go make the call.