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.

Real-time Streaming in AI Workflow Builder

Reimagining AI workflow generation

Most AI solutions present a deceptively simple promise: let us do the work, and you'll reap the benefits. But there's a catch—a frustrating gap between promise and reality when your role is reduced to that of a reviewer. With our AI system, Agentic OS, we initially faced this very issue. Our agents generated entire workflows behind the scenes, and only when they were done did we reveal the outcome to users. The result was often a cycle of waiting, reviewing, and reworking—a process far from efficient.

The pitfalls of the old way

Consider the traditional approach. You initiate a task, step back, and wait for the AI's final output. Then you find a hiccup—a misunderstood direction or a flawed approach. What then? You end up reworking it all, spending precious tokens and time on outputs that might not even stay. This isn't collaboration; this is reviewing your AI's homework.

Most AI tools operate this way. Get a result, refine it, and maybe—just maybe—it's usable. But the process burns resources and leaves the human partner in the dark for too long.

Real-time streaming: a collaborative breakthrough

We built real-time streaming into our workflow builder because we saw a better way forward. Streaming turns users into guides rather than critics. Imagine guiding the AI during the process, not after the fact. Real-time updates transform your relationship with AI from passive to actively collaborative—pair programming, not ordering a report.

By seeing workflow formation live, users can spot incorrect paths early on and navigate the direction themselves. You save time, save tokens, and avoid investing computational resources on undesired outcomes. More human per hour, indeed.

Human-computer interaction redefined

There's a distinct shift in how you interact with AI when its processes are visible and malleable in real-time. This isn't just technological evolution—it's a change in the human-computer dynamic. Real-time streaming engages users continuously, fostering a deeper bond between user and machine.

Think of it as pair programming with AI. You're not waiting for the output; you're part of its creation. Dynamic editing and immediate feedback enhance the workflow's precision, making every step count.

Balancing multi-agent environments

What if you're managing multiple agents on separate workflows? Is real-time streaming still beneficial? We believe it is. Streaming compels focus. It lets you co-create a primary workflow while others run in the backdrop, giving you the choice to shift context if needed. It requires concentration—an increasingly vital skill. It aligns your focus with your ultimate goals.

Flexibility for the future

The world of AI is evolving, and so is our need for adaptable solutions. Our streaming approach offers flexibility. You can choose to engage live, or let the process unfold in the background. It supports both strategies—allowing humans to lead or observe per their need.

In integrating real-time streaming into Agentic OS, we've built not just a tool but birthed a new mode of human-AI collaboration. This transformation from interaction to cooperation is what marks this innovation as truly valuable—an AI solution that partners with its human counterpart. The future of workflow automation isn't in fixing outputs but in building them together.