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 workflows agentic os automation enterprise ai ai engineering hmn.plus

The AI workflow race: why companies should stop building from scratch

Diego · 12 March 2026 · 3 min read

A shift in the AI landscape

We're witnessing a real shift in how companies approach AI integration. Many businesses have moved past the basic use of tools like ChatGPT. They're serious about automating their workflows to drive efficiency. In response, they're hiring AI engineers to build custom systems from the ground up. Sounds proactive, right? But here's the catch—this approach often leads to reinventing the wheel, with engineers frequently lacking the necessary production experience and best practices.

The pitfalls of starting from scratch

Building an AI system that runs a business isn't a side project. It's a full-on job, one fraught with potential errors and inefficiencies if you're starting from a blank slate. These foundational systems are bread and butter for your operations, yet many teams find themselves bogged down, playing catch-up rather than innovating. It's akin to hiring a chef to design a kitchen from scratch rather than letting them create culinary masterpieces. What's getting lost is your zone of genius—maximizing more human per hour efforts.

Focus on learning and automation

Imagine not having to worry about the principles of governance, safety, and reliability every time you roll out an update. This freedom is precisely what hmn.plus Agentic OS offers. We built this system to provide a robust, secure, and transparent framework for companies eager to automate their processes. Let your team focus on what truly matters—learning the business and driving automation, not on maintaining unreliable foundational systems. We've done the learning and made the mistakes, so you don’t have to.

Comprehensive benefits of a tested framework

Using a ready-made system like Agentic OS doesn't mean settling for less. It means choosing strategic before tactical—a mindset that delivers outcome over activity. With Agentic OS, your business isn't entangled in the intricacies of system design, letting your team channel their energy into areas that directly enhance your business's bottom line.

Agentic OS was crafted from real-world lessons. We've painstakingly ensured that our platform meets the highest standards of governance, safety, and reliability. It's not just about having a foundation but a trusted one that allows your initiatives to grow unencumbered by technical debt or recurring errors.

Conclusion: A strategic approach pays off

The race to integrate AI effectively is intense. However, the key isn't in how quickly you can build from scratch. It's in choosing systems that empower your teams to keep their eyes on business goals. Opt for a framework like Agentic OS, and convert your AI aspirations into tangible, reliable business enhancements.