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.

AI consultant: costs, value and when to hire

An AI consultant helps a business find, design, and implement practical AI use cases. They are worth hiring when you have a specific workflow to improve, a clear business outcome, and a handover plan so your team can own the system after launch.

For a single automation, a consultant or small agency may charge around $5,000–$20,000 and deliver in 4–8 weeks. That can be a good deal. But the first invoice is not the real test. The real test is whether you still understand, operate, and change the system when the consultant leaves.

What does an AI consultant actually do?

A good AI consultant does not start with tools. They start with the business constraint.

They should ask where work gets stuck, what is repeated often enough to matter, what a mistake would cost, who owns the process today, and what success looks like in operational terms.

That matters because most AI projects do not fail from lack of technology. They fail because the business picked the wrong problem, skipped the messy process work, or built something nobody could maintain.

We built hmn.plus around that lesson. Advice, build work, and day-to-day execution need different responsibilities. If those blur together, the business can end up with a system that acts before anyone has agreed what good looks like.

A serious AI consultant should help you answer:

Which workflow is worth improving first?
What business result should change?
What data, approvals, and human checks are needed?
Who owns the system internally?
What happens when the process changes?

If a consultant jumps straight to a chatbot, dashboard, or automation without this work, be careful. You may be buying enthusiasm with an invoice attached.

When should you hire an AI consultant?

Hire an AI consultant when the project is narrow, painful, and measurable. Do not hire one to make a vague AI problem disappear.

The best engagements usually start with one workflow. For example, a business might want to sort inbound requests, draft first responses, route issues to the right person, or reduce manual checks before an order moves forward. These are concrete jobs. They have owners. They have failure points. They can be tested.

An AI consultant is useful when they compress your learning curve. They help you see what is worth building, what is too risky, and what should stay human. Then they help you create a system your team can understand.

They are less useful when they become the permanent brain of your AI operation. If every change requires the original consultant, you have not gained capability. You have rented it.

What does an AI consultant cost?

The visible cost is the build fee. The hidden cost is ownership.

A single automation can cost around $5,000–$20,000 and take 4–8 weeks. That can be reasonable if the scope is tight and the workflow is valuable.

But you should also expect business-learning cost, support cost, and change cost. If you outsource to an agency, the effort of teaching them your business can equal roughly 10–15% of the contract value. Ongoing support may be around $400–$3,500+ per month, depending on complexity and reliance.

Over 18 months, that support alone can add $7,200–$63,000 before change requests, internal time, or re-explaining your business when people move on.

That is why a cheap first build can become expensive later. The question is not only, what will this cost to launch? It is, what will this cost to own?

The four ways to bring AI into your business

Most owners frame the choice as hire a consultant or do nothing. In practice, you have four options.

1. Hire in-house

An in-house AI hire gives you the best chance of building capability that stays inside the business. The trade-off is cost and time.

A serious hire can cost $220,000+ per year fully loaded, including salary, benefits, recruitment, management time, and overhead. You may also face a 6–12 month ramp before they understand the business deeply enough to choose the right work.

This can make sense if AI is becoming a core operating capability. It is often the wrong first move if you have not yet worked out which problems are worth solving.

2. Outsource to a consultant or agency

This is usually the fastest route. You can get a first build live quickly, and that speed is valuable when your team is stretched.

The trade-off is dependency. The consultant learns enough to deliver the project, then you may pay again every time the workflow changes, the system needs support, or your team needs a new adjustment.

Support is not bad. Maintenance is real work. The problem is support that exists because nobody inside your company can safely operate the system.

3. Commission a custom build

A custom AI system can be right when the workflow is central to the business and basic automation is too limited.

But this is not a light commitment. A proper custom system can run into six figures, with $2,000–$30,000 per year in retraining, tuning, maintenance, and updates as the business changes.

The upside is control. The downside is obligation. If you go custom, you need documentation, ownership, governance, and a plan for what happens when the original builder is no longer involved.

4. Do it yourself

DIY looks free because there is no invoice. It is not free.

