Field Notes

What an MVP really is, and how it earns pre-seed funding.

A field guide for founders working in the gap between an idea worth backing and a product worth shipping. Written from the inside of dozens of two-week MVP sprints.

CQ Ventures · Your MVP launch partner

Definitions

What an MVP actually is (and what it is not).

An MVP is the smallest real thing that proves the core promise of your product to a real user. It is not a half-built version of the whole thing, and it is not a clickable mockup that falls apart the moment a stranger touches it. The job of an MVP is to make exactly one thing undeniable.

If the promise is a faster checkout, the MVP is a working checkout, used by real people, end to end. Everything that is not that checkout is scaffolding, and scaffolding is the first thing to cut. The point of the work is the proof, not the surface area.

Why it matters

Why a working product beats a deck.

Investors and early customers respond differently to something they can use versus something described to them. A deck asks them to imagine. A working product hands them the experience and reads their face. One of those is a sales meeting. The other is evidence.

Even a small, sharply scoped product builds a kind of momentum a slide deck cannot. It accumulates feedback, signups, sessions, and stories. By the time you are in the funding conversation, the conversation has already happened in the product.

Signals

What pre-seed investors are actually looking for.

Three things keep coming up. Evidence of momentum, even if it is small and recent. A founder who can clearly ship, who has put a thing into the world and learned from it. A sharp wedge, a single insight or unfair advantage that explains why this team, this product, now.

Demand signals matter more than polish. A waitlist of fifty real strangers, a handful of paying users, a conversation rate that bends in your favour. None of these are huge, all of them are real. That is the texture a pre-seed cheque is buying into.

Scope

How to scope a two-week sprint.

Ruthless prioritisation is the entire job. Two weeks means one core loop, built well, and almost nothing else. Auth can be magic links. Settings can wait. Admin can be a database row you change by hand. If a feature is not part of the proof, it is not in the sprint.

The sprint succeeds when the single loop is undeniable. Cold start to first wow in under a minute. One person can use it without you sitting next to them. Everything else, even things that feel essential, gets parked until there is something real to defend.

Outcome

What you walk away with.

You leave the sprint with a real product. Hosted, polished, shareable by a link. Ready to put in front of early customers, ready to bring into a funding conversation, ready to defend on its own. Not a prototype waiting to be rebuilt. A first version that earns the right to be the second.

Ready to give your idea shape?