Skip to content
Building a Shopify app or a SaaS product?Chat on WhatsApp
shopify-development

Shopify Support Retainer vs Project Work: Which One You Should Actually Buy

A retainer buys availability; a project buys a defined outcome. Below about ten hours a month of real work, the project is almost always cheaper. Here is the decision, with a worked cost model on a store doing 2,000 orders a month.

AK
Aashish Kaushik · 9 min read · updated 12 November 2026
On this page

Key takeaways

  • A project buys output you can point at. A retainer buys availability and retained context. Those are different products and the cheaper one depends entirely on how much small work your store generates.
  • Below roughly ten hours of genuine monthly work, buy projects. Above twenty, a retainer is usually cheaper than the same hours bought ad hoc at emergency rates.
  • The clause that decides value is not the monthly fee, it is the effective hourly rate, the overage rate and the rollover policy read together.
  • An SLA that promises a response time is normal. One that promises a resolution time for an unknown bug is a sales device.
  • The hybrid - fixed-scope project to launch, then a smaller retainer to hold - is what most mid-sized merchants end up with, and it is worth asking for directly.

A project buys you a defined outcome. A retainer buys you availability and the fact that someone already knows how your checkout works. Those are different products, and the cheaper one depends almost entirely on how much small, unpredictable work your store actually generates each month.

The short version: below roughly ten hours of genuine monthly work, buy projects. Above twenty, a retainer is usually cheaper than buying the same hours ad hoc at non-retainer rates. Between the two it is a judgement about urgency rather than volume, and this page is mostly about making that judgement well.

If what you want is the anatomy and pricing of a retainer itself, that sits in the Shopify retainer guide. This page is the purchase decision.

The real difference: output or availability

When you commission a project, the deal is legible. There is a scope, a price, a date, and something you can point at when it is done. If it is late, you know. If it is wrong, you can say what wrong means by reading the scope.

A retainer is not that. You are buying a standing claim on someone's time, and the value you extract depends on whether you use it. The most common retainer regret is not that the work was bad; it is that the merchant bought twenty hours, used six, and spent a year paying for the other fourteen.

The flip side is that the project model has a cost you do not see on the invoice. Every project starts with someone reading your theme, mapping your app stack, and working out which of your integrations is fragile. On an existing Shopify store that is realistically five to fifteen hours before anything useful ships. If you commission four projects a year from four different suppliers, you pay that ramp four times, and it is buried inside each quote rather than itemised.

Retained context is the genuine product a retainer sells. Everything else - maintenance, fixes, improvement hours - you can buy another way.

Retainer against project work, side by side

Monthly retainerFixed-scope project
What you are buyingAvailability and retained contextA defined deliverable
BillingMonthly, whether used or notFixed price or capped time and materials
Effective hourly rateLowerHigher, and higher again for urgent work
Response to an emergencyContractual, if the SLA says soWhenever they have capacity
Ramp-up cost per engagementPaid oncePaid every time, usually invisibly
Risk you carryPaying for hours you do not useWaiting in a queue when something breaks
Easiest to justify whenWork is frequent, small and urgentWork is occasional, large and plannable
Typical commitment3-12 months, 30 days' noticeThe length of the project
Who it suitsStores shipping continuouslyStores shipping a few times a year

Five situations where a project is the cheaper purchase

Your store is stable and you ship rarely. If the last six months produced two change requests, a retainer is paying monthly for availability you are not using. Commission the work when you need it and revisit the question when commissioning gets tedious.

You have a single large thing to do. A replatform, a theme rebuild, a B2B launch, an app build. These want a scope and a fixed price. Running a big build out of a monthly block of hours is how a three-month project becomes a nine-month one, because there is no date to miss.

You have an in-house developer. Then your gap is specialism, not capacity - a checkout extension, a Functions migration, a performance problem nobody can crack. Buy the specialism as a project. Paying a monthly retainer alongside a salaried developer is how most agencies end up doing low-value work very expensively.

You are about to rebuild. Retainers are for running stores. Scope the rebuild, deliver it, and start the retainer afterwards when there is something worth maintaining. Buying a retainer on a store you are about to throw away is money spent maintaining a corpse.

Your budget is genuinely tight. This matters more than the modelling suggests. A project is a decision you make once, with a known number. A retainer is a recurring cost that has to survive every budget review, and the ones cancelled in month five rarely delivered the value they were priced to deliver, because the first two months are ramp.

Five situations where a retainer is

You ship continuously. New collections, landing pages, campaign work, seasonal merchandising. Twelve small commissions a year is a scoping and invoicing overhead on both sides that eventually exceeds the rate difference.

Downtime costs real money. If an hour of broken checkout is a meaningful number for you, the SLA alone justifies the fee. This is the clearest case there is, and it is the one merchants most often discover the hard way during a sale.

