What companies your size are already doing
Among firms that reported barriers, the ONS found a lack of expertise was one of the most common, and about 18% of firms with 100 to 249 staff said it had held them back from using AI (ONS, 20 July 2026). That's why rules and ownership come first.
- Effort Days
Every sales call summarised into the CRM
The call's recorded and transcribed, and a summary, the actions and the next step land on the right record.
Stays human The follow-up message. A person writes it.
ProofFirefliesTwenty Our Meeting Intel bot does this for us: it reads each meeting, writes notes and tasks, and doesn't send anything.
- Effort Weeks
Reporting that writes itself
The numbers get pulled together and a first draft of the commentary is written. Then a person adds the "so what".
Stays human A person decides what the numbers mean and what to do next.
- Effort Days
Shared AI rules for the whole team
One short written rulebook: which tools are approved, what data never goes in and who checks what. It's loaded into the tools themselves, so it gets followed instead of filed away.
Stays human Agreeing the rules, and owning the exceptions.
- Effort Days to weeks
Automations replacing admin busywork
n8n and AI handle data entry, sorting and handoffs: a form comes in, a record's created, a task is set and the right person gets an alert.
Stays human Anything that needs judgement goes to a person. So do errors, instead of disappearing.
Show 4 more
- Effort Days
First-draft proposals from the call
After a discovery call, a proposal outline is drafted from the transcript and your past work, ready for a person to rewrite.
Stays human Scope, price and promises.
ProofFireflies
- Effort Weeks
"Ask our docs" for your own team
One searchable place where your staff can ask how a process works and get an answer with a link to the source.
Stays human Keeping the docs accurate. Every page has an owner.
- Effort Days
Launch checks before every campaign
Before any money's spent, your tracking, consent settings and forms are checked, and anything broken gets listed.
Stays human Signing off the launch.
- Effort Days to weeks
Lead triage to the right owner
New leads are read, tagged by type and urgency, and routed to the right person with a short brief.
Stays human The relationship. Anything unusual goes to a person first.
First step this month
Write your one page of rules before you buy anything. List the tools people already use, what data must never go into them, and who checks what. Then pick one job you repeat (usually getting call notes into the CRM) and make it work for one team before you roll it out. If your tracking and CRM data are messy, fix that first, because AI on bad data gives you confident wrong answers.
Not yet
- Don't roll out an AI tool across the company until you've got rules and an owner.
- Don't build agents that act on their own (sending, spending, publishing) until your repeated jobs run well with a person checking.
- Don't judge success by how many people logged in. Measure the one job: time saved, errors, how fast you reply.
Three questions for anyone who offers to help, us included
- Which of our systems will this connect to, and what can it change without asking a person?
- How will we know when it's wrong, and who gets told?
- When you leave, what do we keep: the rules, the workflows, the logins, the documentation?






