I set up the right AI tools for your firm, agree with you what they can see, and train your people until it sticks. Then I automate the admin that's left, and you own all of it.
Kove (kove.nz). Firms across New Zealand. I reply within 1 working day.
Illustrative. The jobs are the kind I automate; the names and numbers are made up.
See what I build
What I build
Automation, internal tools and AI.
For owner-operators losing hours each week to quotes, timesheets and chasing payments.
Automations · Job 1042Fri 2:40 pm
Job board · This weekMon 8:14
Inbox · 5 newMon 8:12
Job 1042 · Harper Builders14 Kowhai St · $4,554
Illustrative. One job through the three kinds of tool I build; the names and numbers are made up.
01Workflow automation
The repetitive bits, run end to end.
Quoting, invoicing, follow-ups, data entry. A job comes in, the paperwork happens, and nobody typed anything twice. You see every run, and you can switch it off any time.
Reading PDFs, drafting quotes, sorting the inbox, summarising email. Work off your plate, measured in hours you get back. Copilot and Microsoft 365 AI rolled out with rules and training count too, not just flows. It drafts, you approve: nothing sends or books on its own.
I rebuilt a two-year software project in six weeks.
The original took one to two developers about two years. I rebuilt it to the same spec in six weeks, with a squad of eight AI agents I designed and ran. They did the development. I set the spec, the direction and the review gate.
To be fair about that number, rebuilding to a spec that already exists is easier than working out what the thing should be. The original team had to discover the requirements. I already had them.
8 agents in the squad12 automated workflows50–200 people use it
Illustrative. The screens show how I work; the names and numbers are made up.
01Open build
You see every step of the build.
The code, the logic, the documentation are all visible throughout. One person does the work, accountable from day one.
$ deploy --to production ✓
02NZ-specific
I already know your stack.
Xero, Tradify, ServiceM8, MYOB, Workflow Max. I've integrated with all of them. I won't bill you to learn what your business runs on.
xero · tradify · servicem8 · myob
03No lock-in
You own everything.
Apps, flows, accounts and documentation. The day we finish, it's yours, in your own tenant. No retainer, no dependency.
your-tenant / your-keys / your-call
04Your data
Built in your own Microsoft 365.
I take a copy of your structure, never your records; prototypes run on made-up data, and you decide what any AI tool can see. I set it up that way.
your tenant · schema only · your call
How it works
From first call to handover.
Project · CallThu 10:30 am
Your project · 4 steps
CallThu 10:30 am · 30 min
PlanWorkflow Review · timesheets to invoices
BuildPreview · week 2
HandoverCode, accounts, keys, docs
What happened
step · when
Call Thu 10:30 am · 30 min, no prep
Plan Mon · one page, yours to keep
Build week 2 · tested on real jobs
Handover day 1 · warranty to day 60
Illustrative. One process through the four steps; the names, dates and numbers are made up.
01
Call
A free 30-minute call about how your week runs. No prep needed from you. We find the jobs eating the most hours.
30 minutes · no prep
02
Plan
The Workflow Review: a written plan for the one process worth automating first. What to build, what it saves, what it costs. Useful even if you stop there.
one-page summary · full report · yours to keep
03
Build
I build in the open. Working software in weeks, and you test it on real jobs while it's still easy to change.
working software · weeks
04
Handover
Your code, your accounts, your keys. I train your team, write the docs, and back it with a 60-day warranty.
Kove is new. The work isn't. The enterprise builds below come from my background in the health sector and are anonymised. The rest are tools I built and run in my own business.
You do. Every app, flow and document sits in your own Microsoft 365 tenant under your accounts, and anything custom-coded goes in a repo you own. Nothing about the build depends on me being around. No retainer lock-in by design.
your tenant · your accounts · your repo
02What if you are unavailable?
I fix bugs in what I build free for 60 days after handover. You own every app, flow and the documentation in your own Microsoft 365 tenant, so if I am unavailable any Power Platform person can pick it up.
60-day warranty · fixed at no charge
03Will this replace my staff?
No. I build tools that handle the dull, repetitive work. Your team does less data entry and more of the work that actually needs a human.
less data entry · more of the work that needs a human
04How long does it take?
A Workflow Review wraps up inside a fortnight. A full build is 4–8 weeks from kick-off to handover. I ship something working early and improve it on real use. I do not start with a 60-page slide deck.
review: inside a fortnight · build: 4 to 8 weeks
The safety net
Low risk by design.
Pay half on acceptance
50% to start, 50% only once you've accepted the work. If you don't accept it, you don't pay the rest.
60-day warranty
Anything that breaks in the first 60 days, I fix at no charge. No arguing about whose fault it was.
No lock-in, ever
Source code, accounts, credentials, hosting are all yours. The day we finish, you could never speak to me again and it keeps running.
Show me the part of the week you dread.
Bring the job that eats your week to a free 30-minute call. Got a quote from someone else? I'll review it free, in writing, within two working days, and if the right answer is to change nothing, I'll tell you that too.
