What to build first: how to find your real MVP

Almost every software idea starts the same way: a long list of everything it could do. That list feels like progress, but it's usually the thing that stalls a project before it starts. The list is too big to price, too big to build, and too big to explain.

The fix isn't to cut features you love. It's to find the one loop your product has to get right, and build only what that loop needs.

Find the core loop

Every product has a core loop, the smallest cycle of actions that delivers the value you promise. For a marketplace, it's usually: someone posts a need, someone else answers it, and the two connect. For a booking app, it's: see what's free, pick a time, confirm it.

Write your loop as one sentence. If you can't, that's a sign the idea is still fuzzy, and worth a few more minutes of thinking before anyone writes code.

A good first version does one loop completely, not five loops halfway.

Everything else is a phase, not a cut

The features you set aside aren't gone. They're Phase 2 and Phase 3. Saying "payments come in Phase 2" is completely different from saying "no payments." It keeps the vision intact while making the first build small enough to actually finish.

This is exactly how a good build plan is structured: a lean Phase 1 that ships, then later phases that add trust, polish, and scale. When you can see your idea laid out that way, it stops feeling overwhelming and starts feeling buildable.

A quick test

For each feature, ask: if this were missing on day one, would the core loop still work? If yes, it's a later phase. If no, it's Phase 1. That single question will shrink most feature lists by half, and make the other half far easier to price and build.

Scoping well isn't about doing less. It's about doing the right less, first.