In December 2020, I sat on a rescue flight back to Vietnam. In my pocket was a purple student ID card from my MBA at Leeds Beckett University. In my head was a 50-page business plan.
I thought I was ready to be a CEO. I thought I had the "playbook" for building a scalable fashion-tech startup.
Reality had other plans.
Over the next 3 years, I burned through $160,000 (~4 billion VND) trying to build a "Phygital" (Physical + Digital) tailoring platform. I learned that while an MBA gives you a map, it doesn't teach you how to survive in the jungle.
Here is the honest breakdown of what academic theory got right, and where it failed miserably against the chaos of a real startup.
Indie hackers often dismiss degrees as "useless paper." I disagree. Without the structural thinking I learned at Leeds, my startup would have died in logistics hell.
In class, Professor Alfred taught me that:
"Supply Chain isn't just logistics; it's the business model."
I nodded politely then. I pray to that sentence now.
My business involves moving data (3D scans) from the US/UK to Vietnam, and moving physical products (Bespoke Suits) back to the customers.
This sounds like corporate CSR fluff: People, Planet, Profit.
But for a bootstrapped startup, "Sustainability" translates to "Efficiency."
This is where the $160k tuition fee of "The University of Life" kicked in.
[INSERT IMAGE 2 HERE: Upload file 3.png (Ảnh cái lồng sắt & $160,000)]
I spent months planning the perfect customer journey.
Day 1 Launch: Customers didn't care about my journey map. They cared that the 3D scanning app crashed because their room was too dark.
The Fix: I threw away the 50-page plan and adopted a "War Room" mentality. We fixed bugs hourly. We pivoted the tech from "User-dependent" to "Auto-correction."
Takeaway: Planning gives you false confidence. Iteration gives you truth.
We built a scanning tool that required users to hold their phone at a 90-degree angle. Simple, right?
Wrong. Users held it at 85 degrees. Or 95 degrees.
The Result: Suits came out wrong.
The Pivot: Instead of "educating" the user (which is impossible), we built algorithms to detect the tilt and correct the data mathematically.
Takeaway: Never design for the "Ideal User." Design for the tired user who just wants to go to bed.
So, was the MBA worth it? Yes.
But only because I combined it with the "Indie Hacker" mindset.
I call this "Strategic Resilience":
If I only had the MBA, I would have quit when the tech failed.
If I only had the Hacker mindset, I wouldn't have built a system capable of global logistics.
Don't throw away your degree, but don't hide behind it either. Use your education as a Toolbox, not a Shield. The
The contrast between what looks sensible in a framework and what actually works under real constraints is an important lesson for founders.
Hardware makes those constraints especially visible because supply chains, manufacturing, cash flow, lead times, and physical failures can all interact in ways that are difficult to model in advance.
I think there is a broader lesson here: frameworks are useful maps, but the real system always contains variables that the map leaves out. The ability to observe those signals and adapt may matter more than following a framework perfectly.
Which assumption from business school changed the most once you encountered the realities of building hardware?
Local Python scripts have a structural advantage in the current market: they're immune to the SaaS subscription backlash. No recurring costs, no vendor risk, no data concerns.
The positioning challenge is that 'script' sounds less polished than 'platform.' Worth double-down on the positioning: 'the tool you own, not the subscription you rent.'