Your stack is complex. Custom checkout extensions, a Functions migration, an ERP or 3PL integration, a headless front end. Re-onboarding someone onto that costs more than it does on a stock theme, and the platform changes often enough that something will need attention.

You have a plan you keep not executing. Speed work, SEO fixes, a CRO backlog. Ring-fenced improvement hours in a retainer turn an intention into a schedule, which is the only mechanism that reliably gets these done. Be aware that bundling disciplines together has a known failure mode, covered in what to expect from a Shopify SEO agency: development work has deadlines and SEO work has intentions, so development quietly eats the hours unless the agreement ring-fences them by discipline.

Emergency hourly work is eating you. If you are repeatedly paying premium rates for same-day fixes, add up a year of them. That total is the number to compare against a retainer, not the standard hourly rate, and it usually settles the argument.

Careful

The most expensive version of this decision is neither. It is having no arrangement at all and then needing a developer urgently, in which case you pay a premium rate to someone who has never seen your store and bills for the time it takes to understand it. That is the real alternative being compared against, and it is why both options usually look like good value next to the status quo.

A worked cost model: 2,000 orders a month

Take a store doing 2,000 orders a month on a customised theme with a dozen apps, one integration, and a marketing team that wants landing pages. Real consumption over a year works out at about fifteen hours a month, lumpy: four hours in February, thirty in November.

Buying ad hoc. Fifteen hours a month at a standard non-retainer rate, plus a premium on perhaps a fifth of those hours because they are urgent, plus a ramp cost each time a different person picks it up. Call the effective rate 30-50% above the retainer rate once the premiums and ramp are included. The annual number is higher than the headline hourly rate implies, and it is unpredictable month to month, which makes it hard to budget.

Buying a retainer. A twenty-hour block at a lower effective rate. In February you use four hours and waste sixteen unless the agreement has rollover. In November you use thirty and pay overage on ten. Over a year, if rollover exists and is generous, you come out meaningfully ahead. If it does not, you come out roughly level and have bought response time for free. If you bought a thirty-hour block because the agency suggested it, you come out behind.

That is the whole model, and it is why the rollover clause and the block size matter more than the monthly figure. A twenty-hour retainer with rollover beats a thirty-hour retainer without it for almost every seasonal business.

What 'support' actually means in the agreement

Support is the vaguest word in agency contracts. Three distinctions make it concrete.

Response time versus resolution time

Response is someone acknowledging the issue and starting work. Resolution is it being fixed. Any agency can commit to the first. No honest agency commits to the second for a bug nobody has seen yet, because the cause might be a third-party app, a Shopify platform change, or a payment provider. Get response time in writing, banded by severity, and treat a promised resolution time as a sign the contract was written by sales.

Business hours versus cover

A response time of four hours means nothing if those are business hours and your checkout breaks at 7pm on the Friday of Black Friday weekend. Ask explicitly what happens out of hours, whether there is a route to a human, and whether it costs extra. Both answers are legitimate. Finding out during the incident is not.

Inside or outside the block

Does emergency work consume your retainer hours, or is it billed separately at a premium? Agencies differ, and both models are defensible. What is not defensible is a contract that does not say.

Read these lines before you sign either agreement

  • Hours included and at what seniority - twenty junior hours and twelve senior ones are not comparable
  • Effective hourly rate: monthly fee divided by included hours
  • Overage rate, and whether it is above or equal to the retainer rate
  • Rollover: does it exist, what is the cap, when do banked hours expire
  • Response time by severity, in writing, with an out-of-hours route named
  • Whether emergency work sits inside or outside the block
  • Minimum term and notice period - three months is normal, twelve is a lock-in
  • Handover terms: code ownership, admin access, documentation of custom work
  • What is explicitly excluded (content, photography, app subscriptions, ad management)

Minimum terms and the lock-in trap

Agencies ask for a minimum term for a real reason: the first month of any retainer is ramp, and they lose money on a merchant who leaves in month two. Three months is a fair ask. Six is negotiable. Twelve, with no break clause, is a financing arrangement dressed as a service agreement, and the thing it most often finances is the agency's cash flow rather than your store.

The compromise worth proposing is a three-month initial term followed by rolling monthly with thirty days' notice. Most agencies will take it. The ones that will not are usually the ones whose retention depends on the contract rather than the work.

Watch for the combination of a long minimum term and no rollover. Together they mean you have pre-paid for a fixed quantity of availability regardless of whether your business needs it that month, which is the arrangement with the worst expected value for you of any on offer.

The hybrid, which is what most merchants actually want

The common end state is a fixed-scope project to build or rebuild, followed by a deliberately small retainer to hold. The project has a date and a price, so it finishes. The retainer that follows is sized for maintenance plus a modest improvement allowance, not for the build velocity you needed during the project, which is the mistake merchants make when they roll straight from one into the other at the same hours.

Ask for this shape explicitly. Agencies quote it happily when asked and rarely propose it unprompted, because the larger continuing retainer is the better commercial outcome for them. If you are still choosing a supplier at all, the agency hiring guide covers the evaluation, and what a Shopify store costs to build covers the project half of the number.

