Software for concrete and masonry contractors

Concrete is unforgiving about time in a way other trades are not. A framer who loses a morning frames in the afternoon. A pour that misses its window does not move an hour; it moves a day, and the day it moves to has its own commitments, a delivery that was booked, and a crew that was promised elsewhere.

The schedule is the product

Most of what goes wrong in a masonry business is not craft. It is the collision of three calendars that do not talk to each other: the customer’s expectations, the supplier’s delivery slots, and the weather.

Software cannot fix weather. It can make the collision visible earlier, which is nearly as useful. A shop that can see on Monday that Thursday has a pour, a delivery and an inspection stacked against a forecast has options. A shop that discovers it on Thursday morning does not.

This is a modest ambition and it is the right one. In this trade the honest promise is not optimisation, it is fewer surprises.

Write down what was agreed on site

The most expensive administrative failure in concrete work is the verbal change. The customer asks for the patio to go two feet further while the crew is already there. Somebody says that is fine. Nobody writes it down. Six weeks later there is a disagreement that both parties are remembering honestly and differently.

The repair is unglamorous: a dated note, attached to the job, ideally with a photograph, sent to the customer the same day. That is all. It does not need a signature workflow or an approvals chain. It needs to exist and to have a date on it, which is one of the plainer things a job record (the framing shops page covers the mechanics) does.

Decorative and structural are two businesses

A shop doing stamped patios and outdoor kitchens for homeowners is running a considered consumer sale: long deliberation, strong visual persuasion, a decision made by two people at a kitchen table. A shop doing footings and slabs for builders is running the relationship business described on the framing page — checked rather than found, bid-driven, repeat customers.

Shops that do both usually have a website that serves neither, because the front page is trying to speak to a homeowner and a developer in the same paragraph. Splitting the two is usually the single largest improvement available, and it costs nothing but clarity. The website page covers how that split is built.

Photographs do more here than anywhere

Decorative concrete is bought with the eyes. A homeowner deciding between finishes is looking for something that resembles what they imagined, and a photograph of your own finished patio in real daylight is more persuasive than every adjective available.

The corollary is that catalogue imagery actively hurts. A reader who senses that the pictures are not yours will assume the work is not either, and in a trade sold visually that assumption is difficult to recover from.

A sensible order

Split the audiences on the site. Get changes written down the same day. Then look at whether the phone is being missed during working hours, which is when answering coverage (the plumbers page covers the mechanics) becomes the priority.

Where to start

Most concrete shops should do exactly three things before considering anything more ambitious.

Split the two audiences on the site, because a page speaking to a homeowner and a developer at once persuades neither. Get changes written down on the day they are agreed, with a photograph, because the verbal change is the expensive failure in this trade. Then look honestly at whether enquiries are reaching a person during working hours.

Everything after that depends on which week keeps going wrong, and the general contracting hub covers the ordering logic that applies across the trades.

The demos are running if you want to see the pieces, and starting a project begins with one sentence about the week that keeps going wrong.

The five pieces

Every one of these is built separately and sold separately. Most shops need two of them, not five, and the order matters more than the count — a CRM with nothing feeding it is a very tidy empty room.

• Website — The site itself — pages, photos, forms, speed, and the search work that makes it findable.
• CRM — Where a lead lands, who owns it, and what happens on day two, day seven and day thirty. Page in progress.
• AI receptionist — Answers the calls nobody can pick up, asks the qualifying questions, books or hands off. Page in progress.
• Automation — The follow-ups, reminders, review asks and status updates that stop depending on memory. Page in progress.
• Estimator — A structured way to turn a job into a number, the same way twice, without a spreadsheet. Page in progress.

If you would rather see the software than read about it, the demos are real and seeded with sample data, and the process page covers how a build actually runs. When you are ready, start a project.