How Agencies Amortize A/B Tool Cost Across Client Rosters
How CRO agencies amortize one A/B testing license across 4–6 clients without tripping per-domain or per-MAU pricing traps — and the break-even test velocity that keeps the model honest.
Quick answer
Run one A/B testing seat across 4–6 client programs and the break-even drops from ~6 tests/quarter per client (solo math) to ~1.5–2 tests/quarter per client. The model only holds if your tool prices per seat or per total MAU — per-domain and per-client-workspace tiers erase the saving by client 3.
Agency A/B tool amortization
Spreading the fixed cost of one A/B testing license across multiple client engagements to lower the per-client test-velocity break-even.
Agency A/B tool amortization is the practice of running 4–6 client experimentation programs against a single shared license (or a small pool of seats) and allocating the platform cost across retainers. The arithmetic is simple: if a €1,200/month seat needs ~6 tests/quarter to pay for itself against one client, splitting it across five clients drops the requirement to ~1.2 tests/quarter each.
The model breaks the moment a vendor prices per domain, per workspace, or per MAU bucket — because adding clients reintroduces the per-unit fee the amortization was designed to dilute. Choosing the right pricing structure matters more than the headline rate.
Most agency leads pitch CRO retainers at €3–8k/month per client, and the experimentation tool is a line item inside that. When the tool costs €15k/year, you need either high per-client test velocity or shared infrastructure to keep margin healthy.
Shared infrastructure is the lever most agencies under-use. It also exposes a hidden compatibility check: not every tool's commercial model survives being shared, and not every client roster is shareable without contractual risk.
How the amortization math actually works
Start with the solo break-even. A standalone brand running a single seat needs each test to produce enough incremental revenue to clear the license cost — roughly 6 statistically-meaningful winners per quarter at typical mid-market AOVs. That bar is set by the minimum test velocity to justify an A/B tool.
An agency running the same seat across five Shopify apparel and beauty stores divides the fixed cost five ways. Each client now only needs to justify ~€240/month of tool spend instead of €1,200 — which translates to roughly 1.2–1.5 tests/quarter producing a measurable lift to stay above water.
The amortization only works if velocity holds
Five clients × 1.5 tests/quarter = 7.5 tests on one platform per quarter. That's only ~2.5 concurrent tests at a 4-week cycle. If your team can't sustain that cadence across the roster, you're paying for unused capacity and the math reverts to solo break-even territory.
Pricing-tier traps that break the model
VWO, Optimizely, and Convert all publish list prices that look agency-friendly on the surface. Read the fine print and you'll find three traps that quietly reintroduce per-client cost.
The first is per-domain pricing. Each client storefront counts as a separate domain, and the per-domain fee compounds linearly — by client 3 you've paid more than just buying a second base license. See per-domain pricing traps that break agency amortization for the worked numbers.
The second is per-MAU tiering. If your roster includes one high-traffic flash-sale brand alongside four steady stores, you'll blow through the MAU bucket and get bumped to enterprise pricing — covered in when per-MAU tiering punishes agencies running high-traffic client mixes. The third is per-seat collaboration caps, where vendor limits force a second license at client 4.
Break-even tests per client by roster size
Break-even tests/quarter per client at €1,200/month seat, assuming €4k average lift per winning test
| Roster size | Allocated tool cost / client / month | Break-even tests / quarter / client | Concurrent tests needed on platform |
|---|---|---|---|
| 1 client (solo) | €1,200 | 5.8 | ~2.0 |
| 3 clients | €400 | 1.9 | ~2.4 |
| 5 clients | €240 | 1.2 | ~2.5 |
| 6 clients | €200 | 1.0 | ~2.5 |
| 8 clients (cap) | €150 | 0.75 | ~2.5 + queue contention |
Past 6 clients, the per-client break-even keeps dropping but platform contention rises sharply. You start hitting goal conflicts, audience overlap, and reporting overhead — which is where shared test queue scheduling across 4–6 client programs becomes the binding constraint, not license cost.
Billing structure: bundle vs pass-through
Two billing approaches dominate. Bundle the tool into the retainer at a marked-up fixed fee, or pass it through at cost as a separate line. Each has tradeoffs covered in retainer bundle vs pass-through billing for shared A/B tool seats.
Bundled pricing hides the amortization win and lets you keep the margin. Pass-through is more defensible during procurement but invites the question, 'why is our share €240 when the tool costs €1,200?' — at which point you're explaining shared infrastructure to a marketing director who didn't ask.
Risks the spreadsheet doesn't show
Two clients in the same vertical on one seat is a contract problem waiting to happen. Audience data, winning variants, and test history all live in the same workspace — review data isolation and contractual risk of running competing clients on one seat before signing a second beauty brand into the same instance.
Mid-quarter churn is the other invisible cost. Lose one client out of five and your per-client break-even jumps from 1.2 to 1.5 tests/quarter overnight — see why mid-quarter client churn resets your per-client break-even tests, and factor onboarding velocity as the hidden variable in per-client test math when replacing them.
Frequently asked questions
It depends on the contract. VWO's agency plan permits multiple client domains under one master agreement; Optimizely's standard license is per-domain and requires a separate agency program. Always check the 'authorized domains' clause before assuming you can amortize.
Three clients is the practical floor. Below that, the queue-scheduling, white-label reporting, and data-isolation work outweighs the licensing saving. Between 4–6 clients is the sweet spot for most boutique CRO agencies.
Per-MAU pricing punishes mixed rosters. One client with 2M monthly visitors can push the whole shared seat into a higher tier that costs more than two separate base licenses. If any client exceeds ~500k MAU, model per-MAU tiering separately before committing.
Bundle if you want to keep the amortization margin and avoid procurement friction. Pass-through if your clients have transparent-cost contracts or you're using the tool spend to justify a higher retainer ceiling. Most boutique agencies bundle; larger agencies with finance-heavy clients pass through.
Nothing technically, but you'll spread your strategist's attention thin and risk underpowered tests. Build a shared test queue with priority rules — usually based on retainer size or test-readiness — rather than first-come-first-served scheduling.
Yes. Metricuno's agency plan is per-seat with unlimited client workspaces under one master account, so the amortization math doesn't break at client 3 or 4. Each client gets isolated data, white-label reporting, and a separate Shopify/WooCommerce plugin install.
Most agencies present the tool as part of a 'CRO platform & analytics' line at €300–500/month per client, regardless of actual amortized cost. This avoids procurement audits and lets you absorb price increases without renegotiating every retainer.
Significant. Even with separate workspaces, you risk perceived conflict of interest and accidental data leakage in shared reporting templates. Either split licenses or get explicit written waivers from both clients before consolidating competitors onto one seat.
Linearly and painfully. Losing one client from a 5-client roster raises per-client cost by 25% overnight. Build a 30-day replacement pipeline and consider charging a 'platform access' fee that survives mid-quarter cancellations to smooth the curve.
When you hit per-seat collaboration caps (usually 5 editors), when one client exceeds 30% of total roster MAU, or when you onboard a competitor to an existing client. The break-even for a second license is roughly 3 additional clients.
Test ideas before you ship them
Run unlimited A/B tests, attach hypotheses to outcomes, and build a searchable archive of what works — and what doesn't.