How a Team Consolidated Twelve Business Managers Into One Workspace

For years, this fast-growing consumer brand did not have one advertising operation. It had twelve. Twelve separate Meta Business Managers — one per region it had expanded into, several inherited intact from acquisitions, a couple left over from old agency setups nobody had retired — and every working day its media buyers paid a quiet tax moving between them. This is the story of how the team learned to consolidate multiple business managers one workspace at a time into a single operating layer, using one System-User token and business_id auto-discovery instead of a wall of separate logins.

This is a composite story, but every beat of it is real for any brand that scales past a single Business Manager. The names and exact numbers are illustrative; the failure mode — and the fix — are not.

The sprawl: a dozen Business Managers nobody planned

No one ever sat down and decided to run twelve Business Managers. They accumulated. The brand started with one, then launched in a second country and spun up a separate BM for it — cleaner billing, cleaner permissions, or so the reasoning went. A third followed for the next market. Two acquisitions arrived with their own Business Managers fully built out, each holding live ad accounts and a tangle of pages, pixels and historical spend nobody wanted to migrate mid-flight. An old agency relationship had left behind a BM that still held a working account. By the time anyone counted, the estate was twelve Business Managers deep, scattered across regions and origins, with no single place that showed the whole picture.

The accounts inside them were healthy. Campaigns ran, spend flowed, performance was fine. The problem was not any one Business Manager. The problem was that there were twelve of them, and the brand's advertising team was a handful of people expected to work across all of it. As we describe in our guide to running multiple accounts inside Business Manager, a BM is an organizational container — and containers multiply far more easily than they consolidate.

The hidden tax: operators switching BMs all day

The cost of the sprawl did not show up as a line item. It showed up as friction, spread thin across every hour. A buyer checking pacing across the brand's top three markets had to log into three Business Managers to do it, one after another, each with its own load, account picker and context to re-establish. Pulling a weekly number for the leadership deck meant opening all twelve, exporting from each, and reassembling the spend by hand in a spreadsheet — an afternoon's work that produced a snapshot already going stale by the time it was done.

Worse was the cognitive switching. Every move from one BM to the next reloaded the mental map: which accounts live here, which naming convention this region uses, who has access, what changed last. None of that was hard in isolation. Multiplied by twelve, by every operator, every day, it was a steady drain the team had normalized. They called it "BM-hopping," half as a joke, and budgeted it into the day as if it were a law of nature. The same friction shows up whenever a team tries to manage multiple Facebook ad accounts without a layer that unifies them — the work is fine; the switching is the tax.

Why this happens to every brand that grows or acquires

The brand had not done anything wrong. The twelve-BM problem is not a symptom of bad operators; it is a structural consequence of how growth interacts with Meta's model. Expand into a new market and a separate Business Manager looks prudent. Acquire a company and you inherit its BM whole, live accounts and all, with no painless way to fold it into yours. Work with agencies and each may stand up its own container. Every one of those decisions is locally reasonable, and the global result is sprawl.

That is the trap. There is no single moment where the estate "goes wrong," so there is no obvious moment to fix it. The Business Managers pile up one defensible decision at a time, and the cost rises so gradually no one flags it. The brand only confronted the problem when a new operations lead, three weeks in and still logging into BMs she had never heard of, asked the obvious question: why are we treating twelve separate logins as twelve separate jobs?

The single token: auto-discovery surfacing every BM at once

The answer turned out not to require migrating, merging or deleting a single Business Manager. The brand moved its operation onto a unified layer and connected the entire estate with one mechanism: a single System-User token. Rather than inviting each operator into each of the twelve BMs — the slow, error-prone, access-spreading approach they had always used — the team added one System-User token, and business_id auto-discovery did the rest, enumerating every Business Manager and ad account that token could see and surfacing them all at once.

