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.
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 :)
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.
- 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 building companies 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 |
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.
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 usHow the work runs
- Find the one workflowWe look for the job costing building companies 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 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
*Every engagement is scoped and quoted up front. Results vary by workflow and business.
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.
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.