Talk numbers
Work

Client stories: the question each business couldn't answer, what we built and what changed.

All work
Built

Tools we built, for clients and for ourselves, when nothing we could buy did the job.

Open to anyone

Runs our work

For clients

See all builds
AI

AI moves fast. Here's how we use it in our own work, and where to start in a business your size.

The AI hub
Approach

Every business is different, so we always start with a conversation.

How we work
  1. 15 minA quick callYour goals, your numbers, and whether we're a good fit.
  2. 1 hourDiscoveryWhere you're losing enquiries, and what's already working.
  3. ThenA clear planPaid ads, a custom build or both, as a one-off project or ongoing.

What we connect

About

We're a small London team of marketers, and we use AI to go faster.

About us
  • Cam BowenCam BowenCo-founder
  • Ben PowerBen PowerCo-founder
  • ElectraElectra
  • MahirMahir
  • NatashaNatasha
  • RahabaRahaba
  • ZobaerZobaer
AI at Pacing

How we use AI

We use it on our own work first. Here's how, and where we'd start in a business your size.

What we've changed Talk to us
pacing / aifrom our workspace, as of 10 Oct 2026
  • $ ai changelog --latest 3
  • 8 Oct rule Every repo now gets a secret check before each commit
  • 25 Sept rule A hook now stops Claude Code sending email or chat for us
  • 25 Sept setup Cursor and Claude Code now follow one set of rules
  • $ ai counts
  • 31 agents, 26 rules, 11 skills, 19 MCP servers
  • 2286 commits and 408 PRs merged in the last 30 days
Our stance

  1. Marketers first.

    We started out in marketing, and we still make the strategy. AI doesn't get that job.

  2. AI to go faster.

    AI does the slow parts of the job, so we get more time to think.

Ben and Cam

In numbers

Our setup in numbers

Counted from our own workspace on 10 Oct 2026. Exact numbers, never rounded up.

  • 26rulesas of
  • 31agentsas of
  • 11skillsas of
  • 19MCP serversas of
  • 41reposas of
  • 2,286commits, last 30 daysas of
  • 408PRs merged, last 30 daysas of
How we count
rules
Written instructions our AI tools must follow, one file each, counted from the rules folder of our shared workspace.
agents
AI helpers with one job and a written playbook each, counted from the agents folder.
skills
Reusable step-by-step recipes an AI tool can pick up when the task needs them, counted from the skills folder.
MCP servers
Connections that let an AI tool read from, or act in, another system such as a calendar or an ad account, counted from our shared connection list.
repos
Code folders we keep a working copy of, counted by folder.
commits, last 30 days
Saved changes to code and documents across those repos in the 30 days before the date shown, counted from the git history.
PRs merged, last 30 days
Pull requests (a change proposed, checked, then merged) merged in our main repositories in the 30 days before the date shown.

Just counts: no names and no client details.

Go deeper

More on how we use it

Where to start

Where to start depends on your size

Verdicts

The tools we pick, and the ones we avoid

  • Claude Code

    Pick

    The AI we trust most to change our code. We run it inside Cursor, with our own rules and a person reading every pull request.

    What would change our mind: Another coding agent that sticks to our rules and review habits better.

    Last known verdict

  • Cursor

    Pick

    The best place we've found to run Claude Code: it's an editor, it syncs with GitHub and our plan covers plenty of use.

    What would change our mind: A better place to run Claude Code, or a plan change that makes Cursor a poor fit.

    Last known verdict

All verdicts

Built with AI

Things we've built with AI

Everything we built

Notes

What we've written about it

More AI notes

If you want a hand

Want this set up for you?

Next step

Bring your numbers.

We'll tell you if the spend makes sense.

  1. A 15-minute callYour goals, your challenges, and whether we're the right fit.
  2. A 1-hour discovery callWe dig into your numbers. Worth a hundred emails.
  3. A concrete planAds, a custom build or both, as a one-off project or ongoing.
Talk numbers
15 minutes · No pitch deck · A straight answer