Estimate how many finance teams could use Terminal weekly in one major market

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.

You are being asked to estimate the weekly addressable usage of Stripe Terminal by finance teams in one major market. For this question, “Terminal” refers to Stripe’s in-person payments product, and “finance teams” should be interpreted as teams inside businesses that need visibility, reconciliation, reporting, controls, or payment operations around in-person transactions.

Choose one major market, such as the United States, United Kingdom, India, or another large payments market, and clearly define the scope before estimating. The focus is not total merchants or total card transactions alone, but how many finance teams could plausibly use Terminal-related workflows on a weekly basis.

Your answer should build a structured estimate from business population, relevant merchant segments, likelihood of using in-person payments, Stripe/Terminal fit, and the frequency with which finance teams would engage with related reporting or operational workflows. You should make assumptions explicit and show how changes in key assumptions would affect the result.

The estimate should consider:

- The selected market and what counts as a “finance team” versus an individual owner/operator or outsourced bookkeeper.

- Relevant business segments that process in-person payments, such as retail, restaurants, services, healthcare, events, or multi-location businesses.

- The unit being estimated: distinct finance teams using Terminal weekly, not devices, transactions, locations, or end customers.

- Adoption filters, including businesses likely to use modern payment infrastructure, Stripe, or integrated online/offline payment workflows.

- Weekly usage frequency drivers, such as reconciliation, payouts, refunds, disputes, reporting, fraud review, and accounting close activities.

- Exclusions and edge cases, such as micro-merchants without finance teams, enterprises using custom gateways, or businesses using competitors like Square, Adyen, PayPal, Razorpay, or bank gateways.

- Sensitivity of the estimate to market size, penetration, segment mix, and the definition of “could use” versus “actively uses.”

- Sanity checks using comparable merchant counts, payment acceptance patterns, and expected finance workflow frequency.

The goal is to produce a defensible, transparent market-sizing estimate that a Stripe product leader could use to reason about the scale of weekly finance-team engagement for Terminal in a major market, while clearly separating assumptions from calculated outputs.