Where Construction Companies Lose Customers Before the Job Starts

Open the spreadsheet. Or the CRM, if someone bought one. Scroll past the jobs you are running now and keep going.

There it is. Forty, sixty, two hundred rows. Names you half remember. A kitchen in March. An extension somebody's wife called about. A fit-out you drove ninety minutes to look at. Some rows have a number in them. Most have nothing after the name and the date. No note of what was said. No owner. No next step. Nothing telling you whether the job is dead or whether the customer is at home wondering why you never called back.

Everyone in the business knows the board is there. Nobody knows what to do with it. So it grows.

That board is not a filing problem. It is money you already spent. Every row cost a phone call, a site visit, the fuel to get there, and an hour or two of the only person in the company who can price work properly. At the average net margin American remodelers reported for 2024, 6.3 percent, you need roughly sixteen dollars of new revenue to replace every dollar of profit that walks out of that spreadsheet. That is arithmetic on the National Association of Home Builders' member survey figure, whose public summary does not state a sample size. Treat the number lightly. The shape of it is not in doubt.

The board is an output, not a character flaw

The usual explanation is that people got busy and let it slip. Try harder next quarter. Buy a system. Send someone on a sales course.

That does not survive contact with the research on why people delay things. Piers Steel's meta-analysis in Psychological Bulletin, drawing on 216 separate works and 691 independent correlations, identified task aversiveness as one consistent correlate of putting something off, with a correlation of r = .40. Fear of failure came in at r = .18, across a far larger evidence base of 57 studies and nearly 11,000 people. That does not prove why a contractor avoids a call. It does suggest an alternative to assuming fear or poor discipline: the call may be unpleasant to start.

So the useful question is not who lacks discipline. It is what made the task unpleasant to start, and whether you built that in yourself.

Walk the process in order and you can see where it gets built.

The lead nobody wrote down

Work arrives through the owner's mobile, a web form, a shared inbox, a message on a social account somebody checks occasionally, and a referral mentioned on a job site at half four on a Friday. There is no single front door.

What is never captured is not on the dead board. It is not anywhere. That makes this the hardest loss to argue about and the easiest one to keep having, because there is no artefact to point at. The first discipline is not follow-up. It is that every inquiry, however it arrives, lands in one place within the day.

Responding is nobody's job

Here is where the popular advice goes wrong, and it is worth being precise about it.

You have read that speed wins, that your odds collapse if you take thirty minutes instead of five. That figure comes from a 2007 study of roughly 15,000 web leads at six companies, co-authored by the chief executive of the company selling software to call leads faster. Those response-time comparisons concern contact and qualification, not construction contract wins. An observational comparison can also be affected by which leads salespeople choose to call first. It does not establish how much faster responses improve a contractor's chances of winning work.

So set the multiplier aside. What is actually measured is worse, and simpler.

A marketing agency, Valve+Meter, ran a secret shopper through the inquiry forms of 466 US home services companies and tracked them for five days. Forty percent never responded at all. Eighty-five percent never attempted a second call. That is the agency's own research, published to sell marketing services, and should be read with that in mind. But it is original, its method is stated, and it matches independent audits elsewhere. Harvard Business Review reported in 2011 that of 2,241 US companies sent a test inquiry, 23 percent never replied.

Read that again. For that substantial group, the problem is not that the response was slow. It is that there was no response. You cannot lose a race you never entered.

That is not a speed problem. It is an ownership problem, and the same absence governs the most expensive thing you do. Most contractors estimate everything that asks, so the estimating capacity you cannot buy more of gets spent on work you were never going to win, and the good opportunity gets a rushed number and a slow reply. There is no gate before the site visit and no gate before the takeoff. The evidence cited here does not establish what a residential estimate costs to produce, which is worth noticing on its own. You are rationing your scarcest resource without knowing what a unit of it costs.

One undifferentiated list, so no cadence at all

Every opportunity sits in the same pile. The eighty thousand extension with a decision due in a fortnight sits next to somebody who asked about a patio in passing.

When everything is treated the same, the only cadence you can sustain across the whole list is no cadence. Classification is not tidiness. It is what makes differentiated follow-up possible at all. A high-value job with a decision date needs a call on a named day. A speculative inquiry needs something lighter and much slower. Without the distinction, both get nothing.

Follow-up was never a process

The proposal goes out. And then the process ends, and the contractor waits to be told.

Three things are missing, and all three are load-bearing.

