How much custom development budget should a $20M-$500M merchant expect to set aside annually just for ongoing theme customization, separate from the initial build?

Why does an annual theme budget need two lines?

An annual theme budget needs two lines because upkeep (maintenance) and new work grow from different drivers, so one blended figure underfunds one of them. The decision before this budget is whether to build a section library: reusable theme sections that marketing assembles pages from. We found no published benchmark that gives a dollar figure for theme upkeep at $20 million to $500 million in revenue. So the method is a share of build cost plus the marketing calendar.

How does a theme's update stream drive the upkeep line?

A theme's update stream drives the upkeep line because each release you take on a customized theme is merge work, and the busiest theme here shipped 13 releases in 2026. Shopify copies theme editor changes into an update and includes code edits only when they don't conflict. Otherwise, "you need to copy them to the new version of your theme" (Shopify Help Center, October 2026). How often that happens depends on the theme, whether Shopify's free Dawn and Horizon or the paid Prestige and Impulse:

Skipping updates is free this year and expensive in year three, which means a skip policy only defers the bill.

What else pushes the upkeep line up?

Three more drivers push theme upkeep up: app count, store and market count, and how far your code has drifted from the vendor's.

• App count. Each install is a possible regression on a template you didn't touch. App widgets also break at theme updates and odd breakpoints, a pattern Deploi's theme section library record reports from merchant communities (October 2026). The separate question is how many apps is too many.
• Stores and markets. In Shopify's case study, the skin care brand Dermalogica ran Shopify's free Dawn theme across numerous implementations. "Any theme update or fix had to be applied many times over" (Shopify, October 2026). Deploi's shared design system record scores one shared code repository BUILD from three stores in one brand family (October 2026).
• Code drift. Every code edit you carry is one more conflict a vendor release can cause, so the more edits, the bigger the line.

How do you size the new-work line?

Size the new-work line from the marketing calendar and work backward, because campaign tempo drives it and build cost doesn't. A brand running one campaign a quarter plans 4 a year; a brand running one every two weeks plans 26, six and a half times as many (Deploi arithmetic). Both can own identical builds.

1. Count next year's campaigns and launches.
2. List the new sections each one needs that your section library doesn't have yet.
3. Add product and collection page tests and any new template types.
4. Price only that list, because everything else should assemble from sections you own.

What does an annual theme budget leave out?

An annual theme budget leaves out projects, which need their own budget line:

• Rebuilds and redesigns, including a Dawn to Horizon rebuild, because moving to Horizon means switching themes rather than taking an update.
• Headless storefronts, built outside Shopify's themes, where upkeep on Hydrogen, Shopify's headless framework, follows Shopify's quarterly release calendar instead.
• Scope the ratio can't see. The 15 to 20% is a planning ratio from Deploi's records, not a quote, so agency, market and language count all move it.

The budget also assumes marketing can use the section library. If every campaign page needs a developer, the new-work line is a bottleneck with a dollar sign in front of it. The fix is the library decision, not a bigger budget.

When is an annual customization budget the wrong instrument?

An annual customization budget is the wrong instrument when most requests are variations of the same few jobs, because funding repeats pays rent on a problem a configurable section retires.