The COVID SGD 500K Story: Crisis Management at Scale

I remember the family meeting clearly.

It was early March 2020. Singapore had just begun tightening movement restrictions. The room felt heavy in a way that had nothing to do with the weather. My family had been running a distribution business for years-good relationships with suppliers, a stable customer base, a business built on handshakes and reliability.

Within a week, it was all in question.

Suppliers in the region had frozen shipments. Retail foot traffic-our primary distribution channel-had collapsed. We were watching revenue drop 60-70% month-over-month. The people who depended on this business were sitting in that room, and nobody had a clear answer.

I didn't either.

But I knew where to start.

The Crisis: What Was Actually Breaking

The first thing I did was resist the urge to panic and instead do what I'd been doing since I was 18: map the system that was failing.

Most crises aren't one catastrophic event. They're a chain of connected failures exposing vulnerabilities that were always there. Our situation had three distinct fracture points:

Supply chain: Our main suppliers were based in regions hit hardest by early COVID disruptions. Shipments were delayed indefinitely. We didn't know when-or whether-they'd resume.

Distribution channel: Our business was built on physical retail. Overnight, that disappeared. We had inventory and relationships, but no way to reach customers.

Cash flow: With revenue dropping and overhead continuing, the timeline was finite. We couldn't wait six months for things to normalize. We needed to move in weeks.

I made a list of what we still had: existing supplier relationships (strained, but not gone), inventory, a brand that customers trusted, and something most of our competitors didn't-eight years of my own e-commerce experience and a decade of automation skills.

That last part mattered more than I expected.

Assessment Under Pressure

One thing early financial independence taught me: when you've operated without a safety net before, crises feel more like problems than catastrophes. I didn't need this family-run electronics trading enterprise for my own survival. That removed a layer of panic that might otherwise have clouded the analysis.

I spent two days doing nothing but mapping flows. What comes in, what goes out, where it breaks, where it could be rebuilt. I wasn't trying to be comprehensive-I was looking for leverage points. Places where a relatively small intervention could change the trajectory.

Three emerged quickly:

We needed a new distribution channel, fast. E-commerce was the obvious answer-I'd built and run my own since 2018.
We needed alternative suppliers. Single-source dependency had become catastrophic. Diversification was urgent, not optional.
We needed to automate the operations. If we were rebuilding the distribution model under pressure, we needed it to run with minimal manual overhead from day one. We couldn't afford to staff up and train people mid-crisis.

The game plan took shape: three parallel workstreams, executed simultaneously. Not sequentially-we didn't have the time for sequential.

The Three-Pronged Pivot

Workstream A: E-Commerce Infrastructure (Weeks 1–2)

This was the fastest workstream because I'd done it before.

I used the same platform and workflows I'd built for my own electronics business. The goal wasn't to build something perfect-it was to build something functional in 72 hours that we could refine while running.

Week 1:

Online store live with core product catalogue
Payment gateway integrated
Connected to logistics providers for contactless delivery
Automated order confirmation and tracking notifications built

By day four, we were taking orders.

That sounds anticlimactic. It wasn't. The speed of execution was the whole point. Every day without a sales channel was a day of overhead without revenue. The imperfect store taking orders on day four was worth more than the perfect store taking orders on day fourteen.

I did use some shortcuts: templates I'd already built, supplier integrations I'd already tested, fulfillment workflows adapted from my electronics business. This is the compounding value of building systems-the investment I made in 2018 paid forward into 2020.

Workstream B: Alternative Supply Chain (Weeks 2–4)

This is where language skills became unexpectedly valuable.

Being fluent in both English and Mandarin opened supplier conversations that competitors couldn't access. I reached out to manufacturers and distributors in China, Southeast Asia, and locally in Singapore. Many were in the same situation we were-trying to find new customers as their existing channels collapsed.

The negotiation environment had changed. Normally, suppliers held the power. In March 2020, many were desperate for reliable buyers. I negotiated:

