Canterbury · Applied AI

Built and supported here – the way a Timaru business would actually use it.

We've worked with enough operators in Timaru to know that the brief that arrives in our inbox is rarely the brief that ends up shipped. The first thing we do on any AI personalisation project is sit with your team for a day before we propose anything.

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

Canterbury

What's different about doing this work in Timaru.

  • South Canterbury runs on port logistics, food processing, and dairy – AI here is about coordinating shifts and shipments with fewer phone calls.
  • Port of Timaru, food processors, dairy, and a wide trades sector. AI tools that integrate with existing ERP and POS land best.

We work with teams across Timaru: Timaru CBD · Marchwiel · Highfield · Geraldine · Temuka · Pleasant Point.

Talk to us about this →

How we build AI personalisation for a Timaru team.

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

Talk to us

The outcome for Timaru teams

The shape of the result for Timaru teams: Conversion lift of 18-32% over generic site experiences. Built on Claude, hardened with the rest of the stack as it scales.

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.

Questions

FAQ

What's a typical engagement length for Timaru businesses?

Six to twelve weeks for the build, then a short managed-services month while the system goes from "shipped" to "owned by your team". After that you keep us on retainer if you want, or take it from there yourself.

Do you do hourly billing or fixed price?

Fixed price for the pilot, every time. After that it's your call – fixed price per milestone or a small monthly retainer for ongoing iteration. We don't run open-ended T&M because it disincentivises us from finishing.

Has this actually shipped for a real Timaru?

Yes. Conversion lift of 18-32% over generic site experiences. We'll share comparable engagements on the call.

Can you work with our existing systems?

Yes. The default AI personalisation stack we reach for is Claude, Vercel Edge, Postgres, Klaviyo, but we'll bend it around whatever you already run – Xero, HubSpot, Shopify, Cin7, your own in-house apps. The discovery week maps every data source before any build starts.

Ready to talk specifics?

Scroll up – the form's right there.

Get in touch

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.