A while ago we shared what changed for a regional builder nine months after they moved to Housebuilder Pro. The line most people remember is their operations lead’s, that the team got back roughly a day a week each. It’s a good line. But a day a week is the result, not the method, and the question we get asked most is the practical one: what did they actually set up to get there?

This is that write-up. No theory. The fields, the automations, and the report their sales director now opens instead of building one by hand.

The starting point

The builder does around 80 plots a year across the West Midlands. When they came to us they were running plot sales the way most regional housebuilders do. A CRM the directors looked at, a spreadsheet the sales team kept current, and a separate plot list operations maintained. Three systems, three versions of the truth.

They agreed about 70% of the time. The other 30% was where the problems lived. A plot marked available in one place and reserved in another. An enquiry that sat for four days because everyone assumed someone else had picked it up. A reservation that exchanged without site ever being told to start.

Here is what they configured to close that gap.

1. Enquiry routing, with a clock running

The first thing they fixed was the dead time between an enquiry landing and someone actually responding to it.

Every enquiry, wherever it comes from, the website, a portal, a phone call logged by reception, now lands in one place and is auto-assigned to a named sales lead based on the development it relates to. No more shared inbox that everyone can see and nobody owns.

The part that did the real work was the clock. Each assigned enquiry starts a response timer. If it isn’t actioned within their agreed window, it escalates, first to the sales manager, then visible on the director’s dashboard. They didn’t set this up to police the team. They set it up because the four-day silent enquiry was costing them sales nobody could see they were losing.

What they configured: enquiry source fields, development-based routing rules, a response SLA timer, and a two-step escalation.

2. The reservation workflow, deposit to sign-off, no re-keying

The second fix was the handoff that used to fall down: a reservation moving from “buyer paid a deposit” to “site knows to build it.”

Previously this lived in three separate actions in three systems, and the gaps between them were where reservations went cold or got missed. Now it’s one workflow. A reservation moves through defined stages, deposit taken, reservation confirmed, contracts issued, exchanged, with the right people notified at each stage automatically. When a reservation reaches sign-off, the plot updates for site and aftercare in the same moment. Nobody re-keys anything.

The quiet win here was the deposit-stage buyer who used to slip through. Because the reservation now sits in a visible stage with an owner, rather than in someone’s memory, the buyer who’s gone quiet between deposit and exchange is now obvious instead of invisible.

What they configured: reservation stage definitions, stage-change notifications to sales, site and aftercare, and the rule that pushes a signed-off reservation straight into the plot record.

3. The dashboard that replaced the Monday spreadsheet

The third thing was the report. Their sales director used to spend part of Sunday evening, or early Monday, pulling numbers from the three systems into a spreadsheet so they had something to take into the Monday meeting.

That report is now a dashboard that’s always current. Enquiries this week and how many are still unactioned. Reservations by stage. Plots available, reserved and sold by development. Response times against the SLA. The director opens it instead of assembling it.

The point isn’t that it’s prettier. It’s that it’s the same numbers everyone else is looking at, generated from the live data rather than someone’s overnight copy-and-paste. The Monday meeting stopped being an argument about whose figures were right.

What they configured: a sales director dashboard view with live enquiry, reservation and plot tiles, filtered by development.

What changed

Nine months in, the operations lead’s summary was the day a week. The sales director’s was simpler: the team stopped arguing about which list was right, and just sold more houses.

The number underneath that: their enquiry-to-reservation rate went from 7% to 16% over the nine months. Same enquiries, same team. The difference was that fewer of them fell down the gaps between the three old systems.

None of this is exotic. It’s enquiry routing, a reservation workflow, and a dashboard, set up once so the team isn’t doing the same job in three places. That’s where the day a week comes from. Not from working harder. From not doing the work twice.

If you want to see how the same setup would map onto your developments, twenty minutes on a screen share will show you. Your plots, your process, and where it would and wouldn’t fit.

This is a composite drawn from several Housebuilder Pro customers. The numbers are representative of what regional builders see, not a single named account.