In one step, twelve separate logins became one connection. The Business Managers stayed exactly where they were on Meta's side; nothing was moved or restructured. But the brand stopped treating them as twelve destinations. This is the mechanism we point to in our piece on separate logins versus a multi-brand operating layer: the fix for login sprawl is not better login management, it is removing logins from the operating path entirely.

Unifying a dozen BMs into one workspace and one role model

Surfacing the accounts was half the win. The other half was governance. Once every BM's accounts lived in one workspace, the team replaced the old patchwork of shared logins and scattered BM invitations with a single role-based model. Each operator got a named seat with a scoped role and worked through it — never touching the underlying Business Managers directly. A junior buyer could be given exactly the accounts and permissions their job required, across whichever BMs those accounts lived in, without ever holding Meta access to any of them.

That collapsed two old problems at once. The access-sprawl problem — people invited into BMs they should not personally hold, with no clean way to revoke it later — disappeared, because operators no longer had BM-level access at all. And the consistency problem disappeared too: instead of twelve permission setups to keep in sync, there was one role model governing the whole estate, spanning all twelve Business Managers as a single coherent layer rather than twelve improvised ones.

Reporting across all of them on one screen, for the first time

The change leadership noticed first was not the token or the roles. It was the report. For the first time, someone could open one screen and see spend and performance across the entire estate — every account, from all twelve Business Managers, in a single view — without logging into anything twelve times or rebuilding a spreadsheet by hand.

The weekly deck that used to consume an afternoon became a glance. Cross-market comparisons that meant opening three BMs in three tabs became a single sorted list. And because the view read across the whole workspace at once, questions that had been effectively unanswerable — total spend this week across every region and acquired brand — suddenly had a one-screen answer. This is the outcome we walk through in our guide to consolidating ad account reporting: the value is not a prettier dashboard, it is the disappearance of the manual stitching that made whole-estate questions too expensive to ask. The reporting reflects what actually happened on the accounts, kept current by Meta's API on a roughly fifteen-minute sync — which, for a weekly leadership view, is invisible.

What ending the BM-switching tax frees the team to do

The point of consolidation was never tidiness for its own sake. It was reclaiming the hours the team had been paying as a switching tax. When BM-hopping stopped being part of the day, operators spent that reclaimed time on the work the switching had been crowding out.

Buyers who used to lose the first stretch of every morning re-orienting across Business Managers started the day already looking at the whole estate. The operations lead could finally see the brand's advertising as one operation instead of twelve, which made it possible to standardize naming, set consistent guardrails, and onboard new markets into the existing layer instead of standing up yet another silo. New acquisitions stopped being a problem to absorb and became a single token to connect. The team had not gained a new tool so much as it had stopped paying a tax it assumed was permanent.

The lesson: BMs are a Meta artifact, your operating layer should not inherit it

The brand's twelve Business Managers never went away, and they never needed to. The lesson the team took from the exercise is clean: a Business Manager is a Meta organizational artifact, and there is no reason your day-to-day operating layer should inherit its shape. Meta has its reasons for the BM boundary — billing, ownership, regional structure — but none of them obligate your operators to experience your advertising as twelve separate jobs.

Once the team separated the two — let Meta keep its containers, put the actual work on a single layer connected by one System-User token with business_id auto-discovery — the sprawl that had defined their operation for years simply stopped mattering. Wevion's plans start at a permanent free tier (€0), then Starter at €99/mo, Pro at €499/mo, and Plus at €1,499/mo (annual billing at -20%), with Enterprise as a custom plan, and every paid tier includes a 14-day trial that coexists with the free plan — so a team can connect a token, watch its Business Managers auto-discover, and see the whole estate in one workspace before committing. The rest of the playbook lives in the agency tools cluster.

The principle generalizes to any brand that grows or buys its way into a multi-BM estate: do not let the number of Business Managers decide the number of places you work. Connect them with one token, govern them with one set of roles, report on them in one view — and the twelve become one without anyone having to merge, migrate or delete a thing.