An owner. One named person per opportunity, not the team. Karau and Williams meta-analysed 78 studies of effort in group versus individual work and found the drop-off largely vanishes when an individual's contribution can be seen, falling to d+ = 0.08 where output was evaluable against 0.59 where it was not. In a small contractor the named owner is usually also the person running jobs, so sales gets whatever time is left after the site emergencies. Which is none. Naming someone does not create time. It creates the one condition under which the work is visible enough to be protected.

A cadence. What happens, on which day, if the customer has not come back. Set in advance and per classification, not improvised per opportunity in the van.

A dated next action on every record. The cheapest of the three and the one most often skipped. Gollwitzer and Sheeran's meta-analysis of 94 independent tests found that specifying when and where you will do something had a medium-to-large effect on whether it got done, d = .65. Those were mostly people planning their own personal goals rather than work assigned in a system, so the transfer is an argument rather than a finding. It sits alongside Locke and Latham's summary of forty years of goal-setting research in organisations, which is blunter: "when people are asked to do their best, they do not do so."

There is peer-reviewed work on exactly this failure in sales. Sabnis and colleagues, studying 461 sales representatives across four firms in the Journal of Marketing, found that whether leads get worked is driven by organisational lead qualification and managerial tracking. The lead black hole is an organisational output. That is the whole argument of this piece in one line.

Why the dead board defends itself

This is the part I find most interesting, and the part most likely to be recognised.

Suppose someone does open the board. They find a name, a date, a number. No record of what the customer was worried about, what was promised, or why it went quiet. Re-entering that conversation means either admitting you lost the thread or bluffing and hoping. Both are uncomfortable. So it gets left for a better moment, and every week that passes makes the opening line harder to write.

Research on why people stop checking their own progress fits this closely. Chang, Webb and Benn asked 221 people to describe real instances of avoiding monitoring a goal. The most strongly endorsed reasons were that the information would demand a change in beliefs, and that it would demand action they did not want to take. Looking is what obliges you to do something. In a study of 1.17 million retirement accounts, logins fell by 9.5 percent after market declines.

I want to be careful here, because this is where I am reasoning past the evidence. These studies did not examine a contractor deciding whether to reopen a stale lead. The research supports two things: people delay tasks they find aversive to start, and they avoid looking at records that would oblige them to act. The step from there to "so the board gets worse the longer it is left" is my inference, not a result.

The practical conclusion does not depend on it. Logging what was said, as it is said, keeps the cost of re-entry near zero. That is the entire point of writing it down, and it is why documentation that exists but is never used is a different problem from documentation that does not exist.

Nothing is ever closed, so the number is fiction

There is no forcing function. Records sit in limbo indefinitely. "Quoted" covers a customer signing next week and a customer who stopped answering in March, so the pipeline total means nothing and cannot be used for capacity or cash planning.

Worse, loss reasons are almost never captured. So the business never learns whether it loses on price, on schedule, on responsiveness or on trust, and pricing gets adjusted on feel. In one study of how people choose a home improvement professional, 5,215 validated US respondents in the American Economic Journal: Applied Economics, price words appeared in 49 percent of open-text answers about why they hired someone, and reviews mattered more than verified licensing. If you have never recorded a loss reason, you are guessing about the one thing you could know.

The scope that did not survive the handoff

The sale does not end at signature, and neither does the leakage.

It happens twice. First when the estimator's assumptions, exclusions and allowances never make it into the document the customer actually reads. Then again when what was promised at the kitchen table never reaches the crew or the schedule. The customer only experiences the second one, and they experience it as a broken promise.

The best measured evidence on where quality failure costs money points at exactly this interface. Love, Teo and Morrison analysed 7,082 categorised non-conformance reports across 218 projects delivered by one contractor over nine years. Six factors accounted for 82 percent of total non-conformance cost, and the largest by a wide margin was subcontractor management at 34.4 percent, ahead of inspection and process control at 18.8 percent and design at 13.9 percent. Work-method error came to 4.7 percent, supervisory error to 4.6 percent. In this dataset, management, inspection and design categories account for more cost than the listed work-method and supervisory errors. My reading is that the handoffs between scope and execution deserve just as much attention as workmanship.

Two honest caveats. That study covers large commercial and infrastructure work, and building projects within it had the lowest recorded failure cost of any sector. And the same research group has since said in print that the widely quoted figures putting rework at five or twelve percent of project value were "guesstimates" drawn from questionnaires rather than measured costs. That study does not establish what rework costs a residential contractor. The causes may be relevant, but the percentages cannot simply be transferred, and I am not going to borrow one.

