← All posts
Entrepreneurial Journey

Building My First Business at 18: The Game Automation Story

At 18, I built automated scripts that farmed virtual resources in an online game while I studied. By month three I was earning SGD 2,000/month. This is where systems thinking started.

I was 18 years old, sitting in the Singapore Polytechnic library between classes, watching lines of code run on my laptop. On screen, my character was mining virtual ore in an online game-except I wasn't controlling it. The script I'd written three weeks earlier was doing all the work.

By the time I closed my laptop and headed to my next lecture, I'd made SGD 40.

While my classmates were applying for part-time retail jobs paying SGD 6-7 per hour, I was building something that would fundamentally change how I thought about money, work, and systems.

This wasn't just a "side hustle." It was my real education in building systems that scale.

The Problem: Time Doesn't Scale

Like many teenagers in 2008, I played online games. The particular game I was into had a functioning economy-virtual items, currency, and most importantly, a real-world market where these digital assets could be sold for actual money.

The game required repetitive "resource farming"-spending hours clicking through mining, harvesting, or crafting activities to generate valuable items. The math was simple but brutal:

  • Manual farming: 4-6 hours of clicking daily
  • Income: SGD 50-80 per day
  • Effective rate: About SGD 10-15 per hour
  • Sustainability: Utterly exhausting

Players who wanted to earn money were essentially trading their time and attention in the least efficient way possible. You had to be present, clicking, watching. Miss a few minutes and you'd lose positioning or resources.

I lasted exactly three days doing this manually before thinking: There has to be a better way.

The Realization: This Can Be Automated

The breakthrough came when I realized the game's economy had patterns. Resources spawned in predictable locations. Crafting followed fixed recipes. Market prices fluctuated on cycles I could track. And most importantly-the game client accepted scripted inputs.

I'd done some basic programming in polytechnic (C, a bit of Python), but nothing sophisticated. I started with AutoIt, a simple Windows automation tool. The first script was embarrassingly basic:

Loop:
  Click(coordinates)
  Wait(2 seconds)
  Click(different coordinates)
  Wait(3 seconds)
Repeat

It worked. Barely. My character clumsily mined ore while I did homework. I made SGD 15 that first night-not much, but I hadn't been clicking for four hours.

Building a Real System

Over the next few weeks, I got serious. I taught myself more Python, learned image recognition to make the bot respond to game state rather than blindly clicking coordinates, and built in error handling so it wouldn't break when things went wrong.

The system evolved into something far more sophisticated:

Resource Farming Automation:

  • Image recognition to identify resource nodes
  • Pathfinding to move efficiently between locations
  • Inventory management to maximize gathering time
  • Anti-detection measures (randomized timing, human-like movement patterns)

Market Arbitrage:

  • Price scraping across different trading hubs
  • Buy-low-sell-high automation when spreads exceeded thresholds
  • Market trend tracking to predict price movements

Risk Management:

  • Multiple accounts (if one got banned, others continued)
  • Account rotation schedules to avoid detection patterns
  • Profit distribution across accounts to minimize loss from any single ban

By month three, I was running five accounts simultaneously. The system ran 24/7 on my laptop. I'd check in for 30 minutes each morning to verify everything was working, adjust pricing strategies based on market conditions, and let it run.

The numbers shifted dramatically:

  • Time investment: ~10 hours per week (mostly monitoring and optimization)
  • Income: SGD 2,000 per month
  • Effective rate: SGD 50+ per hour
  • Scalability: Could add more accounts with minimal additional effort

At 18-21 years old, pulling in SGD 2K monthly was significant. That's more than many entry-level jobs, with a fraction of the time commitment.

What This Actually Taught Me

Looking back 15 years later, the money was the least important part. What I actually learned formed the foundation for everything I've done since:

1. Systems Thinking: Build Once, Benefit Indefinitely

The manual approach traded time for money linearly: Work four hours, make SGD 50. Stop working, make nothing.

The automated approach required upfront investment (learning to code, building the system, testing and refining), but then generated value continuously with minimal maintenance.

This became my core philosophy: Time invested in building good systems compounds indefinitely. I invested maybe 100 hours total building and refining the automation. It ran for three years, generating over SGD 70K total.

ROI: 700 to 1.

That ratio-initial investment vs. ongoing returns-became how I evaluate every project since. Whether it's a corporate automation saving 250 hours annually or a business process generating SGD 500K in crisis situations, I'm always asking: What's the ROI over time?

2. Risk Management: Diversification and Monitoring

I learned risk management not from textbooks, but from losing my first account to a ban.

