The short version: this is a per-seat question. Microsoft 365 Copilot costs enough per person per year that some of your seats will clear the bar inside a week and others never will, and firms that buy it for everyone are paying for the second group to ignore it. Buy it like you'd buy a ute: for the people whose job needs one.
The cost, in NZ dollars
As at July 2026, list pricing runs USD 20 to 30 a user a month, on top of the Microsoft 365 subscription you already pay for. With the US dollar at about NZD 1.72 in late July 2026, Microsoft 365 Copilot costs roughly NZD 35 to 52 a user a month before GST. For a ten-person firm buying every seat, call it $4,000 to $6,000 a year. That's a mid-sized line item, and it deserves the scrutiny of one.
It sits on top of any Business plan, so you don't need to move to Premium first. What each Business tier buys you is a separate question with its own wrong assumptions, covered in the licensing post.
The seat-by-seat test
Copilot's value concentrates in seats that live inside documents, email and meetings all day. Ask one question per person: how much of their week is spent producing or digesting words?
- Seats that clear the bar. Whoever writes your proposals and reports, anyone managing a full inbox of long threads, anyone in back-to-back meetings who owes minutes and follow-ups afterwards. Drafting, summarising and finding things in your own tenant is the product working as designed.
- Seats that rarely do. Work that is process-shaped: entering jobs, moving information between systems, chasing approvals, running the same report every Monday. Copilot can't do a process for you. That work wants automation rather than conversation.
In the 5 to 20 person professional services firms I've sat with, that test lands on a third to a half of the seats. In a trades business it's often just the office.
What people mean when they ask for Copilot
Half the time, the thing a firm wants when it says "we should get Copilot" is one specific job: answer staff questions from our own documents, triage the shared inbox, summarise incoming applications. A per-seat assistant is the wrong shape for a single job. A Copilot Studio agent is built for exactly one job and billed by usage rather than by seat, which for one task at small volume is usually far cheaper. The two products get confused constantly, and the difference is worth two minutes before you buy either. What an agent's usage costs is worked through here.
And sometimes the job needs no AI at all. Data moving between systems on a schedule, approvals that chase themselves, reports that build overnight: plain automation does those cheaper and more reliably than anything with a chat window. If the week's pain is process-shaped, start there.
A sane way to buy it
Pick the three or four seats that clear the words test hardest. Buy Copilot for those, and set a calendar note for one month out. At the review, ask each person one question: what did you produce with it this week? People who got value will have specific answers within seconds. If they do, expand to the next tier of seats. If they don't, you've spent a few hundred dollars to learn something true about your firm.
One warning from running this on the Microsoft stack for years: adoption doesn't happen by licence. The seats that get value are the ones shown how it applies to their actual Tuesday, not the ones sent a login. Budget an hour of walking each person through their own work, or the licences quietly become shelfware.
Questions I get about Copilot seats
How much does Microsoft 365 Copilot cost in NZ?
As at July 2026, list price runs USD 20 to 30 a user a month on top of an existing Microsoft 365 subscription. At around NZD 1.72 to the US dollar, that's roughly NZD 35 to 52 a user a month before GST, or about $4,000 to $6,000 a year for ten seats. It's an annual commitment per seat, which is why buying it for everyone at once is the expensive way to find out who uses it.
Is Copilot worth it for a firm of 5 to 20 people?
For some seats, usually yes. For all seats, almost never. The value concentrates in roles that live in documents, email threads and meetings all day. Roles whose work is process-shaped, moving information between systems and chasing approvals, get almost nothing from a Copilot seat, because that work needs automation, not an assistant.
Do I need Microsoft 365 Copilot or a Copilot Studio agent?
They're different products. M365 Copilot is a per-seat assistant across Office apps. A Copilot Studio agent is a purpose-built bot for one job, priced by usage rather than by seat. If what you actually want is one task handled, like answering staff questions from your own documents, an agent or a plain automation is usually the cheaper, better fit.
Get an answer for your own seats
I build on the Microsoft stack for NZ firms and I don't sell licences, so I have no horse in this race. Book a free 30-minute call, tell me who does what, and I'll tell you which seats I'd buy Copilot for, which jobs want an agent or an automation instead, and which want nothing at all.