AI personalisation that fits a roofing company's week, not the other way around.

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

AI personalisation is overhyped at the macro level and underused at the workflow level. For a NZ roofing company, that gap is where the actual ROI lives - and where most of our work happens.

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 we keep hearing from NZ roofing companies.

  • Roofers quote off photos, chase weather windows, and juggle insurance jobs that all move at different speeds.
  • Fast, accurate quoting from a photo is the single biggest lever for a roofing business's close rate.
Talk to us about this →

How we build AI personalisation for roofing companies.

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

Talk to us

How the work runs

The outcome for roofing companies

The shape of the result for roofing companies: 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.

FAQ

How long does AI personalisation take to ship for roofing companies?

We aim for a working pilot inside 4-6 weeks - narrow scope, real roofing companies data, measurable outcome. From there it's another 6-8 weeks of hardening before you'd consider it production. Full rollouts (multiple sites, multiple teams) typically land in 3-4 months.

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 roofing companies are surprised how small the first cheque is.

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.

Who owns the code and the model setup?

You do, on delivery. We deploy AI personalisation into your own cloud account where possible, with the model setup, prompts, evals and integration code all checked into a repo you own. Claude sits in your account too - we don't operate it from ours.

Worth a conversation?

Even if you don't end up working with us, you'll leave the call knowing what's worth building.

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.