Scoping an MVP your first funding round can actually support

A founder came to us with a 40-item feature list for a pre-seed MVP: multi-tenant workspaces, a permissions matrix, five integrations, a mobile app to match the web app. Twelve weeks of runway. We cut it to one screen and one transaction. That's the actual job when we scope an MVP: not adding structure, but taking it away. The list almost never survives contact with a 12-week clock, and founders rarely want to be the one holding the knife. What we look for first is the single core value transaction — the one thing a user does that proves the business works. For an affiliate platform, that's tracking a click all the way to a paid-out dollar, not a polished dashboard around it. Everything that doesn't directly serve that transaction gets deferred, not deleted — a backlog, not a graveyard. Security and auth are the one place we don't cut corners, even under a tight clock; everything downstream of "is this account real" can stay deliberately plain. Settings pages, admin tooling, onboarding polish — all of it waits. The founder who cut the list shipped in nine weeks with real usage data instead of a deck full of hypotheticals. That's what a seed-stage technical diligence call actually wants to see.