Careers
Part of Why does MarTech stack management start with capabilities, not logos?
The martech stack management case studies worth studying twice
MarTech stack management case studies examine two Adobe stories about IBM consolidation and Volkswagen standardization, with careful evaluation lessons.
What to take away
- Both examples are Adobe customer stories, so every figure and every benefit in them is a vendor claim, not an independent result.
- IBM's account reports more than 40 marketing platforms reduced to five core platforms plus Salesforce, and the lesson sits in the integration work, not the smaller count.
- Volkswagen's account puts one shared Adobe content platform behind many brands, with local variation rules that keep brand difference intact.
- Use both to form questions about baseline, cost, migration, retired systems and measured benefit. Do not use them to forecast your own results.
- Independent evidence does exist. Public adoption data, your own licence history and reference calls with comparable companies sit outside vendor control.
What vendor publication changes
A customer story is marketing material with a real customer logo on it. It can be truthful and still selective. Baselines, exclusions and abandoned pilots tend to stay out.
That does not make the IBM and Volkswagen accounts worthless. It moves them from proof to a worked example of an operating pattern.
A capability-first stack management view explains why a product count misleads on its own. Costs, timelines and operating roles still need numbers taken from your own environment.
Ask what changed in the customer's own numbers, not what the platform made possible. Those are two different claims.
IBM: more than 40 platforms to five
Adobe's account of IBM reports a move from more than 40 marketing technology platforms to five core platforms plus a Salesforce CRM instance. The same page reports more than 40 digital asset repositories holding 171,000 assets. Five products are not an integrated suite.
IBM consolidation by the numbers
- 40+martech platforms consolidated
- 5core platforms remaining
- 1Salesforce CRM instance
- 171,000assets in 40+ repositories
The lesson to carry over is to map data, assets, identities, workflows, integrations and ownership onto the target platforms before anything is switched off. Consolidation stays unfinished while repositories, templates, contracts, credentials, support work and legacy dependencies remain live. None of that appears in the headline.
A register that lists every platform, owner and renewal date makes those leftovers visible, and how to keep a stack register honest shows how to run one.
Volkswagen: one platform, many brands
Adobe's Volkswagen One CMS story describes a shared content and experience platform used across brands, with differentiated brand experiences preserved. The page claims savings, faster time to market and more innovation. Neither story shows independently audited cause and effect.
The pattern worth copying is a governed core, reusable components, local variation rules, decision rights and written exceptions. Buyers should still ask how migration cost, regional requirements, integrations, operating roles and legacy retirement were measured.
How to test a stack story
- Name the publisher and whoever paid for the story.
- Write down the baseline, the review period and the formula behind each benefit.
- List systems retired, contracts still running and data left behind.
- Ask for a reference customer that matches your scale, regulation and data profile.
- Record who owns each capability once the project closes.
Diligence questions for a stack story
- Who published and funded it
- Products and teams included
- Baseline and time period
- Costs and migrations
- Retired systems and incidents
- Result definitions and references
Diligence sheet for a stack story
| Claim area | Evidence to request | Where a claim fails |
|---|---|---|
| Scope | Starting systems, brands, regions, workflows | Headlines omit boundaries |
| Change | Migration work, integrations, roles, timeline | Technology is one workstream |
| Benefit | Baseline, formula, review period, exclusions | Vendor figures can be selective |
| Closure | Retired systems, contracts, residual data calls | Consolidation can stay incomplete |
The martech stack management checklist carries those rows into a working document you can assign and review before a pilot starts.
Where non-vendor evidence comes from
Vendor numbers are unaudited. For an outside reference point, Statistics Canada publishes business technology adoption and spending data that no platform vendor controls.
Your own licence and invoice history comes next. That record is the only cost baseline you can defend in a budget meeting.
No independently audited account of either deployment is available in the sources we can verify, so this article keeps the two vendor stories and shows how to test them instead.
What US advertising rules expect from a stack story
Objective performance claims in advertising need a reasonable basis before they run, under the FTC advertising substantiation policy. A customer story that states savings is an advertising claim.
FTC guidance on soliciting and paying for online reviews covers hidden relationships and conditioned incentives, which is how a paid placement can read like a neutral endorsement. Canadian buyers handle the same trust question under PIPEDA and CASL consent rules.
