The reason we take on work in Blenheim is that the businesses here tend to be sharper about what they want than the brief lets on. AI HR assistant for a Blenheim team almost always ends up looking different to AI HR assistant for a downtown Auckland one.
Marlborough · Applied AI
AI HR and people ops – wired into a Blenheim workflow, not bolted on the side.
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
Marlborough
What Blenheim teams tell us when they get on a call.
- Marlborough is wine, aquaculture, and tourism – three industries running on tight margins where AI quickly pays for itself.
- Vineyards, cellar doors, mussel farms, and a thriving cycle-trail tourism economy. AI here means forecasting the season and never missing a booking.
We work with teams across Blenheim: CBD · Renwick · Picton · Havelock · Seddon.
Talk to us about this →
How we build AI HR assistant for a Blenheim team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Blenheim business, so value lands before the build is finished. AI HR and people ops.
Talk to usThe outcome for Blenheim teams
The shape of the result for Blenheim teams: HR enquiries drop 65% in the first month – leaders get their week back. 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
*Every engagement is scoped and quoted up front. Results vary by workflow and business.
Questions
FAQ
How fast could we have AI HR assistant in production?
Eight to ten weeks for most Blenheim businesses. Faster if your data is in good shape and slower if we're untangling a legacy integration first. We'll give you a realistic number on the scoping call rather than the optimistic one.
What's the smallest engagement you'd take on?
A two-week paid discovery for Blenheim 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.
Do you have proof this works for Blenheim businesses?
Direct case study: HR enquiries drop 65% in the first month – leaders get their week back. Happy to walk you through full numbers on a call.
What if our Blenheim doesn't have any data ready?
Most don't. Getting the data into shape – ingestion, cleaning, the lightweight contracts you need before any model is useful – is part of the engagement. For AI HR assistant specifically, we typically run that work on Claude, Employment Hero API, BambooHR, Vercel and assume messy starting conditions from day one.
One reply, one direction.
We don't run sequences or follow-up automation. One useful answer, one decision on your side.
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.