Ongoing · The system after launch
Ongoing monitoring and improvement of the systems connecting your website, search visibility, lead flow, CRM, automation, and measurement.
Growth systems decay. An integration changes its API, a follow-up sequence silently stops firing, a tracking tag gets removed during an unrelated edit, a competitor rewrites the page you were ranking against, and the CRM slowly fills with records nobody maintains.
None of that announces itself. The usual way a business discovers it is a quarter of flat numbers and a conversation that starts "when did this stop working?"
Care exists because a system that nobody watches is a system quietly reverting to the state it was in before you paid to fix it.
Fit
Symptoms
Scope
Uptime, form delivery, automation runs, integration health, and conversion tracking watched continuously. When something stops, it raises an alert rather than waiting to be noticed.
Dependency and security updates, broken-link repair, redirect hygiene, and performance regressions caught before they compound.
Search Console reviewed on a fixed cadence: indexation problems, crawl errors, structured-data warnings, and movement on the queries that actually produce inquiries.
A small number of deliberate changes each month, made one at a time against a baseline, so the effect of each is legible rather than guessed at.
Workflow fixes when a tool changes underneath you, deduplication, field hygiene, and small process changes as the business shifts.
Tracking kept accurate as pages change, event definitions kept current, and attribution kept intact when tooling moves.
One written summary and a call: what changed, what it did, what broke, what was fixed, and what is worth doing next month. Short, specific, and honest about what did not move.
Process
Before the first month, the current state of every system is recorded: performance, tracking coverage, integration inventory, search health, and CRM hygiene. Improvement is meaningless without it.
Alerts on the paths that matter — form delivery, automation runs, tracking events, uptime — so a failure surfaces the same day rather than at the next review.
Each month has a small, agreed set of changes drawn from a shared backlog you can reprioritise. One change at a time where the effect needs to be measurable.
A written monthly review against the baseline, then next month is agreed together. If a month produced nothing worth reporting, the review will say that.
Outcomes
These are the kinds of change this work produces. No numbers appear here, because no client result has been measured and published yet. When one has, it will appear in Work with its baseline, method, and time window.
Tooling
Scope is agreed in writing at the start and covers the systems in place. New systems are quoted as work, not absorbed silently.
Where this sits in the system
Straight answers
If yours is more specific, put it in the audit form.
support@ariadne.fyiFrom $3,500 CAD per month with a three-month minimum, then rolling with 30 days’ notice. The starting figure reflects a defined monthly hour band; the actual number depends on how many systems are in scope and how much of the stack is bespoke. You will see the band and the scope in writing before you commit.
No, but a system built by someone else needs an audit first so I know what I am agreeing to maintain. Taking over an undocumented stack without inspecting it would be a promise I could not keep.
It gets quoted as a project. Rolling large builds into a retainer is how retainers quietly become underdelivered — the hours get consumed by one thing and everything else stops being watched.
After the three-month minimum you can cancel with 30 days’ notice, and you keep everything: code, accounts, data, documentation, and monitoring configuration. There is no lock-in and nothing stops working because you stopped paying me.
The hours go to the improvement backlog instead — conversion changes, content, search work, automation extensions — prioritised by you. Uneventful months are the goal, not a problem.
Your practical starting point
Care begins with an audit, because maintaining a system means knowing its current state. If the audit finds the systems are in good shape, the retainer is smaller than you expected.