BLDWELL.
Blog

Case notes: from 9 days to same-day invoicing.

An example case study: how a 42-person residential builder replaced a spreadsheet, an invoicing app and a lot of group texts with one system.

Case notesSeptember 10, 20263 min read
On this page

The starting point

Hartley Homes is a residential builder with 42 people across sales, project management and site crews. When we first mapped how the business ran, the work moved through five different places.

Leads lived in a shared spreadsheet. Some came from the website form, some from referrals, and some from calls that were written down later, if they were written down at all. Once a project was signed, it moved to a project board. Invoices were created in a separate invoicing app, from details copied by hand out of the spreadsheet and the board. Files and photos sat in a shared drive. And clients got updates through group texts, which meant the project manager's phone was, in practice, the system of record.

Nothing was broken in a dramatic way. But every step depended on someone remembering to move information from one place to the next. The clearest symptom was invoicing: on average, it took nine days from a milestone being finished to the invoice going out.

What we built

We started with the leak that cost the most: the gap between finishing work and getting paid. Then we built outward from there, one module at a time, all on the same database.

CRM. Every lead source now creates a record in one place. Each lead has an owner and a next step, and follow-ups are scheduled by the system.

Billing. Invoices are drafted automatically from project milestones. When a project manager marks a milestone complete, the invoice is ready for review the same day.

Projects. Schedules, tasks, files and site photos live with the project they belong to, not in a drive or a chat thread.

Client portal. Clients log in to see progress, approve changes and pay invoices, which replaced the group texts almost entirely.

What changed

The headline change was speed. Time to invoice went from nine days to the same day, which pulled cash forward and ended the Monday-morning ritual of chasing paperwork.

The second change was visibility. For the first time, the owner could see the whole funnel, from new leads to booked projects to paid invoices, without asking anyone to build a report.

+34%
revenue in the first year (example figures)

In this example, revenue grew 34% in the first year, driven mostly by faster follow-up on leads that used to go quiet.

The third change was quieter, and the team noticed it most: fewer "where is this?" messages. When everyone works from the same records, nobody has to ask.

What we'd do again

Start with the most expensive leak. Fixing invoicing first meant the system paid for itself early, which made every later module an easy decision.

Build around the real process. The site-visit step, the client-approval step and the milestone billing all mirror how Hartley actually works. Nobody had to learn a generic product's idea of how a builder should operate.

Measure before you build. We recorded how long invoicing, scheduling and lead follow-up took before the first module went live. Without that baseline, "it feels faster" is all you can say; with it, the improvement is a number everyone agrees on, and it tells you which module to build next.

Move the clients in early. The portal turned out to be the feature clients talked about most. It made the business feel bigger and more organized from the outside, and it cut the project managers' phone time significantly.

Written by

BLDWELL Team

We build the machine that runs your business.

ShareXLinkedIn

Build the machine.

Scale now