Company Context

You’re the PM for LedgerLite, a Series B fintech startup (raised $85M) building financial tools for small businesses. LedgerLite has 2.4M monthly active users on its free expense-tracking app and monetizes via a $12/month “Pro” subscription (8% of MAUs). The company’s north-star goal this year is to expand into accounts receivable to increase paid conversion and reduce churn.

LedgerLite is competing with QuickBooks Online, FreshBooks, and Wave. QuickBooks is the default for many SMBs but is perceived as complex; Wave is free but has weaker support and fewer automation features. LedgerLite’s brand is “simple and fast.”

User / Market Scenario

LedgerLite’s core audience is US-based SMBs with 1–20 employees. Current research suggests a large portion of LedgerLite users still invoice clients using Word/PDF templates or spreadsheets.

Key Personas (from research)

Competitive notes

• FreshBooks: strong invoicing + reminders + online payments; higher price ($19+/mo).
• QuickBooks: comprehensive accounting; steep learning curve.
• Wave: free invoicing; monetizes payments; limited automation.

Problem / Opportunity

LedgerLite’s data science team analyzed 120k users who connected a business bank account:

• 41% have incoming payments that appear to be client invoices (memo patterns), but only 7% use any invoicing tool integrated with their workflow.
• Users who manually tag incoming payments as “invoice paid” have 15% higher 90-day retention than similar users.

A beta landing page offering “Invoicing is coming” collected 18,000 sign-ups in 3 weeks. In follow-up interviews (n=24), users consistently said the “must-have” is: create an invoice fast, send it, and get paid without awkward follow-ups.

Leadership asks you to launch an Invoicing MVP in 10 weeks that can validate:

1. users will adopt LedgerLite for invoicing (not just try it once), and
2. it can drive incremental revenue (subscription upgrade and/or payment processing).

Your Task (what you must deliver in the interview)

1. Define the MVP: What is the minimum set of features LedgerLite must ship in 10 weeks to credibly solve the core job and compete?
2. Explain your prioritization approach: Walk through how you decide what’s in vs out (e.g., Jobs-to-be-Done, Kano, RICE), including key assumptions.
3. Specify the MVP user experience: Outline the end-to-end flow (create → send → pay → reconcile) and where you’ll cut scope.
4. Define success metrics and guardrails: What metrics prove the MVP works within 30–60 days post-launch?
5. Identify risks and mitigations: Adoption, trust, compliance, and operational risks—what could sink the MVP?

Constraints (non-negotiable)

• Timeline: 10 weeks to GA (general availability) for US users.
• Team: 6 engineers (4 backend, 2 mobile), 1 designer, 1 data analyst; no dedicated QA team.
• Payments: Must use Stripe for card/ACH; LedgerLite does not have an in-house payments stack.
• Compliance: Must meet basic requirements for handling PII; invoices may include addresses and tax IDs. No international launch.
• Tech limitations: No existing template builder; PDF generation exists but is brittle and sometimes fails at high load.
• Business requirement: The MVP must include at least one monetization lever (subscription or payments revenue) without materially increasing churn of existing Pro users.

What we’re looking for

We’re evaluating how you translate ambiguous user needs into a tight MVP scope, make trade-offs under constraints, and define measurable criteria for “ship / iterate / kill.”