Build and run
What “build” actually means.
Not a chatbot, not a software license, not an IT project. The workflow your diagnostic designed, installed in your own tenant with a person on every decision that moves money — then run and improved until the numbers say otherwise.
The anatomy of a build
Four things are true of every build, or it doesn’t ship.
- 01
It starts as a line on your own map
Every build traces back to a fix the diagnostic ranked and your team agreed to. Nothing gets installed because it's fashionable, sellable, or easy — if the numbers didn't call for it, it doesn't exist.
- 02
The process comes first
What actually gets designed is a workflow — how the quote leaves faster, how the extra gets billed, how the follow-up never depends on memory. The automation exists to hold that process in place, not the other way around. That's the difference between infrastructure and a pile of bots.
- 03
It's installed in your tenant
The automation goes into your own environment, on licenses you most likely already own. Approvals arrive in the tools your people already work in, and every decision that moves money stops for a person — the machine drafts, holds and reminds; people release.
- 04
It's handed over like infrastructure
Every build comes with its workflow export, configuration, runbook, test fixtures and rollback procedure. If you end the engagement, you keep a running system — there's nothing hosted with us to switch off.
What gets installed
Six patterns, and where each one stops for a person.
These are the shapes builds take. Which of them your business needs — and in what order — is exactly what the diagnostic is for.
Quote from your own job history
Pulls comparable jobs with what they actually cost — not what they were quoted at — and drafts at your target margin.
Stops for a person: The estimator argues with a draft instead of starting at a blank sheet.
Extras captured when they happen
Watches for work that went beyond the order and raises it while the job is open, not at month-end when nobody remembers.
Stops for a person: A person confirms it's billable before it reaches an invoice.
Walk this one through →Invoice the day it ships
Reads the shipment confirmation, drafts the invoice against the order, and has it ready the same day rather than next week.
Stops for a person: One approval releases it. Anything that doesn't match the order is held, not guessed.
Walk this one through →Follow-up that doesn't wait on memory
Chases on a schedule you set, escalates when a bucket ages, and keeps the whole thread in one place.
Stops for a person: You decide who gets a call and who gets a hold. The machine never talks to a customer unprompted.
Walk this one through →Material that stops sitting
Surfaces stock and work-in-progress that has stopped moving, with the cash attached to each so it can be ranked.
Stops for a person: Buying and scrapping stay decisions, made by people, with better numbers in front of them.
Walk this one through →Terms and payment timing that suit your cash
Keeps vendor terms in one register, flags discounts worth taking, and times payment runs against your own position.
Stops for a person: Every payment run is still released by a person.
How it connects
Against your systems, not a list of ours.
You won’t find a logo wall here. A system gets named on this page once it has run in a real engagement — not because a connector exists for it.
The connection into your ERP and accounting is scoped in the diagnostic, against what you actually run. Nothing gets replaced and nothing gets migrated to make room for us.
What’s named today: your Microsoft 365. Teams, SharePoint and Power Automate — built and fired end to end, with approvals arriving where your people already work.
The full detail — whose account it runs in, where the data goes, the model question, and what happens if you stop — answered in your IT function’s own words.
Then we run it
“Run” means it keeps working after the consultants would have left.
A workflow that nobody watches decays back into the old process in a quarter. Running it — and improving it — is the half that makes the build worth having.
- Month to month, thirty days’ notice
- No minimum term. The retainer continues only while it earns its keep — and what it has to earn it on is published below.
- Scored on two numbers
- Working capital freed and cash flow from operations. Not tickets closed, not uptime, not activity — the numbers your business already tracks.
- Run and improved, not just maintained
- Exceptions get reviewed, thresholds get tuned, and the next fix on your map gets built when you say so. The system gets better while it runs — that's what you're paying for.
- Your first build is included
- Up to ten build days on a fix your own map named, delivered inside the partnership. The eligibility rule is published on the diagnostic page, so you can check which fixes qualify rather than take our word for it.
Builds aren’t sold here. They’re found.
Every build starts as a line on a diagnostic’s map — ranked, costed, and agreed with your team before anything gets installed.