Recently, social media giant Meta has witnessed a personnel change that has drawn significant attention from the industry. On November 18, John Hegeman, Meta’s Chief Revenue Officer, officially announced that he would be leaving the company, which holds a prominent position in the social media landscape, to start his own startup. This decision not only represents a major turning point in Hegeman’s personal career but also marks a key leadership change for Meta as it pursues the cutting-edge field of superintelligence. During his tenure at Meta, Hegeman made substantial contributions to the company’s revenue growth and business expansion with his outstanding business acumen and leadership skills. He accumulated rich experience in advertising business and revenue strategy formulation, playing a crucial role in the expansion of Meta’s business empire. His decision to leave and venture into the uncertain and challenging realm of startups has undoubtedly sparked speculation and concern about Meta’s future development among the outside world.

According to the message Hegeman posted on Facebook, after his departure, his current main responsibilities will be taken over by another Meta executive, Andrew Bocking. Bocking currently leads Meta’s advertising products and strategy team and has demonstrated outstanding performance in product innovation and strategic planning for the advertising business. With extensive industry experience and sharp market insights, Bocking is expected to lead Meta in maintaining its leading position in the advertising and revenue sectors after taking on Hegeman’s responsibilities.

Separate entitlement from payment rail

A fan benefit should have a clear entitlement record independent of whether the purchase used a card, app-store payment, token or stablecoin. This prevents product access from becoming tightly coupled to one settlement technology. Portable entitlements can then move across supported platforms without requiring every platform to reproduce the original payment flow.

Use auditable rules for creator splits

When revenue is shared among creators, affiliates and platforms, each percentage and deduction should be traceable to a rule version. Changing the split later should not rewrite historical settlements. Versioned rules make it possible to explain why two transactions from different periods produced different payouts.

Measure unit economics after automation

Automated settlement reduces manual work but does not eliminate payment fees, fraud, refunds or generation cost. Track net contribution by product type so a high-volume creator program remains economically sustainable.

Define the settlement base before automating payouts

Revenue-sharing logic needs an explicit definition of eligible revenue. Gross purchase value, payment fees, refunds, taxes, platform share and creator share should be represented clearly before any on-chain or automated settlement runs. A smart contract can execute a formula perfectly and still produce the wrong business outcome if the formula itself is ambiguous.

Design for corrections rather than assuming finality

Refunds, chargebacks and attribution changes often arrive after an initial payout calculation. Append-only correction records or reserve mechanisms can preserve auditability without pretending the first calculation can never change. The system should show both the original event and the later adjustment so creators can reconcile balances over time.

Connect wallet actions to human-readable intent

Before a user or agent signs a transaction, the product should display what asset moves, how much, to whom and under which limits. Machine-readable constraints are valuable, but the final authorization still needs to be understandable to the person responsible for the wallet. Clear intent reduces the risk of technically valid transactions that do something the user did not expect.

Use limits as a first-class safety primitive

Budget envelopes, per-transaction caps and time-based allowances reduce the amount an automated agent can spend even if a later decision is wrong. Limits should be enforced independently from the model and reset only under explicit policy. This creates a bounded-loss model that is easier to audit than unrestricted wallet authority.

Make settlement state observable

Creators and operators should be able to see pending, confirmed, reserved, refunded and disputed amounts without interpreting raw chain events. A clear ledger view makes automated settlement easier to trust. Where blockchain transactions are used, transaction hashes can support verification while the product still presents the business meaning in normal language.

Plan for off-chain failure

Payments often depend on app stores, card processors or internal entitlement systems before any on-chain settlement occurs. Reconciliation must handle the case where one layer succeeds and another is delayed or reversed.