Client stories: the question each business couldn't answer, what we built and what changed.
All workTools we built, for clients and for ourselves, when nothing we could buy did the job.
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
Our staff manual for the stack: tool notes, guides, prompts and scripts, searchable.
Push one event from your page. The server picks it up, adds the consent state and forwards it.
window.dataLayer.push({ event: "generate_lead", form_name: "contact", value: 1});
The notes on how our stack works were already written as Markdown files in a repo. That's fine for the person who wrote them. It's no use when someone asks mid-call where the tracking setup is documented, or which tool does what. A folder of files isn't something you can search.
The docs live at docs.pacing.agency, and they're internal: you need a Pacing Google login to open them. That's deliberate, because the notes cover how our systems fit together.
A browsable site built straight from the Markdown we already keep. Docusaurus generates it, Cloudflare Pages hosts it, and Algolia makes it searchable. The theme uses Pacing's logo and styling rather than the default Docusaurus look.
tools/ folder.Before every build, scripts read the tool notes and script packs, write them in as pages, and check the MDX. They escape emails, turn file links into code, and flag secret-looking strings. Then Docusaurus builds, and Cloudflare Pages deploys when a change merges to main.
The Markdown is the source of truth. The generated tool and script pages are never edited by hand.
| Layer | What it does |
|---|---|
| Source | Markdown in the repo: tool notes, guides, prompts, agent playbooks, script packs |
| Sync | Prebuild scripts turn the tool notes and script packs into pages |
| Site | Docusaurus, with Pacing branding and an MDX check before every build |
| Search | Algolia keyword search (Cmd+K) and an Ask AI index with one record per page |
| Access | Cloudflare Access with Google sign-in, Pacing staff only |
| Deploy | Merge to main and Cloudflare Pages builds it, no separate publish step |
Press Cmd+K (or Ctrl+K) on the site to search. There are two Algolia indexes: a keyword index split by heading, and an Ask AI index with a record per page, so answers draw on whole pages.
Our Cursor setup queries the same keyword index, so the notes are searchable from the editor too. The build also generates an llms.txt for AI tools.
We already had the writing habit. We were missing a host and a search box, and Docusaurus on Cloudflare Pages was enough.
Real screens from the working product. Where a screen would show client data, it shows made-up examples instead.
The stored visits and forms from one person on one timeline.
+4Our in-house scanner lists the tools and tracking a website runs. A quick scan takes about 5 seconds.
Our own CRM: a form fill becomes a person, a deal and an instant alert.
+2We'll tell you if the spend makes sense.
