Agency, DIY, or Learn to Build It Yourself: The Third Option for AI Automation

There are three, not two. A DIY build, where you or a staff member wires up a single tool yourself. An agency build, where an outside team scopes, builds and then charges a monthly retainer to keep it alive. And a capability build, where an outside team trains your own people to build the systems and then leaves, so the knowledge stays in-house with no ongoing retainer. Each is right for a different kind of problem. The reason the third door matters is that the first two share a failure mode the people who buy automation describe better than any vendor does. As one operator put it on r/automation: "They pay high fees, consultant leaves, automation dies." That one line is the whole problem. The system was never the deliverable. The ability to keep it running when its builder is gone was the deliverable, and nobody bought that. Another put it this way: "The actual product is not the workflow but rather the ability to continue maintaining it even when its creator is no longer around."

That is how nearly every guide frames it, and the framing is rigged. An operator on r/automation stated the real trap in a single sentence, and it closes both of the usual doors at once: "Education doesn't scale to people who have a day job. Agencies recreate the dependency problem." This is a genuine trilemma, so let us take all three horns honestly. Horn one, pure DIY. It does not scale to a busy owner. You start a build, a job comes in, the half-finished workflow sits for three weeks, and you never come back to it. Horn two, the agency. It works, and then you are renting your own operations forever. The economics are worth seeing from the builder's side, because they are rarely this frank. One builder on r/nocode: "Cost per client to me: about 7 pounds/month infrastructure... I charge 300-500 pounds/month retainer. Margin is the business." The infrastructure costs almost nothing. The retainer is not paying for servers. It is paying for the fact that only the agency understands the system. Dependency is not a side effect of that model, it is the product. Horn three, generic training. Sitting a busy team through a course on a Tuesday afternoon does not stick, for a reason the same thread names precisely: "I don't think Sam from HR and Rob from Accounting are to be expected to learn mentioned tools or the procedural thinking flows need. It's not their talent." Every one of these objections is correct about what it is objecting to. The resolution is not to pick the least-bad horn. It is to notice that all three assume the skill being transferred is tool-wrangling, and it is not.

The reason "your staff can't learn this" feels true is that people picture staff learning to drag nodes and read JSON. That is the wrong skill, and it is also the one being automated away fastest. The durable skill is diagnosis. As one builder put it on r/n8n: "The real skill isn't building it's diagnosing. Anyone can wire up n8n or connect APIs. The rare skill is listening to a store owner for 30 minutes and identifying the ONE workflow costing them the most." Your staff already hold the half of this that cannot be taught from outside: they know the process. What they lack is the method to map it, pick the one workflow worth automating, design what happens when it breaks, and own it. That is teachable in weeks, and once taught it does not walk out the door with a consultant. This is what a capability build transfers. Not node-dragging, diagnosis and ownership.

Concede this plainly, because it is true. Hire an agency when the work is: Genuinely complex. A complex integration across several legacy systems, custom middleware, real engineering. This is not a weekend project and pretending otherwise helps nobody. One-off. A single migration or a one-time data cleanup you will never touch again. There is nothing to own, so there is nothing to transfer. Pay once and move on. Integration-heavy or high-risk. Anything touching payments, regulated data, or infrastructure where a silent failure is expensive. Sometimes you want an accountable outside party. If the work is one of these, a retainer can be fair value. The failure is not agencies. It is using an agency for the recurring, evolving, business-critical automations that your team should own, and then paying rent on them for years.

Also true, and worth saying so you trust the rest. Do it yourself when the automation is: Simple and single-trigger. One event in, one action out. A form submission that drops a row into a sheet. A booking that fires a confirmation. Modern tools genuinely handle this, and paying anyone is a waste. Low-stakes. If it breaks, you notice within a day and fix it in ten minutes. No need for error design or a maintainer. Stable. The process is not going to change every quarter, so nobody needs to keep evolving it. If your problem is a single-trigger, low-stakes, stable task, close this article and go build it. You do not need a program and you do not need us.

