What companies your size are already doing
A government survey found 36% of large businesses (250 or more staff) were using AI (DSIT, fieldwork February to May 2025). Using AI is one job. Having proper rules around it is another.
- Effort Weeks
An approved AI stack with data boundaries
A short list of approved tools, a plain rule for what data goes where, and one owner. Your staff know what to use and what never to paste in.
Stays human Approving tools and exceptions. A named person is accountable.
ProofOur own rules: hooks that stop one tool doing another's job, and nothing sent unless a person asks
- Effort Weeks
Agents watching your sites and tracking overnight
Agents check pages, tags and forms while you sleep, and leave a short note or an issue for someone to look at in the morning.
Stays human Anything that changes a live site. Agents suggest the change and a person merges it.
ProofBrowser checks Our own bots watch like this: Site Watch watches live sites and files what it finds, and Ship Guard watches our repos and files issues. A person merges every fix.
- Effort Weeks
Pilots that ship in weeks, not quarters
One workflow, one owner, a written test for success and a review date. If it works, it goes live. If it doesn't, it stops.
Stays human Deciding go or no-go, and setting the success test.
ProofTechStack AnalyserUser Journey Analyser Both started small: TechStack for our own pre-pitch scans, Journey for a single client first.
- Effort Weeks to months
Answer engines recommending you (GEO)
Your content and key facts set out so ChatGPT, Gemini and similar tools can find them and repeat them correctly.
Stays human Deciding what you want to be known for, and checking what the AI tools actually say about you.
ProofContent and SEO
Show 4 more
- Effort Days to weeks
A no-blame amnesty on unofficial AI, and a register
Ask staff what they already use, with no blame, then record it all in one register: the tool, the data it touches, who owns it and what you've decided.
Stays human Deciding what happens to each tool.
- Effort Weeks
A test set before anything customer-facing
Before an assistant talks to customers, run it against 50 to 100 real questions and have people score the answers. Run it again every time something changes.
Stays human Scoring the answers, and deciding whether to launch.
- Effort Weeks
Tracking and consent checked across every site and market
Agents check tags, consent settings and where data goes across all your sites and markets, and flag anything that's drifted.
Stays human Legal and privacy sign-off.
- Effort Weeks
Brand and tone rules built into the tools
Your brand rules, claims and banned phrases are loaded into the tools, so drafts start on-brand and fewer need rewriting.
Stays human Approving claims and anything regulated.
On our own work We do this on this site: one written rule set that every AI tool reads.
First step this month
Find out what's already in use. Run a no-blame survey of the tools people use and the data they touch, and write it up as a one-page register. You can't set limits on tools you haven't listed. Then pick one pilot, give it one owner, and write down the test before it starts.
Not yet
- Don't sign a multi-year, company-wide AI contract before you've run a pilot.
- Don't let an agent send, spend or publish without a person checking.
- Don't run ten pilots at once. Two with owners will beat ten without.
Three questions for anyone who offers to help, us included
- Where does our data go, who at your end can see it, and is it used to train anything?
- Show us the review step. Who signs off, what gets logged, and can we audit it?
- What happens to the work, the prompts and the setup if we end the contract?