Bringing Consumer Financial Services into Meta's Messaging and Social Apps

You are a product manager at Meta. Design a banking product that Meta would offer within its own products. Explain why Meta should build it, which users it serves and what money problem it solves for them, what the first version does, how it would grow, and how you would measure success. ```hint Start from why Meta Banks already handle personal accounts, balances and transfers well. Look for money problems that arise inside the conversations, groups and commerce already happening on Meta's apps, where Meta has an advantage a bank lacks. ``` ### Clarifying Questions - Should Meta become a licensed bank itself, or offer banking features through partner banks and payment providers? - Which app should host it first (WhatsApp, Messenger, Facebook or Instagram), or is choosing it part of the task? - Which market should launch first, given that banking rules and payment habits differ sharply between countries? - What is the business goal: engagement with Meta's apps, direct revenue, or support for commerce on its platforms? ### What a Strong Answer Covers - A credible reason for Meta to enter banking, tied to its mission and existing assets, plus deliberate choices of app, market and partnership model - A focused user segment with concrete money pain points that a messaging or social app is well placed to solve - A specific first version and a phased roadmap, prioritized by user impact against regulatory and trust cost - Success metrics for adoption, engagement and revenue, with guardrails for fraud, losses and complaints - Trust, privacy and regulatory risks, given public skepticism about Meta and its earlier, abandoned digital currency project ### Follow-up Questions - A partner bank worries that Meta will own the customer relationship. How would you structure the partnership? - How would the design change in a market where many people have no bank account? - What results after the first year would make you shut the product down?