Mercury · Strategy · Senior · 45 to 60 minutes

Set Mercury's pre-launch product bar

Mercury is a fintech that provides digital banking services for startups and small businesses through partner banks. Answer this product management case and get it graded line by line against a weighted rubric.

Product strategy
Prioritization
Regulatory thinking
Risk management
Metrics

The situation

The CEO has asked you, the senior PM helping shape Mercury's first product, for a launch strategy recommendation. The team believes startup banking is badly underserved, but it is entering a regulated category where trust, compliance, and money movement reliability matter more than in a typical SaaS launch. Early research suggests founders want a business account that can fully replace their existing bank, yet investors are pushing for faster, narrower options, such as a lighter analytics layer on top of existing bank accounts or a reduced first release that skips some hard use cases. At the same time, the first bank partner is slower than expected on capabilities Mercury needs, raising the possibility of delay, rework, or changing partners. You need to decide what product bar Mercury must hit before launch, what should wait, and how to handle the bank partner dependency. The decision matters now because the company can either spend more time doing hard compliance and core banking work up front, or launch sooner with a thinner offer and learn in market. Your recommendation should balance speed, credibility, scope, and the realities of building in fintech.

What to produce

Write a 1 to 2 page strategy memo.

Your answer must

State a clear recommendation for Mercury's launch thesis, full primary bank account versus a narrower wedge, and explain why.
Define the minimum launch bar, including what capabilities must be in v1 and what should be deferred.
Propose a sequencing plan across onboarding and compliance, account access, and core money movement flows.
Address the bank partner dependency, including decision triggers for staying the course, escalating, or switching partners.
Define early success metrics and product-market-fit signals that fit this business.
Identify the biggest trust, regulatory, and execution risks, with mitigations.

Constraints

Mercury must launch as a fully digital experience, with no branch or in-person fallback.
The product is being built on a sponsor bank model, not a bank charter.
The founding team is small, so the first release cannot support a wide surface area beyond core banking needs.
Customers may move operating funds into Mercury immediately, so onboarding and money movement failures are high stakes.

Format

Use headings: Recommendation, Launch Bar, Sequencing, Partner Plan, Metrics, Risks.

How Mercury actually played it

Serial founder explains why Mercury invested in perfecting core banking experiences and doing hard compliance work early, even when it meant duplicate work. Illustrates quality as a strategic choice in fintech.

Do the hardest work first so later features stand on it
Perfect core flows before widening scope

Built from Mercury's Path to Product-Market Fit: Do the Hard Part First by First Round Review.