The version of AI personalisation that building companies still use a year after launch.

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

When a building company asks us about AI personalisation, the first question we put back is the same one every time: which part of your week, if it disappeared, would change how you feel on a Friday? We start the build from that answer.

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

Where most building companies engagements actually deliver value.

  • Builders run multiple sites at once, and the paperwork behind each one grows faster than anyone has time to manage.
  • Variations, supplier orders, and client updates are the admin layer that determines whether a build stays on schedule.
Talk to us about this →

How we build AI personalisation for building companies.

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

Talk to us

How the work runs

The outcome for building companies

What changes for building companies after this lands: the work that used to need a person stays done, the work that needs a person gets done with their attention undivided. Conversion lift of 18-32% over generic site experiences.

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 building company - so the savings start landing before the rest of the build is finished.

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.

Can you walk us through a comparable build?

Yes - on the first call we'll pick the closest engagement we've shipped to what you're describing and walk through the outcome, the headcount and the time it took. Conversion lift of 18-32% over generic site experiences.

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.