← Portfolio Home · Work Library · Related operating model: MFan
Type: Research Essay Stage: Working Hypothesis Evidence basis: Public creator/fan journey signals, public company signals, and operational inference Last updated: August 2026 Boundary: This is not a description of METUB’s internal strategy, roadmap, metrics, or operating model.
What kind of operating infrastructure do creators need when creating becomes a business—and what responsibility does a platform inherit when more of that operation flows through it?
This started while I was mapping creator and fan journeys across memberships, creator websites, content access, orders, payments, and support. A fan could move from membership to payment, from payment to order, or from community to support, while identity, entitlement, payment context, order history, support records, and relationship history did not necessarily move with them. From outside, it looked like one ecosystem; operationally, the state appeared distributed.
My first interpretation was fan-side fragmentation. Following the same dependencies back to the creator side made the question wider. If a fan journey already needs coordination across identity, entitlement, commerce, payment, and support, what happens when the creator is also carrying brand commitments, approvals, livestreams, settlement, fulfilment, reporting, rights, and audience expectations?
Public signals around creator-economy companies include work across operations, commerce, partnerships, analytics, livestream, strategy, and business support. That does not prove a specific company is building an integrated creator operating system. It was enough to make the operating layer worth inspecting.
What kind of operating infrastructure starts to matter when creating becomes recurring commercial work?
Once several commitments are live at the same time, the job is no longer only to publish content. A creator may have to keep campaign terms and approvals straight, deliver a livestream, track affiliate or store activity, wait for settlement, handle reporting, respect rights and platform rules, and still respond when a fan or customer has a problem.
The useful part of that list is not its length. It is the way one failure can spill into another area: an unclear approval can become a public claim problem; a fulfilment issue can become a support burden; a delayed payment can interrupt the creator’s ability to keep working; a rights mistake can become a takedown or relationship dispute.
That gave me a more specific question than “how should creator platforms grow?”: which parts of recurring creator work become easier to coordinate when they move through one platform, and which new dependencies appear at the same time?
If more recurring activities pass through one platform, the value can come from coordination and continuity, not only distribution or monetization. Onboarding, campaign coordination, commerce, livestream operations, settlement, reporting, fan entitlement, support, compliance records, and business history can start to share context instead of being rebuilt in separate places.
The switching cost in that situation is not only technical. A creator may be able to open another tool tomorrow, while still needing to move unfinished commitments, payment context, partnership history, audience relationships, support records, and prior decisions. That is the mechanism I was trying to describe.
I use Share of Operations as shorthand for one question:
How much of the creator’s recurring business operation flows through the platform?