Tom runs a small building firm with four staff. He prices jobs, manages sites, orders materials and does much of the work himself. New enquiries matter, but they compete with everything else.
This is a typical week before and after automating enquiry capture and qualification.
Before: Monday
Tom starts the day on site at a kitchen extension. His phone shows five new enquiries from the weekend. He reads them at lunch. Two are from homeowners with realistic projects. One is outside his area. One wants a price for a job he does not do. One is a supplier. He replies to the two good ones that evening, after dinner.
Before: Tuesday
A homeowner who enquired on Sunday calls to say they have already booked another builder for a site visit. Tom realises his Monday evening reply was too late. The homeowner had contacted three builders on Sunday, and the first to reply with a sensible question and a visit time got the job. For a firm Tom's size, one lost extension is several weeks of work gone.
Before: Thursday
A subcontractor Tom relies on messages to say they are free next week, but the message is buried under enquiries and supplier emails. Tom only sees it on Friday, by which point the subcontractor has taken other work.
Before: Wednesday
Tom drives forty minutes for a site visit. The homeowner's budget turns out to be a fraction of what the job needs. He drives back, having lost half a day.
Before: Friday
Tom spends Friday evening answering messages: questions about lead times, prices and whether he does loft conversions. All of it is on his website, but people still ask.
Counting the cost
Across the week, Tom loses at least one good project to slow replies, wastes half a day on an unsuitable visit and spends several evening hours on repeat questions.
After: Monday
Tom adds a website assistant trained on his own pages. SpideyChat for contractors and builders answers questions about services, area, lead times and typical costs, and captures project details: type, location, timeline, budget range and whether plans exist. It does not give quotes or promise dates.
On Monday lunchtime, Tom sees five enquiries. The out-of-area and wrong-job enquiries were answered politely with suggestions. The supplier was logged separately. The two good ones are waiting with full details.
After: Tuesday
Tom replies to both good enquiries on Monday lunchtime, with proposed visit times. Both book.
After: Wednesday
Because the budget range was captured up front, Tom only visits projects that fit. Qualifying before visits is covered in project enquiries that need qualifying before a site visit.
After: Friday
The repeat questions have been answered on the website. Tom's Friday evening is his own.
What does not change
Tom still meets every serious client personally, still prices every job himself and still runs his sites. The assistant handles first contact. He handles the building.
Lessons from other businesses
The pattern is familiar in many sectors. A gym front desk goes through the same shift, described in a gym front desk week before and after automation. The general approach to automating repeat questions is covered in how to automate your top 20 support questions.
Fixing the website first
The assistant is only as good as the website it learns from. Common gaps that trip contractors up are covered in contractor website mistakes that lose projects. Fix those first.
Getting started
Update your pages on services, area, lead times and typical costs, then let first contact happen at any hour. See the capture options on the features page, or try SpideyChat on your own site.