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's role in future economic development and exploration

The role of AI in economic shifts

As AI technologies progressively take on roles traditionally held by humans, we're witnessing a substantial shift in economic development. Businesses deploy AI for automating processes that span from data management to customer service. Currently, most automation aims to streamline operations and cut costs. But this isn't the end goal. Instead, the question is: What happens when AI handles nearly everything?

The concern often heard is that wealth becomes concentrated among those who own these technologies. Community-driven economic engines might falter, creating a landscape where a few control the many. This possibility isn't lost on us at hmn.plus. We've built our solutions with these dynamics in mind, knowing that while AI provides efficiency, it also demands careful management.

Guided by wisdom — harvested and applied

Those with foresight recognize that AI's role isn't just to liberate resources and time. Instead, it empowers us to tackle more challenging problems. Historically, whenever a group amassed wealth, they didn't just keep hoarding it—they sought out new ventures. Wise people manage these technologies, continually applying their hard-earned insights to foster long-term benefits, steering AI towards advancements.

Pushing the boundaries of human exploration

Economic development through AI doesn't signify an end to human experience. Far from it. When AI takes on repetitive tasks, human beings are freed to explore uncharted territories. This involves solving medical mysteries, advancing theoretical physics, and working towards off-world discoveries. Such endeavors exemplify man's innate quest for more.

Consider space exploration. Many with extensive resources will look beyond Earth for answers, seeing endless potential beyond the stars. A renaissance of risk-taking emerges—those willing to gamble where few dare become invaluable.

The new economy of experiences

When wealth accumulates, the thirst for new experiences grows. Whether through virtual realms or deep space, the appetite for adventure reignites time and time again. Historically, kingdoms funded groundbreaking expeditions. Similarly, today's digital moguls may chart courses to distant planets or immersive virtual landscapes.

This evolving economy doesn't eliminate risk; it simply shifts the framework. Risk-takers become assets themselves. Entire industries will cater to those who say, "What if?" and "Why not?" It's a historical echo—wealth funneling into exploration and discovery. The human journey, despite AI’s influence, refuses to be static or confined.

The reassurance of history's lessons

As AI reshapes the economy, echoing patterns from our past offer assurance. When the familiar economic engines change gears, we adapt. Our task is to ensure AI is part of a broader solution—one that paves the way for human potential. In kai-zen tradition, it’s not about leapfrogging but consistently improving, knowing that each step, no matter how small, is pivotal.

So, the crux isn't about battling against AI-driven changes—they’re inevitable. It's about steering these changes to complement human tenacity and vision. Every era has faced its giants. For us, AI is both a tool and a challenge. Let's use it wisely, paving the runway to the stars and beyond.