One day I logged in and saw: "Account suspended for ToS violation." Gone. All progress, all accumulated resources, everything.

That hurt. But it taught me something crucial: Single points of failure are unacceptable.

I restructured immediately:

  • Multiple accounts with different IP addresses
  • No single account holding more than 20% of total assets
  • Randomized behavior patterns to avoid detection algorithms
  • Regular monitoring for policy changes or enforcement patterns

These exact principles showed up years later when I restructured supply chains during COVID. When suppliers failed, I had alternatives. When one distribution channel collapsed, I had backups. The game automation taught me that diversification isn't optional-it's survival.

3. The 80/20 Rule: Automate the Common Case

I never tried to automate everything. Some situations were too complex, too random, or too rare to be worth scripting.

Instead, I focused on the 80% use case:

  • Standard resource farming: Fully automated
  • Market arbitrage on high-volume items: Automated
  • Complex quest chains: Manual
  • Unusual market conditions: Manual intervention

This became critical in corporate work: Don't try to automate every edge case. Build systems that handle the common patterns flawlessly, flag exceptions for human review, and move on.

The 70% efficiency gain at my current role? Same principle. I automated the 80% of complaints that follow standard patterns. The weird 20%? Still reviewed manually, but now that's manageable because we're not drowning in the routine 80%.

4. Financial Independence Is Achievable

The most profound lesson was this: Financial pressure is optional if you build the right systems.

By age 21, I was making SGD 2K monthly from game automation, plus additional income from hardware reconditioning flipping I'd started around the same time. That's more than most entry-level jobs, with far less time commitment.

This completely changed my relationship with work. I didn't need my first corporate job for financial survival-I wanted it to learn and grow. I've never optimized my career for maximum salary because I removed that pressure early.

This freedom-working for craft and interest rather than necessity-became the foundation of how I approach everything since. I'm not climbing corporate ladders or playing office politics because I don't need to. I can focus entirely on building excellent systems and doing my duty well.

That game automation at 18? It bought me 15 years of working on my own terms.

The Evolution: Same Principles, Bigger Stakes

The game automation eventually ended (the game shut down, and I'd moved on to other things), but the principles never stopped working:

2009-2010: Consumer electronics reconditioning and resale

  • Same arbitrage thinking: Buy broken, fix, sell for profit
  • Same systems approach: Standardize repair process, optimize sourcing
  • Same risk management: Quality tiers, warranty offerings

2018: E-commerce launch

  • Same automation-first approach: Built with workflows from day one
  • Same compound thinking: Invest time in setup, benefit indefinitely
  • Same result: Semi-passive income requiring minimal ongoing effort

2020: COVID supply chain restructuring

  • Same crisis response: Diversify suppliers, automate processes, move fast
  • Same ROI thinking: Time invested vs. value generated
  • Result: SGD 500K additional revenue when family-run electronics trading enterprise needed it

2022: Corporate automation at a global medical aesthetics and technology company

  • Same methodology: N8n workflows eliminating 70% manual work
  • Same maintenance approach: 0.01% ongoing effort
  • Result: 250+ hours annually recovered for senior management

Every single one of these used the exact same principles I learned at 18 running game automation scripts in a polytechnic library.

Looking Back: No Regrets

Some people might see this as wasted time-spending years on a video game instead of "real" work. I see it differently.

That game automation taught me systems thinking, risk management, ROI optimization, and financial independence. Those lessons were worth far more than any formal business education could have provided.

Most importantly, it taught me something business schools don't: Financial pressure is a choice. If you build systems that generate value while requiring minimal ongoing input, you buy yourself the most valuable asset-the freedom to work on what matters to you.

At 18, I thought I was just making money playing games.

At 33, I realize I was getting a Master's degree in building systems that scale.


The Takeaway

You don't need to start with game automation. You don't need to be 18. You don't even need to build a business.

But if you're reading this and thinking "I could build something better than how things work now"-do it.

Start small. Focus on one inefficient process. Build a system that handles it. Refine until it runs itself. Then move to the next one.

Fifteen years from now, you'll look back and realize those small systems you built compound into something far bigger than you imagined.

That's how you go from SGD 2K/month at age 18 to recovering SGD 500K in a crisis, or eliminating 70% of manual work across APAC, or positioning yourself as a top-tier consultant with proven methodology.

Systems thinking scales. It always has. It always will.

The question is: Will you start building?

Shi Jun

Shi Jun

Senior Regional Technical Operation and Quality Engineer, Medical Technology / Pharma Industry. Building automated systems since 2008. Philosophy: "Using less resource and achieve big time."