What is your dev queue actually costing you?
Most stores can’t answer this. The hours are spread across sprints, the deferred requests never get written down, and the delay is treated as a fact of life rather than a line item.
Four questions, and you’ll have a number.
Two minutes. No email required to see your results.
How your team works today
Campaign pages, section changes, banner swaps, layout tweaks. Not new features or integrations.
Internal salary-loaded rate, agency rate, or a blend. A rough figure is fine.
The ones you wanted and couldn’t — not the ones you decided against.
Based on the 40 hours a month you told us go to content and layout work, at $125 an hour, assuming % of that work moves off the developer queue on a block-based build — the routine content and layout requests, not the genuinely technical ones.
75% of the 8 changes you deferred last quarter. Some deferred work was deferred for reasons other than capacity. This is usually the number that matters more to the business than the dollar figure above.
The wait between someone wanting a change and the change being live. For most stores this is the most visible difference, and the one your team will notice in week one.
Annual value of recovered capacity ($28,800) against a $40,000 migration investment.
Every assumption we used, in one place.
We’d rather show you these than have you find them.
| Assumption | Default | Why |
|---|---|---|
| Share of content and layout work that moves off the dev queue | 60% | Routine content, section, and layout changes move; genuinely technical work doesn’t. Adjustable above — a number you’ve set yourself is a number you’ll defend internally |
| Deferred requests that become shippable | 75% of what you reported | Some deferred work was deferred for reasons other than capacity |
| Post-migration turnaround on a typical change | Under one business day | What teams on block-based builds typically report; varies with how the build is done |
What this calculator cannot know: how much of your theme is custom, which of your apps have a Horizon path, how much recoverable weight your store is actually carrying, or whether migrating is the right call for you at all. Those need measurement, not arithmetic. It also deliberately makes no claim about conversion impact — speed on a customized store is driven mostly by accumulated apps, scripts, and images, and nobody can honestly estimate what a rebuild recovers without measuring your store.
Want this as something you can forward?
Most people running this are building a case for someone else. We’ll send your results with the assumptions attached, so nobody has to take your word for the math.
Done — your results are on their way.
That didn’t go through — check the email address and try again.
One email. No sequence unless you ask for one.
These are estimates built on four numbers you typed.
Useful for sizing the decision. Not enough to make it.
The Readiness Audit replaces every figure above with measurements from your actual store — your real theme drift, your real app compatibility, your real recoverable weight, and a recommendation that includes not migrating if that’s the honest answer.
Five days. $2,500. Credited in full against a migration booked within 30 days.
Questions.
Where do these numbers come from?
Entirely from what you entered, plus the assumptions listed above. We haven’t applied any industry benchmark or third-party study, because none of them would know anything about your store.
Is 60% realistic for how much work moves off the dev queue?
It’s a reasonable middle estimate for a store with typical customization, and it’s adjustable. If most of your developers’ site work is genuinely technical rather than content and layout, set it lower. If your team is filing tickets to move sections around, set it higher.
What if we’re multistore or multimarket?
The value tends to be larger, because every change is currently being made several times — but so is the investment. The calculator uses the higher tier when you flag it. More on how those are priced.
Do I have to give you my email to see the results?
No. The results appear on the page. Email is only if you want them sent to you to forward.
Why is there no conversion-lift estimate?
Because it deserves more caveats than a calculator can carry. Speed on a customized store is driven mostly by accumulated apps, scripts, and images rather than by the underlying theme, so any promise of a conversion lift from switching themes would be dishonest. What a rebuild genuinely offers is the chance to shed that accumulated weight — but how much you’re carrying is something we’d have to measure.
Two minutes gave you a range. Five days gives you the answer.
Or see where your store stands first — free, two minutes, nothing to install.
