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.

Back to Blog

ai automation business workflows n8n agentic os business growth usability automation pitfalls

From AI automation with N8n to building agentic OS for business owners

Diego Ramirez · 15 March 2026 · 2 min read

Navigating the limitations of existing AI automation tools

A year ago, we embarked on a journey with N8n, a tool celebrated for its ability to automate workflows in a more human way. But as we dug deeper into AI automation, we encountered a major roadblock: most automation fails. The reasons were clear—integration issues, rigidity, and the lack of business owner involvement in creative processes.

Why existing tools fall short

N8n is robust, but we quickly found that its application in AI workflows was hindered by integration challenges. Businesses need tailor-made solutions. Unfortunately, existing tools demand extensive technical expertise not all small business owners possess.

Moreover, automation efforts often dwindle due to insufficient ROI-based validation. We learned that no matter how seamless a tool claims to be, if the generated outcomes aren't aligned with business goals, the initiative flounders.

From realization to creation: Building agentic OS

Recognizing these pitfalls, we pivoted towards a goal-driven framework—agentic OS. It focuses on outcome over activity, offering business owners an environment to develop workflows that are flexible and impactful, without developer dependencies.

What sets agentic OS apart?

Scalability: We designed the platform to grow with the business, allowing for seamless enhancements without overhaul.
Governance: Ownership is crucial for confidence and control. Business owners maintain their automation frameworks, ensuring compliance and security.
Usability: Our system demystifies workflow creation, facilitating engagement even for those without a technical background.

Automating with a human touch

The essence of agentic OS lies in creating more human per hour efficiencies. We've transitioned from a tool-focused setup to fostering creativity and control within businesses. This move is more strategic before tactical—empowering users to focus on their zone of genius, crafting workflows that genuinely align with their industry-specific needs.

Planning for the future

We're already envisioning the next phase of agentic OS—integrating advanced reporting and dashboarding features. These enhancements will further bridge the gap between AI and actionable insights, offering businesses a robust grip on their growth trajectories and the efficacy of their automations.

Through agentic OS, we're championing a fundamental shift. Business owners no longer have to settle for off-the-shelf solutions. They can build, scale, and refine their AI workflows—ensuring that their unique business puzzles come together as intended.