After launch: retainers that compound instead of restarting

Launch is when most agencies send a bouquet and disappear, or invent a new “phase” so the invoice never changes meaning. AERVIO’s growth systems are duller: measure what started a conversation, ship the next change, keep the lights on. The stack stays yours if the retainer stops.

This only works if the site, CRM, and search already share objects. Otherwise we would be reporting on ghosts.

What a month contains

Not 40 hours of “strategy decks.” A typical month:

• One money-page change (copy, internal link, form field, speed)
• Search Console notes on queries that moved — or did not
• CRM: conversations started, stuck >5 business days, source URL
• Restore or uptime check on the surfaces we agreed (hardening)
• Editors: French/English pairs if you are on a Bill 96 split

If we cannot point at a shipped change, we failed that month. Closed tickets in a portal are not the artefact.

Analytics without a shrine

We use the smallest analytics that can answer “which URL started this CRM record.” That might be first-party events into the CRM, not a second Google account with 86 custom dimensions.

Consent banners are not a strategy. If you run tags, we keep them few, documented, and aligned with Law 25. We will not install a tag manager soup “for remarketing” on day one of a site that cannot rank a service page.

CRO is a sentence, then a test

Conversion work here is usually:

• The H1 did not match the ad or the Maps category
• The form asked for a novel
• The French page was stale
• The button went to `/contact.html` (templates do this)

We change one of those, wait, look at CRM sources. We do not A/B-test button colours on 200 visits.

What we will not restart

Quarterly rebrands, new slogans, a second blog platform, a new CRM “because the dashboard is prettier.” Compounding means the objects stay stable so the numbers mean the same thing in December as in March.

New Insights articles are part of compounding when they answer a question from calls — like this cluster — not when they exist to hit a publish quota.

Hand-off if you stop

You get: hosts, DNS, repos, tenant roles, a one-page map of forms and processors, last restore date. We will not hold the keys. That is written in the proposal, the same place as the price.

Fixed-scope customers can skip retainers entirely. Many should, until they have someone inside who reads the monthly note.

If you already pay a retainer and cannot name last month’s change, that is the problem to solve — with them or with us. A sentence to hello@aervio.io plus access to Search Console is enough to see whether a growth slice would even bite.

A monthly note you should be able to forward

Our note is short enough to paste into Slack:

• Shipped: URL + what changed
• Evidence: Search Console query or CRM source
• Next: the candidate change for next month
• Risk: backup restore date, or a form that 500’d

If a vendor’s monthly is twelve slides and no URL, you are buying theatre. We will not compete on slide count.

When not to retain us

If nobody inside will read a 200-word note, pay for launch only and stop. A retainer without a reader becomes our guilt and your auto-pay. We would rather you come back in six months with Search Console than ghost-pay.

Compounding vs “new always”

The objects stay: offer, lead, language. New articles in this cluster compound because they point at those objects. A second blog on another domain does not. A second CRM does not. Say no more often than yes. That is the retainer.

Search Console access plus “we cannot name last month’s change” is a complete brief.

Questions

Is a retainer mandatory?

No. Fixed scope can end at launch with a written hand-off. Retainers are for companies that want the next change shipped on a cadence.

What do you measure?

Which URL started a real conversation in the CRM, plus Search Console queries, plus whether forms still post. Vanity sessions without a source in the CRM do not run the meeting.

Do we lose the site if we stop paying?

No. You keep hosting, DNS, repo, and tenants. That is the point of the stack staying yours.