What Small Businesses in NZ Are Actually Asking Me About AI
Every week I have conversations with small business owners across New Zealand about AI. Trades, health, real estate — the industries differ, but the questions are remarkably consistent.
I am writing this post because I think the questions themselves are useful. If you are asking any of these, you are not alone — and the answers might save you time before we even speak.
"Is this actually going to work for a business like mine?"
This is the first question almost every business owner asks, and it is the right one to start with. They have been burned before by technology that sounded good and delivered poorly.
My honest answer: it depends on what you are trying to do. AI is genuinely excellent at tasks that are repetitive, rules-based, and high-volume. It is less useful for tasks that require deep human judgement, relationship, or novel creative thinking.
For a tradie, the tasks that AI handles well include: generating quotes from standard inputs, sending follow-up messages to customers who have not responded, creating job completion reports, and answering common customer questions outside business hours. For a physio or health practitioner, it includes: client intake forms, appointment reminders and rebooking messages, treatment note templates, and client progress summaries. For a real estate agent: property description drafts, buyer follow-up sequences, market report summaries, and database maintenance.
If your work is primarily relationship-based and requires real-time human judgement, AI is not going to replace that. But the admin around that work? Almost certainly automatable.
"Is it going to be complicated to set up?"
The honest answer to this one is: it can be, but it does not have to be. The complexity of the implementation depends on what you are building and how it fits with the systems you already use.
What I tell clients is this: the goal is not to install something complicated. The goal is to remove something complicated — to take the manual, fiddly, time-consuming work and replace it with something that runs automatically. If the implementation creates more complexity than it removes, it is the wrong implementation.
Most of the things I build with clients are not technically complex. They are well-designed. There is a difference. A well-designed automation feels simple to use because all the complexity is hidden inside it, not exposed to the user.
"Am I going to be dependent on you forever?"
No — and I would not want you to be. The goal of every engagement is for you to understand what has been built, to be able to use it without my involvement, and to be able to make basic changes yourself. I build things you own, not things that evaporate if you stop paying me.
I also document everything. Every workflow I build comes with plain-English documentation that explains what it does, why it is built the way it is, and what to do if something breaks. Dependency is not in my interest and it is not in yours.
"What is it actually going to cost?"
This question deserves an honest answer, not a vague one. My engagement fees vary based on scope, but the tools themselves are typically very affordable — many of the most powerful automation tools cost less than fifty dollars a month. Some are free.
The more useful calculation is: what does it cost not to automate? If a business owner is spending fifteen hours a week on admin, and their time is worth one hundred and fifty dollars an hour, that is over two thousand dollars of value being consumed every week by tasks a machine could handle. Even a relatively expensive implementation pays for itself in weeks.
I am happy to run that calculation with you for your specific situation. It changes the conversation from "is this affordable" to "how quickly does this pay back."
"Is my data safe?"
This is an important question and I respect people who ask it directly. The short answer: it depends on what tools we use and how we configure them.
I do not use your business data to train AI models. I am careful about what data flows through which systems. If you handle sensitive client information — which most health and real estate businesses do — I take that seriously and build workflows that keep sensitive data where it belongs.
I will always explain exactly what data is moving where before we build anything. If you ask me a question about a specific tool and I cannot answer it clearly, I will tell you that rather than give you a vague reassurance.
"Where do I even start?"
This is the question I find most encouraging — because asking it means someone is ready to actually do something, not just think about it.
My answer is always the same: start with the thing that is costing you the most time right now. Not the most impressive thing to automate — the most painful one. Fix that first. Build confidence. Then move to the next one.
If you are not sure what that is, that is what the discovery call is for. We talk through your week, find the biggest drain, and figure out whether there is a clear solution. No jargon, no obligation. Just an honest conversation about your business.
Book a free call if you would like to have that conversation.