We've worked with enough operators in Oamaru to know that the brief that arrives in our inbox is rarely the brief that ends up shipped. The first thing we do on any AI fraud detection project is sit with your team for a day before we propose anything.
AI fraud + anomaly, built for businesses operating in Oamaru.
Our goal is to give Oamaru businesses a three-day weekend, so people can spend more time with their families and the people they love :)
What AI fraud detection actually does
Pattern-watching AI for refund abuse, chargebacks, fake reviews, employee fiddles, and odd supplier invoices. Flags weirdness early - before it's a real problem.
- 01 Learns your normal patterns and flags outliers
- 02 Daily anomaly report, not a constant alert flood
- 03 Explainable scoring so you can act with confidence
- 04 Integrates with Xero, Shopify, and POS systems
Built on: Claude DuckDB Postgres 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 fraud detection 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 Oamaru 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 fraud detection 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's different about doing this work in Oamaru.
- North Otago blends historic tourism with strong primary industry - AI here is about doing more with the team you can keep.
- Dairy, horticulture, heritage tourism, and a steady local trades sector. AI tools land well when they're practical and quiet.
We work with teams across Oamaru: Oamaru CBD · Weston · Waitaki · Kurow · Hampden.
Talk to us about this →
How we build AI fraud detection for an Oamaru team.
We scope narrow, ship a working pilot, then harden it into production. The first slice is the highest-leverage workflow for your Oamaru business, so value lands before the build is finished. AI fraud + anomaly.
Talk to usHow the work runs
- Find the one workflowWe look for the job costing Oamaru 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 Oamaru teams
The shape of the result for Oamaru teams: Recovers 3-5x its cost in caught fraud within 6 months. 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
When does AI fraud detection actually pay back?
Inside the first quarter, in our experience. We pick the first slice specifically because it's the highest-leverage workflow for an Oamaru - so the savings start landing before the rest of the build is finished.
How do you price AI fraud detection 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 Oamaru businesses 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. Recovers 3-5x its cost in caught fraud within 6 months.
Will this run on our own infrastructure?
Yes, where it makes sense. AI fraud detection can sit entirely in your cloud account, with model calls routed through endpoints you control. We default to Claude, DuckDB, Postgres, Vercel but the architecture supports your existing platform choices.
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.