scandiweb
Magento support takeover

Adobe Commerce support, recosted.

€19/hr for a full-time developer. €29/hr for a blended team. Same engineers, same standards, structured to fit your size. Bring your last support invoice — we'll show you what this looks like on your monthly bill.

our rates
€19/hr
developer
full-time, single human
€29/hr
dev · PM · QA
blended team rate
€58/hr
BA · PO
only when needed
Adobe Commerce support & engineering, billed by the hour. No retainer minimums. No long-term lock-in.
Trusted by 700+ leading brands worldwide
PUMAOM Digital Solutions / OlympusBoy Scouts of AmericaThe New York TimesSamsungAcerAdobe
three tiers · pick the one that matches your size

One offer, three shapes, priced for the merchant on the other end.

Most agencies price one band and either over-charge small merchants or under-staff enterprises. This program is three distinct offers tuned to merchant size – so the rate, the team shape, and the economics actually fit.

under €10M GMV

Small merchants

€19/hr
blended
Productized full-time developer

One senior Adobe Commerce engineer, dedicated to your store. Roadmap, fixes, releases, the lot. Priced to fit a small-merchant budget without forcing you onto a generic ticket system.

who reads this · Founder · Head of engineering
€10–50M GMV

Mid-market

€29/hr
blended
Blended dev · PM · QA team

A right-sized team that covers development, project management, and QA at one rate. BA / PO time priced separately at €58/hr, billed only when you need it.

who reads this · CFO · COO · CEO
over €50M GMV, large in-house team

Enterprise

€29/hr
blended
Cut the team in half, same or better output

If you run a 10–20 person Magento team, we replace the bottom half of the bill without losing throughput. The math: your current rate × your team size × twelve months, versus ours.

who reads this · CEO · CTO · CIO
All three rates cover Adobe Commerce engineering, support, releases, integrations, and ongoing optimization. Hourly. Billed monthly. No retainer minimums. No setup fees. No platform lock-in.
why this campaign exists

The market is reassessing every line item. Your Magento support contract is one of them.

Four patterns we hear from merchants on existing Adobe Commerce support contracts. None of them are new. All four are louder this year than last.

the invoice

Your support spend is creeping

Hourly rates have drifted up since the contract was signed. The same monthly bill now buys fewer hours, fewer releases, fewer fixes. Nobody had a conversation about it.

the team

The team is bigger than the work

Eight people billed against your Magento, four of them productive. The other four exist because someone, somewhere, agreed they were necessary. Cutting them is hard from inside the contract.

the inertia

Switching feels expensive

The current vendor knows your codebase. They built half of it. Moving feels like a six-month exercise in re-discovery before any work gets done. So the spend continues.

the conversation

No one will give you a math comparison

Every pitch comes back as a deck about ‘value’ and ‘partnership.’ What you actually wanted was rate × team × twelve months, your number vs. theirs. Hard to get a straight one.

We did this once before, in 2008. Cut our hourly rates 5×. Got a flood of inbound from buyers who were reassessing spend in a downturn. The price became the unlock. The market is moving again. We're moving first.

the math, on paper

Three real shapes. Three real numbers against the market rate.

Market rates below are typical Western European Adobe Commerce agency rates as of 2026. Your current contract may be higher or lower — bring it to the math call and we'll run the comparison against your actual numbers, not these.

Scenario 1

Under €10M GMV

1 dev · 160 hrs/month

Productized full-time developer. Same hours, same person every month, fraction of the bill.

market rate
€8,800
at €55/hr
our rate
€3,040
at €19/hr
monthly delta
−65%
Scenario 2

€10–50M GMV

3 dev · 1 PM · 1 QA · 800 hrs/month

Blended team rate. PM and QA included. BA / PO billed at €58/hr only when scoping new work.

market rate
€52,000
at €65/hr
our rate
€23,200
at €29/hr
monthly delta
−55%
Scenario 3

Over €50M GMV

12-person in-house Magento team · 2,000 hrs/month

Half the bill. Same throughput as your current 12-person setup, on the same release cadence. Math on the table.

market rate
€140,000
at €70/hr
our rate
€58,000
at €29/hr
monthly delta
−59%

Numbers shown are illustrative monthly totals at common team shapes. Bring your last support invoice to the math call; we'll do the comparison against your real spend, your real team, your real hour count.

this isn't a discount. it's a playbook.

We've done this once before, in 2008.

