Ongoing Enablement
Models get updated, your product changes, someone leaves and takes the undocumented half with them. Nothing breaks loudly — it just degrades, and the first person to notice is usually a customer. This is the standing engagement that keeps the system current and builds the next workflow when you need it. Or I run the programs outright.
Start with the free snapshotA broken form throws an error, a dead link 404s, a down site pages somebody at 2am.
AI systems don't do that. A model update shifts the tone slightly. A prompt that returned five options starts returning three. An encoded rule stops being applied and everything still looks fine, because the output is still fluent — just off.
So the drift goes unnoticed for a quarter. Then someone reads a draft and says this doesn't sound like us anymore, and nobody can point to when it changed.
Here's the uncomfortable part: the failure mode of a good AI system isn't an outage. It's a slow return to average — and average is exactly what you built the system to escape.
Nobody is assigned the second set of questions. That's the whole product.
Built and installed in your environment as your team finds the next bottleneck.
Against real work, with corrections applied — not a report saying corrections are needed.
What actually changed in the major models, and specifically what it changes for you. In plain language, not release notes.
A standing working session for your team. Live problems, live fixes. Recorded, so the session is useful to someone who missed it.
So the system survives whoever is running it.
Not released at the end.
You could run this yourself. Everything here is written down well enough that you could stop the retainer and keep going. That's the design, not a concession.
Some teams want the system built and run. That's sold the same way — flat monthly, six-month minimum, documented so you're never trapped.
Every managed engagement still ships documentation. You could take it in-house any month you decide to. That's the difference between this and an agency, and it's deliberate.
The receipt
I took a B2B email program from a 20% open rate to 40%, with click-through up two to three points.
20% → 40%
Not from a rewrite. From running it properly, month over month — list hygiene, authentication, segmentation, and a subject line discipline that didn't slip when the calendar got busy.
Programs don't improve in a launch. They improve in the maintenance.
It isn't a support contract. Nobody's waiting for a ticket. The work is scheduled, proactive, and reported — new builds, drift checks, briefings, office hours.
It isn't an open-ended commitment. Six-month minimum because nothing meaningful compounds in less than that, then month to month. If it isn't earning its place, end it — and you'll still have every document and source file.
It isn't a lock-in. The documentation is written so your team could run everything without me. That's not a risk to this business. A client who could leave and doesn't is the only kind worth having.
Flat monthly retainer, six-month minimum. Never hourly, never a percentage of media spend.
The number depends on how much is enablement and how much is execution — a team that wants briefings and office hours pays differently from one handing over their entire email program.
Exact pricing comes with your proposal. When a retainer follows a build, the shape of the work is already known.
The snapshot is free, takes 48 hours, and tells you whether the system you have is actually working where your buyers are looking.
I run a limited number each month, so there may be a short wait.
Takes about a minute. The more precise the last two answers, the sharper the report.
I'll only use this to run and send your snapshot. No list, no sequence you didn't ask for, and you can tell me to delete it at any time (see the privacy policy). I run a limited number each month, so there may be a short wait.