The Systems That Made It Scalable
The community was growing. The bigger market was delivering. I was living out of a backpack in Southeast Asia and the business was finally moving. There was just one problem: it still needed me for everything.
In Part 3, I talked about the levers that unlocked the transition to full-time: community, market selection, the right constraints. But at some point I realized that pulling levers harder wasn't the answer. The machine itself needed to change.
Every order still went through me. Every payment still needed my confirmation. Every question from a buyer in a different time zone still waited for me to wake up. I was the bottleneck — and the business couldn't grow past me.
So I started removing myself from it. One system at a time.
The Problem with Manual Everything
Picture this: I'm in a café in Chiang Mai, 32°C outside, fan overhead, iced coffee going warm. I've got twelve tabs open. Half are orders waiting to be processed. The other half are questions from buyers I haven't answered yet.
As a side business, I'd managed like this for years. Manageable, even satisfying — every sale felt personal.
As a full-time business with real volume, it was a wall. The business couldn't grow faster than I could process orders. And I could only process so many orders before my brain turned off.
Three systems removed the ceiling. Not all at once — one by one, each one solving a specific bottleneck that had become obvious.
System 1 — The Website
For years, my storefront was a thread on a gaming forum. A good thread — detailed, well-reviewed, trusted — but still a thread. Dependent on a platform I didn't control, with a design I couldn't change, and no way to automate anything.
Building a proper website changed three things at once.
Credibility came for free. A real site with its own domain, clean product pages, visible reviews — it just looks different from a forum post. Buyers who'd hesitated before often converted without asking a single question.
Availability became 24/7. Instant delivery meant a customer in the US buying at 2am their time didn't need to wait for me to wake up on the other side of the world. The system handled it while I was asleep.
Surface area expanded. The site gave me space I didn't have on a forum. I launched a new service — ready-to-use accounts — and gave it its own page, its own descriptions, its own proof. A forum thread is a conversation. A website is a storefront.
Moving from forum to website was an infrastructure decision. The forum was the front door I borrowed. The website was the one I owned.
System 2 — Accepting Card Payments
PayPal was fine. Most of my customers had it, used it, trusted it. But "most" isn't "all" — and the ones who didn't simply disappeared at checkout. A lost sale I never knew about.
I don't know how many orders I lost that way over the years. A lot, probably.
Adding Stripe didn't change my product or my prices. It just let more people complete a purchase they already wanted to make. That's it. A friction removed, revenue unlocked.
There was also a margin side. Stripe's fees were lower than PayPal at volume — not dramatically per transaction, but over a month of real sales, it added up.
Every friction between "I want to buy" and "purchase complete" is a leak. You don't need a better product to fix a leak — you just need to find it.
System 3 — The Email List
For years, every PayPal payment came with a customer's email address attached. I collected hundreds of them without realizing it. Past buyers, people who'd already trusted me with real money — sitting in a list I'd never opened.
At some point I finally sent them something (with a 1-click opt-out option of course).
Nothing clever. One to two emails a month. Promotions for subscribers, inventory updates, the occasional announcement. No sequence, no funnel, no nurturing strategy.
Past customers came back. Some bought the same week. Revenue started moving from a list that had been dormant for years, without me having to find a single new customer.
But that's not the real lesson from this system.
My Discord server was the center of my business. Thousands of customers, years of relationship-building, all my active client conversations — everything lived there. Then one day, the server was gone. Banned without warning, no explanation, no appeal process that actually worked.
I started rebuilding. Got partway back. Then the second ban hit — same thing, same silence, same automated wall. Two bans, back to back, before I could recover from the first.
I looked into legal options. Consulted a lawyer. Started building a case against Discord for banning a server that hadn't violated their Terms of Service. Then I saw the cost of going up against a company that size in court. I dropped it.
Only later did I understand what had actually happened: automated bot detection flagging certain keywords in public servers. No human ever reviewed it. No process existed to contest it meaningfully. One algorithm, one decision, no recourse.
I rebuilt the server a third time. From zero to 2,000 members again — giveaways, events, community activity, all of it rebuilt from scratch. It worked. But the experience left a mark that changed how I thought about every platform I used.
The second time Discord wiped out my server, I stopped rebuilding on someone else's land. I started building on mine.
A Discord server can be deleted overnight. A forum thread can be removed. A game account can be terminated with a Code=045 and an OK button. Your email list is the one asset none of that can touch. It's yours. It moves with you. It survives platform changes, algorithm updates, and automated ban waves.
If I had prioritized building the list five years earlier, the Discord bans would have been painful but contained. Instead, they nearly took down the whole operation (twice).
What These Systems Have in Common
Three systems. Three different problems. But they all do the same thing: they took me out of the loop.
Website + instant delivery — orders fulfilled without me. A buyer in the US at 3am gets their key. I'm asleep in Thailand.
Stripe — buyers who couldn't or wouldn't use PayPal could now pay. A friction removed. Sales that were previously invisible became real.
Email list — revenue that no platform could delete. Not Discord, not a forum, not a game publisher. Mine.
What's left after that is the work that actually matters: judgment, reputation, complex clients, strategic decisions. The stuff that genuinely requires a human. That's where I put my energy once the systems were running.
A business that depends on you entirely is a job. You stop — it stops. A business with systems keeps running when you're traveling, sleeping, or dealing with two Discord bans back to back.
The Result
By the end of that period, I barely recognized the business I'd started with. Orders fulfilled automatically. Two payment systems running in parallel. A customer list I actually owned. A site I controlled. A community I'd rebuilt twice — and understood better for having lost it.
It ran from wherever I was. A café in Bali, an airport lounge, a guesthouse at midnight in northern Thailand. Not perfectly — nothing ever is — but well enough that I stopped spending energy on maintenance and started spending it on growth.
That's where this chapter closes. Not because the story ends here, but because the building part does. What came next — the pivot toward teaching, Gamoniz as a brand, RMT Accelerator — is a different story. One I'll write about soon.