Book a fit call
Book the free 30-minute fit call

Or call 0161 543 7189

Co-founder, one of two

Adam Gillett

Process, implementation and adoption

Adam Gillett is co-founder of AGMM, a UK AI consultancy. While 95% of the work runs without the founders, Adam owns the 5% that is judgement about people and process: how the work really runs, what a new system must fit, and whether the team really adopts it.

By Sam Wall and Adam Gillett · Checked on

Adam Gillett, co-founder of AGMM, an AI consultancy
Adam Gillett, co-founder, AGMM.Decides how the work really runs, and who keeps which decision.

Where his time goes

95% of AGMM runs without Adam. He keeps the 5% that lands.

That is the design. The outreach engines he built find, qualify and send every day while he is in the room with the people whose work is changing. What is left for him is the part a system cannot do: listen properly, decide, and stay accountable for the decision.

95%

of AGMM runs without Adam. The systems carry it, every day, at a volume a large team would struggle with.

5%

is Adam’s: the calls that decide whether a system gets used.

  1. Client builds
  2. Proposals and pricing
  3. Running client systems
  4. Outreach engines
  5. Content line
  6. Autoposter
  7. Model fleet
  8. Quality gates and review
  9. The operating brain
  10. Research
  11. Finance and admin
  12. Library and learning

Adam’s 5%

What the work really is

The job as it is actually done, workarounds included, not as the process document says.

Who keeps which decision

Where a person must stay in control, written down before anything is built.

Which team goes first

A rollout sequenced so the business keeps running while the new route arrives.

The client relationship

The conversations that decide whether a client stays for years.

A week at AGMM, illustrated. Each square stands for five pieces of work done by our systems. Gold squares are the calls Adam keeps. Volumes illustrative.

The 5%, in a calendar

What that slice looks like across a week.

Process walk-throughs, team interviews, training sessions and the calls that settle which team goes first. Every meeting has a small agent sitting in, taking notes and filing what we learned, so the next rollout starts further ahead.

  1. Monday, 08:30Founders: the week aheadDecided: What gets built first
  2. Monday, 13:00Outreach engine reviewDecided: Daily caps rise slowly
  3. Tuesday, 16:00Founders: pipelineDecided: Which calls become Audits
  4. Wednesday, 13:45Change plan reviewDecided: One team goes first
  5. Wednesday, 15:00Founders: pricingDecided: The Audit stays £2,000
  6. Thursday, 11:00Audit read-outDecided: Ranked plan signed off
  7. Thursday, 16:45Release: go or no-goDecided: Ship on Friday
  8. Friday, 08:30Founders: the week behindDecided: Retire two skills, add one
  9. Friday, 13:00Process sign-offDecided: New way of working agreed
  10. Friday, 15:30Week close: decisions logDecided: Next week's priorities
MondayTuesdayWednesdayThursdayFriday
  1. Founders: the week aheadDecided: What gets built first
  2. Process walk-through
  3. Fit call
  4. Outreach engine reviewDecided: Daily caps rise slowly
  5. Audit session 1 of 3
  6. Adoption check-in
  1. Team interviews
  2. Fit call
  3. Audit session 2 of 3
  4. Workflow mapping
  5. Training session
  6. Founders: pipelineDecided: Which calls become Audits
  1. Fit call
  2. Shadowing the ops team
  3. Audit session 3 of 3
  4. Fit call
  5. Change plan reviewDecided: One team goes first
  6. Founders: pricingDecided: The Audit stays £2,000
  7. Adoption review
  1. Discovery session
  2. Fit call
  3. Audit read-outDecided: Ranked plan signed off
  4. Handover training
  5. Fit call
  6. Release: go or no-goDecided: Ship on Friday
  1. Founders: the week behindDecided: Retire two skills, add one
  2. Adoption check-in
  3. Fit call
  4. Process sign-offDecided: New way of working agreed
  5. Week close: decisions logDecided: Next week's priorities

Behind every week, the systems keep running:

  • Content line, up to 15 short-form videos and one YouTube film a day.
  • Autoposter, up to 10 posts a day, five platforms, receipts kept.
  • Outreach engines, Instagram and LinkedIn, ramped caps.
  • Model fleet, every job routed, every output reviewed.
  • The brain, what each meeting taught us, filed.

