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.

The importance of workflow mapping for SOPs

Understanding the starting point

Before jumping into creating standard operating procedures (SOPs) or task lists, it's vital to have a comprehensive understanding of the processes within your business. Workflow mapping is where this all begins. It might seem tedious, but failing to do so results in disorganized execution and can cause more harm than good.

What is workflow mapping?

Workflow mapping visually lays out each step involved in a process, from start to finish. It uncovers the who, what, and why of each step, spotlighting dependencies and potential bottlenecks. By mapping workflows, you gain insights that are often missed when trying to document procedures too early. Overlooking these insights can lead your team astray.

Seeing the entire process

When we built hmn.plus, mapping our workflows allowed us to see the process holistically. This visibility gave us the opportunity to optimize—not react to—how work was being done. You see, the challenge isn't the lack of SOPs or tasks; it's knowing what to document in the first place. A well-mapped workflow highlights the critical touchpoints and areas of friction that you might not even know exist.

Preventing inefficiencies

Consider a task being repeatedly delayed. Without workflow mapping, you might blame poor time management, missing the systemic inefficiency lurking in the shadows. We found that once we understood the intricacies of our workflows, we could restructure them to streamline efforts, saving everyone from unnecessary headaches. A good map highlights inefficiencies that SOPs and task lists alone cannot solve.

Creating clarity and alignment

Perhaps most importantly, workflow mapping aligns your team. It clarifies roles, eliminates redundant steps, and ensures that everyone knows the entire picture—not just their piece of the puzzle. When roles and responsibilities are clear at each stage, there's less cross-talk and confusion, and results improve dramatically.

Preparing to build effective SOPs

Effective SOPs originate from a clear understanding of your processes. Without workflow mapping, you risk developing SOPs based on assumptions rather than facts. This not only confuses employees but also derails the efficiency you seek. We've learned that a robust SOP is less about detailed instructions and more about empowering people to achieve outcomes predictably—something only achievable with accurate workflow maps.

A dynamic, evolving map

It's important to recognize that workflow mapping is not a one-and-done process. Businesses evolve, and so will your processes. Regular reviews of your workflows keep your team adaptable and informed. This ensures that your SOPs and tasks remain relevant and effective over time.

Conclusion

In a world that prizes agility and efficiency, ignoring the foundational step of workflow mapping is a risk no forward-thinking business should take. It sets a solid groundwork for SOPs and tasks that are clear, effective, and born from a real understanding of your business's operations. Don't shortcut this critical step—map your workflows first, and your operations will thrive as a result.