Run
You could run this yourself. Some months you would rather we did
Design and Build end with a handover. Run is the other choice: we keep operating the go-to-market we built, month over month, with one of us accountable for it.
Most monitoring only notices when something is technically broken. A campaign can send perfectly and still be commercially wrong: reaching the wrong accounts, drafting from stale context, quietly skipping the leads that matter most. Knowing the difference takes someone who has run GTM, not only someone watching a dashboard.
§1First, a question
Is this yours to run, or ours?
If nothing is live yet, this is the wrong page. That is a build question, and Design & Build is where it belongs. This page is for a go-to-market that exists, and needs someone operating it.
§2What happens without someone watching
Four ways a live campaign stops being worth trusting.
Scroll the diagram
The API changed. The sequence failed silently. Five weeks passed before anyone noticed.
The person who set it up left. It still sends. Nobody knows why the reply rate dropped, and nobody will touch it.
A model update degraded the drafts. Nothing was evaluating them, so a prospect noticed first.
The 10% case. The sequence handles ninety percent of replies correctly. One person has quietly handled the rest by hand for eight months.
That last one is the most common and the most expensive, because it looks like success.
§3What we guarantee
Reliability, and the part that is not reliability.
It keeps sending. Monitored, alerted on, fixed when it breaks. You find out from us, not from a prospect.
It keeps being right. Anything with an AI step is checked against known cases on a schedule, so drift is caught while it is small.
It keeps up. When a tool changes, when you add a product line, when the ICP moves, the campaign is updated rather than quietly outgrown.
Someone is accountable who is not an employee who has since left.
What has to be true first
- Something is already live. We built it, or you did. Either is fine
- We can get into it, and to the people who use it every day
- One person on your side can accept a change. Without that, everything queues
What we will not do
- Be your sales team. We run the system. We do not carry a quota
- Absorb unlimited volume. If the campaign load triples, that is a new conversation about scope
- Rebuild the foundation under cover of a retainer. If the core is wrong, that is a build, and we will say so rather than bill you monthly to hold it together
If what you want is an agency running outbound for you as a service, that is close but not quite this: the system stays yours, and the retainer covers running it, not owning it. Worth being precise about before month one.
§5The upper band
When staying upright is not enough.
Some accounts need more than reliability: senior GTM capacity working a prioritised backlog, making the thing better month over month rather than merely alive. That is scoped on top of the base, as a set number of days rather than an open-ended retainer, so you can see exactly what you are buying and stop it without a negotiation.
Needs: a suitable core already exists, a backlog someone can prioritise, and a client owner.
What it costs
Monthly, with an initial commitment period, scoped to what is actually being watched. A single internal workflow and a campaign engine running an agency's whole client base are not the same engagement.
What we will not claim
A retainer has a far narrower range than a project does, which is the honest reason D31's no-prices argument is weaker here than on Design & Build. What we will still not do is publish a number that fits some accounts and misleads the rest. Two things you can hold us to: the thing is still doing what it was built to do, and when it stops, you hear it from us, not from a prospect.