From idea to MVP: my scoping checklist

Most inbound requests start with a sentence: “I have an idea for an app.” Before writing code, I try to de-risk three things: who it is for, what the first version must do, and how it fits with existing systems.

1) Clarify the problem and users

I ask who the app serves, what problem it solves for them, and what already exists. This flushes out constraints (devices, roles, privacy) early.

2) Map journeys and trim scope

I sketch the core user journeys, then cut anything that is not needed in the first 4-6 weeks. Must-haves go in a "Phase 1" lane; nice-to-haves become a backlog, not a promise.

3) Choose a stack that fits the context

I pick tech based on team skills, hosting preferences, and integration points. Often Next.js + Tailwind + shadcn/ui for speed, with Contentlayer/MDX for content. For more operational apps, I add a small API and background worker.

4) Write a tiny delivery plan

A one-pager with scope, risks, and acceptance criteria keeps everyone honest. It also makes pricing and timelines sane.

5) Build and validate in slices

I build the smallest slice that proves value, ship it to real users, and measure whether it solves the stated problem. Only then do we extend into Phase 2.

If you want to see this in practice, check the Dialogue Time case study. Exactly this flow, just in a consulting setting.