
Scale of operations
260 business units. One Marketing Cloud standard.
IHOP
Multi-BU SFMC · ~260 business units
IHOP runs Marketing Cloud across ~260 internal business units: shared naming, QA, and release rhythm without a free-for-all of freelancers. Cell Ops installs the patterns and staffs the depth each BU still needs.
Situation
Where the work sat
At IHOP scale, Marketing Cloud is less a campaign tool and more an operating system for many internal business units. Each BU has local urgency. The enterprise still needs shared naming, shared QA, and a release rhythm that does not melt the instance.
Without a standard, every BU invents folders, data extensions, and send practices. Support cost explodes. Deliverability and brand risk follow. Local journey families (local store promos, loyalty nudges, seasonal offers) still have to ship, but they ship inside one operating standard.
What was broken
Why it was hard
Orphaned business units, conflicting data extensions, and inconsistent send practices pile up fast. Adding more contractors usually multiplies the chaos: each freelancer optimizes for their BU’s next send and leaves behind another private convention.
Governance that only lives in a slide deck fails. Governance that blocks every local launch also fails. The operating problem is standards with enough specialist depth that BUs can still move.
What the Cell did
How we approached it
Cell Ops installs shared patterns (naming, QA, release rhythm, queue coverage) and staffs the specialist depth each BU still needs when they spike. Journey work stays concrete at franchise scale: local offer and promo journeys, loyalty and visit re-engagement, seasonal campaign paths, and shared suppression / preference rules that every BU inherits. The Cell is the keeper of the standard and the surge capacity, not a ticket desk that rubber-stamps every one-off.
Week to week
How it ran
A cadence for releases and reviews that BUs can plan against. Intake that distinguishes “needs a local exception” from “needs to follow the standard.” Training and templates so new BU operators do not invent a second Marketing Cloud inside the first. Resize when BUs spike or pause without rewriting the whole relationship.
Outcome
What stuck
One operating standard across IHOP business units. Specialist coverage without fragmenting decision-making. Flexible resize when demand shifts. Proof that multi-BU SFMC can run without freelancers-gone-wild.
Why it still matters
What buyers should take
If you are evaluating Marketing Cloud staffing for a franchise, multi-brand, or multi-region estate, ask vendors how they prevent BU drift. The IHOP ~260-BU pattern is the concrete answer we put in front of buyers.
Next step


