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.

New Features in HMN.plus Studio: Enhance Your Insights

Unlock workflow data

We’ve been where you are—juggling metrics, struggling to see the bigger picture of how your workflows impact your business. Most systems promise clarity but deliver confusion. It's frustrating and inefficient.

That's why we've focused on visibility and precision with our latest release. Our new features in HMN.plus Studio are crafted to give you actionable insights, turning data into a powerful ally in your decision-making process.

Dashboard: Your workflow overview

This isn’t just another data board. The new dashboard in HMN.plus Studio gives you the workflow overviews that matter. See the number of workflows run, average execution times, and insights into workflow generation data. This isn’t about clutter—it's about clarity.

Imagine knowing at a glance how your processes are performing. The dashboard provides the transparency you need to make informed decisions instantly. No more waiting around for updates or digging through spreadsheets.

Insights page: Deep dive into your data

Understanding your business dynamics is crucial—and our Insights page offers precisely that. Now, you can analyze workflow data at both the macro and micro levels. Assess customer treatment efficiency, measure response times, and track workload execution timelines with ease.

One of the standouts? Our AI-powered querying. It sifts through internal log data, identifying bottlenecks and delays that can derail your operations. This means you spend less time troubleshooting and more time optimizing.

Execution log: A historical edge

Ever needed to backtrack to find that one piece of sent communication or previous document version? With the new Execution log, you can access historical workflow outputs like emails and generated PDFs effortlessly.

It’s about maintaining a historical edge—having the context of past actions enhances decision-making for future strategies.

Empower your departments

These features aren't just about data—they're about empowering your entire organization. Whether you're in customer service, operations, or management, the visibility provided by these tools will streamline your processes and uncover valuable insights.

The aim here is simple: turn your data into accessible, actionable intelligence. With comprehensive workflow tracking, you'll understand where uptime excels or falters and how resources are being allocated.

Available for download

Ready to take control of your workflow data? These features are now live and available for download. We encourage early adoption—use the insights this upgrade provides and allow it to communicate directly across your business sectors.

We thrive on your input. Download our release, and let us know how it impacts your workflow. Your feedback is more than welcome; it’s invaluable.

Agentic OS: Looking Forward

In the words of Diego from HMN.plus, “These updates are just the beginning.” The Agentic OS features promise even more integration and intelligence, continuing to place power in your hands by design.

In an era where data drives decisions, the enhancements we've made are essential for modern enterprises. Equip your teams with our updated tools—let’s convert potential into performance.