The honest read on AI for desktop publishers in NZ and Australia.

Every desktop publishers team we've worked with has a different definition of "broken".

Office and Administrative SupportBuilt in New ZealandProduction AI, not slidewareHours back, not headcountOffice and Administrative SupportBuilt in New ZealandProduction AI, not slidewareHours back, not headcountOffice and Administrative SupportBuilt in New ZealandProduction AI, not slidewareHours back, not headcountOffice and Administrative SupportBuilt in New ZealandProduction AI, not slidewareHours back, not headcount

By the numbers

Canada's overall AI usage sits at 4.37x its expected level, with Singapore leading at 5.53x.

Adoption is already well ahead of the curve, and the edge goes to whoever turns it into a concrete workflow first.

Talk to us

0.16% of all Claude.ai conversations map to this kind of work (Anthropic Economic Index, March 2026).

Start a conversation

On the tools or running at scale, the admin still eats the week :)

Quotes with GST, consent paperwork, LBP records and health and safety logs: the admin every New Zealand trade business carries.

Start a conversation

*Illustrative example based on nine hours a week of admin. Actual results vary by workflow and business.

If we build the right slice first, Desktop Publishers feel the difference inside the first month. 0.16% of all Claude.ai conversations map to this kind of work (Anthropic Economic Index, March 2026) Kiwi Dynamics

What changes for desktop publishers week to week

Desktop Publishers sits within Office & Administration, one of the sectors we build production AI for.

Draft and answer routine email
Move data between systems
Schedule and chase follow-ups
Generate documents from templates

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

Start a conversation

*Every engagement is scoped and quoted up front. Results vary by workflow and business.

How the work runs

We find the one workflow costing Desktop Publishers the most hours, ship a working slice into production in weeks, prove it pays for itself, then harden it and hand it over.

To start, tell us about your week

Straight answers

Who owns the code and the model setup?

You do, on delivery. We deploy AI into your own cloud account where possible, with the model setup, prompts, evals and integration code all checked into a repo you own. Draft and answer routine email sits in your account too - we don't operate it from ours.

Do you have proof this works for Desktop Publishers?

Direct case study: 0.16% of all Claude.ai conversations map to this kind of work (Anthropic Economic Index, March 2026) Happy to walk you through full numbers on a call.

How long does AI take to ship for Desktop Publishers?

We aim for a working pilot inside 4-6 weeks - narrow scope, real Desktop Publishers data, measurable outcome. From there it's another 6-8 weeks of hardening before you'd consider it production. Full rollouts (multiple sites, multiple teams) typically land in 3-4 months.

Can it keep track of ACC levies?

Yes. ACC work levies are set by the classification unit your work falls under, and self-employed people are invoiced after filing their tax return.

Can it remind us about the annual return?

Yes. Every company must file an annual return with the Companies Office each year, separate from its tax return.

Let's chat

Start

Contact us

Tell us what you're trying to do and we'll reply with how we'd build it, no obligation.