What a Shopify maintenance retainer should include.

Why stores outgrow a one-off build

A Shopify store is never really finished. Apps update, Shopify ships platform changes, checkout and theme code drift as marketing adds tags and popups, and every sale event is a small stress test on speed and uptime. The stores that stay fast a year after launch are the ones with someone actively watching them, not the ones built well once and left alone.

That's the case for a retainer over a one-off project: it buys ongoing attention, not just a finished build.

What should actually be in scope

• Bug fixes and QA. Broken variants, checkout errors, layout breaks after a Shopify update, caught and fixed without a support ticket queue.
• Performance and Core Web Vitals. Page speed doesn't stay fixed after launch. Someone should be watching it and fixing regressions as they appear, not just once a quarter.
• Theme releases and app updates. New features, seasonal changes and app upgrades shipped without breaking what already works.
• On-call support with a real response-time commitment. "We'll get to it" is not a commitment. Ask for a number, in hours, and ask what happens outside business hours during a sale.
• Security and backups. Regular backups and a plan for what happens if an app or a bad deploy breaks something live.
• A technical point of contact. Not an account manager relaying your message to a dev team two time zones away. The person who answers should be able to open the code and fix it.

In-house, agency or freelancer

Each has a real trade-off, not a right answer:

• In-house gives you full-time attention and context, at the cost of one salary covering one skill set, one set of working hours, and the risk of a single point of failure when they're on leave.
• A freelancer is often the cheapest option and can be excellent for a narrow scope, but rarely covers design, performance, CRO and backend depth all at once, and has no backup if they're unavailable.
• A retainer with an agency or small studio trades some of the in-house context for a full team's range: development, performance, design and often growth support, covered even when one person is out.

The right choice depends on your order volume and how much beyond "keep it running" you need. A store doing a handful of releases a year needs less than one doing weekly drops.

Questions worth asking before you sign

• What's your average response time, in hours, on a working day, and can you show it rather than claim it?
• Who exactly answers when something breaks: a developer, or someone who relays to one?
• What happens during a flash sale or a launch, outside normal hours?
• Is performance work (speed, Core Web Vitals) included, or billed separately as "optimisation"?
• How many other stores does this team support at the same time as mine?

What this looks like in practice

We've managed Oxie Nutrition's Shopify store since August 2023, keeping it technically robust while supporting their performance marketing and CRO alongside it. Miduty has been on retainer for 3.5 years since their migration, with our team managing their entire Shopify experience on a high-traffic store running hundreds of daily orders. Neither relationship started as a retainer; both became one once the one-off build proved out.

FAQ