The reason we take on work in Oamaru is that the businesses here tend to be sharper about what they want than the brief lets on. AI personalisation for an Oamaru team almost always ends up looking different to AI personalisation for a downtown Auckland one.
AI personalised CX - wired into an Oamaru workflow, not bolted on the side.
Our goal is to give Oamaru businesses a three-day weekend, so people can spend more time with their families and the people they love :)
What AI personalisation actually does
Every customer sees the right product, message, and offer - based on what they've bought, browsed, and asked. Built on first-party data, no creepy tracking required.
- 01 Per-customer recommendations across web and email
- 02 Dynamic landing pages tailored to traffic source
- 03 Lifecycle messaging triggered by real behaviour
- 04 GDPR + NZ Privacy Act compliant by default
Built on: Claude Vercel Edge Postgres Klaviyo
Without Kiwi Dynamics
With Kiwi Dynamics
What you actually get
Every engagement is scoped and quoted up front. This is what is in the box.
- A working pilot, in productionNot a prototype on someone's laptop. The first slice of AI personalisation runs against real work within weeks.
- Your data stays yoursIt runs on your accounts and your tools. If we part ways you keep the system and everything in it.
- The workflow mapped before codeWe write down what good looks like for Oamaru businesses first, so nobody is guessing at handover.
- Support after it landsThe people who built it stay reachable when the business changes shape around it.
How AI personalisation compares
The two things most businesses do instead, and where each one runs out.
| Hiring for it | An off-the-shelf tool | Kiwi Dynamics | |
|---|---|---|---|
| Fit to how you work | Fits perfectly, costs a salary | You bend your process to suit the tool | Built around the workflow you already run |
| Time to something useful | Immediate, and permanent | Quick to switch on, slow to make fit | A working slice in weeks, then hardened |
| Who owns the data | You do | The vendor, on the vendor's terms | You do, in your own accounts |
| When it breaks | That person sorts it, if they are in | A support queue and a ticket number | The people who built it |
| What it costs | A salary, every year, forever | Per seat, forever, used or not | Scoped and quoted up front |
The pattern across Oamaru engagements we've shipped.
- North Otago blends historic tourism with strong primary industry - AI here is about doing more with the team you can keep.
- Dairy, horticulture, heritage tourism, and a steady local trades sector. AI tools land well when they're practical and quiet.
We work with teams across Oamaru: Oamaru CBD · Weston · Waitaki · Kurow · Hampden.
Talk to us about this →
How we build AI personalisation for an Oamaru team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Oamaru business, so value lands before the build is finished. AI personalised CX.
Talk to usHow the work runs
- Find the one workflowWe look for the job costing Oamaru businesses the most hours or the most leads, and deliberately ignore the rest for now.
- Ship a working sliceA narrow version goes into production in weeks, against real work, so the value shows up before the build is finished.
- Prove it, then widenWe measure it against what the work cost before. If it does not pay for itself, we say so rather than scaling it.
- Harden and hand overLogging, fallbacks and a real handover, so it keeps running when we are not in the room.
The outcome for Oamaru teams
Conversion lift of 18-32% over generic site experiences. For Oamaru teams, that almost always shows up as fewer interruptions and a calmer week, not a dashboard chart.
Not your typical AI agency.
Honest about what AI can and cannot do
Ships the one workflow that pays for itself
Hours given back, never the size of the invoice
*Every engagement is scoped and quoted up front. Results vary by workflow and business.
FAQ
How fast could we have AI personalisation in production?
Eight to ten weeks for most Oamaru businesses. Faster if your data is in good shape and slower if we're untangling a legacy integration first. We'll give you a realistic number on the scoping call rather than the optimistic one.
What's the smallest engagement you'd take on?
A two-week paid discovery for Oamaru businesses that aren't sure whether the build is worth doing at all. You get a one-page write-up of what we'd build, what we'd skip, and what it would cost. About 30% of those discoveries end with us recommending you don't proceed.
Has this actually shipped for a real Oamaru?
Yes. Conversion lift of 18-32% over generic site experiences. We'll share comparable engagements on the call.
What if our Oamaru doesn't have any data ready?
Most don't. Getting the data into shape - ingestion, cleaning, the lightweight contracts you need before any model is useful - is part of the engagement. For AI personalisation specifically, we typically run that work on Claude, Vercel Edge, Postgres, Klaviyo and assume messy starting conditions from day one.
Talk to us about this
Tell us what you're trying to do and we'll reply with how we'd build it - no obligation.