Construction companies rarely lose work because they cannot build. They lose it in the quiet week after someone called about a project.
The site visit happened. Photos are on a phone. The estimator is on another job. The homeowner or developer is collecting three prices. Whoever sends a clear estimate first, with a named next step, usually gets the job. The rest of the “pipeline” is a WhatsApp thread.
This is not an argument for a construction ERP. Most firms we talk to need a credible website and a lead-to-estimate path that a human can run on a Tuesday. We have shipped that kind of presence for Yukonhaus. We have not built a fictional job-costing suite to sell you.
The actual path
Write yours down. It usually looks like this:
- Enquiry (web form, phone, referral, Google)
- Qualification (budget, timeline, location, project type)
- Site visit or drawing review
- Estimate
- Follow-up
- Won / lost
- Kickoff and client updates
Every handoff is a place the job goes cold. The website only owns step 1. Software people who start with a “client portal” are often skipping the leak at steps 4–6.
Qualification is not a contact form named “Get a quote”
“Name, phone, message” produces tyre-kickers and a calendar full of unpaid site visits. Ask for:
- Project type
- Location / site constraints
- Rough budget band
- Target start
- Drawings or photos, if they exist
You will still take walk-ins. You will stop treating every Facebook comment as a tender.
If volume is high, missed-call text-back keeps the lead warm until an estimator can talk. That is a CRM behaviour, not a slogan on the homepage.
Estimates need a home
The estimate is a document and a pipeline object. If it only lives as a PDF in email, you cannot answer “what is waiting on the client?” without opening three inboxes.
Minimum fields:
- Date sent
- Amount
- Valid until
- Outstanding documents
- Next follow-up date
- Lost reason, when it dies
Follow-up should be scheduled when the estimate is sent, not remembered on Sunday night. Two touches beat eight “just checking in” messages.
Job tracking without theatre
Once the job is won, the leak changes. Clients want photos and dates. Project managers want not to write the same paragraph fourteen times.
A lightweight update flow is:
- Milestone list the client can understand
- Photo drop after key inspections
- Change orders in writing
- A weekly note even when nothing dramatic happened
That can be a CRM, a simple shared page, or a disciplined email template. It does not need BIM integration. If someone is selling you that before your estimates are tracked, they are selling their product, not your bottleneck.
What the website must do
The site has one job before the form: prove you can build. Fast project photography, real addresses of completed work where you have permission, and a scope of services that matches what you will actually bid.
A template contractor theme with stock hard hats does the opposite. That is why the construction page leads with proof, not a feature grid.
Roofing and other trades
If you run roofing or remodeling, the same lead-to-estimate physics apply. We published a roofing CRM guide because the operations question is real. We did not publish a roofing sales page, because we do not have a roofing case study to put on it.
What to do this month
- Count enquiries vs estimates sent vs jobs won for the last 30 days.
- Put every open estimate in one list with a follow-up date.
- Add three qualification questions to the website form.
- Decide whether the next spend is photography and the site, or the pipeline.
If you want help, bring those four numbers. We will not open with an ERP demo. The commercial page is software for construction companies.