Kerikeri sits in a regional context that genuinely changes the build. Connectivity assumptions, the rhythm of the working week, the proximity of your team to your customers - none of those are details our default AI HR assistant template would catch.
AI HR assistant that lives in your stack, not on a vendor's roadmap. Shipped from Northland.
Our goal is to give Kerikeri businesses a three-day weekend, so people can spend more time with their families and the people they love :)
What AI HR assistant actually does
An AI HR assistant trained on your policies, awards, and the Employment Relations Act. Answers staff questions, drafts contracts, screens applicants, and flags HR risk - without replacing your people lead.
- 01 Answers leave, pay, and policy questions 24/7
- 02 Drafts contracts, warnings, and PIPs from templates
- 03 Screens CVs against role criteria with reasoning
- 04 Flags ER risks before they become disputes
Built on: Claude Employment Hero API BambooHR Vercel
Without Kiwi Dynamics
With Kiwi Dynamics
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 HR assistant 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 Kerikeri businesses 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 HR assistant 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 |
What we keep seeing in Kerikeri.
- Kerikeri is horticulture, tourism, and a fast-growing lifestyle community - AI here is about connecting orchard, paddock, and storefront.
- Kiwifruit, citrus, and a steady hospitality scene serving the Bay of Islands. AI tools that work in low-signal areas land best.
We work with teams across Kerikeri: Kerikeri central · Waipapa · Kaitāia · Russell · Paihia · Mangonui.
Talk to us about this →
How we build AI HR assistant for a Kerikeri team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Kerikeri business, so value lands before the build is finished. AI HR and people ops.
Talk to usHow the work runs
- Find the one workflowWe look for the job costing Kerikeri businesses 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 Kerikeri teams
HR enquiries drop 65% in the first month - leaders get their week back. For Kerikeri 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
*Every engagement is scoped and quoted up front. Results vary by workflow and business.
FAQ
How quickly can we see something running?
Week three for a clickable internal demo against real data. Week six for a slice your team can actually use. We hold ourselves to those numbers because they're what stops a project drifting into "endless discovery".
What's the smallest engagement you'd take on?
A two-week paid discovery for Kerikeri businesses that aren't sure whether the build is worth doing at all. You get a one-page write-up of what we'd build, what we'd skip, and what it would cost. About 30% of those discoveries end with us recommending you don't proceed.
Anyone else in this space using AI HR assistant?
Plenty. HR enquiries drop 65% in the first month - leaders get their week back. The interesting question is rarely "does it work" - it's "is your team ready to use the output." That's what we'd scope on the call.
What tools do you build AI HR assistant on?
For AI HR assistant we usually reach for Claude, Employment Hero API, BambooHR, Vercel. We're tool-agnostic at heart - we pick what your Kerikeri team can actually run after we hand the build over, not what looks good on a vendor sticker.
One short call.
Tell us what you're trying to fix. We'll come back inside a working day.
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.