— Practice / Ongoing care
The site shipped. Who keeps it healthy?
Most websites peak on launch day and decay quietly after. Dependencies age, links rot, the AI answers drift from the business, and nobody notices until a customer does. Ongoing care is a standing arrangement: we watch, maintain, and improve what you launched, and report on it in writing.
— Best fit
Who this is for.
Something in production
A website, a tool, or an AI surface that now carries leads or operations. It is past the project phase, and quiet breakage now costs money.
Nobody tending it
The build was a project, and keeping it healthy was never anyone’s job. The agency’s last invoice was also the end of its attention.
Month over month
You want a standing relationship with a team that already knows the system, so a creaking integration does not start with a discovery call.
Anywhere, with Atlantic roots
Remote-first for clients worldwide; on-site across Nova Scotia when hardware or people make it useful.
— What care covers
The quiet work, done on a schedule.
Updates and dependencies
Platforms, packages, certificates, and integrations kept current on a schedule instead of in a panic. Most breakages on mature sites are just maintenance that was deferred until it became an incident.
Backups with tested restores
Backed up on a schedule and restored on a test schedule. The day you need a backup is the wrong day to learn whether it works.
Monitoring and performance
Uptime and performance watched continuously, with small regressions fixed before they become a slow quarter. Core Web Vitals get measured.
Publishing support
Content changes, seasonal updates, and new pages shipped through the same design system, so two years on you still have the site you paid for at launch.
AI surface freshness
For sites with search, agents, or AI features: answers re-grounded as the site and the business change, and agent-readiness kept current as the standards move. We do this on our own site daily.
Quarterly written check-in
A plain-language review of what changed, what was fixed, what it cost, and what is worth doing next. You decide on evidence instead of finding out at renewal time.
— The full catalog
What a care relationship includes.
- Dependency, platform, and certificate updates
- Scheduled backups with tested restores
- Uptime and performance monitoring with agreed responses
- Analytics and search-console review, in plain language
- Content updates and new pages through the existing design system
- AI and agent-surface re-grounding as content and standards change
- Security-patch windows that respect business hours
- A written quarterly review: state, risks, recommendations
— How it works
The relationship.
Care usually begins where a project ends: a site we built, an AI-readiness sprint, or a takeover assessment of something we did not build. The first step is a short written brief: what runs today, what worries you. We reply in writing within one business day with fit / no-fit and, if fit, a scope and price. Coverage, cadence, and response expectations are written down before anything starts. There is no rate card on this site by design. The price lives in the reply, scoped to what you actually run.
— Questions
Before you write.
What does ongoing care cost?
It is scoped in writing per engagement. Coverage, cadence, and price are in the proposal, and none of them is published here. That is deliberate: a care arrangement priced without seeing what it covers would be a guess, and you would be the one holding it. Send a brief and the price comes back in writing within one business day.
We already pay for hosting. Is this that?
No. Hosting is one ingredient. Care is the layer above it: updates, backups, monitoring, improvements, and one person accountable for the lot. Our builds typically run on Cloudflare, and care works with what you already have, wherever it runs.
Can you take over a site you did not build?
Usually, yes, after a short paid assessment. We document what exists, what is at risk, and what care should actually cover, so both sides commit with eyes open. Occasionally the honest answer is that a rebuild is cheaper than a lifetime of workarounds. You would hear that in the assessment, before anyone signs.
What happens when something breaks in the evening?
Whatever we wrote down before it broke. Care engagements specify which failure classes get an immediate response and which are next-business-day, so nothing depends on goodwill or interpretation. If your business needs stronger coverage than we offer, we say so in the proposal.
How do we start?
Send a short written brief: what you have running (site, tools, any AI features), how it is hosted today, and what worries you. We reply in writing within one business day with fit / no-fit and, if fit, a scope and price.
— Engage
Launched, then left alone?
Tell us what you have running and what worries you. We reply in writing within one business day.