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.

Defaults over intelligence: grow your business with AI

Why the AI replacement obsession misses the mark

The tech world is abuzz with the potential of AI agents to replace human workers. These programs can perform tasks, remember details, make choices, and aim for goals—all at speeds and costs that seem impossible for humans. Superficially, they promise a streamline of operations and an economizing of resources. But here’s the catch: while they mimic human intelligence, AI agents also replicate human flaws. They're forgetful, overconfident, and often lack the nuanced judgment that seasoned professionals bring to the table.

In our race to replicate human intelligence, we forget that intelligence itself is inherently messy. Centuries of evolution have equipped humans with a mix of cognitive abilities, instincts, and, yes, flaws. While AI might come across as a faster, cheaper, more confident version, it is, at best, a naive intelligence with little experience or context. Most glaringly, if human-level AI ever becomes a reality, it likely won't stay cheap for long.

Human mimicry vs operational design

For businesses, the promise of AI-driven markets sounds enticing. However, let’s pause and consider a vital truth: business scale has never solely depended on the intelligence—artificial or otherwise—of its operatives. What transforms a business at its core is operational design. Systems, defaults, and consistency drive sustained growth, not trying to make AI mimic human creativity or judgment.

AI agents shine when they're deployed for narrow, well-defined tasks. They're toolkits, not judgment calls. Decision rights—those should always remain with humans. Let’s stop buying into the fantasy that AI can autonomously drive strategic decisions or foster human-like creativity.

Defaults drive consistent performance

If you want predictable business outcomes, don't expect intelligence—artificial or human—to behave consistently. Instead, implement strong defaults. Design your operations around robust systems that guide behavior without constant oversight or micromanagement. Defaults set clear expectations and reduce the need for continuous decision-making—a way more reliable method for ensuring repeatable performance.

Where AI fits well: constrained execution inside good systems

The real value of AI lies within bounded tasks—inside systems that have been meticulously designed and where the scope is clear. Think of an AI performing data entry, automating emails, or sorting customer queries. These tasks are precise, and their successful execution doesn't require complex decision-making or creative insight.

AI tools are tremendous complements to human creativity and relational abilities. They handle the temporary, predictable, and mundane—to free humans up for the unpredictable, complex, and creative.

Practical takeaways for businesses

The path to smart business growth isn't lined with autonomous intelligence replacements but with meticulous planning and design. Focus on building workflows, guardrails, and strong defaults. Let humans do what they excel at: imagining the future, building relationships, and steering the ship. Meanwhile, let AI handle the grunge work, comfortably nestled within the constraints of sound systems.

Stop falling for the hype. As long as business owners keep their decision rights intact and focus on operational excellence, they won't be missing out—they'll be moving ahead.