What We Do
How we
can help.
Four ways we work with New Zealand businesses. Most engagements start with one of them and grow into another—and we'll tell you if what you need is none of them.
01 — Capability
AI Strategy & Policy
Before anything gets built, it's worth knowing what's worth building. We look at how your organisation actually works, find where AI would genuinely help, and say plainly where it wouldn't—then write it down in language the whole team can act on.
What's involved
- An honest assessment of where AI fits your operations, and where the claims don't survive contact with how you actually work.
- A prioritised roadmap: what to do first, what to leave alone, and a realistic sense of what each step costs.
- A written AI use policy—what staff may and may not put into public tools, how that sits with the Privacy Act 2020, and who signs off on what.
- Tool selection that isn't tied to a vendor. We don't take commissions, so the recommendation is just the recommendation.
Usually right when
- >Someone has asked what your AI plan is and there isn't one yet.
- >Staff are already using AI tools, without guidance on what's safe to put in them.
- >You need a position you can defend to a board, an auditor or a client.
What's involved
- Natural conversation—not a phone tree, and not a voicemail box someone has to work through later.
- Books into the calendar you already use and writes the details to your CRM while the call is still happening.
- Answers your real frequently asked questions, in your tone, with the answers you'd give.
- Recognises an urgent call and escalates it to a human instead of handling it itself.
Usually right when
- >Calls arrive while you're on the tools, with a client, or outside office hours.
- >The phone is the main way work comes in, and a missed call is a lost job.
- >Someone is spending their day on the same handful of questions.
What's involved
- Enquiries land as properly filled-in records with the follow-up already assigned, instead of being re-typed later or not at all.
- Job details flow into your accounting or job-management system once, so the second copy can't drift from the first.
- The weekly report someone assembles by hand gets collected, combined and delivered on a schedule.
- Bookings, confirmations and reminders run unattended, without anyone watching the diary.
Usually right when
- >The same information gets typed into two or more systems.
- >Something important depends on one person remembering to do it.
- >Your tools each work well on their own, but nothing talks to anything else.
What's involved
- One tightly-scoped thing: an internal dashboard, a calculator, a form-driven workflow, a client-facing portal.
- Built on your real data rather than a demo set, so you can tell straight away whether it actually works.
- Handed over as something you can keep and run, with the code and the documentation that goes with it.
- A clear decision at the end—extend it, rebuild it properly, or walk away having spent days instead of a quarter.
Usually right when
- >You want to test an idea before committing real budget to it.
- >A spreadsheet has quietly outgrown itself and become a system of record.
- >An off-the-shelf product almost fits, but not quite, and the gap is the expensive part.
Not sure which one?
That's a normal place to start.
Most people arrive describing a problem rather than a service. A short conversation is usually enough to work out which of these fits, whether it's worth doing at all, and what it would take. If the answer is that you don't need us yet, we'll say so.