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.

Secure Credentials in Multi-Tenant AI Deployments

Multitenant AI deployments: A closer look at credential security

At hmn.plus, we've embraced the multifaceted world of multi-tenant AI deployments so businesses can scale effectively. Still, we know there's a common concern—how do we keep each tenant's credentials secure and isolated? This issue isn't trivial. If you're asking these questions, you're not alone.

There's often skepticism when multiple organizations share the same AI infrastructure. The fear is that one organization's API keys or OAuth tokens could leak into another's workflows. Let's cut to the chase—this doesn't happen at hmn.plus, and here's how we make sure of it.

Credential isolation per tenant

Credentials are like the keys to your kingdom, and in multi-tenant environments, keeping these keys secure is paramount. At hmn.plus, we isolate credentials using tenant-specific encryption keys and ensure strict access control. This means each organization's sensitive credentials—be it API keys, OAuth tokens, or service accounts—are encrypted and stored independently.

We've seen numerous systems falter at this stage due to shared storage mechanisms. Our approach prioritizes straightforward separation, making sure there's no accidental cross-pollination between tenants. Your secrets don't leave the vault and only your workflows have the necessary keys to access them.

Governance layer: Your control panel

Every tenant is part of a robust governance model. This ensures each AI agent adheres to specific rules: restricted_to_actors, allowed_tools, and data_classification. Simply put, your AI agents can only see and do what they're authorized for. This governance layer acts as a sentinel, ensuring no rogue agents interfere with others' data or workflows.

We've observed that without a governance layer, unsanctioned access can become a real issue. But with our method, you're always in control. You decide the boundaries of what your AI agents can access, maintaining a secure environment.

Sandboxed workflow execution

Imagine a world where executing one tenant's workflow accidentally triggers another’s. For us, that's unimaginable. Our workflows run in sandboxed environments, each restricted to its tenant's data and configurations.

This isn’t just a technical measure. It's a trust-building exercise. We've architected our infrastructure so each workflow is like an island—no bridges connecting them that shouldn't be there. It’s the essence of keeping interactions between different tenants' data non-existent.

Practical user advice: Staying within your governance rules

You should continue using AI-powered automation confidently. Implement your own governance rules without anxiety over secret leakage or cross-tenant interference. Our system is grounded in the philosophy that security should be invisible.

What does that mean for you? It means you can focus on your zone of genius—leveraging AI to drive your business objectives—while we seamlessly manage credential management and tenant isolation behind the scenes.

The philosophy behind our security

Our philosophy is simple. Secure all the parts, so you can concentrate on strategic outcomes—not the underlying technical challenges. We built this with transparency and user empowerment in mind. You do what you do best; we handle the credential complexities. You're not here to worry about security, and with hmn.plus, you won't have to.

Entrust your processes to our platform and concentrate on sculpting the future with your innovations. After all, that's the benefit of more human per hour automation—where technology is the enabler, not the obstacle.