AI & Automation · What we build
Give Copilot the induction it never got.
Out of the box, Copilot is a capable generalist that has never seen your business. We give it what you would give a new starter: your approved material, how the work is actually done here, the things you never claim, and someone who checks its output before it counts.
Why Copilot on its own does not do this
Copilot started on day one. Nobody told it anything.
A new starter gets shown the templates, the good examples, the things that always go in and the things you never put in writing. Copilot got a licence. It has never seen any of it, and most of it has never been written down in the first place, so people fill the gap themselves, one piece of work at a time.
The same long prompt, every time
People retype the same instructions into every chat, and the draft still misses sections your documents are required to have.
Last year's document as the template
The nearest previous proposal gets copied and edited. Whatever was wrong or out of date in it carries straight through.
The reviewer is the only control
With no agreed standard written down, every draft costs your senior person the same time to check, and nothing gets easier.
What we build
A generalist can see your data. A specialist knows your process.
Out of the box you have one generalist serving everybody. It can reach whatever your permissions allow, but it does not know how the work is done here or which detail matters. What we set up is a bench of specialists: each one built for a single job, and each one knowing the part of your business it works in.
Six examples, not a menu. We build one at a time, starting with the job that costs your senior people the most hours.
What we set one up to do
Four jobs a specialist Copilot does well.
We build one job at a time, and the first one deliberately narrow. Where the answer has to come live out of your ERP or practice management system, that is AI for your ERP rather than this.
Write it
Drafts from your approved material, to your template.
- Proposals, fee proposals and scopes
- Tender and bid responses
- Client status and project reports
- Policies, procedures and follow-ups
Check it
Reviews what already exists against your standard.
- Missing exclusions or assumptions
- Mandatory criteria not answered
- Claims you have decided not to make
- Sections still left unfilled
Match it
Compares one thing against another and lists the gaps.
- A client brief against your scope
- Tender requirements against your capability library
- Subcontractor insurances against your requirements
- A drawing register against what was issued
Analyse a file
Works through a spreadsheet or document set you point it at.
- A supplier price list against your current rates
- A register or schedule, with exceptions flagged
- A long document set, reduced to what changed
- A returned questionnaire, checked for completeness
How we build it
Five steps, from your best examples to a team using it.
We sit with the people who do and review this work today, and collect your best examples.
Those examples become a written standard: sections, wording, evidence, and what is never claimed.
The Copilot is set up against that standard, on approved sources, handing off to your reviewer.
We run real briefs, including the awkward ones, and your reviewers score what comes back.
A pilot group, training on the real workflow, and a named owner who maintains it after we leave.
What you walk away with
Six things you own at the end.
Copilot Setup
A working drafting system for one document type, and everything needed to keep it running without us.
And what changes
The standard is the part you did not have before.
The Copilot is the visible half. The written standard behind it is the half that keeps working when the tool changes, the team changes, or you decide to draft something by hand.
Written down for the first time, so it can be taught, argued with and improved instead of guessed at.
The first version already carries the required sections, your wording and the caveats that belong there.
Your reviewer checks against the same standard the draft was written to, rather than against memory.
A new starter drafts to the same standard as the person who has been doing this for fifteen years.
Where the line is
It drafts, checks and flags. A person decides.
Every design keeps the same boundary. The Copilot produces the work and hands it to a named person, who approves it against the same standard it was produced to. It has no path to a client and no path into a system of record on its own.
The standard also states what the Copilot is not allowed to decide: pricing, dates, commitments, technical claims and policy positions all come back as a question rather than a guess.
- Approved sources onlyIt draws on material you have signed off, not the open internet and not whatever else happens to be sitting in your tenant.
- It asks instead of inventingMissing scope, dates, prices or technical detail come back as a question. It does not fill the gap and hope.
- Internal material stays internalSources marked internal-only are kept out of anything client-facing by design, not by reminding people.
- Sources are namedWhere a claim has to be right, the draft shows what it came from, so the reviewer can check it in seconds.
Where it fits
It works when there is already a standard to copy.
This builds on how your business already writes. Where that does not exist yet, there is nothing to point Copilot at, and a smaller piece of work comes first.
Not the right first workflow
- No usable examples, templates or agreed standard to build from
- The document is rare and heavily bespoke every time
- You want it to send to clients or publish without a person approving
- The source material sits in systems nobody has approved for this yet
A good first workflow
- Proposals and scopes in a professional-services business
- Project reports and client updates from a delivery team
- Customer correspondence handled by a service team
- Tender and bid responses where an approved answer library exists
If the left column describes you, an AI Blueprint or a smaller content-standardisation piece is the better first step.
A sensible place to start
Bring us the document your team rewrites most.
Tell us which document type takes the most senior time to review, and who signs it off today. We will tell you whether it is a good first workflow.