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.

Why video creativity is inherently human

The human touch in video content creation

You're probably inundated with promises of AI taking over content creation. It's fast, efficient, and always evolving. However, there's one thing it can't replicate: the human ability to create culturally and emotionally resonant content. When we talk about producing compelling video content, AI can assist, but it cannot replace our intrinsic creativity and marketing judgment.

AI: A powerful assistant, not a creator

We built our AI tools to help speed up tasks, from ideation to editing support. They're fantastic for execution and efficiency. For instance, AI can generate a range of ideas in minutes or repurpose existing content quickly. It can even suggest edits that save hours. But the final judgment about what feels culturally relevant or emotionally impactful still depends on human insight.

Cultural relevance is human work

AI lacks the nuanced understanding of cultural trends and emotional undertones. It's our judgment that determines if a video will resonate with its audience or fall flat. A marketing piece that truly engages is one that understands and speaks to cultural context. That understanding can't be replicated by lines of code. We consider the subtleties, the shared experiences, the untold emotions that make content resonate.

Emotional resonance: Beyond algorithms

Have you ever felt moved by a video? That emotional pull doesn’t come from perfectly executed edits or algorithmic spite. It's from the human touch—the nuanced storytelling, the choice of music, the intentional pacing. These decisions are grounded in emotional intelligence, not computational logic. Our senses guide us to create videos that touch hearts, sparking connections that data can't capture.

Brand-right content is more than data

Creating brand-right content requires deep understanding of a brand’s ethos and audience. We know our clients' values and their customers' perspectives. Sure, AI can analyze metrics and predict trends, but determining whether a video aligns with a brand’s unique voice requires human taste. Our experience guides us to tailor content that feels authentic and strategic.

The limits of AI in strategic sharpness

Strategy in content creation is not just a sequence of calculated moves. It’s the intuition about when to follow rules and when to break them. It’s recognizing an opportunity that others might not see. AI can support the groundwork—testing variations and analyzing results—but the strategic leap, that comes from us. It’s the product of our experience and foresight.

Where AI and humans meet in creation

No doubt, AI is a remarkable tool in our toolkit, brilliantly enhancing our productivity and expanding our potential. But in the arena of creativity, cultural exchange, and emotional impact, human touch remains irreplaceable. By combining our human taste with AI's capabilities, we craft video content that's not just seen, but felt.

Video content creation, at its core, is about connection. And connection is uniquely human territory.