Which brings up the change order, and a claim worth arguing for.

A change order is a sale. It has a scope, a price, an approval and a signature, and all four belong before the work proceeds. Treated as after-the-fact paperwork it leaks margin directly and manufactures the disputes that turn into slow payment. The US Department of Transportation, reporting a Texas DOT finding covering 2001 to 2015, noted that roughly a quarter of all change orders and about a third of all change order value were related to errors and omissions. Arcadis's annual disputes research puts the same things at the top year after year: parties failing to understand or comply with their obligations, and errors or omissions in the contract documents. That is a consultancy's own casework, publishes no sample size, and covers disputes averaging tens of millions of dollars. The values have nothing to do with your business. The causes are documentary and human, and those scale down.

So put change orders inside the sales process, where approval before execution is already the rule, rather than in the accounts process, where they arrive as an invoicing question after the money is spent.

The referral left to chance

In a poll of 5,000 UK adults responsible for arranging home repairs, conducted by Opinium for Citizens Advice, 36 percent of those who had used a trader found them through someone they knew. Past customers, and the designers, architects, agents and property managers around them, are a lead source where the trust is already built and the entry cost is already paid.

Almost nobody has a defined process for staying in front of them. It is treated as something that either happens or does not.

What good actually looks like

None of this requires a system. It requires a few structural properties.

Every opportunity carries a classification, and the classification drives the cadence rather than sitting there as a label. Every opportunity has one named owner, a person and not a team. Every opportunity has one next action with a date on it, and the working rule is that an opportunity with no dated next action is not in the pipeline, it is a memory. Activity is logged as it happens, so context survives absence, handover and time. Stages have entry and exit criteria, so the pipeline number means something.

And then the one that actually kills the dead board. Every opportunity is either progressing, parked with a date it wakes up, or closed with a reason. There is no fourth state. Limbo is not available. A board cannot go dead if nothing is permitted to sit in it undecided.

A standing review that forces those decisions is what keeps it true, because the decision does not make itself.

What this does not fix

Three things, honestly.

Software will not do this for you. The famous claim that most CRM projects fail has no traceable original study behind it. The Gartner figure it descends from measured projects that "failed to meet expectations," and the analyst responsible disowned the failure reading in print. The peer-reviewed work is narrower and more useful. Reinartz, Krafft and Hoyer, studying 211 European firms, found that implementing CRM processes predicted performance positively while CRM technology had a negative main effect on how managers rated their own performance. Other work finds small positive effects from the technology itself, so the honest reading is that neither the software nor the reorganisation does the job alone. We have seen the failure mode directly. A client had bought a CRM and had no system around it, so barely anyone used it. The fix was to design the workflow first, build the automations behind it for assignments, status triggers, escalations and reporting, then document it and train the team so it held after we stepped back. The order mattered.

A cadence set too tight does damage. In residential work the customer is making a large, slow, personal decision, often with a partner, often about the place they live. Following up daily on a decision that will take five weeks reads as pressure, and pressure loses jobs that patience wins. The cadence has to match the size of the job and the length of the decision, which is another reason classification comes first.

A five-person contractor should not run enterprise process. Across the EU in 2023, 94.2 percent of construction enterprises had fewer than ten people. In a historical BLS cohort of establishments born in 1998, construction businesses began with an average of 3.6 employees. That is not a current staffing benchmark, and the case for process here is not fear of failure. The argument is for the minimum discipline that makes the work survivable, not for a system, and certainly not for starting with notation and diagrams. I am BPMN certified and I would not begin there with a twelve-person builder.

The point

The dead board is not evidence that your people lack discipline. It is the predictable output of a process that was never defined, and it will re-form after every clear-out as long as the process that produced it stays the same.

Somewhere in that spreadsheet is a customer who liked you, wanted the work done, and never heard back. You paid to meet them. The only thing that stopped the job was that following up was nobody's job on no particular day.

Ahmed Fahmy is Co-Founder and CEO of Blackwing. He has spent eight years in business analysis, business process management, requirements gathering, process reengineering and operational documentation, including two and a half years at enterprise level and a period as Head of BPM at New Age leading a team of four. He is BPMN certified.

Related reading

Why SOPs Fail: The Document Is Not the System

SOP Management: Why Documentation Alone Fails to Create Consistency

Common Obstacles with BPMN Documentation

Back to blog