Estimate the infrastructure or operational load needed to support a major Treasury launch

Problem Statement Description

Product context: Stripe is financial infrastructure for internet businesses; its products include payments, Checkout, Billing, Connect, Radar, Issuing, Terminal, and tax tools.

Stripe is preparing for a major Treasury launch that will allow platforms and businesses to embed financial accounts, money movement, and balance-management capabilities into their own products. As a PM, you are asked to estimate the infrastructure and operational load required to support this launch at a reliable standard for financial services.

This is a guesstimate exercise, not a systems design deep dive. Focus on structuring the problem, defining the units of load, sizing the expected customer and transaction volume, and translating those assumptions into operational needs such as API traffic, ledger activity, risk reviews, compliance checks, support volume, and incident readiness.

Your estimate should reflect Stripe’s context: developer-facing financial infrastructure, high reliability expectations, regulated money movement, platform customers with many end users, and risk teams that must monitor fraud, compliance, and financial exposure during launch.

The experience should consider:

- The launch scope: geography, customer segment, platform size, and which Treasury capabilities are included.

- The unit of estimation, such as active platforms, connected accounts, end-user financial accounts, transactions, balances, API calls, or risk events.

- Adoption assumptions, including ramp-up speed, early-access customers, launch-day spikes, and steady-state usage.

- Frequency assumptions for account creation, deposits, withdrawals, transfers, card or payment activity, balance checks, and webhook events.

- Infrastructure load drivers, including API requests, ledger writes, reconciliation jobs, notifications, data storage, and peak-to-average traffic ratios.

- Operational load drivers, including KYC/KYB reviews, fraud alerts, compliance escalations, support tickets, account holds, and incident-response needs.

- Sensitivity checks for low, base, and high scenarios, especially around a few large platforms driving disproportionate volume.

- Sanity checks against financial reliability expectations, regulatory risk, and the consequences of underestimating launch capacity.

Your goal is to present a clear, defensible estimation approach that shows how you would size both technical and operational readiness for a Stripe Treasury launch, while making assumptions explicit and identifying which inputs would most affect the final capacity plan.