The uncomfortable answer

A retainer is wrong for a lot of stores, and we sell retainers. If your store is stable, your theme is close to stock, your app stack is small and your team is not shipping campaigns, you do not need one. You need a paid half-day twice a year to apply updates safely, and someone's phone number. Buying a monthly agreement because it feels like insurance is how merchants end up resenting an agency that has not done anything wrong.

The test is not whether a retainer feels safer. It is whether you can name ten hours of work you would give someone next month. If you cannot, the answer is projects, and you can revisit it in six months when you can.

Frequently asked questions

What response time should a Shopify support retainer actually guarantee?
Response time banded by severity, in writing. A reasonable shape is: same business day for anything cosmetic, four business hours for anything that degrades buying, and one hour with an out-of-hours contact route for a checkout that is down or a store that is offline. Note that this is response - someone acknowledging and starting work. Resolution time for an unknown bug cannot honestly be guaranteed by anyone, and an agency that offers it has either not read the clause or is relying on you not to invoke it.
Is it cheaper to keep a developer on retainer or to call one when something breaks?
Call them when it breaks, if it breaks rarely. Ad hoc work is more expensive per hour, often substantially, but you only pay for hours you use. The crossover is driven by two things: how many hours a month you genuinely consume, and how much of that work is urgent. A store needing five predictable hours a month should buy them ad hoc. A store needing five unpredictable, urgent hours a month is buying response time, not hours, and that is what a retainer prices.
What happens to my store if I cancel the retainer mid-project?
That depends on a handover clause most contracts do not have, which is why you should ask for one before signing. At minimum, get in writing that you own the code and the theme, that you hold or can obtain admin-level access without the agency's cooperation, that work in progress is delivered in whatever state it is in, and that documentation of custom work is provided. Thirty days' notice is standard. The real risk in an abrupt exit is not the fee, it is a half-finished custom feature that nobody else can safely finish.
Can one retainer cover development, SEO and CRO, or do I need separate agreements?
One agreement can cover all three, and frequently should for a store under roughly $500,000 a month, because splitting it creates coordination work you then pay for twice. The risk is that the three compete for the same hours and development always wins, because development has deadlines and the other two have intentions. If you combine them, ring-fence the hours by discipline in the agreement itself. If the SEO work keeps getting eaten, the honest fix is a separate agreement, and our guide on what to expect from a Shopify SEO agency covers what that should look like.
How many hours a month does a typical Shopify store genuinely consume?
A stable store on a lightly customised theme with a small app stack consumes two to six hours of real maintenance a month - updates, checks, the occasional small fix. Add campaign work, landing pages and seasonal merchandising and it rises to ten to twenty. A store with custom checkout extensions, an ERP integration or a headless front end starts at fifteen and goes up. Track what you actually commissioned over the last six months before you buy a block of hours; most merchants over-estimate by roughly double.
Do I still need a support retainer if my store runs on a stock theme with no custom code?
Probably not. A stock theme with a small app stack is the single best case for buying work ad hoc: Shopify maintains the platform, the theme vendor maintains the theme, and your exposure to a platform change breaking something custom is close to zero. What you should still do is schedule a paid half-day twice a year to apply theme and app updates on a duplicate theme and check that nothing regressed. That is a project, not a retainer.

Building a Shopify app or a SaaS product?

ByteInfy designs, builds and ships them. Tell us what you are making.

Chat on WhatsApp

Or reach us directly

About the author

Aashish Kaushik

Founder

Builds Shopify apps and SaaS products at ByteInfy.

More from Aashish

Get new articles by email

No more than one a week. Unsubscribe in one click.

Comments

Comments are reviewed before they appear.

Keep reading

Entrepreneur at a desk using a laptop for business planning. Ideal for tech and startup themes.

Shopify Retainer Cost: The Tiers, Hours and What's Included

A Shopify retainer buys availability rather than output, which is why two at the same price differ enormously. Priced tiers from $500 a month, the exclusions nobody writes down, and the honest answer for a small store that probably should not buy one.

15 September 2026 · 14 min readRead
Minimalist image featuring a shopping cart with products and a sale-tagged bag.

How Much Does a Shopify Store Cost to Build in 2027?

The honest answer is that a Shopify store costs anywhere from a few hundred to six figures, and the range is not agencies being evasive. It reflects genuinely different projects. This breaks the cost into its four real components so you can work out which end of the range you are at.

16 September 2026 · 8 min readRead

Shopify CRO: What an Agency Programme Costs and What It Actually Fixes

A one-off Shopify conversion audit runs about $1,500-$5,000; an ongoing testing programme $3,000-$10,000 a month; a Plus-scale programme $8,000-$20,000+. Here is what sits inside each band, and when none of them is the right purchase.

5 November 2026 · 11 min readRead
WhatsApp