Define the North Star metric for Atlas serving SaaS companies
- Metrics
- Stripe
- Hard
- 15 min
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 Atlas helps founders form and set up companies, and in this case the focus is SaaS businesses that need to move from incorporation to a reliable, compliant, revenue-generating operating setup. In this interview, you are asked to define a North Star metric for Atlas specifically for SaaS companies, not for Stripe overall or for all Atlas users.
The problem requires identifying the core value Atlas should create for SaaS founders and how that value should be measured over time. A strong response should distinguish between company formation activity, successful business readiness, and durable merchant growth, while accounting for Stripe’s broader role in payments, billing, fraud prevention, financial infrastructure, and global compliance.
Because this is a metrics question, the emphasis is on building a precise, decision-useful metric framework. You should clarify the user journey, define the population and denominator, specify what events must be instrumented, and explain how the metric would guide product and business decisions without being easily gamed.
The metric definition should consider:
- Which SaaS companies are in scope, including stage, geography, company size, and whether they are new founders or existing businesses.
- The exact denominator: all Atlas sign-ups, incorporated companies, eligible SaaS companies, activated Stripe merchants, or another clearly defined cohort.
- What “success” means for a SaaS company using Atlas across formation, compliance setup, payments readiness, billing readiness, and early monetization.
- How to distinguish leading indicators from the North Star metric, and how supporting metrics would diagnose movement in the North Star.
- Instrumentation needed across Atlas onboarding, incorporation completion, Stripe account setup, billing/payments activation, subscription activity, and retention.
- Cohort cuts such as company geography, founder type, acquisition channel, time since incorporation, SaaS business model, and compliance complexity.
- Guardrails around fraud, compliance quality, failed incorporations, poor founder experience, support burden, and low-quality or inactive businesses.
- How the metric would help Stripe make roadmap trade-offs versus adjacent offerings and competitors in payments and financial infrastructure.
The goal is to define one clear North Star metric and explain why it best represents durable value creation for SaaS companies using Atlas, while also showing how Stripe could measure, interpret, and act on it responsibly.
What this question tests
- Metric Definition
- Instrumentation
- Counter-metrics
- Decision Quality
Practise this question under interview conditions. Answer it out loud against a timer with an AI interviewer that asks follow-ups, then review the scored report.
Related Metrics questions
- How would you detect unhealthy growth in BillingStripe · Metrics · Easy
- Design an experiment to measure whether Terminal improved outcomes for developersStripe · Metrics · Easy
- Design an experiment to measure whether Terminal improved outcomes for developersStripe · Metrics · Hard
- Create a metric dashboard for the executive team reviewing PaymentsStripe · Metrics · Hard
- What metrics would you use to evaluate a new Radar feature for enterprise merchantsStripe · Metrics · Hard
- How would you detect unhealthy growth in TreasuryStripe · Metrics · Hard
All Metrics questions · Product manager interview questions by skill area