The small mark on each meeting: an agent sits in, takes notes, and files what we learned.

A typical week in Adam's calendar. The meetings are representative; the systems running behind them are real.Demonstration of our real architecture. Timings compressed.

What he decides

What does Adam decide?

For you, it means the system is specified from how your team really works, and the change lands with them rather than being announced at them. These are the calls Adam keeps.

  1. What the work really is

    The job as it is done, workarounds included, not as the process document says.

    For exampleThe onboarding checklist says five steps. The team does eight, and three live in one person’s head.

  2. Who keeps which decision

    Where a person must stay in control, written down before anything is built.

    For exampleThe system drafts the supplier order. The buyer signs off anything over the limit.

  3. Which team goes first

    A rollout sequenced so the business keeps running while the new route arrives.

    For exampleFinance closes first because that is where the hours are. Customer service follows once the records are clean.

  4. When it has landed

    The point at which your team no longer needs AGMM in the room.

    For exampleThe team runs two month-end closes in a row without calling us.

What he builds

What does Adam build?

The half of a system that decides whether anyone uses it. Software that is technically correct and operationally wrong is a common and expensive outcome, and it happens when the build is specified from a process document rather than from the work. Adam builds against the work.

In practice that means:

  • Tracing a job end to end through the people who do it, including the workarounds nobody wrote down.
  • Turning that into requirements a system can be held to, with the exceptions named rather than discovered later.
  • Deciding where a person must stay in control of a decision, and writing that down before anything is built.
  • Sequencing the rollout so the business keeps running while the new route is introduced.
  • Adoption: the handover, the operating record and the point at which the team no longer needs AGMM in the room.

Sam Wall owns the other half: the technical decisions, integrations, AI behaviour, testing and deployment. Neither half works on its own, which is why AGMM sells AI consultancy where the founders who diagnose the problem stay until the answer is running in ordinary use.

How he runs the audit

How does he run the £2,000 audit?

The AI Constraint Audit runs for fourteen days around three sixty-minute working sessions. Adam's job in them is to get past the version of the process that exists on paper. That usually means talking to the person who does the job rather than the person who owns it, and asking what they do when the normal route fails, because the exception is where the cost lives.

He also names the constraint that is not technical. Plenty of businesses arrive certain they need AI and leave with a ranked list on which the top item is a rule that needs agreeing, a field that needs defining or a hand-off that needs one owner. Writing that down plainly is worth more than a build proposal that would have failed on contact with the frontline.

You keep the constraint map, the AI opportunity map, the economic cases and the ranked next step whatever you decide afterwards. The fee is not deducted from a build, so there is no financial reason for the audit to recommend one. A fuller audit always follows inside any build proposal.

What it runs on

Inside the systems he built for AGMM

AGMM runs on the same ideas it sells: one record, clear owners and a person on the decisions that matter. The outreach engines Adam built find, qualify and send every day, inside daily caps that rise slowly. One of our knowledge bases holds 4,535 notes, 5.9 million words and 1,023 skills, and it is where each lesson from a client session is filed.

Adam decides which of those conversations become audits, where a person must stay in the loop, and when a new way of working has landed. Under the hood it is folders, files and links, organised properly. Every department of the business is drawn on Inside AGMM.

Verification

How to check any of this

The company
AGMM LTD, company number 16384156, incorporated 13 April 2025. Read the Companies House record.
The systems
What runs inside AGMM while the founders are in their 5% is drawn, department by department, on Inside AGMM.
The price
£2,000 for the fourteen-day audit, published on what it costs and compared with other UK firms on the cost comparison.
Your data
What AGMM does with client information during an audit and a build is written down on security and data protection.
Adam directly
LinkedIn, or 0161 543 7189.

Thirty minutes with the people who would build it.

The fit call is free and nothing is bought on it. Adam and Sam are both on the call, so the process question and the technical question get answered in the same thirty minutes.

Book the free fit callCall 0161 543 7189

The Audit: £2,000, 14 days, four outputs you own.

  1. MessyPacks built by hand the night before
  2. OrganisedOne set of figures every Monday
  3. RunningPacks assemble themselves; you decide
Lit: Leadership and decisions, where the call starts. The audit then looks across all twelve departments for constraints, weak points and money to save or earn.