Between those two edges sits most of the work that actually matters: the recurring, business-critical systems that change as the business changes. Quote-to-cash. Enquiry response. The reporting that ties three tools together. Too involved to leave half-built on a busy week, too central and too alive to rent from a stranger forever. This is exactly what small businesses say they want, and it is neither of the usual doors. As one put it on r/automation: "small businesses do not want to have an automation platform at all they want a system that keeps on running by itself." A system that keeps running by itself needs an owner inside the building. That is the whole case for training your own people. It also answers the resentment that runs loudest through Australian threads, where the children of tradies and IT-literate owners watch the pitches land on their parents. One on r/ausbusiness described sellers "quoting businesses like my dad five/six figures for what sometimes is just a GPT wrapper with no second thought." You cannot be sold a five-figure GPT wrapper if your own staff know what a GPT wrapper is and can build one in an afternoon. Capability is the best defence against being overcharged there is.

The standard three-tier ladder every competitor publishes is really a dependency ladder. It runs DIY, then configured-plus-retainer, then full-custom, and every rung upward hands more control to someone outside your business. Redraw it around capability and it points the other way. For a simple, stable task, the old framing says DIY and hope it holds; the capability framing says DIY, and it is genuinely fine. For recurring, evolving, core work, the old framing puts an agency on retainer; the capability framing has your staff build and own it. For genuinely complex or one-off work, the old framing sells a bigger agency and a bigger retainer; the capability framing uses an agency for the build and your staff for everything after. The goal is not to climb toward more outsourcing. It is to move the recurring work into your own hands, and to use outside help only where it cannot be owned internally. That is what 13Labs' buildAutomation program does: over 6 to 12 weeks it trains two or three of your own staff to diagnose, build and maintain the systems your business runs on, then it steps back. No retainer, because there is nothing left to depend on us for.

You will see the stat everywhere: an MIT study found roughly 95% of enterprise generative-AI pilots delivered no measurable return. It is real, and every agency in the country quotes it to sell you the safety of their retainer. Read it the other way. The 5% that worked were not the ones with the biggest vendor. They were the ones that picked a single high-value workflow, built error handling for when it broke, and kept an owner who understood it. Those three things are not a product you buy. They are a capability you hold, and they are precisely what the failed 95% outsourced and then lost when the consultant left. Source: MIT NANDA study, reported by Fortune, August 2025. There is also a real Australian sweetener for building capability in-house rather than expensing a retainer. Where the work is genuine experimental development, the R&D Tax Incentive offers a 43.5% refundable tax offset for companies with turnover under A$20 million. Building and owning novel systems can qualify in a way a fixed monthly service fee generally does not. Check your eligibility with a registered tax agent. Source: business.gov.au / ato.gov.au, R&D Tax Incentive.

Pay an agency when the work is complex, one-off or high-risk. Do it yourself when it is simple, stable and low-stakes. For everything in between, which is most of what runs a business day to day, the third door wins: train your own people to build and own it, so the capability stays when the invoice is paid. That is the option nobody selling a retainer will offer you, and it is the reason we built it.

What is the third option for AI automation, besides an agency or DIY? Training your own staff to build and own the automations, instead of outsourcing them or wiring them up alone in your spare time. An outside team teaches two or three of your people to diagnose, build and maintain the systems, then leaves. The capability stays in-house with no ongoing retainer. Why do so many AI automations stop working? Because nobody owns them. As one operator put it on r/automation, "they pay high fees, consultant leaves, automation dies." The system was built, but the ability to maintain and evolve it was never transferred to anyone inside the business, so it quietly breaks and gets abandoned. Isn't building automation too technical for non-technical staff? The technical part, wiring up tools, is the part being automated away and the part you can hire for cheaply. The durable skill is diagnosis: mapping the process, choosing the one workflow worth automating, and designing what happens when it breaks. Your staff already know the process, which is the hard half. The method is teachable in weeks. When should I just hire an agency? When the work is genuinely complex, a one-off you will never touch again, or high-risk work touching payments or regulated data where you want an accountable outside party. For recurring, evolving, business-critical automations, owning it in-house beats renting it on a retainer. When is doing it myself good enough? When the automation is simple and single-trigger, low-stakes, and stable. One event in, one action out, and if it breaks you notice quickly and fix it easily. Modern tools handle this well and you should not pay anyone for it. How is buildAutomation different from an automation agency? An agency builds the system and charges a monthly retainer to keep it running, which keeps you dependent on them. buildAutomation trains your own staff to build and own the systems over 6 to 12 weeks, then steps back with no retainer. You keep the capability, not a subscription.