Chapter 01
A contractor that prices more work without hiring another estimator.
Twelve tenders a month, just over nine hours each. Five more clear bid/no-bid and nobody ever prices them. Meanwhile the site records arrive as photographs in a group chat at seven in the evening.
Illustrative
A composite company, not a client. We model the inputs and the queue examples, then derive every total from the assumptions shown. A real audit measures each workflow in your operation.
- Profile
- Contractor
- Revenue
- €18M
- People
- 70
- Live sites
- 6
Engagement timeline
-
01
Audit
2 weeks
from $2.5K
Discovery, a 90-minute deep dive, an optional checkpoint, then the walkthrough and build order.
-
02
Implementation
4 to 12 weeks
priced from the audit
We build what the audit put first, inside the tools you already use.
-
03
Operated
ongoing
monthly, you can stop
Weekly quality checks, a monthly report of what slipped and what we fixed, and the next thing to build agreed before work starts.
We publish the audit price above, and half of it comes off the build. What moves the price on the last two: how many processes, how many people touch them, and how scattered the information is. You get that number at the walkthrough on day 14, before you decide anything.
What gets built
Not new software. The AI reads what arrives and drafts what comes next, inside the tools your team already opens. A person checks it before it goes anywhere, so nobody has to learn to work a new system.
The arithmetic
Estimating and take-off
The one process the audit put first, and what a year of running it the current way adds up to. These are the assumptions behind that, not a quote.
- Tenders priced today
- 12 a month
- Time each
- 550 min
- Blended loaded staff cost an hour
- €46
- How much of it the system could do
- 55%
- Hours a year
- 1,320
- Cost a year
- €60,720
- Hours a year it could take off your team
- 726
Read from the top: this one process costs €60,720 a year as it runs today, and 726 of those hours could come off your team.
Put your own numbers in the four rows above and the rest follows the same way. The deep dive settles the share. It runs low wherever the information sits in many places, which is why the audit finds yours before anyone promises a number.
What else the audit found
Four more processes in the illustrative roadmap. In a real audit we watch each one and time it in your operation. Here we show the modelled inputs so you can swap in yours.
- Estimating and take-off
- 1,320 h · 55%
- Supplier price chasing
- 680 h · 70%
- Site reports and daily logs
- 1,040 h · 65%
- Changes, variations and valuations
- 430 h · 60%
- Subcontractor document collection and expiry tracking
- 310 h · 75%
What you would otherwise do
Three other ways to solve this.
-
Hire another person
Another salary, and about three months to fill it. The process stays as it is. If the work is growing, this is the right answer and we will say so.
-
Take a free assessment
Free ones exist and they are worth doing. They end in a report. So does ours, and three things differ. The people who would build it price the build order. Half our fee comes off that build. If we find nothing worth building, you do not pay. If a free assessment already told you what to build, skip us and go build it.
-
Ask your IT provider
They can sell you licences and a training day. Two questions worth asking them. Who writes down your team's judgment so the AI applies it? Who checks every week that it is still right?
This is not for you if you want work leaving the system with nobody reviewing the risky decisions. Nor if you were hoping to replace the people who do it. Both are possible. Neither is what we build.