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.

Balancing convenience and control: data ownership

The allure of instant access

We've all been there. Logging into an app with just a click using your Google or Outlook credentials. It’s effortless—no passwords to remember, no forms to fill out. You’re directly and instantly engaged with the app’s value. This seamless entry removes barriers and the frictionless experience feels rewarding.

For many, especially in fast-paced environments, this level of convenience is essential. That instant gratification allows you to bypass the usual gatekeepers of technology usage and dive right into productivity. However, while the front end feels like magic, there’s a cost lurking around the corner—ownership.

Ownership versus convenience

The trade-off for such convenience is often less discussed but profoundly impactful. What you're handing over in exchange for that click—your data, your control, your sovereignty over what’s being built—is significant. These companies don’t just make the sign-on easier for you; they collect your data, analyze your preferences, and potentially influence your choices.

At hmn.plus, we believe that this model doesn’t necessarily benefit the business owner or consumer in the long run. Products, like agentic OS, have begun to chart a different course, one where the end user, not the developer, owns the data. This shift doesn’t come without some initial effort—a bit more setup than a single click, but with a substantial payoff in control.

The minimal setup, maximum control

Why should business owners consider this path? In our experience, a mild upfront investment of time—potentially 30 minutes—results in perpetual data ownership. Instead of being locked into a system where a developer has access to your information, the setup for tools like agentic OS reduces that gatekeeping period from weeks to mere minutes.

Admittedly, it's a longer process than the one-click sign-in but once done, you have secure ownership and control over your data. It's an approach that, although initially slower, aligns more with the principles of autonomy and privacy. This makes it particularly pertinent in today's AI era, where data is not just king—it's the entire kingdom.

The evolving role of SaaS

Some voices in the industry claim that SaaS, as we know it, is dead. This might be an overstatement, but it raises an important question: should every SaaS product have control over your data? At hmn.plus, we don’t think so. We built our platform believing that the user should retain great ownership over their data. It's our commitment to your autonomy—a pledge that underpins every decision we make in product development.

However, we also understand that for some, ease of use remains paramount and that trusting a developer with your data is an acceptable compromise. We’re exploring solutions for those needs as well, respecting that segment of the market that values seamless access above all.

Conclusion: your choice, your effort

The question of ownership versus convenience isn't a binary decision but a continuum of choice. If real ownership is your priority, the effort—though moderate—is worth it. With hmn.plus and products like agentic OS, you’re empowered to become the custodian of your data, forever.

But if maximum convenience aligns more closely with your current needs, knowing the trade-offs is crucial. The digital landscape thrives on informed decisions. Whichever path you choose, ensure it’s one that aligns with your values and growth strategies. Remember, a one-time setup can lead to lasting empowerment.