---
title: Scoping the first version — solve one problem
slug: app-mvp-single-problem-scope
summary: Why first-time founders should ship an app that solves one problem (not a multi-tool), and how Steve P. Young pairs a one-feature build with one keyword and a hard paywall to test demand.
domain: mobile-apps
tags: [product-strategy, mvp, scope, validation, common-mistakes]
related: [app-idea-tentacle-strategy, app-growth-stages-organic-to-paid, app-development-cost-and-tooling-2026, app-design-for-conversion-and-ux, hard-vs-soft-paywalls]
sources: [yt:SHctL0V73BE, yt:cq6KhOH6GAw]
updated: 2026-10-23
---

# Scoping the first version — solve one problem

## TL;DR
- Mistake #1 Jaime (B7 Dev) sees in first-time founders: building a super-complex **multi-tool** with "whistles and bells".[^1]
- Build something that fixes **one common problem**; add features only after revenue and feedback.[^1]
- Every extra feature is dev time, and an early app is a **race of budget against the clock**.[^2][^1]
- Facebook/Instagram are the result of years of stacking features — their v1 was stripped down; funding news is the tip of an iceberg.[^3]
- Steve's version: **one feature → one searched keyword → aggressive hard paywall** to test willingness to pay, then expand.[^4]
- While building, "good enough is good enough" — reaching #1 for the keyword matters more than polish.[^5]

## Details
**The founder trap.** Founders point to Instagram's layered features; [[people/jaime-b7-dev]] answers that those came from years of iteration after a minimal first release.[^3] AI ("agentic") development shortens timelines and lets companies get funded earlier, but the conceptual discipline is the same: focus limited energy on solving one simple thing well.[^6]

**Why it pairs with search-led ideas.** A single-problem app maps cleanly onto one keyword cluster (e.g. "brown noise"), which is what lets it rank #1 against broad apps that cover many tentacles ([[app-idea-tentacle-strategy]]).[^4][^5]

**Practical scope test (synthesis of both speakers):**
- Can you describe the problem in the words users search? If not, it's probably several problems.
- Does v1 need anything beyond the core job + paywall? Defer it until the app has downloads and revenue ([[app-growth-stages-organic-to-paid]]).[^4][^7]

## Disagreements / caveats
- Steve still insists the **paywall** and conversion-aware design are in v1 — "minimal" doesn't mean unmonetised ([[app-design-for-conversion-and-ux]]).[^4]

## See also
- [[app-development-cost-and-tooling-2026]] — what a v1 costs in 2026
- [[app-growth-stages-organic-to-paid]]

[^1]: yt:SHctL0V73BE @ 01:39 — Jaime (B7 Dev)
[^2]: yt:SHctL0V73BE @ 00:51 — Jaime (B7 Dev)
[^3]: yt:SHctL0V73BE @ 02:39 — Jaime (B7 Dev)
[^4]: yt:SHctL0V73BE @ 14:24 — Steve P. Young
[^5]: yt:cq6KhOH6GAw @ 15:54 — Steve P. Young
[^6]: yt:SHctL0V73BE @ 03:49 — Jaime (B7 Dev)
[^7]: yt:cq6KhOH6GAw @ 15:54 — Steve P. Young