# The Construction Software Stack Small Builders Actually Need

Source: https://hitchensgroup.com/insights/the-construction-software-stack-small-builders-actually-need.html
Author: John Hitchens (Hitchens Group)
Business: Forge Command (https://forgecommand.co.uk/)
Updated: April 2026

If you are running a small construction outfit in the UK, you have almost certainly tried to adopt a project management tool at some point and been quietly defeated by it. The big names, Procore, Buildertrend, CoConstruct, aim mostly at mid-sized and larger contractors. Their pricing reflects it, their workflows reflect it, and the setup effort assumes a back office person who exists to feed the software. If you are a two-person or five-person outfit where the boss is also on site most days, those tools are the wrong shape.

This is the actual stack that small construction operators need. It is deliberately short, because the software most builders need is a subset of the software most builders think they need, and the rest is a distraction that burns time instead of saving it.

## Start with what the job actually requires

Before any software discussion, it helps to list what a small builder genuinely needs to track to run a job without losing money or missing a deadline.

- Which job is active right now and what its current stage is
- Who is on which site today
- The running cost versus the quoted price
- What has been paid in, what has been paid out, what is owed
- The running list of snags, notes, and photos from each site visit
- The client's open questions and unresolved changes
- Materials ordered, delivered, and outstanding
- The weekly schedule for crews and subbies
- Key documents for each job — quotes, variations, certificates, warranties

That is the complete list for most builders up to about ten employees. If a software tool is not directly helping with one of those, it is noise.

## Where the enterprise tools are overkill

Procore, Buildertrend, and the other enterprise-grade platforms are very good at what they do. They also assume a company that has:

- A dedicated accounts person or bookkeeper inside the business
- A full-time project manager who spends their day inside the tool
- Dedicated estimators with training in the software
- Sub-trades that will accept being invited to, and actually log into, the client's platform
- A culture of data entry and process discipline across multiple roles

Almost no UK operator under ten people has all of those. The result is that the software is bought, onboarded, partially used, and then abandoned in favour of "the old way" within six months. The subscription carries on, costing real money every month, while the actual work happens in WhatsApp groups, scribbled notebooks, and a folder of email attachments.

This is not the fault of the tools. It is a mismatch. A small builder does not need Procore. They need something that respects the reality of running jobs when the same person is quoting, scheduling, buying materials, and pouring concrete.

## The stack that actually works

Here is the stack I recommend to small builders who come to me for a sanity check.

### A command centre for the jobs

One place where every active job lives, with stage, cost, client, notes, and documents all in one view. Not an accounting system. Not a full project plan. Just the operational pulse of the business. **[Forge Command](https://forgecommand.co.uk/)** was built specifically for this. It is the tool I would pick if I were running a small construction operation today.

The key thing a command centre gives you that a WhatsApp group and a spreadsheet cannot is a single source of truth. When the client phones to ask when you are starting the ensuite, you open one page and have the answer. When a supplier rings about a delivery, same page. That change alone is often worth the price of the tool.

### An accounting system

Xero is the default in the UK for good reason. Simple, well-integrated with bank feeds, understood by most accountants, and capable of handling VAT returns cleanly. FreeAgent is a strong alternative for one-person operations. Neither is a project management tool, and you should not ask them to be one.

The command centre handles "is this job profitable". Xero handles "does the business as a whole have cash in the bank". They are different questions, both important, both handled by the right tool.

### A quoting and proposal tool

Quotes are often the thing that decides whether you win the job at all. A quote that looks thrown together in Word tells the client you throw work together. A quote that looks considered tells them you consider the work. **[QuoteSmith](https://quotesmith.co.uk/)** was built for exactly this moment — professional proposals for tradespeople, delivered in under a minute. It is a sister company to Forge Command inside Hitchens Group, and the two integrate cleanly where it matters.

If QuoteSmith is not your thing, a well-structured Word template is a respectable alternative. Paste it into a PDF, brand it properly, and send. The point is that the client sees something they would expect from a professional business, not a hastily assembled estimate.

### A secure file storage

Google Drive, Dropbox, or OneDrive. Pick one and stick to it. Every job gets a folder, every folder is shared with the client if they need access, every document lives in a predictable place. Do not spread files across WhatsApp, email, a phone camera roll, and a physical folder in the van. The goal is that anyone in the business can find any job's documents in under thirty seconds, including you in two years' time when a warranty issue comes back.

### Communication

WhatsApp is fine for quick operational messages. It is not a project management tool and should never be the system of record. Anything important that happens in WhatsApp should end up in the command centre within a day — a photo, a decision, a dimension, a price change. If it stays in WhatsApp, it will be lost by the time anyone needs it.

For client communication on bigger jobs, keep email in the loop so there is a clean record. For internal scheduling, a shared calendar (again, inside the command centre or via Google Calendar) is more reliable than messages that scroll away.

### AI assist for the paperwork grind

The single biggest time sink on many small builds is the paperwork at the end of each day — daily logs, compliance notes, client update emails, photo captions. This is where an AI assistant earns its place. **[Site Manager AI](https://sitemanagerai.com/)** is built specifically for on-site managers who need to turn voice notes and a handful of photos into a proper daily report in under two minutes.

AI is not magic and should not be expected to be. Used well, it is a translator between the reality of a building site and the paperwork that reality has to produce.

## What the stack should look like on a page

For most small UK builders, the stack should fit on a single sticky note:

- **Command centre:** Forge Command
- **Accounting:** Xero
- **Quotes:** QuoteSmith
- **Files:** Google Drive (one folder per job)
- **Daily reports / site logs:** Site Manager AI
- **Messaging:** WhatsApp for quick ops, email for records
- **Calendar:** Google Calendar or the command centre's built-in view

That is the whole stack. If a tool is not on the list, ask hard whether it earns its place. Most do not.

## The common mistakes

A few patterns I see repeatedly in operators who get the stack wrong.

**Trying to run everything out of WhatsApp.** This works for a three person outfit for about a year. It stops working the moment you start running more than one job at once, or the moment a team member leaves and takes the history with them.

**Adopting an enterprise tool and letting it half-run.** The worst outcome is a paid platform that is partially populated, because now you have two sources of truth and neither is complete.

**Treating accounting software as project management.** Xero is brilliant at being Xero. It is not a command centre. Asking it to be one leads to awkward workarounds and lost data.

**Paying for a CRM you do not use.** Most small builders do not need a CRM. They need a command centre where each job has the client details attached. A separate CRM is usually a distraction.

**Buying tools instead of sorting the process.** If a builder's process is broken, software will not fix it. Software will only accelerate whatever the current process is. A clean process running on a sticky note beats a messy process running on Procore every time.

## The wider Hitchens Group view

Hitchens Group operates two specialist construction businesses — **[Forge Command](https://forgecommand.co.uk/)** and **[Site Manager AI](https://sitemanagerai.com/)** — that were built from the same frustration. Both began with a hard look at what small construction operators actually do every day, and a commitment to build the software that would have made the job easier, rather than the software that would look good on a pitch deck to enterprise clients.

If you are running a small operation and the stack above sounds familiar, have a look at both. The pricing is built for the size of business that actually uses them, the onboarding is designed to be done by the boss in an hour, and the workflows assume the person using the software is also the person on the tools.

**Visit [Forge Command](https://forgecommand.co.uk/)** for the command centre, and **[Site Manager AI](https://sitemanagerai.com/)** for the paperwork side. Both are part of Hitchens Group.

---

Visit Forge Command: https://forgecommand.co.uk/
All Hitchens Group insights: https://hitchensgroup.com/insights/