Most of our Griffith engagements start the same way: a 20-minute call where the owner describes a workflow we've heard before in shape but never in detail. AI HR assistant is then designed against the detail, not the shape.
Built and supported here - the way a Griffith business would actually use it.
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 Koala Dynamics
With Koala Dynamics
What's different about doing this work in Griffith.
- Griffith is irrigated horticulture and wine in the Riverina, where water, season and freight decide the year.
- Citrus, wine, rice and food processing built on the Murrumbidgee Irrigation Area, with a strong family-business culture. Compliance paperwork, freight coordination and multilingual customer contact are all real daily loads.
We work with teams across Griffith: Griffith CBD · Yoogali · Hanwood · Yenda · Leeton.
Talk to us about this →
How we build AI HR assistant for a Griffith team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Griffith business, so value lands before the build is finished. AI HR and people ops.
Talk to usThe outcome for Griffith teams
The shape of the result for Griffith 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.
FAQ
What's a typical engagement length for Griffith businesses?
Six to twelve weeks for the build, then a short managed-services month while the system goes from "shipped" to "owned by your team". After that you keep us on retainer if you want, or take it from there yourself.
Are there hidden costs we should plan for?
Three to know about: model/API spend (which we set up under your own account, not ours, so you see and control it), any new SaaS subscriptions we recommend, and your team's time during rollout. We surface all three in the quote so there are no surprises.
Do you have proof this works for Griffith 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.
Can you work with our existing systems?
Yes. The default AI HR assistant stack we reach for is Claude, Employment Hero API, BambooHR, Vercel, but we'll bend it around whatever you already run - Xero, HubSpot, Shopify, Cin7, your own in-house apps. The discovery week maps every data source before any build starts.
The honest version of a sales call.
No deck. No discovery doc. Just whether this is worth building and what it would cost.
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.