Founder time is expensive. Every hour spent testing prompts, connecting workflows, cleaning inputs, and fixing edge cases is an hour not spent on sales, hiring, customers, or cash.

DIY can be useful for learning. It becomes costly when the founder gets trapped in experiments and never turns them into a stable business process.

Compare 18-month cost, not day-one price

Day-one pricing makes the consultant route look obvious. A $12,000 project looks small beside a senior hire. DIY looks free. Custom looks expensive.

Sometimes the consultant is the right answer. But compare the full 18-month picture before you sign.

What will the build, support, and change requests cost?
How much time will your team spend explaining the business?
Who can change the system safely?
What happens when the workflow changes?
Can a non-technical team member operate it?
Can you stop working with the consultant without starting again?

This is where the decision changes. A $10,000 build plus 18 months of support can become a much larger commitment. A DIY experiment can quietly consume months. An in-house hire can be powerful, but only once the role is clear enough to justify the cost.

The right option gives you capability, not just output.

The trap: the consultant becomes the only person who understands it

The most expensive AI projects are not always the ones with the highest invoice. They are the ones that cannot be changed safely.

A provider builds something quickly. It works. Your team starts relying on it. Then a process changes. A customer type changes. A key person leaves. Suddenly nobody inside your company knows why the system behaves the way it does.

You go back to the original builder. Not because they are the best option, but because they are the only option.

That is dependency.

AI makes this sharper because a demo can hide weak operating rules. From the outside, a careful system and a fragile system can look similar. The difference shows up later, when something breaks or a human approval should have stopped an action.

Our view is simple: governance you only talk about is theatre. If the rules are not built into how the work is done, they will not protect the business under pressure.

For an owner hiring an AI consultant, that means one thing. Do not accept a black box. You need to know what the system does, where humans stay involved, what can go wrong, and who is responsible for changes.

What a good AI consultant engagement looks like

A good engagement leaves your business stronger, not just temporarily faster.

Look for these conditions:

One painful workflow, not a broad AI programme with no first step.
A clear business outcome, such as faster routing, fewer manual checks, or better response handling.
A named internal owner who learns the system during the project.
Plain-English documentation that explains the process, assumptions, and failure points.
Human checks where mistakes matter, especially before money, customers, or compliance are affected.
Team training, not just a launch call.
An exit plan so ongoing support is optional, not forced.

The consultant should challenge your thinking before they build. They should make trade-offs visible. They should explain why one workflow is worth doing now and another should wait.

If they are maintaining the system, you should know exactly what they maintain and why.

Red flags when hiring an AI consultant

You do not need to be technical to spot risk. You need to ask ownership questions.

Be careful if a consultant:

Starts with tools before understanding your workflow.
Cannot explain the system in business language.
Offers no documentation or training.
Requires a retainer without defining what support includes.
Builds something only they can modify.
Promises broad AI adoption without choosing a first use case.
Treats approvals and human checks as optional.

The biggest red flag is vagueness. Vague scope becomes vague cost. Vague ownership becomes dependency. Vague success measures become disappointment.

Questions to ask before you sign

Before hiring an AI consultant, ask direct questions:

What exact workflow are we improving first?
What will be true after 8 weeks that is not true today?
What do you need to learn from our team?
What will ongoing support cost after launch?
What can our team change without you?
What documentation will we own?
Who inside our company will be trained?
Where do humans stay in the loop?
What are the known failure modes?
If we stop working together, what happens?

The last question matters most. If the answer is uncomfortable, listen to that discomfort before the contract is signed.

The better goal is ownership

The point is not to avoid AI consultants. The point is to avoid renting your own operating knowledge.

For most SMEs, the right path is staged. Start with strategy. Pick one workflow. Build enough to prove value. Keep the logic visible. Train an internal owner. Then decide whether to expand, hire, outsource support, or build more deeply.

Pay an AI consultant for speed, judgment, and implementation help. But do not pay forever because nobody else knows what was built.

The real win is not the first automation. It is a business that can keep improving after the consultant leaves.