Do I need to know what should be automated?

No. Most people arrive with a feeling rather than a specification — something takes too long, or only one person can do it, or it gets dropped whenever the week is busy. That is enough to start from. If you can point at one job you would gladly stop doing by hand, we can work with that. If you can’t point at one yet, start with the free diagnostic instead: it finds the constraint first, and the workflow follows from it.

What happens with the first workflow?

We build it. You describe the job the way you would explain it to somebody starting on Monday — what comes in, what you would check, what should go out, and what you would never let leave without reading it. That becomes a working workflow, connected to the tools you already use, running on your account. You watch it run on real work before you rely on it. One workflow, start to finish, so what you are judging is a thing that works rather than a proposal for one.

What happens after that?

It runs. Keeping it running is the recurring part — hosting, the models it calls, monitoring, and the fixes for when something upstream changes its mind about a field name. Most people then add a second workflow, and it is usually one they spotted themselves while watching the first one work. There is no bundle to commit to up front. The next workflow is a decision you make when you want it, and not before.

Can my team eventually build workflows themselves?

That is the intended end state, and the training exists for it. Once your team has watched a few workflows get built, the skill turns out to be the describing — knowing what the work actually involves and where the judgment sits — which is the part your team already has. Some businesses would rather we kept building, and that is a legitimate choice rather than a failure. Most want at least one person inside who can change something without picking up the phone.

Do I become dependent on hmn.plus?

It is the right question to ask any vendor, and the honest answer is that you can be for exactly as long as it is useful. Three things are deliberate: the workflows are described in plain language rather than locked in a format only we can read, they run on infrastructure that can sit in your own name, and we teach the building instead of keeping it. Being the only people who can change your systems would be a business model. It is not ours.

Can we eventually own the system?

Yes, and it is an option rather than a destination — plenty of businesses would rather we kept running it, and that is a reasonable thing to want. When you do want it, the workflows, their definitions and the infrastructure transfer to you, and your team keeps the training that makes them usable. We would rather you stayed because staying is worth it.

The first automation is a fixed price, so the first decision is a small one: NZ$500 + GST to map it and get it built. After that, the platform it runs on is NZ$150 + GST a month for each person who builds workflows — everyone else who uses it is free — and that covers hosting, running your workflows, monitoring and support. Workflows you build yourself cost nothing extra; the ones we build are quoted one at a time, on what each actually involves. No annual lock-in, and nothing larger to sign before you have seen something of your own working.

Why not use ChatGPT, Claude, Zapier or n8n?

They answer a different question. Chat tools put something capable on the other end of a conversation, and then nothing happens unless a person types — every session starts again, and what the business knows ends up living in whoever writes the best prompt. Zapier and n8n wire apps to each other; the wiring holds until a field name changes, and it never makes a judgment call. Both leave the work depending on a particular person. What we build has a fixed shape: the same steps in the same order, your rules written in, a record of every action and the reason for it, and a person standing where a person should stand. The thinking inside a step can be as sharp as it needs to be. The path through it does not change because somebody phrased something differently. That is the difference between a tool one person is good at and a system a business runs on.

Where should AI actually be used?

On the judgment inside a step, not on the whole step. Reading an enquiry and working out what kind it is: yes. Drafting a reply in your voice, from your own past replies: yes. Moving money, or telling a client something binding, with nobody looking: no. What we build to is that anything with consequences waits for a person, and everything in front of it does not have to. A faster version of a bad process is still a bad process, which is why deciding where AI belongs happens before anything gets built, and is most of the value.

Build AI automation yourself: A third option

The overlooked third option for AI automation

When it comes to AI automation, many business owners see only two routes: hiring in-house or outsourcing to a consultant or agency. These paths may seem straightforward but have their challenges. A third option—more empowering and surprisingly accessible—is building the automation yourself.

The pitfalls of hiring in-house

Consider the in-house hire. An AI engineer can be a strong asset, but before they're genuinely productive, significant groundwork is necessary. They must set up tools, develop software, effectively use AI, and learn your company's processes and industry intricacies. Mistakes in hiring can cause real repercussions, even if those issues can eventually be fixed. This means time, money, and focus can be diverted from your core business activities while you onboard and train them effectively.

The hidden limitations of outsourcing

Outsourcing to a consultant or agency might seem safer. After all, they usually bring experience. However, they lack intimate knowledge of your industry, processes, or people, leading to longer onboarding and adaptation periods than anticipated. They also charge by the hour or project, and you often only gain a few pieces of automation to own. These consultants might appear to simplify AI integration, but understanding your unique business needs is where the real value of skilled AI engineers lies. It's their ability to translate these needs into solutions that matters most.

Embrace the third option: build it yourself

Many business owners hesitate, thinking they lack the skill, time, or resources. These are limiting beliefs. Tools like HMN.plus make AI automation accessible without requiring large blocks of time or expertise. AI coding agents can work in parallel, allowing you to invest just minutes at a time—enough to move a project forward, step away, and return later. It's a flexible approach that empowers you to take control of your automation process.

Addressing the money concern

If money is a concern, consider that the obstacle is often a lack of prioritization. Automation's ROI can begin compounding the very same day effort is applied. Realize that initial investment in AI capabilities isn't just an expense; it's an investment into scalable growth.

Overcoming the expertise barrier

The belief that you lack expertise is another common barrier. The truth is, AI forces you to formalize and extract your business expertise. While learning AI is challenging, valuable skills often are. This is a skillset that will matter for the next decade and beyond. It’s about progress, not perfection—develop this capability in bite-sized pieces.

Don’t get left behind

Imagine refusing to learn to use computers or social media when they first emerged. Whether it feels natural or not, they became essential. AI is no different. Stop treating AI automation as something solely purchased externally. Begin to see it as a core capability—one that you own, build, and develop. It's a mindset shift that positions you to lead rather than follow.

Invest the time to explore this third path. You'll not only be building automation, but building a more agile, resilient business along with it.