Visionary Digital Evolution Strategist
Rooted in Formula 1 excellence, with over 30 years in IT starting as a child in the 1980s, âŠ

Why do you need more crafters in your software organization?
Hey there, digital warriors! âïž
Last week, we sat down with Jeremy Krell to explore what happens when 40% of your investment portfolio is software. The takeaway?
If your CTO doesnât understand software due diligence, youâre already bleeding capital.
But what if 100% of your portfolio is software? đ±
Welcome to the world of Most Capital!
This week, we step into the high-volatility landscape of Web3, AI-generated MVPs, and startups built entirely on code. Kamila Michalkiewicz and ĂgĂșst Berg arenât just investors. Theyâre due diligence tacticians with more than a behavioral lens. People who know that flashy prototypes can hide catastrophic tech debt.
And in todayâs AI-fueled market, the risks arenât just bigger: theyâre explosive đ„. Especially when organizations blindly cross the lines between using AI as a support tool and letting it hijack the build. VibeCode and GenAI agents might impress in demos, but when misused, they turn software organizations into digital minefields đŁ. One wrong push to production, and the entire system can implode:
Quietly, catastrophically, and often without a single person knowing how to fix it.
At first glance, AI feels like a miracle for software organizations: instant code generation, 10x developer productivity, and MVPs launched in days. But beneath that surface lies a dangerous mirage.
Velocity without control. Itâs like driving a race car blindfolded. Fast, impressive, and headed straight for a cliff.
AI tools like Copilot, ChatGPT, Claude, Windsurf, and Cursor can output code faster than any junior or senior developer. But speed isnât wisdom. These tools lack judgment. They lack contextual understanding. They lack secure architecture, design principles, and ethics. Most of all, they lack the creative discipline to align engineering with product vision.
So what do we end up with?
One-click MVPs that demo like magic⊠and implode the moment scale enters the conversation.
This isnât innovation, itâs manufactured fragility. Prototypes are fine, as long as you know theyâre prototypes. But when those prototypes get shipped to production? Thatâs when the blast radius hits the boardroom. đ„
The seduction of AI as a means to âregain controlâ over software teams has deep roots. For decades, weâve cycled through tool-driven illusions: COBOL, UML, No/Low Code. Each promises liberation from developer dependency. But hereâs the truth every board should tattoo on their strategy wall:
You canât replace software engineers.
Finding them is even more complicated than ever. Less than 3% of the global dev community can pass a basic engineering bar. Of those, most are locked into tech giants, paid handsomely, drained daily, and unavailable to you. Hiring true engineers is rarer than winning the Christmas lottery.
So when AI shows up offering speed, volume, and working demos, of course itâs tempting. Especially after decades of developer scarcity and relentless digital disruption.
But be warned: AI isnât fixing the system. Itâs accelerating its dysfunction.
Letâs be blunt:
AI as an assistant? Brilliant. AI as the lead architect or a senior developer? Thatâs when the spiral begins.
Why?
AI builds in bulk. Big chunks of code, big assumptions, and no feedback loop. And that bulk, no matter how fast it ships, shatters the foundations of DevOps, Extreme Programming, and cloud-native discipline.
Hereâs what collapses:
The result?
A shiny AI-built product that looks like a unicorn⊠but snaps like glass the moment 10 users stress it.
And the hype machine? Still humming. Most of todayâs AI success stories? They come from AI vendors. Meanwhile, researchers and Nobel prize winners are sounding alarms; economic, ethical, and social:
Weâre facing a brutal trade-off:
Speed now⊠or stupidity later?
So what do we do?
Do we rock the AI boat, and risk losing the race? Or do we continue to pretend itâs all under control?
Contrary to the hype, AI isnât lowering the startup failure rate. Itâs accelerating it.
Recent data shows that:
And hereâs the kicker:
The problem isnât the AI. Itâs the absence of SW engineering and craftsmanship.
Most of these codebases rot before revenue even arrives. Why? Because AI-generated code, especially under the hood of tokenized heuristics, prioritizes output, not outcomes. Itâs built for speed, not survival.
The DRY (Donât Repeat Yourself) principle? Obliterated. Duplication skyrockets. Refactoring is ignored and Tech Debt is growing at hyperspeed. Worse, tests are either missing or misaligned testing implementation over code behaviors, turning every release into a game of roulette. Debugging becomes a recursive nightmare. Costs surge. And suddenly, youâre not building software: youâre feeding a costly Frankenstein.
But even when the code holds, something deeper collapses: product-market fit. That slick AI-crafted MVP may look investor-ready, but without user personas, real product discovery, and hard-earned learning cycles, itâs just a hollow shell. Beautiful in the demo. Broken in production. And deadly, once daily costs outrun the customer base.
So how was it possible that startups like Uber and Airbnb became so disruptive? They required over $1 billion in debt just to survive long enough to scale. đ±
Now imagine a startup built on fragile AI-generated code instead of solid engineering. Could it even survive Series A?
Thatâs the real question every investor, founder, and board member should be asking today:
Is your codebase quietly sabotaging your runway?
This is why IT due diligence is no longer optional, especially in an AI-driven world. Itâs not enough to skim a codebase or skim through a CTOâs rĂ©sumĂ©. You need to observe the social fabric behind the software: how teams think, collaborate, and evolve code under pressure. Only then can you spot the difference between a resilient culture of engineering mastery⊠or a startup propped up by hype, duplication, and a demo built by machines.
Because when everything looks like itâs working, but nothing is truly designed to last, what exactly are you investing in?
Most Capital isnât investing in features or roadmaps. They invest in founder behavior.
Before even hearing a pitch, they ask 40 behavioral and technical questions. They bring in real software auditors, not tool-pushers or checkbox consultants. They scrutinize the codebase, governance model, team resilience, even tokenomics, and long-term product adaptability.
What are they looking for?
Founders with unicorn DNA: clarity, commitment, integrity, and a willingness to grow and evolve in the face of pressure.
And when it comes to building the company? They know one truth:
âIf you hire vibe-coders, youâll get vibe-products solid as a house of cards.â
Thatâs why IT due diligence isnât just about architecture reviews anymore. Itâs about understanding whoâs writing the code, how they work and communicate under pressure conditions, and whether their practices can scale. Youâre not just betting on tech:
Youâre betting on good craft paired with good engineering.
And hereâs the final super power cape layer:
To truly de-risk in this AI-era, investors need a tech advisor embedded with deep roots in software development, XP-style Agile, and modern DevOps. Someone whoâs spent the last three years in the trenches, where marketing AI promises failed, and real engineering had to find a way to make it work.
Thatâs what separates sustainable scale from superficial sizzle.
Thatâs why our podcast this week isnât just another startup story. Itâs a blueprint.
Itâs time to stop pretending software is a commodity. It isnât.
Software is a living system. Craftsmanship is its immune system. And AI? Itâs only healthy when surrounded by mastery.
So ask yourself: Is your organization led by a CFO whoâs capped software development under a strict budget? Have you cut training in favor of GenAI shortcuts? If either answer is yes, my digital warrior, youâre not just flirting with risk, youâre inviting collapse.
Whether you see it now or not, that pressure will build until someone (maybe you) is forced to pay the price.
Your next move? Onboard a NED or a fractional CTO with real battle scars. Someone who understands software craftsmanship, XP (not the theater Agile version), DevOps, and what it really takes to evolve a codebase and a culture under AI-stress.
Itâs time to stop hiding behind decks and start asking for help. Because only when we make engineering mastery visible, on the board, in the strategy room, and in our investor updates, can we actually course correct.
If you donât⊠the ROI of that brilliant AI-driven idea? It wonât just be zero.
Itâll be the reason you were replaced.
To stay in the loop with all our updates, be sure to subscribe to our newsletter đ© and podcast channels đ§:
đ° LinkedIn
đ„ YouTube
đ» Spotify
đ» Apple Podcast
Visionary Digital Evolution Strategist
Rooted in Formula 1 excellence, with over 30 years in IT starting as a child in the 1980s, âŠ