Built in-house by Uppercut Digital

AI in every role.
A person on
every change.

Everyone at Uppercut Digital uses large language models every day, in every department. We built our own tools on top of them, with guardrails the team actually trusts.

Claude Claude Code Our MCP server Google Ads Google Analytics 4 Search Console Business Profile Meta HubSpot

The models we use, and the systems our MCP server connects them to

Stylised illustration with a demo client and sample figures

Training

No person left behind.

That's what we call it, because AI has a use in every job here, not just in PPC. Most of what we know, we taught each other.

1 on 1s

Taught one to one

Most of what we know, we taught each other, one person at a time.

Team sessions

Training and lunch and learns

Team training sessions and lunch and learns, plus dedicated resources we set aside for AI education.

Show and tell

The part people like most

Anyone can show something they've built, and that's how a good idea gets past the person who had it.

Scalable processes

Good workflows become shared skills

A workflow that proves itself becomes a shared skill, so it runs the same way for everyone on the team.

Every department

What we use it for

ContentKeyword researchData analysisAd copyStrategy decksCampaign buildsDaily account checks
I've spent years at other agencies, and AI was always something one or two people tinkered with on the side. Uppercut is the first place I've worked where everyone is expected to use it, and taught how. The show and tells are my favourite part. You see what a teammate has built and you're using it yourself soon after.
Ryan Syed, SEO Strategist, Uppercut Digital

How it works

One engine. Connected to everything we run on.

Our own Model Context Protocol (MCP) server connects Claude to the systems we run on, from HubSpot to Google Ads. The same engine answers live data questions, builds campaigns and drafts strategy decks.

What it reads

HubSpot, Google Ads, GA4, Search Console, Business Profile and Meta, for every client.

Our MCP server + Claude

Reads by default, with every call logged. Before any change to a live system, the person says which account and what change.

What it does

Answers questions from the real numbers, drafts builds and decks, and proposes changes for a person to approve.

One rule

The model can read anything, but it can't change a live account on its own.

What we built

Tools we built on top of the models.

Built by our own team, for the agency and for our clients. Two of them have their own pages.

The foundation

Our MCP server

Connects Claude to HubSpot, Google Ads, GA4, Search Console, Business Profile and Meta, and logs every call.

Account health

Daily account audit

Budget pacing and search term reviews used to wait until someone had time. Now an audit runs every day and proposes the actions for a person to approve.

Quality control

AI reviewer with a scorecard

Every Google Ads and Meta build goes past it before a person approves. Fixed checks first, then a judgement call against our standards.

Quality control

A reviewer that earns trust one rule at a time.

A rule isn't trusted until it has agreed with the team 10 times in a row, and every human correction is stored as a learning for that client.

AI reviewer, Demo Dental Co buildScorecard
FIXEDCharacter limitsEvery headline and description is counted.
FIXEDRequired assetsSitelinks, callouts and the rest are all there.
JUDGEDIs the offer really on the site?The ad's offer is checked against the client's own page.
Rule: offer is on the siteTrust

Agreed with the team 10 times in a row. Now trusted.

What we got wrong: an early version marked a dental client's free consults as "not on the site", because it had only read the top of the page. It now reads the parts of a page that carry offers.

Demo client, for illustration

Governance

The rules we wrote down early.

Because so much of this is new, we wrote hard rules down before anyone needed them.

READModels read by defaultChanges to anything live need a person.
SENDNothing goes to a client until a person presses SendOr to anyone else.
KEYSCredentials never go into code, a chat or a URLNo exceptions.
SAY ITBefore any live change, the person says which account and what changeSo nobody approves something they didn't mean to.
PAUSEDPerformance Max in a new build is always created pausedSwitching it on is a separate decision.
PreviewWaiting for approval
Add 14 negative keywords to Demo Dental Co
AccountDemo Dental Co, Google Ads
CampaignSearch, Implants
Change14 phrase match negatives
Confirm code4F7K

Anything that changes an account (negatives, budgets, bid targets, tag publishes) hands back a preview and a confirm code. Nothing applies until a person approves that exact preview.

ApproveSend back

Demo client, for illustration

Challenges

What we got wrong, and how we fixed it.

Trust

Wary account managers

Our account managers were wary of a model touching client money, and they were right to be. So we fixed it in the design. The model reads freely, changes nothing without approval, and the scorecard makes each rule earn its place from the team's own verdicts.

Accuracy

Wrong answers that look right

The reviewer once missed an offer because it had only read the top of the page. We changed the data tools as well, so when a source can't be read they say so plainly instead of reporting zero.

Pace

Keeping up

The tools change faster than anyone's habits, which is why the rules are written down and the training never stops.

For our clients

The time we save goes back to clients.

Speed

Faster launches

Research, strategy deck and campaigns in under 72 hours, so a new client is live sooner.

Data

Answers from real numbers

"Why did our dental client's calls drop last week?" gets answered from the client's own data, in chat or in Oko.

Care

Accounts checked every day

Budget pacing and search terms are reviewed daily, not when someone has time, and every build is checked against our standards first.

Key numbers

Every role. Every day.

12 / 12Of our team use LLMs every day, whatever the role.
< 72 hrsFor a new client's research, strategy deck and campaign build. It used to take 2 to 3 weeks.
76Onboardings completed since August 2026, for about US$71 of tracked model spend in total.
123 / 123Account changes approved by a person, out of 11,000+ tool calls in one 47 hour stretch in October.

Figures from Uppercut Digital's own records, October 2026.

See the tools

Two of our tools have their own pages.