Lothian

AI for Construction Firms in Lothian

Any firm with Lothian on its patch is running three different businesses under one roof. Out east the work is coastal and hospitality-led, hotel refurbs in North Berwick, small commercial jobs tracking the tourist pound along the coast road down to Dunbar. West of the city the register shifts to warehouses around Livingston, light industrial units at Bathgate, the leftover flavour of the motorway corridor that shaped who the clients were a generation ago. Midlothian sits in the middle with a commuter-belt mix of small commercial and residential. The owner of a firm like this has an estimator pricing a Livingston warehouse on Monday morning, a Haddington hotel refurb after lunch, and a Penicuik extension on Tuesday. The scope shape, the supplier list, the labour rates, the client expectations, none of it transfers cleanly. Owners here already suspect the context-switching is eating their week.

What we do

How we help construction firms in Lothian

Quoting the jobs you should already be winning

A fit-out contractor down in the north of England came to us with the same quoting complaint we hear across the trade. They were losing roughly a third of the tenders on the desk, not because the bids looked weak, but because the estimator simply could not pull six to ten hours of focused pricing work out of a week that also involved walking live jobs, fielding client calls and turning up to site meetings. The tenders the firm was built to win kept drifting past their deadlines.

The tool we built for them reads the tender pack, holds the firm's standard scope wording in a proper library instead of scattered across six old quotes, and pulls in current merchant prices so the estimator is not chasing round suppliers for the same information twice a week. From a short brief he types in himself, the tool drafts a structured starting quote. He then goes over the lines, adjusts the rates where his experience tells him the standard price is wrong for this particular job, puts in the labour judgement, and signs the quote off himself. The retyping, the price chasing and the scope assembly is what comes off the estimator's plate.

After a quarter of use the numbers came out like this. Turnaround on a typical quote came down from six-to-ten hours to around ninety minutes. Monthly volume moved from twelve to twenty-six. Win rate climbed from twenty-two per cent to twenty-eight. The owner reckoned the firm was suddenly able to chase around £1.4 million in annual pipeline it had quietly been declining under the old setup.

Pricing a Livingston warehouse in the morning and a Haddington hotel refurb in the afternoon

What quietly wears out an estimator in a firm like this is the switching, more than the volume. A warehouse fit-out near Livingston needs a different scope library, different merchant prices, different labour assumptions and a different house style for the quote document than a seaside hotel refurb in North Berwick. A small industrial unit in Bathgate does not look anything like a shopfront job in Haddington. By the time the estimator has finished the Livingston quote and sat down to start the Dunbar one, he has already lost twenty minutes to changing gear mentally. Over a week, most owners already know that is where their Sunday night went.

We build tools that hold a separate scope library, a separate merchant price file and a separate quote template for each kind of work the firm does, and pick the right one automatically from the short brief the estimator types in. A warehouse job gets warehouse rates and a warehouse scope draft. A hotel refurb gets hospitality scope and the soft-finish supplier list. A commuter-belt residential extension gets the smaller domestic kit. The estimator still owns the numbers for every line, because a Livingston warehouse and a North Berwick hotel are different jobs and need different judgement. What goes away is the context-switching that was silently eating an hour out of every quote. The realistic saving is around half of the day-to-day quote cycle, and it lands quietly rather than dramatically.

First-call enquiry handling for the jobs you should be picking up

Enquiries do not wait in this trade. A contractor pings WhatsApp at seven looking for a concrete load by ten. A hospitality client rings the office about a shopfit that needs a price before the weekend. The calls the office picks up get answered, the ones it does not fall away. Most owners suspect the drop-off is costing them work without being able to put a number on the damage.

For a ready-mix concrete supplier we worked with, the phone-and-WhatsApp chaos was the single biggest source of walked revenue. What we built pulled every inbound enquiry into one screen regardless of how it came in, stitched it to the caller's account, recent order history and current plant availability, and handed the dispatcher a complete picture in seconds. The dispatcher still decided whether the slot was worth taking. No load left the plant without a human confirming. First-call confirmation moved from about forty per cent up to seventy-eight, and the recovered revenue across a year came in at roughly £420,000 that had previously been drifting off to whichever competitor answered on the second ring.

I was ready not to like it. I have seen too many tools that try to be cleverer than the lads. This one just does the donkey work and lets them think. That is all I ever wanted.
Owner, 30-person fit-out contractor
How we work

One problem at a time

We work on one problem at a time. No transformation programmes, no glossy strategy decks, no retainer signed before you have seen anything running. The first conversation is a free AI Opportunity Report. Fifteen minutes of your time, and within twenty-four hours you get a written report back that picks out two or three places where AI would pay for itself quickly in your firm, with honest estimates of what it would cost and how long it would take.

If one of the ideas looks worth doing, we talk about doing it. If none of them do, the report is yours to keep. No sales call, and no pressure to move any faster than you want to.

Why Lothian

We are just across the border in the north east

We are based just across the border in the north east, which in practice means the coast road up from Newcastle to Dunbar and then on into the rest of Lothian is a drive we are already used to. We are an English firm working with Scottish contractors, and we would rather say so honestly than pretend otherwise. The owner-managed firms we work with tend to be ten to fifty staff with an owner who started on the tools, and the shape of that work translates cleanly whether the job is a warehouse fit-out near Livingston, a light industrial unit on the edge of Bathgate or a hotel refurb down the coast at Dunbar. Lothian is a wide patch, and we are used to firms that do not fit neatly into a single market. We pick one problem, fix it properly, and move on to the next one only when the first is settled.

FAQs

Common questions from Lothian practices

What kind of AI tools do you actually use?

The tool gets picked to fit the problem. No reseller relationships sit behind any of this, so nothing gets recommended because a vendor is pushing it. For construction work the stack typically settles around document extraction for scope packs and drawings, workflow platforms like Make or n8n underneath as the plumbing, purpose-built LLM wrappers for the language-heavy bits, and integrations into whatever job management or accounting software the firm already runs. Your existing software stays where it is. We build to get more work out of it.

Is it safe to use AI with client and job data?

Yes, provided the setup is right. We only use deployment patterns that keep your job records and client data under your own control, with nothing routed into training for any third-party model. Scottish firms we work with are usually careful about supplier pricing and commercial relationships, which is the right instinct. Rather than asking you to take that on trust, we walk through exactly how each specific tool handles it inside the free report.

Can it really handle scope for different kinds of jobs in the same week?

Yes, and that is usually the point for a firm with a mixed book. The tool holds a separate scope library for each kind of work you do and picks the right one from the brief the estimator types in. A warehouse fit-out gets warehouse scope and warehouse rates. A hotel refurb gets the hospitality scope and the soft-finish supplier list. The estimator still owns the final numbers on every line. What the tool removes is the gear-changing that was silently eating time in the middle of every quote.

How long does a typical project take?

The first piece of work normally runs two to six weeks, from the first conversation to something actually running inside your firm. We keep the first project deliberately small so you see a result quickly and can decide for yourself whether we are worth having back for the next one. Bigger pieces of work come later, once trust has been earned.

Will this replace my estimator or my office staff?

No. The firms we have worked with finish the first project with the same people still on the payroll, doing more of the work they actually care about and less of the admin nobody wanted. This is not a quiet headcount exercise dressed up as automation. Good estimators are genuinely hard to come by, good office staff even harder to hold on to, and nobody in their right mind is looking to push either out the door.

Run a construction firm across Lothian?

Fifteen minutes from you, and a detailed written report back within twenty-four hours. No sales call required.