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.

Estimate the number of finance teams in one major market that could use Stripe Terminal on a weekly basis. In this context, Terminal refers to Stripe’s in-person payments product used by merchants that need card-present payment acceptance connected to online payments, reporting, reconciliation, refunds, payouts, disputes, and financial controls.

The estimate should focus on finance teams rather than individual consumers or payment devices. A “finance team” could mean the accounting, finance operations, revenue operations, or payments operations function inside a merchant business that reviews Terminal-related payment activity at least once per week. Relevant merchants may include retail, restaurants, healthcare, events, services, hospitality, and omnichannel businesses that accept in-person payments.

You should choose or clarify one major market, define the population you are estimating, and build a structured sizing approach. The goal is not precision, but a defensible estimate with clear assumptions, logical segmentation, and sensitivity to adoption, merchant eligibility, and weekly usage behavior.

The experience should consider:

- The exact market scope, such as the US, UK, India, or another large payments market

- The unit of estimation: finance teams, not merchants, locations, devices, or employees

- Which merchant segments are likely to use in-person payments and have a finance function

- How many eligible businesses exist in the chosen market and how they break down by size or vertical

- Terminal adoption among eligible businesses, including competition from Square, Adyen, PayPal, Razorpay, Checkout.com, banks, and legacy POS providers

- The frequency threshold for “weekly use” and what finance-team activity qualifies

- Assumptions around multi-location merchants, omnichannel merchants, and small businesses without dedicated finance teams

- Sanity checks, sensitivity ranges, and the biggest drivers of uncertainty

Your goal is to produce a transparent, business-relevant estimate that Stripe could use to reason about the reachable weekly finance-team audience for Terminal in a major market, while clearly explaining assumptions, trade-offs, and confidence ranges.