I almost hired two people last year.
I was overwhelmed. Content wasn't getting done. Research was piling up. My inbox felt like a second job. The instinct: this is a human problem, so I need humans to solve it.
Then I did the math.
A decent VA in Malaysia: RM5,000-8,000 per month. A good content executive: RM6,000-10,000. Two hires: RM11,000-18,000 per month, before benefits, before equipment, before the management overhead that nobody factors in.
Then I looked at my actual bottlenecks. Not the surface symptoms, the underlying tasks. Research. First drafts. Scheduling. Analytics reporting. Email sorting. Meeting prep.
Every single one was automatable.
I spent one month building the system instead of hiring. Total ongoing cost: roughly RM600 per month in tools and agent infrastructure.
The output exceeded what two humans would have produced. The processes run while I sleep.
This is not an anti-hiring post. Humans are essential - I have them working with me. But the order matters. And most SEA founders get it backwards.
Why Founders Hire Before They Should
The instinct to hire is natural. You're overwhelmed, something is broken, and humans are the familiar solution.
But hiring into a broken process doesn't fix the process. It gives you more people running the broken thing.
The right question before any hire: is this a capacity problem or a systems problem?
Capacity problem: the workflow is right, you just need more hands to run it.
Systems problem: the workflow is wrong, inefficient, or doesn't exist yet.
Most early-stage founders have systems problems. They hire for capacity and wonder why things don't improve.
Build the systems first. Hire for the gaps that survive automation. In that order.
The 10 Things to Automate
These are tasks most SEA founders do manually, or skip entirely because they don't have time. All of them can be automated or heavily assisted with tools available today.
1. Research - If you're manually searching for information, reading through articles, and compiling notes, you're spending high-value time on low-value work. A research agent or well-configured AI tool can surface, filter, and summarize relevant information while you focus on what to do with it.
2. First drafts - Content creation and writing are two different things. Content creation is turning briefs and direction into first drafts. Writing is the voice, the judgment, the specific angle only you can bring. Automate the creation. Keep the writing.
3. Content scheduling - If you're manually scheduling every post, you're doing something Buffer, Later, or a dozen other tools have done automatically for a decade. This should not require any human time.
4. Analytics reporting - Weekly reports on what content performed, what traffic came in, what metrics moved. This is data aggregation. Automatable. Set up a dashboard that aggregates everything automatically. Review it. Don't compile it.
5. Email sorting and filtering - Not email writing. Email sorting. Creating folders, applying labels, routing newsletters to a digest, flagging messages that need urgent attention. This takes 30 minutes to set up properly and saves 20 or more minutes every day.
6. FAQ responses - If you answer the same five questions every week, you're doing human work that belongs in a system. Stop typing the same answer manually.
7. Meeting preparation - Brief documents before client calls. Context summaries before sales conversations. Agenda preparation. A system that pulls relevant client info, recent interactions, and meeting context into a single brief before a call saves several hours per week.
8. Social listening and trend monitoring - Knowing what's happening in your industry, what competitors are doing, what topics are gaining traction. An automated monitoring system surfaces the relevant signals daily.
9. Invoice and payment follow-up - Payment reminders cause founders disproportionate stress for how straightforward they are to systematize. The sequence is identical every time: invoice sent, reminder at 7 days, reminder at 14 days, escalation at 30 days. This belongs in a system.
10. Distribution - Publishing content to multiple channels, repurposing posts across platforms, sharing updates to email lists. A distribution workflow that triggers automatically after content is approved handles this without anyone manually copying and pasting between platforms.
What You Should Never Automate
Your POV and voice. The angle you take on a topic. The belief you bring to a conversation. This is your kernel. It doesn't automate.
Client relationships. The initial call with a serious prospect. A check-in with a client going through something difficult. These require you.
Live teaching and delivery. If you run workshops, do coaching, or teach live, the experience is the product.
Brand voice decisions. What topics you engage with publicly. How you respond to criticism. What you amplify and what you ignore.
Anything requiring your specific judgment about your specific business. Pricing calls. Partnership decisions. Hiring choices. Strategy pivots.
The Principle Behind the List
AI amplifies. Humans decide.
The tasks on the automation list are amplifiable - give a system the right inputs and it produces consistent, useful outputs at scale. The tasks on the never-automate list require judgment embedded in your specific experience, values, and relationships.
Build systems for the amplifiable tasks. Protect your time for the judgment calls.
The Order That Works
Automate the 10 things above. See what's left. The gaps that survive automation, the tasks that genuinely still require a specific human with specific skills, those become your first hire list.
Hiring before automating means you're managing people who are doing work systems should do. Expensive, slow, and difficult to restructure later.
Build the machine first. Then hire for the gaps.
I built mine over three months before making any hires. By the time I brought someone on, I knew exactly what the human layer needed to do because I'd already defined everything the system could handle. The hire was specific. The expectations were clear. The integration was fast.
If you want to map this for your specific business - look at your actual bottlenecks and figure out what belongs in a system and what belongs in a person - book a call with my team. We'll work through your stack together.
- Jackson