Work · Flagship · clinic marketing agency

A clinic marketing operating system, operated from Claude

Multi-tenant CMS plus an agency CRM and a per-clinic CRM, one codebase on Cloudflare, every action available as a tool through its own MCP server.

Book a 30-minute call See the live thing

66tables

199migrations

180tools in the MCP server

1codebase for CMS + two CRMs

Numbers as cleared by the owner. Nothing rounded, nothing added.

The situation

An agency that markets clinics: a site per clinic, a CRM for the agency, a CRM for each clinic, and a per-seat subscription for the workflow in between.

Three tools, three logins, nobody owning the whole.

What was built

One codebase: a multi-tenant CMS with every clinic on its own tenant, the agency CRM and the per-clinic CRM on the same schema, on Workers and D1.

On top, an MCP server with 180 tools, so the agency operates the system from Claude: content, leads, follow-ups, reports.

What changed

The per-seat subscription is gone; the agency and every clinic operate the same CRM they own.

New clinics are a tenant, not a project. The schema has grown through 199 migrations without a rewrite.

How it runs

Cloudflare Workers and D1, 66 tables, scheduled tasks with proof of their last run. The agency's account, the agency's repository.

How the pieces connect

The system on one map. Arrows show what feeds what; hover a piece to light its path.

Claude

The operator

The agency team works from Claude.

MCP

MCP server · 180 tools

Every action of the system as a tool, with an audit trail.

CMS

Multi-tenant CMS

A site per clinic, each on its own tenant.

CRM

Agency CRM

Leads, follow-ups, reports for the agency.

CRM

Per-clinic CRM

The same CRM, one per clinic, owned.

D1 · 66 tables

One schema, 199 migrations, on Workers.

Runs on

Workers
Sqlite
Typescript
MCP
Claude
Actions

If you want one of these

Three steps. The six-step version, with the brief and the video request, is on the home page.

01
Scoping call
30 min, free
You describe the situation; I ask three questions and propose a shape.
02
Roadmap and architecture
$1,250 deposit
A written plan with a date. The deposit is credited to the first invoice; the documents are yours either way.
03
Build, handoff, operate
date on the roadmap
One engineer builds every layer on your account, documents it, and can keep operating it.

Questions I get about this

Tap a question. The answer comes back like a text.

Scoping calls · most weeks

What does the $1,250 deposit cover?

A written roadmap and an architecture for your system, delivered after the scoping call. If we build together, the full amount comes off the first invoice. If not, the documents are yours to take to anyone.

Who owns the code and the accounts?

You do. The repository, the Cloudflare account, the domains and the data sit under your company from day one. I get access, not ownership.

How fast will something be live?

The roadmap gives you a date before you commit to the build. The stack is small and one person builds every layer, so nothing waits in a queue between departments.

Do you sign NDAs?

Yes, before you send the brief if you need it. Send yours or use mine.

Something else? Ask it on the call

A 30-minute call, free

Thirty minutes, then a written plan

Leave an email. I reply within one working day with three questions and a proposed plan, not a deck.