Monthly Store Retainers

Launch is the start of the store’s life, not the end of the work

Most stores are built as projects. There is a scope, a deadline and a launch date, and on launch day the project is finished. The store is not. It keeps running every day after that, on a platform that keeps changing, with apps and plugins that keep updating, and with a business behind it that keeps wanting new things from it.

What usually happens next is that nobody owns it. The freelancer who built it moves on to the next client. The agency is happy to help, but every change needs a quote. The owner learns to avoid the theme editor because the last time they touched it a section broke. Updates pile up because nobody is sure which one will break something, and each month the store becomes a little harder to change safely.

A retainer is the fix for that specific problem. It gives the store an owner: someone who knows how it was built, keeps it current, notices when something goes wrong, and works through the list of improvements a month at a time.

What actually breaks

On Shopify, the platform itself is rarely the problem. Shopify runs the servers, the checkout and the security patches. What breaks is the layer on top: the theme and the apps. An app update injects a script that shifts the product page. Two apps both try to control the cart drawer. A theme customisation made two years ago stops working when the theme it was built on changes underneath it. None of these is dramatic, and all of them cost orders until someone notices.

On WordPress and WooCommerce there is more to look after, because more of it is yours. Core updates, plugin updates, plugin conflicts, the PHP version your host runs, backups, and the security of the admin itself. A WooCommerce store that has not been updated for a year is not stable. It is a store with a year of changes waiting to be applied at once.

In both cases the pattern is the same. Small problems are cheap to fix when they are found early and expensive when they are found by a customer. Most of the value of a retainer is in finding them early.

What a month contains

Every tier starts from the same routine.

Updates, staging first. Theme, app and plugin updates are applied to a staging theme or a staging site, checked against the templates that matter — home, collection, product, cart — and only then released to the live store, with a rollback point taken before they go.

Fixes. Bugs reported by you or found by monitoring are fixed, logged, and traced back to their cause where the cause can be found. A fix that does not explain why the bug appeared tends to be needed again.

Monitoring. The storefront’s uptime is checked around the clock, and Core Web Vitals field data is reviewed by template, so a product page that has become slow is noticed in the month it happens rather than the quarter after.

The report. At the end of the month you get a health report in the same format every time: what was updated, what was fixed, how speed and uptime looked, and how the hours were spent, task by task. If nothing went wrong that month, the report says so, which is the point of having one.

Improvement, not just upkeep

Keeping a store working is half the job. The other half is making it better, and that is what the Growth Retainer and Dedicated Team tiers add.

New sections and landing pages. Built into the theme as proper sections rather than one-off pages, so your team can reuse them for the next campaign without asking again.

Conversion testing. One test a month, each starting from a written hypothesis — this change, on this page, should move this number — and read against a metric agreed before it runs. Testing is only worth doing where a page has enough traffic to produce a readable result. On pages that do not, we make the changes that are clearly right and measure before and after, rather than running a test that cannot tell you anything.

A roadmap. The list of what the store needs next, prioritised and reviewed with you every quarter. It is what stops the hours each month going to whichever request arrived most recently.

Choosing a tier

Store Care is for a small business that wants the store kept healthy and nothing more complicated. Up to 11 hours a month covers updates, fixes, monitoring and the report, with replies within two business days, and it can be cancelled with 30 days’ notice.

Growth Retainer is for a growing brand with a list of improvements and no one to work through it. Up to 28 hours a month covers everything in Store Care plus new sections, landing pages, a monthly conversion test and the quarterly roadmap.

Dedicated Team is for a business that needs development and design on the store continuously. Up to 71 hours a month, a named lead who owns the roadmap, and replies the same business day.

If the hours run out every month, the work does not stop silently: it waits for next month in roadmap order, or it is quoted before it starts.

When a retainer is the wrong answer

A retainer keeps a sound store sound. It does not fix a store that is structurally wrong.

If the same fault comes back every month, if the theme has been customised so heavily that no update can be applied safely, or if every small change takes a day because the code underneath is tangled, monthly hours are being spent on rent rather than progress. The better order is to find the cause with an audit, remove it once with a focused project or a rebuild, and then put the store on a retainer. We will say when that is the situation, even when it means a smaller invoice from us this quarter.

What stays with you

Everything is done in your Shopify admin or your WordPress install, with the code kept in a repository or dated backup you own. The runbook, the update log, the reports and the roadmap are yours as well. If the retainer ends, the store and its history stay with you, documented well enough for whoever looks after it next.