When the 2008 financial crisis hit, every merchant we worked with was reassessing every line item on their spend. Including ours.

We cut hourly rates 5×, structured the offer around the merchants we wanted to win, and stayed there until the market normalized. Inbound went up. Margins held because our delivery model fit the rate. The merchants we won then are still merchants we work with today.

The market is reassessing again. The Magento Support Takeover is the 2026 version of the same play — lower rates, productized offerings, structured for the size of the merchant on the other end.

what backs the rate
20+
years building on Magento / Adobe Commerce
700+
merchants we've supported, migrated, or scaled
rate cut we made in 2008 — the precedent for this
Adobe
Solution Partner since the Magento 1.x era
“The price isn't the discount. It's where the market is going. We'd rather get there first than wait for the next contract cycle.”
scandiweb executive board
how this actually runs

Four steps. No pitch deck. No sales theater.

We don't lead with case study slides. We lead with the math against your actual spend, then a transition plan, then the work. The whole process from call to live is usually inside a calendar month.

01
30 minutes

Math call

Thirty minutes. You bring your current support invoice and a rough sketch of your team shape. We bring rate comparisons against your actual numbers, not generic averages. If the math doesn't beat your current setup, we say so on the call.

02
2–4 weeks

Transition plan

If the math works, we map the handover. Codebase walkthrough, ticket triage, on-call rotation, releases, key access. Most transitions complete in 2-4 weeks of parallel work; no big-bang switchovers, no gap in coverage.

03
ongoing

Live in production

Same team every month. PR reviews, releases, bug fixes, integration work, performance tuning. Monthly invoice with hour-by-hour breakdown. No surprise scope changes, no mid-quarter rate adjustments.

04
quarterly

Quarterly math review

Every three months we look at the numbers together. What was billed, what was delivered, what changed. If the math stops working for either side, we say so. Predictable spend, no annual renewal theater.

what people ask first

The obvious questions, answered.

If yours isn't here, put it on the math call. We'll answer it then.

How is this rate possible?
Twenty-plus years on Magento means we've compressed almost every kind of Adobe Commerce work into a delivery model that fits inside these rates. The 2008 rate cut, repeated in 2020, taught us how to structure the work so the margin holds at low headline rates. We're not subsidizing this from another line of business and we're not running a loss leader.
Are these your real engineers, or junior teams under a senior badge?
Same engineers we put on enterprise migration projects. Senior Adobe Commerce specialists, Hyvä-fluent where the stack supports it, certified where the platform recognizes certifications. No bait-and-switch between sales call and live work.
What's the catch?
No catch on the rate. The honest constraint is volume: we run this program at scale, so each merchant gets a productized shape (a team configuration we've already optimized) rather than a bespoke org chart. If you need a custom team structure with handpicked individuals, we have a separate offering at standard market rates.
Will the rate hold, or does it climb after twelve months?
It holds for the duration of the program. We're not running a teaser rate that resets at month thirteen. Quarterly math reviews are the moment to re-scope hours if your needs change — rate stays.
What if the math doesn't beat our current setup?
We tell you on the math call. About one in five comparisons comes back as ‘you're already in a good place, stay put.’ We'd rather lose a 30-minute call than win a customer who isn't actually saving money.
Can we keep our current vendor and add you alongside?
Yes. Several merchants run a hybrid: current vendor on the legacy critical-path stuff, scandiweb on new feature work and BAU support. The math still works because you're shrinking the higher-rate spend.
How does transition work without breaking production?
Parallel work for 2-4 weeks. We onboard onto your codebase, ticket queue, deploy pipeline, and on-call rotation while your current vendor stays operational. Cutover happens when both teams agree the handover is complete. No big-bang switches.
Do you sign a multi-year contract?
Month-to-month is the default. We don't need lock-in — if the math holds, the merchant stays. If the math stops working, they leave. Contracts are a sales tool, not an engineering one.
30 minutes · no demo, no pitch

Bring your last invoice. We'll bring the math.

Thirty minutes. You share your current Adobe Commerce support spend — rate, team shape, monthly hours. We run it against the three tiers and tell you what the math looks like. If you're already in a good place, we'll say so.

“We'd rather lose a 30-minute call than win a customer who isn't actually saving money.”
scandiweb executive board
  • Response within one business day
  • 30 minutes · math comparison, no sales deck
  • Your invoice stays confidential
  • If you're already optimized, we tell you

We respond within one business day.