What the career actually is
Be clear about the shape before assessing it. This is not a job you get hired into. It is a service business you run, where you find businesses, build systems for them, and maintain those systems for a monthly fee.
That distinction decides almost everything. If you want a salary, a manager and a defined role, this is the wrong path and no amount of upside changes that. If you want to build something you own, it is one of the more accessible routes available.
The case for it
- No qualification gate. Clients ask whether the system works, not what you studied. Very few technical fields are this open.
- No coding requirement. The platforms are visual, and clear thinking matters more than a computer science background.
- Delivered remotely and paid internationally. Your income is priced by a global market while your costs are local.
- Recurring rather than one-off. A maintained system pays every month, so you do not restart from zero.
- Low startup cost. A computer, internet, a way to get paid, and the platform. There is no inventory and no premises.
- Demand is genuinely unmet. Most small businesses still do not answer an enquiry outside working hours.
The case against it
Stated properly, because a list of upsides alone is marketing rather than advice.
You have to sell, and most people will not
Roughly half the job is finding businesses and convincing them. It is uncomfortable, mostly silent, and feels like failure for weeks before it works. This is where the overwhelming majority of people stop, and it has nothing to do with technical ability.
Income is unstable at the start
There is no salary. Early months may produce nothing at all while you learn and do outreach. If you have dependants and no buffer, that instability is a real consideration and not a mindset problem to be overcome.
Platform dependence
Most of this work sits on software you do not control. Pricing and terms can change and you absorb it. Learning a platform-independent workflow tool alongside is the mitigation, not a cure.
The entry level is getting crowded
Basic work is competitive and priced accordingly. What is not crowded is deep knowledge of a specific industry combined with reliability over years. The bar is higher than three years ago, and it is not closed.
How it compares to the alternatives
| Local job | Marketplace freelancing | Automation agency | |
|---|---|---|---|
| Income ceiling | Set by local salary bands | Set by global rate competition | Set by how many systems you maintain |
| Stability | High, until it is not | Low, project to project | Low at first, then compounding |
| Who decides your rate | An employer | The lowest bidder | You, if you are specific enough |
| Entry requirement | Degree, usually | A portfolio and a review | A system that works |
| What you own at the end | Experience | Reviews on someone else's platform | Client relationships and recurring revenue |
The honest read: a job is better for the first two years if you need certainty. The agency path is better after that if you can survive the uncertain part. Many people do both, running this alongside a job until it replaces the income.
What could make this a bad bet
Worth thinking about rather than dismissing.
- The platforms get simple enough that businesses do it themselves. Partly true already for the basics. The judgement about what to build has not become easier, and that is what you actually sell.
- AI makes the building trivial. Likely. It also makes the systems more capable and therefore more valuable, and someone still has to decide what to build and be accountable when it breaks.
- The market saturates. At the entry level, yes. At the level of knowing an industry deeply and being reliable for years, that has never saturated in any service business.
The realistic risk is not that the work disappears. It is that the easy version stops paying, which is an argument for getting properly good rather than an argument against starting.
Who should do this
You are comfortable with uncertainty for a while, willing to talk to strangers about their business, patient enough to debug something that half-works, and interested in how businesses operate rather than only in technology.
Who should not
You need predictable income now. You want to avoid sales. You want a title and a team. You want a result within a month. You want something no platform can take away.
If several of those describe you, a job is the better decision and there is nothing wrong with that. The worst outcome is spending a year and a course fee to discover you never wanted the business, only the income that was described to you.