Not sure where to start?Book a call
Industry · Construction
On a construction job, the paperwork trails the work. Tenders need pricing, and before every monthly valuation someone has to prove the variations. Most of it gets typed up at night from photos and WhatsApp messages. For contractors with about 10 staff and up, we build software around your jobs that works from day one like a standard product, fitted to how you run your sites, at the price of a standard solution.
Thanks for watching.
| Process | Today | With custom software |
|---|---|---|
| Tenders and estimates | Tender packages arrive as PDFs and spreadsheets, and the estimator spends days pulling out items and quantities | AI reads the bill of quantities and the specification, matches items to your rates and prepares a draft for the estimator to check |
| Site diaries | Foremen send photos and voice messages, and the site manager writes up the diary in the evening | A voice note and photos on site become the diary entry in your template, filed against the job with labour, deliveries and weather |
| Variations and valuations | Extra work agreed on site goes unrecorded, and at month end the QS chases the evidence for the valuation | Each variation gets logged on site with photos and a note, priced from your rates and ready for the next application for payment |
AI for construction earns its keep with messy input: scanned PDFs, spreadsheets in every layout, a voice note recorded next to a running mixer. It reads the mess and writes the first draft. Pricing the job and signing off variations or RAMS stay with your people.
Procore and Fieldwire already cover drawings, tasks and daily reports, and both offer an API. If you use them, we feed them rather than build a second project system next to them.
If your jobs already run cleanly in Procore or Fieldwire, you may not need us for this part.
| Construction software off the shelf | Off the shelf plus integration | Custom software | |
|---|---|---|---|
| Fits when | your processes match how the software expects a job to run | the software fits, but tenders, diaries or variations still get retyped | you work differently from the standard, for example with your own rate build-ups or framework agreements |
| Cost | licence with the vendor | licence plus a one-off integration | built in sprints, no licence per head |
| When something changes | you wait for the next release | the integration gets updated | we change templates, rates and rules |
Example calculation
20 reports a week, 4 instead of 15 minutes each
Pays for itself inabout 7 months
Hourly rate: what an hour of work really costs, including holidays, sick leave and employer on-costs. Value per year: hours saved × hourly rate × 46 working weeks.
Usually not. What works stays, and we take over the typing before and after it.
No. It reads the documents and suggests rates from your library. The estimator decides what goes into the bid.
Yes, with tenders, main contractors and follow-ups in one place instead of a spreadsheet nobody updates. A CRM for construction companies only gets used if tenders and jobs feed it without extra typing, so that’s how we build it.
After the intro call you get a first prototype, built on a real tender or diary from one of your jobs. The first piece your team can use comes at the end of the first sprint, after two weeks.
Let’s take the next step. Now.
Drop us a line