MuleSoft, beyond the platform decision

MuleSoft itself works. Anypoint Platform is mature, the connectors are extensive, the runtime is solid. If your rollout is stalling, it is almost certainly one of three things — none of them on the product roadmap.

Governance written for the first three APIs, not the next three hundred. When you have ten APIs, anyone can keep the catalogue tidy. When you have three hundred APIs across fifteen business units, you need a published operating model: who owns what, who approves what, who gets called at 02:00 when something breaks. Most rollouts hit a wall at the governance limit they accidentally set in week six.

No path to cost recovery. The platform team gets funded centrally for the first eighteen months. Then someone in finance asks: who pays for this next year? Without a chargeback model, a published TCO per business unit, and a defensible value story, the funding gets cut in half before the rollout is half-done.

Country four syndrome. The first three countries onboard. Then everything stops. The first three had strong local champions, simple landscapes, helpful sponsors. Country four has none of that. Without an onboarding playbook calibrated to the hard cases, the rollout grinds to a halt.

Most consultants will sell you the technical platform rollout. Some will add the governance. Very few connect the platform decision to the economics that have to make it sustainable. I work all three from week one.

The platform layer: the Anypoint hierarchy set up correctly — business groups for headquarters and each country, environments per business need, role-based access from the top down. I have made the mistakes here at scale and know what is expensive to rework later.

The governance layer: a working Centre for Enablement (C4E), not a slideware one. The operating model — federated ownership, central standards, escalation paths — that actually scales past the first thirty APIs. The published kind, not the implicit one that lives in someone's head.

The economics layer: chargeback model, TCO per business unit, and a value story you can put in front of the CFO. Without this, every rollout becomes a budget fight in year two. With this, you renew.

The Rapid Decision Framework runs alongside any of these — when the question is "MuleSoft vs Workato vs UnifyApps?", that is an evaluation problem I will solve with the same mathematical approach I use everywhere else.