How I Learned That Some Startup Problems Are Too Big For A Minimum Viable Product

We have been fed the Lean Startup gospel for over a decade. The advice is always the same: build a tiny version of your idea, push it into the wild, and let the market tell you how much it sucks. It is a great framework for photo-sharing apps or project management tools, but for anyone building in the guts of the financial system or high-stakes AI, the MVP is often a death trap.

The Compliance Ceiling

In the fintech world, there is no such thing as being slightly compliant. You either have the licenses, the security protocols, and the trust, or you have nothing. When you are dealing with people's money or sensitive data, you cannot ship a broken product and iterate your way to safety. The stakes are too high, and the regulatory hammer is too heavy.

Daniel Kjellén, who founded Tink and eventually sold it to Visa, is seeing this transition first-hand with his new venture, Freda. He is arguing for a shift in how we think about product development. For repeat founders, the goal isn't just to see if an idea works; it is to build the infrastructure that makes the idea possible in the first place. You cannot do that with a minimum viable product. You need a maximum viable foundation.

Why Lean Thinking Fails Big Problems

The problem with the traditional MVP approach is that it forces you to shrink your vision to fit a launch window. If you are trying to solve a complex, interconnected problem—like how AI manages financial risk—you cannot just solve 10% of it. A 10% solution in a regulated industry is just a 100% liability. If you can't handle the edge cases, you don't have a product; you have a lawsuit waiting to happen.

For builders, this means the 'move fast and break things' era is evolving. We are moving into the 'move fast and build things right' era. The difference is subtle but expensive. It requires more capital upfront, more credibility with partners, and a much longer development cycle before the first customer ever touches the UI.

The AI Accelerator

This is where things get interesting for those of us tracking the intersection of crypto and AI. AI allows us to build complex systems much faster than we could five years ago. It handles the heavy lifting of code generation, data mapping, and even regulatory documentation. But that speed shouldn't be used to launch half-baked apps. It should be used to build the comprehensive systems that were previously impossible for a small team.

If you are a founder, you have to ask yourself: am I building a feature or a system? Features are for MVPs. Systems require a different level of commitment. The advantage that repeat founders have isn't just their bank account; it is the scars they earned from seeing how easily a small product can be crushed by a large problem.

Capital as a Barrier to Entry

We are seeing a trend where the barrier to entry for meaningful startups is rising. You need more than a laptop and a dream now. You need the ability to navigate the legal landscape from day one. This favors founders who can raise significant seed rounds based on their history rather than a prototype. It feels exclusionary, but it is the reality of building in sectors that actually matter to the economy.

If you are building in AI or fintech right now, don't rush to ship a buggy beta just to say you are live. Use the tools available to build a robust, secure, and fully realized version of your core vision. The market is tired of broken promises and 'coming soon' features that never arrive because the founder didn't realize how hard the backend was going to be.

The Founder Perspective

I have seen too many teams burn through their initial hype because their product couldn't handle the reality of the industry they were trying to disrupt. They spent all their energy on the 'minimum' and none on the 'viable.' In 2024, viability is defined by your ability to integrate with legacy systems, protect user privacy, and follow the rules without slowing down.

Building something big requires you to ignore the itch to launch for a while. It requires you to be honest about the complexity of the problem. If your product requires a disclaimer that it might get the math wrong or lose a transaction, it isn't ready. The goal is to build something that doesn't just work, but something that cannot be easily replaced by a competitor who actually did the hard work of building the full stack.

Takeaway for Builders

Stop trying to shortcut the hard stuff. If you are tackling a big problem, embrace the fact that you can't MVP your way through it. Spend the time to build the foundation. Use AI to speed up the boring parts of development so you can focus on the architectural integrity of your system. Credibility is the only currency that matters in the long run, and you earn it by shipping things that are actually finished.

Read the original at Crunchbase News →