Still chasing valuations and variations by hand? Build the process that runs itself.
Pick the process that costs you most. It gets built round the tools you already use and tested on your own projects, so it runs without anyone chasing it.
More than one process worth fixing?
Look at the AI Partnership
Illustrative monthly estimate: 60 hours gathering and drafting valuations falls to 15, including your QS’s checks. Actual savings depend on records, workflow and review time.
What you’ll want to know before you build anything.
“We already bought a system that everyone stopped using.”
That usually happens when software gets bought and nobody sets it up round the work. This gets built round the one job that costs you most, and the people who’ll use it test it on your own records before it goes live.
“If it gets something wrong, it’s my name on it.”
It does the routine work and flags the odd ones. Someone on your team signs off everything before it goes out.
“Who fixes it when a portal or template changes?”
Your team gets written controls at handover, so they know what they can change. For the rest, the Support Plan looks after it every month, so it’s never left with nobody minding it.
“We don’t want a system only its builder understands.”
It runs on your own accounts and you own it. It’s handed over with documentation, so your team knows how it works and who to call.
Right for you if
- One process eats hours every week, and you can name it.
- It relies on one or two people who know how it works.
- You can free up a decision-maker and the people who do the work today.
- You’d rather own the system than rent another piece of software.
Not for you if
- You’re happy with the margin you’re making.
- You want software dropped in without changing how the work gets done.
- You’re not willing to look honestly at where the time and money go.
- Nobody will own it once it’s live.
What’s included, and what isn’t.
Scroll sideways to compare the options.
| What you get | Custom-Built System | With the Support Plan |
|---|---|---|
| What it covers | One process, the one that costs you most | The same build |
| Built round the tools you already use, on your own accounts | Included | Included |
| Tested by your team on your own records before it goes live | Included | Included |
| A person on your team checks every output before it’s used | Included | Included |
| Handover with documentation and written controls | Included | Included |
| The process measured again at weeks 8 and 12 | Included | Included |
| A follow-up a month after go-live to check how it’s going | Included | Included |
| You own it. Your data stays in the UK or EU and is never used to train AI | Included | Included |
| Fixes if something stops working after go-live | First month after go-live | Included |
| Updates when a portal, template or connection changes | First month after go-live | Included |
| Small changes as the way you work changes | First month after go-live | Included |
| A monthly check that it’s still getting it right | Not included | Included |
| A named person to call | First month after go-live | Included |
| WhatsApp support | Included | Included |
| Licences and running costs | Listed before work starts | Listed before work starts |
| Investment | £4,000 to £16,000 + VAT | Build price, plus a monthly fee |
| How to book | Book a call about your build | Book a call with the team |
Not sure which one fits, or want to talk it through first? Book a call about your build
How a build runs
Nothing goes into use until your team says it’s ready. The schedule is agreed once the scope is known.
Stage 1
Scope
The result you want, the process it covers, the information it needs and what stays outside it.
Your team providesA decision-maker and the people who do the work today.
Stage 2
Design and build
How it connects to your systems, and who signs what off, is agreed before the build starts.
Your team providesAccess, sample records and answers on how the odd cases get handled.
Stage 3
Test with your team
Checked with the people who’ll use it: the quality of what it produces, the odd cases, and how it fits normal work.
Your team providesTime from the people who’ll use it, and a decision on when it’s ready.
Stage 4
Hand over
Who does what, the documentation and the written controls, all made clear before it goes live.
Your team providesA named owner once it’s live, so it stays part of the routine.
After go-live, the Support Plan keeps it working: fixes, updates when something it connects to changes, and a monthly check that it’s still getting it right.
Choose how it’s looked after
-
Custom-Built System
£4,000 to £16,000 + VAT
The job that costs you most, built round your tools and handed to your team with documentation and written controls. The first month of support is included, then your team looks after it.
Right if you have someone in-house who’ll own it and keep it up to date.
Book a call about your build -
Custom-Built System with the Support Plan
Build price, plus a monthly fee
The same build, then kept working: fixes, updates when a portal or template changes, small changes as your work changes, and a monthly check that it’s still right.
The monthly fee is agreed with the build, in writing, before any work starts.
Book a call with the team
More than one process worth fixing? The AI Partnership builds one a month.
What a build would cost, set against what it saves.
Move the slider to what the process would save you in a year. The build is priced on the value it puts back.
£10,000£150,000
Builds run from £4,000 to £16,000 + VAT. The exact fee is agreed in writing once the process is scoped, before any work starts.
- Estimated build price
- £10,000 + VAT
- Pays for itself in
- 3 months
- Saving over three years, after the build
- £140,000
Questions
What does it cost, and how do we know it paid back?
A build is usually £4,000 to £16,000 + VAT, priced for its process. The scope, fee and information required are agreed before work starts. The payback measure is agreed before the build from your own records: hours on the process, time to complete it, or the cost of getting it wrong.
How long does it take?
A smaller build is usually working in your business within two to three weeks. A larger one takes five to six weeks. Your exact dates are agreed once the scope is set.
Do we need our data sorted first?
Not perfectly. A first build needs enough reliable information for one process, not a tidy company-wide data estate. Where the data blocks the work, the specific fix is named before going further.
Who owns the system once it’s built?
You do. It’s built on your own accounts, and ownership, access, licences and documentation are set out in the agreement before work starts.
What happens after it goes live?
Your team gets written controls at handover, so they know what they can change and who to call. The first month of fixes and small changes is included, and a follow-up a month after go-live checks how it’s going. After that, if you’d rather not look after it yourselves, the Support Plan covers fixes, updates and a monthly check, for a monthly fee agreed with the build.
Build the process that costs you most
- Built round the tools you already use
- Tested with your team before it goes live
- Measured again at weeks 8 and 12
- Yours to own, on your own accounts
£4,000 to £16,000 + VAT
The exact fee for your process, the scope and what’s needed from you are agreed in writing before work starts. Add the Support Plan and it’s looked after every month.
Book a call about your buildPrefer to write? Send an enquiry about your system.
More than one process worth fixing?
Look at the AI Partnership