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, enabling platforms and businesses to embed financial accounts, money movement, and related banking-like capabilities into their products. As a PM, you are asked to estimate the infrastructure and operational load required to support this launch at scale.

Frame the estimate around the concrete systems and teams that would be stressed during launch: account onboarding, identity and risk checks, ledgering, money movement, API traffic, customer support, compliance operations, incident response, and risk review queues. The users include platforms building on Stripe Treasury, their end customers, internal risk and compliance teams, support agents, and infrastructure teams responsible for reliability.

This is a guesstimate exercise, so focus on building a clear, defensible estimation model rather than trying to know Stripe’s actual numbers. You should define the launch scope, identify the key units of demand, make explicit assumptions, and show how those assumptions translate into operational capacity or infrastructure load.

The experience should consider:

- The launch scope: geography, customer segment, platform size, rollout phase, and expected adoption curve.

- The core unit of estimation, such as active Treasury accounts, API requests, transactions, onboarding reviews, support tickets, or risk alerts.

- Population and adoption assumptions, including how many platforms launch, how many end users they bring, and how quickly usage ramps.

- Usage frequency assumptions, such as account creation, balance checks, transfers, payouts, deposits, disputes, and compliance events.

- Infrastructure dimensions, including peak API throughput, ledger writes, data storage, monitoring volume, and failover capacity.

- Operational dimensions, including KYC/KYB reviews, fraud/risk queues, compliance escalations, customer support contacts, and incident coverage.

- Sensitivity analysis for high-growth, low-growth, and stressed launch scenarios.

- Sanity checks against comparable financial infrastructure products, launch ramp patterns, and reliability expectations.

Your goal is to produce a structured estimate that helps leadership understand the order of magnitude of capacity needed, the most important assumptions driving the estimate, and where Stripe should pay closest attention before and during launch.