AI personalised CX, built for businesses operating in Rotorua.

Our goal is to give Rotorua businesses a three-day weekend, so people can spend more time with their families and the people they love :)

Most of our Rotorua engagements start the same way: a 20-minute call where the owner describes a workflow we've heard before in shape but never in detail. AI personalisation is then designed against the detail, not the shape.

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

What you actually get

Every engagement is scoped and quoted up front. This is what is in the box.

How AI personalisation compares

The two things most businesses do instead, and where each one runs out.

 Hiring for itAn off-the-shelf toolKiwi Dynamics
Fit to how you workFits perfectly, costs a salaryYou bend your process to suit the toolBuilt around the workflow you already run
Time to something usefulImmediate, and permanentQuick to switch on, slow to make fitA working slice in weeks, then hardened
Who owns the dataYou doThe vendor, on the vendor's termsYou do, in your own accounts
When it breaksThat person sorts it, if they are inA support queue and a ticket numberThe people who built it
What it costsA salary, every year, foreverPer seat, forever, used or notScoped and quoted up front

What's different about doing this work in Rotorua.

  • Rotorua is forestry, tourism, and a strong Māori-led economy - AI here works hardest when it respects relationships first.
  • From iwi-owned enterprises to international tour operators, Rotorua businesses want AI that handles peaks without flattening the manaakitanga.

We work with teams across Rotorua: CBD · Ngongotaha · Lake Tarawera · Reporoa · Tokoroa.

Talk to us about this →

How we build AI personalisation for a Rotorua team.

We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Rotorua business, so value lands before the build is finished. AI personalised CX.

Talk to us

How the work runs

The outcome for Rotorua teams

Conversion lift of 18-32% over generic site experiences. For Rotorua 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

Start a conversation

*Every engagement is scoped and quoted up front. Results vary by workflow and business.

How much is not automating costing you?

Nine hours a week of admin is 468 hours a year. With Kiwi Dynamics, that drops to about 52.

Try the calculator

*Based on 9 hours a week of admin at Kiwi Dynamics' typical 80% automation rate. Your number may vary, the calculator uses your own.

FAQ

When does AI personalisation actually pay back?

Inside the first quarter, in our experience. We pick the first slice specifically because it's the highest-leverage workflow for a Rotorua - so the savings start landing before the rest of the build is finished.

How do you price AI personalisation engagements?

Fixed-scope pilots first, then either project pricing or a small monthly retainer for the ongoing work. No long lock-ins, no 18-month black-box deals. Most Rotorua businesses are surprised how small the first cheque is.

Do you have proof this works for Rotorua businesses?

Direct case study: Conversion lift of 18-32% over generic site experiences. Happy to walk you through full numbers on a call.

Will this run on our own infrastructure?

Yes, where it makes sense. AI personalisation can sit entirely in your cloud account, with model calls routed through endpoints you control. We default to Claude, Vercel Edge, Postgres, Klaviyo but the architecture supports your existing platform choices.

Ready to talk specifics?

Scroll up - the form's right there.

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.