Most supply chain training is a snooze-fest. We changed that. β‘
Introducing https://t.co/jQimGFw0Ch: An interactive simulation where your decisions actually matter.
No boring slides. No hypothetical formulas. Just pure, high-stakes decision-making.
It's cheaper than one bad purchase order going sideways.
Try it now! π
I recently put together a short book called "Cracking the O-Levels Code," aimed at helping students navigate their Cambridge exams more effectively.
You can find the digital copy here: https://t.co/qRA4PX3UkG
Major changes have taken place across https://t.co/WWB54fRGI0 .
The whole in game UI/UX has been upgraded and the game mechanics now work a lot better than before.
@Timseo_ How do you manage to sell leads e.g we have a financial calculator, but so far we've been unable to find ways to monetize it let alone sell leads?
Spent a good chunk of the last few months on things nobody will ever list as a "feature": the turn summary redesigned so the income-statement rows read at a glance, the procurement screen rebuilt, the in-game dashboard reworked, and custom icons replacing emoji across the game.
I'm looking for ways to monetize the SWP calculator page on my website that's receiving around 15-20 clicks daily (Mostly from Pakistan since the website focuses on the Pakistani financial market.) But I'm open to hosting products belonging to different niches than just finance.
The inventory system in Supply Chain Disaster uses FIFO aging.
Units don't just sit forever. They accrue holding costs over time. Old stock is quietly eating your margin every quarter.
I built the same FIFO logic for Pakfolio β my personal finance tracking app β but for tax lot accounting instead of physical goods.
When you understand accounting, supply chain makes more sense.
When you understand supply chain, accounting makes more sense.
They're the same underlying problem: time + value + the cost of holding.
This started as a "let me vibe-code a supply chain simulator" project.
It became:
β 8 narrative chapters with escalating crises
β 3 industry tracks (Electronics, FMCG, Pharmaceuticals)
β 12 event types
β A Bullwhip Effect algorithm
β Real-time analytics
β An Android mobile app (soon to be)
β A full payment system
β Something I'm genuinely proud of
This started as an experiment.
It's now a full-blown crisis.
See you tomorrow.
Me: *finds something moderately interesting*
Shows little to no interest
Also me: *Finds Mr Akash Gupta's post going deep on it"
* Spends the next 1-2 minutes reading that post that explains the original post just because Mr Gupta wrote it.*
Genuinely interesting.
The data on founder-led sales is hard to ignore:
Companies where the founder personally closed the first 50 customers grow 2.4x faster in year 2β3.
(First Round Capital, portfolio study)
Why?
Because you learn things no sales deck can teach:
β’ The exact words customers use to describe their pain
β’ The objection that kills 70% of deals
β’ The trigger that makes someone buy TODAY vs. "maybe next quarter"
Don't hire a sales team to avoid selling.
Sell yourself until it physically doesn't scale.
Then hire someone who can replicate what YOU learned.
The year is 1950. Your doctor lights a cigarette and tells you smoking is fine. He read it in a study. He is telling the truth about having read it. He does not know, or is not saying, that the study was funded by the tobacco industry.
The year is 1958. Your doctor tells you to eat less fat. The evidence is contested. The contestation is not in the public messaging. The food industry has been helpful in clarifying which findings deserve attention. Some researchers who published contradictory data have been quietly defunded. Ancel Keys is on the cover of Time magazine.
The year is 1962. Your doctor prescribes thalidomide to your pregnant wife for morning sickness. It has been approved. The FDA gave it the green light in Europe. Twelve thousand children will be born with severe limb malformations before anyone in an official capacity acknowledges the problem. The families are told the drug was safe. The drug was approved. Both of these things remain true.
The year is 1972. Your doctor prescribes Valium. Britain is in the grip of a benzodiazepine wave that will last two decades. The dependency risk is known internally. It is not shared. Your doctor is not lying to you. He was not told either.
The year is 1999. Your doctor prescribes Vioxx for your arthritis. It is newer than ibuprofen, well-tolerated, and Merck has a study showing it works. Merck also has internal data suggesting it roughly doubles the risk of heart attack. This data will not reach your doctor for four more years. Fifty thousand people are estimated to have died in the interim. Merck eventually settles for 4.85 billion dollars. No criminal charges are brought.
The year is 2002. Your doctor prescribes OxyContin. Purdue Pharma trained its sales representatives to tell doctors the addiction risk was less than one percent. That figure came from a letter, not a study. The letter was about patients with terminal cancer on short-term doses in hospital settings. Your doctor is a GP with a patient who has a bad back. Nobody draws a distinction. Nobody is required to.
The year is 2008. Your doctor checks your cholesterol. Your LDL is elevated. You are prescribed a statin. Nobody mentions that the number needed to treat for primary prevention is approximately 250. Nobody mentions that the muscle deterioration you'll notice over the next two years is listed as a rare side effect rather than a documented pattern affecting a meaningful percentage of patients. The trial that informed the prescription was funded by the manufacturer.
Now it is today.
Your doctor has new guidelines. New studies. New consensus.
He is confident.
He has always been confident.
The confidence has never been the problem.
The confidence is, in fact, precisely the problem.
I've launched apps. Software products. Self projects.
A game is different.
A game asks something from the player. It asks them to care. To feel the loss. To want to replay and figure out what went wrong.
I don't know yet if Supply Chain Disaster does that for everyone who plays it.
I know it does it for me.
Tomorrow we find out.
Thinking seriously about a "Student Mode" for Supply Chain Disaster.
Stripped-back UI. Concept explanations alongside each decision. Designed for MBA classrooms, supply chain certification courses, and self-directed learners.
If you're a supply chain professor, trainer, corporate L&D manager, or educational content creator β I want to talk to you.
Building something that belongs in classrooms, not just on phones.
DM open.
2 AM.
The full game loop just ran clean for the first time. All 8 chapters. No state corruption. Correct transitions. Analytics rendering.
I've built apps before. Never built a game.
There's something different about a game loop closing correctly for the first time. It feels like a system coming alive rather than just a product going live.
Shipping soon.
Dashboard evolution. π
Before: Wireframe-level mess. Every metric competing for attention. Dense. Anxious. Wrong.
After: Clean grid. Dark palette. Each metric earns its space. Silence where there's nothing to say.
The design principle I borrowed from Regent Scents: restraint is luxury. Show less. Make what you show matter.
7 cognitive biases silently destroying your decision-making as a founder
Your brain was not built for startup decisions. Here are the biases costing founders the most β and how to neutralize them.
1. Survivorship bias
You study successful founders and copy their habits. But you never study the 95% who did the same things and failed. Success stories are not a representative sample.
β 95% of startups fail β you mostly only hear from the 5%
2. Confirmation bias
You seek data that validates your existing roadmap. Customer interviews that challenge your thesis feel like outliers. They are usually signals.
3. Sunk cost fallacy
You keep a feature, hire, or strategy alive because of how much you have invested in it β not because it is working. The time already spent is gone regardless of your next decision.
β 42% of founders cite 'persisting too long' as their biggest mistake (CB Insights)
4. Planning fallacy
Every founder underestimates timelines. Projects take 2β3x longer than planned. Buffer accordingly β then add more buffer.
5. Optimism bias
Founders overestimate the probability of good outcomes and underestimate risks. Useful for resilience, dangerous for financial planning.
β Entrepreneurs overestimate success odds by 2x on average (Cooper et al.)
6. Recency bias
Last week's metrics feel more significant than the 6-month trend. Do not make hiring or pivot decisions based on one good or bad week.
7. Availability heuristic
You overweight the advice of the last founder you spoke to. Their context is not your context. Sample widely before drawing conclusions.
Save this. Re-read it before your next major decision.
Full tech stack for Supply Chain Disaster:
β Vanilla JS + Vite β fast, no framework overhead, instant HMR
β Chart.js β real-time Bullwhip Effect and cash flow analytics
β Pure CSS β custom design system, no Tailwind, no component libraries
β if and when needed: Capacitor β web β Android native build
β Lemon Squeezy β one-time payment processing
β Vercel β hosting + serverless API
No React. No Next.js. Just clean, modular JS that ships fast.
The constraint made the code better.