Smaller minimum order quantities (critical when cash flow was uncertain)
Faster payment terms in exchange for lower prices (I'd take the margin hit for the cash flow certainty)
Sample batches before committing to larger orders

I diversified across five suppliers for our core products. No single source ever exceeded 25% of our inventory. This was a direct application of what I'd learned a decade earlier running game automation accounts-never let a single point of failure take down the whole operation.

The first alternative shipments arrived in week three.

Workstream C: Distribution Restructuring (Weeks 3–8)

The hardest mental shift was moving from B2B to direct-to-consumer.

Our existing business was built around selling to retailers, who sold to end customers. That entire middle layer had evaporated. We had to build direct relationships with people who'd previously been invisible to us.

This required:

Logistics partnerships: Negotiated with three delivery providers. Different coverage, different pricing-we routed orders based on destination and timeline requirements. Automated the routing decision using simple conditional logic.

Contactless fulfillment: Designed warehouse workflows that minimized handling and met the safety expectations customers had in a pandemic. Not complex-just documented and systematized.

Customer communications: Automated throughout. Order confirmation, packing notification, dispatch alert, delivery confirmation. Each touchpoint scripted and triggered automatically. We had no customer service team-this had to work without one.

The automation wasn't sophisticated. It was mostly conditional workflows connecting existing tools-the e-commerce platform, logistics APIs, email triggers. Nothing that required budget approval or an IT team. Just understanding how the pieces could connect.

How It Unfolded, Week by Week

Week 1: Online store live. First 12 orders processed manually while we verified the workflow. Painful but necessary-couldn't automate what we hadn't tested.

Week 2: First alternative supplier shipments ordered. Automation deployed for order processing. Average fulfillment time: 4 hours, down from 24.

Week 3: Revenue from new channel covering approximately 30% of pre-COVID levels. Not good, but trajectory was clearly upward. Tweaked pricing based on real data-what customers actually purchased at what price points.

Week 4: Broke even on the new model. Alternative suppliers consistently delivering. Beginning to see repeat customers.

Month 2: Profitable on the new model. Original suppliers beginning to come back online-now an additional source rather than the only source. Cash flow stable.

Month 3–6: Scaled. Not aggressively-we were careful about inventory in an uncertain environment-but consistently. By August 2020, the new channel had generated SGD 500,000 in revenue that simply wouldn't have existed without the pivot.

The family-run electronics trading enterprise survived. Not just survived-emerged with a more resilient model than it had before COVID.

What Actually Made It Work

Looking back, a few factors mattered more than anything else:

Speed of first action. We had the store live within 72 hours of deciding to pivot. That speed wasn't heroic-it was practical. Every week of deliberation is a week of overhead without revenue in a crisis. The bias toward action, toward imperfect execution now over perfect execution later, came directly from years of building things iteratively.

Systems thinking under pressure. I wasn't trying to "save" the business through force of will. I was mapping the system that was failing and finding the leverage points. This sounds cold, but it's actually more compassionate than panicking-structured thinking gets to solutions faster.

Existing infrastructure. The e-commerce workflows I'd built in 2018 weren't built for this crisis. But they were directly applicable to it. The automation skills I'd developed since 2008 weren't built for supply chain restructuring. But they were exactly what was needed. This is the compounding value of building skills across contexts-you rarely know in advance which capability will matter when, but broad systems-building expertise generalizes.

Financial independence as confidence. I want to be careful here-not everyone has this advantage, and I don't take it for granted. But it mattered. I could take risks with the restructuring that might have felt too risky if I'd been personally dependent on the outcome. I moved fast on suppliers, took inventory positions I wasn't certain about, and made pricing decisions that might have taken months of committee debate elsewhere. Being able to act decisively without excessive caution accelerated everything.

Multilingual access. Finding alternative suppliers in the middle of a global supply chain crisis required reaching manufacturers directly. English wasn't always sufficient. Mandarin opened conversations that resolved faster and on better terms.

What It Proved

I don't tell this story to impress anyone. SGD 500K sounds large, but for a business under existential pressure over six months, it's really just survival math.

What matters is what it confirmed:

The principles I'd been applying since age 18-build systems that handle the 80% case, diversify to eliminate single points of failure, automate the repetitive work, execute fast and refine as you go-worked at a completely different scale and in genuinely high-stakes conditions.

This wasn't theory. It wasn't a simulation. It was a real business, real family pressure, real consequences.

The skills held.

There was something else I noticed during those months. I'd been applying automation and systems thinking inside corporate environments for years-in controlled settings with IT support, established processes, and time to be methodical. The COVID restructuring was chaotic, fast, and underfunded.

And the same principles worked.

That universality is what I find genuinely interesting about systems thinking. It doesn't care about the industry, the stakes, or the timeline. The structure of the problem-identify the pattern, automate the repetitive case, design for resilience-is the same whether you're running game automation bots at 18 or restructuring supply chains at 30.

What I Learned That I Hadn't Expected

The practical lessons are obvious in retrospect: diversify supply chains, automate from day one, move fast before optimizing.

But there was one lesson I didn't anticipate.

Crisis management is mostly preparation. The reason we could execute in weeks rather than months wasn't speed of thinking-it was that most of the components already existed. The e-commerce platform was live. The supplier networks were in place, just needing to be expanded. The automation patterns were established. We weren't building from scratch; we were reconfiguring.

This changed how I think about preparation. I'm not someone who worries much about worst-case scenarios. But this experience made me genuinely value the capability portfolio you build through diverse experience. The hardware reconditioning taught me sourcing. The game automation taught me to build resilient systems. The 2018 e-commerce launch taught me digital distribution. Each one felt like its own thing at the time. In March 2020, they converged.

You don't know what you'll need. Build broadly, and trust that the skills will connect when they need to.

Back to the Room

The family meeting in early March ended without conclusions. Nobody had a plan yet. The uncertainty was real.

By August, we had numbers we could report. Business stabilized. Model transformed. Revenue recovered.

I don't think of this as my achievement. It was a collective effort with family members who kept operations running while I focused on rebuilding the model. I just happened to have the specific toolkit the moment required.

That's the thing about systems thinking at scale: it's not about being the smartest person in the room. It's about having built the right capabilities before you need them, and recognizing when the moment calls for them.

March 2020 called for them.

We answered.

The Ripple Effect

Six months after the crisis resolved, I started at a global medical aesthetics and technology company. My role there involved exactly the same skills: automation, process optimization, cross-functional coordination, regional operations.

The pandemic restructuring wasn't a detour. It was a compression of everything I'd learned across 15 years, stress-tested in real conditions. When I designed automation workflows at a global medical aesthetics and technology company-workflows that would eventually eliminate 70% of manual work across APAC operations-I was drawing directly on what I'd built and learned between March and August 2020.

Crisis management at scale confirmed what game automation at 18 first suggested: systems thinking isn't limited to any particular domain. It's a way of seeing problems.

Learn it once. Apply it everywhere.