Retention for subscription businesses declined in Treasury. What is your analysis plan

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 Treasury supports businesses that want to embed financial accounts, money movement, and cash-management capabilities into their own products. In this scenario, retention among subscription businesses using Treasury has declined, and you are asked to lay out an analysis plan to understand what changed, why it changed, and what actions the product and business teams should consider next.

Assume the affected users are subscription-oriented merchants or platforms that rely on recurring customer payments, predictable cash flow, and integrations across Stripe products such as Billing, Payments, and Treasury. A retention decline could reflect product friction, financial reliability concerns, pricing or compliance changes, competitive switching, customer health issues, or measurement artifacts, so the problem requires structured root-cause analysis rather than jumping to a fix.

Your task is to define how you would investigate the anomaly, segment the business, validate the data, generate hypotheses, and identify the evidence needed to prioritize next steps. Focus on how you would reason through the issue in a Stripe-like environment where trust, uptime, compliance, developer experience, and merchant growth are critical.

The experience should consider:

- How you would define “retention” for Treasury subscription businesses, including the denominator, time window, and whether retention means active usage, balance held, account status, transaction volume, or continued product integration.

- How you would confirm the decline is real by checking instrumentation, cohort definitions, reporting changes, seasonality, customer mix shifts, and data pipeline issues.

- Which segments you would examine, such as business size, geography, industry, tenure, integration type, Treasury feature usage, Billing or Payments attachment, risk tier, and revenue contribution.

- What product, operational, financial, compliance, or support-related hypotheses could explain the drop, including onboarding friction, failed money movement, account freezes, pricing changes, payout delays, KYC issues, or reduced perceived value.

- How you would use quantitative signals and qualitative inputs, including usage funnels, transaction failures, support tickets, customer interviews, sales/account feedback, churn reasons, and competitor mentions.

- How you would distinguish between customer churn, lower activity, temporary dormancy, migration to another Stripe product, and true loss to a competitor.

- What mitigations, customer communications, and escalation paths you would consider while the investigation is ongoing, especially for high-value or high-risk accounts.

- How you would prevent recurrence through monitoring, alerting, ownership, instrumentation improvements, and clearer health metrics for Treasury customers.

The goal is to present a rigorous RCA plan that narrows a broad retention decline into testable causes, identifies the highest-impact customer segments, and produces decision-useful evidence for product, risk, engineering, support, and go-to-market teams without prematurely prescribing a solution.