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.

Remote AI Workflows: Business Transformation

Remote control over your business processes

Imagine sealing a deal or managing inventory simply by sending a voice note while riding in the back of a self-driving car. Feels futuristic? It's not. With AI workflows that can be triggered remotely via platforms like WhatsApp and Discord, this capability is within your reach.

This blog nosedives into how remote-triggered workflows can transform how we interact with business processes. If you've ever been hamstrung by systems that don't allow in-the-moment decision-making, it's time to rethink your operations.

Moving beyond static operations

Most businesses operate with a certain level of inertia. Processes are often static, and teams follow them rigidly. It's not always by choice but by necessity—until now.

Triggering workflows on the fly means giving your operations the flexibility they need. Imagine you're about to close a deal, but you're away from your desk. Through a quick WhatsApp message, you can execute tasks like sending quotes or updating a CRM system. This isn't just a convenience; it's strategic agility.

First-hand empowerment

We built this capability into our operations strategy because we saw the need for more human per hour. Integrate technologies that enhance human presence without chaining your team to their desks and you'll unlock potential you didn't know was there.

Take a simple task like paying a supplier. Traditionally, accounts would need to manually log into multiple systems. Today, a quick query sent through Discord can handle everything—routing through a pre-set workflow, confirming transactions, and updating the books.

Integrating advanced technology

Let's explore the real game-changers: self-driving cars and XR glasses. Traveling doesn't mean being off the grid. In a self-driving car, finalize contracts and trigger production—just as effectively as if you're sitting in the office. The car's sensors and XR glasses seamlessly merge the digital with the physical, offering a dynamic experience where your presence is amplified, not diminished.

These technologies are more than tools; they redefine interaction, providing critical strategic outcomes. Before using these, confirm the compatibility with your existing systems to leverage their full capabilities.

Outcome over activity

Ultimately, it's all about focusing on outcomes rather than activity. The ability to act and decide swiftly enhances your zone of genius—where your true potential is realized. These innovations aren't just about technology. They're about fostering an environment where strategic decisions are just a voice note away.

In summary, empowering your business with remote-triggered AI workflows isn't just about keeping pace with technology. It's about leading with strategic foresight—placing outcomes over activity, and ensuring that every action contributes to the broader business objectives.

Adopt these practices, and watch how it translates to efficiency, flexibility, and a truly more human per hour work environment.