AI training for Copilot, Claude and OpenAI. Book your slot now 09 974 2379Already a client?Client PortalGet help now
Belton IT Nexus
Belton · Run / Protect / Improve / BuildView all services ›
Belton · Knowledge, not gatekeepingResource library ›
Belton IT Nexus · Est. 2004 · Newmarket, AucklandAbout us ›
Home/ AI & Copilot/ Build agents

Everyone wants an agent. Almost nobody has picked a job for it.

An agent is not a chatbot with ambition. It is a piece of software that does a job you would otherwise pay a person to do, hands the work back finished, and waits to be told whether it got it right. This page is twenty-four of them worth building, what each one has to reach, what the platforms actually charge, and the honest answer on hosting it yourself. Prices for other people's products are theirs, not ours, and we have printed the date we checked them.

24Agents worth building 5Platforms compared NZ$3.38Per million tokens, from $1,889Build session, per person
First, the definition

Three different things get called an agent.

Only one of them is

The word has been stretched to cover almost anything with a model behind it. The distinction matters because the three cost different amounts, fail in different ways, and answer to different people in your business.

Not an agent

An assistant

Waits to be asked, answers, forgets. Copilot in your Outlook is an assistant. It is genuinely useful and it is priced per seat, because the value scales with how many people are sitting there asking.

Not an agent

An automation

Fires on a trigger and does exactly the same thing every time. Enormously valuable, far cheaper, and the right answer more often than anyone selling agents will tell you. If the rules never change, you want an automation.

This one is

An agent

Given an outcome rather than a script, it works out the steps, uses the systems it has been given, and comes back with the work done and its reasoning shown. You want one when the job needs judgement in the middle, and the judgement is the expensive part.

The honest filter. If you can write the rules down completely, build an automation and spend the difference elsewhere. An agent earns its cost when the input varies, the right answer depends on context, and a person is currently making that call fifty times a week.
The library

Twenty-four agents worth building.

Filter by where they sit

These are not hypotheticals. Each one exists because the manual version of it is already happening somewhere, badly, in a spreadsheet. Size is relative rather than a quoted duration, because the real number is fixed at scoping and not before it.

Medium Finance

The invoice coder

Reads every supplier invoice as it arrives, proposes the account code and cost centre, and puts it in front of a person to approve.

Reaches Xero or MYOBthe accounts inboxSharePoint
Guardrail. It proposes the coding. It never posts to the ledger on its own.
Small Finance

The debtor chaser

Drafts the follow-up on every overdue invoice, in your tone, ranked by what is worth chasing first rather than by what is oldest.

Reaches Xeroemail
Guardrail. Drafts sit in a queue. Nothing reaches a customer until someone sends it.
Small Finance

The reconciliation explainer

Takes the transactions nobody can place and searches two years of history for the ones that looked like them, with the reasoning shown.

Reaches Xerothe bank feed
Guardrail. Explains and suggests. The match itself is still a human click.
Large Finance

The quote-versus-actual checker

Compares what each job was quoted at against what it actually cost to deliver, and tells you which kinds of work quietly lose money.

Reaches the job systemtimesheetsXero
Guardrail. Only as good as the join between systems. Getting the keys right is most of this build.
Medium Operations

The job sheet reader

Turns a photographed, scanned or handwritten job sheet into a structured record, and asks a human about anything it could not read.

Reaches the job systema phone cameraSharePoint
Guardrail. Low confidence must route to a person, not resolve to a best guess.
Medium Operations

The supplier price watcher

Reads supplier price lists as they land, flags exactly what changed, and works out what the change does to your margin before you find out at invoicing.

Reaches the purchasing inboxyour price book
Guardrail. Never let it update a price book directly. Changing sell prices is a decision.
Small Operations

The exception triager

Reads carrier and supplier notifications, and separates the ones a customer genuinely needs to hear about from the noise.

Reaches emailthe order system
Guardrail. Draft the customer message. Do not send it automatically.
Large Operations

The procedure writer

Drafts a written procedure from a recording of someone actually doing the task, then re-checks it each quarter and flags the steps that no longer match reality.

Reaches SharePointscreen recordingsthe documentation system
Guardrail. A procedure nobody approved is not a procedure. Publication stays a human step.
Small Sales

The enquiry qualifier

Reads every inbound enquiry, works out who the company is, and drafts both the reply and the suggested next step before anyone has opened it.

Reaches the website formsemailthe CRM
Guardrail. Enrichment from public sources only, and the draft is a draft.
Medium Sales

The proposal first-drafter

Assembles a first draft from your own previous proposals and the notes from the call, so the blank page stops being the reason quotes go out late.

Reaches the CRMpast proposalsmeeting notes
Guardrail. Pricing must come from the price book, never from a previous proposal it happened to read.
Medium Sales

The CRM housekeeper

Finds the duplicates, the records owned by someone who left, and the opportunities that have not moved in a year, and proposes the fix for each.

Reaches the CRM
Guardrail. Merges and deletes are proposals. Bulk edits from an agent are how a CRM gets ruined in one afternoon.
Large Sales

The tender mapper

Reads the tender, maps every requirement to the evidence you already hold, and tells you plainly which ones you cannot currently answer.

Reaches the tender documentyour policy setpast submissions
Guardrail. The value is in the honest gap list. An agent that fills gaps with plausible text is a liability.
Medium People

The onboarding co-ordinator

Turns a start date into the whole checklist, raises the requests across every system, and chases the ones nobody has done by Friday.

Reaches the HR systemMicrosoft 365the ticket system
Guardrail. It can raise access requests. Granting the access stays with the approver.
Small People

The policy answerer

Answers staff questions from your actual policies, quotes the clause it used, and says so plainly when the policy does not cover the question.

Reaches SharePointTeams
Guardrail. Must cite, and must be able to say it does not know. A confident wrong answer on leave or conduct is worse than no answer.
Small People

The timesheet checker

Flags the timesheets that do not look like the person’s normal pattern, before payroll rather than after it.

Reaches the time systempayroll
Guardrail. Flags to a manager. This one never messages the employee.
Small People

The interview structurer

Turns everyone’s scattered interview notes into the same scorecard, so candidates are actually compared on the same things.

Reaches the ATS or a shared drive
Guardrail. It structures what the panel said. It does not score or rank candidates.
Medium IT & security

The alert triager

Takes a security alert, gathers the context from every other system that saw the same device or account, and writes the short summary of what it actually is.

Reaches the monitoring platformthe endpoint toolsthe ticket system
Guardrail. Isolating a device or disabling an account is never the agent’s call.
Medium IT & security

The access reviewer

Lists who can currently reach what, and flags the access that does not match the job the person actually does.

Reaches Microsoft 365the file serverthe line-of-business systems
Guardrail. Read-only. Removing access is a change with a rollback plan behind it.
Medium IT & security

The licence reconciler

Compares what you are billed for against what is actually assigned, and what is assigned against what anyone has used this quarter.

Reaches Microsoft 365the billing export
Guardrail. Reducing a licence count can breach a contract minimum. It reports. You decide.
Large IT & security

The documentation gap finder

Compares what you are being billed for against what is actually documented, and surfaces the things running in your business that nobody has written down.

Reaches the documentation systemthe billing datathe monitoring platform
Guardrail. Findings belong in a dated report, never written silently into a live document.
Medium Legal & risk

The contract register builder

Reads the contracts you already signed and pulls the dates, notice periods, liability caps and auto-renewals into one register you can actually search.

Reaches the contract folderSharePoint
Guardrail. Every extracted term links back to the clause it came from, so it can be checked.
Small Legal & risk

The renewal early warning

Tells you a notice period is closing while you still have time to do something about it, rather than the week it renews.

Reaches the contract registercalendars
Guardrail. Warns early and warns twice. Silence is the failure mode that matters here.
Large Legal & risk

The privacy request mapper

Works out where one person’s data actually lives across your systems, so a privacy request is a task rather than a fortnight.

Reaches Microsoft 365the CRMthe file server
Guardrail. Under the Privacy Act you have 20 working days. Build this before you need it, not during.
Large Legal & risk

The incident timeline builder

Assembles a defensible chronology from logs, tickets and email when something has gone wrong and the question is what happened when.

Reaches the monitoring platformthe ticket systememail
Guardrail. Evidence handling matters. This one is built to preserve, never to tidy.
Yours is not on the list?
Good. The list is the obvious ones, and the obvious ones are rarely the most valuable thing in a particular business. Describe the job and we will tell you honestly whether it is an agent, an automation, or something you should not build at all.
Describe the job
The platforms

What to build it on, and what each one really charges.

Vendor prices in NZD, checked August 2026

Every price in this section belongs to the vendor, not to us. They move without notice, and one of them moved during the week this page was written. Two of them are shown exactly as the vendor publishes them in New Zealand dollars. The rest are billed in US dollars and converted here at NZ$1.69 to the US dollar as at 28 August 2026, which means those ones drift with the exchange rate and the card is still charged in USD. Each card says which it is. Check the vendor's own page before you commit to a number.

Microsoft Copilot Studio

Hosted
NZ$323.60 per monthMicrosoft's New Zealand list price for a 25,000 credit pack, about 1.3 cents a credit, or pay as you go with no commitment
Vendor’s own New Zealand list price
Where it wins

Agents that live where your people already are, inside Teams and Microsoft 365, working on your SharePoint and Graph data with the identity and permissions you already run.

What bites

You are billed per credit, so a popular agent gets expensive quietly rather than loudly. What it can reach is bounded by what the connectors expose, and that boundary is where most projects meet their surprise.

Vendor pricing

Microsoft 365 Copilot

Hosted
NZ$48.50 per user per monthMicrosoft's New Zealand list price, paid yearly, before GST; the lower promotional rate closed on 30 June 2026
Vendor’s own New Zealand list price
Where it wins

Helping individual people inside the apps they already have open. It is the per-seat assistant layer across Word, Excel, Outlook and Teams.

What bites

It is an assistant, not an agent platform. It waits to be asked. If you want something that runs on its own and hands work back finished, this is the wrong line item.

Vendor pricing

Claude, Team and Enterprise

Hosted
About NZ$34 per seat per monthTeam, billed annually, about NZ$42 monthly, 2 to 150 seats; premium seats about NZ$169 to NZ$211; Enterprise from about NZ$34 a seat plus usage
Billed in USD, converted at 1.69
Where it wins

Work that is thinking rather than formatting: long documents read properly, analysis that holds up, and processes built once and reused. It is not tied to one software suite, which is why it handles the jobs that do not fit inside an app.

What bites

It is not natively wired into your tenancy the way a Microsoft product is, so connecting it to your systems is real integration work rather than a checkbox. Billed in USD, so your actual cost moves with the exchange rate.

Vendor pricing

Claude API, build your own

Either
About NZ$3.40 to NZ$42 per million tokensdepending on model and direction; see the table below
Billed in USD, converted at 1.69
Where it wins

An agent you own outright, that runs on your schedule against your systems, with no seat count and no dependence on what a product happens to expose.

What bites

Usage priced, so the bill follows the work rather than the headcount. That is honest but it needs a budget and a ceiling set deliberately at build time.

Vendor pricing

ChatGPT Business and Enterprise

Hosted
About NZ$34 per seat per monthBusiness, billed annually, about NZ$42 monthly, 2 seat minimum; Enterprise is quote only, reported around NZ$76 to NZ$127 a seat with a 150 seat minimum
Billed in USD, converted at 1.69
Where it wins

Broad general capability with the widest staff familiarity, which lowers the training cost of getting a team started.

What bites

Enterprise is quote only and carries a large seat minimum, so the entry point is a procurement exercise rather than a subscription.

Vendor pricing

n8n

Either
About NZ$41 to NZ$1,350 per monthcloud, by execution volume; the community edition is free to self-host on a server costing roughly NZ$9 to NZ$17 a month
Billed in USD, converted at 1.69
Where it wins

The plumbing. Moving work between systems on a trigger, with the steps visible on a canvas that a non-developer can actually follow and audit.

What bites

It orchestrates, it does not think. It is the frame you hang a model on, and the cloud tiers are priced by execution volume, which climbs faster than people expect.

Vendor pricing

A model you host yourself

Self-hosted
About NZ$425 to NZ$1,525 per monthall in for a production GPU server, or roughly NZ$3,400 to NZ$25,400 up front to buy one outright
Billed in USD, converted at 1.69
Where it wins

The genuine constraint cases: data that is not permitted to leave your control, a regulator who wants a straight answer about residency, or volume large enough that per-token pricing stops making sense.

What bites

The hardware is the small number. Published analyses put the maintenance at 10 to 20 engineering hours a month, and below roughly 2 million tokens a day an API is usually cheaper than the box, before anyone is paid to look after it.

Vendor pricing
The question everyone asks second

Should we host it ourselves?

Usually not, and here is why

Host it yourself when

  • Your data genuinely cannot leave your control, and you can point at the clause that says so rather than the feeling that says so.
  • A regulator, an insurer or a tender wants a straight answer about where processing happens.
  • Your volume is high enough that per-token pricing has stopped making sense, which is a much higher bar than it sounds.
  • You already employ someone who will still be there in a year and wants to own it.

Do not host it yourself because

  • It feels safer. Feeling is not a control, and a badly run server you own is worse than a well run service you rent.
  • It looks cheaper. Published analysis puts maintenance at 10 to 20 engineering hours a month, which is the real bill.
  • Someone read that it is cheaper at scale. Below roughly 2 million tokens a day, an API is usually cheaper than the hardware before anyone is paid to look after it.
  • You want control. You can get residency, retention and administrative control on a business plan without owning a GPU.

If you are paying by usage, this is the meter.

NZD per million tokens, converted
ModelInOutWhat it is for
Claude Opus 5 $8.45 $42.25 The hard reasoning. Worth it when being right matters more than the unit cost.
Claude Sonnet 5 $3.38 $16.90 The everyday workhorse. Most production agents should start here.
Claude Haiku 4.5 $1.69 $8.45 High volume, low judgement. Classifying, routing, extracting.

A token is roughly three quarters of a word, counted both going in and coming out. The practical read: an agent that reads a hundred long documents a day costs money you will notice, and one that answers forty short questions a day usually does not. The number that matters is not the rate, it is how much you send it, and that is a design decision made at build time rather than a surprise found at invoicing.

The whole bill

Three layers, and only one of them is ours.

Nothing hidden in the middle

Most agent quotes fail because they price the build and go quiet about the running cost. There are three separate layers here and they behave differently. We itemise all three at scoping, including the ones that are not ours to charge for.

Layer 01

The platform

Per seat or per pack

Paid to Microsoft, Anthropic, OpenAI or whoever else, mostly monthly and mostly per seat. Predictable, and the easiest layer to over-buy. Microsoft bills this in New Zealand dollars; most of the others bill in US dollars, so that part of the bill moves with the exchange rate. We will tell you when you are paying for seats nobody is using.

Layer 02

The usage

Per token or per credit

The one that varies, because it follows how hard the agent is actually working. This is the layer people are surprised by, so it gets a ceiling set at build time and a monthly figure you can see rather than infer.

Layer 03

Building and running it

NZD, fixed at scoping

Ours, and the only layer on this page we set. Fixed in writing before we build. If you want it looked after afterwards that is a monthly plan, priced separately and openly.

What we charge.

NZD, excluding GST
WhatPriceBasis
AI readiness assessment $1,499 from, one off Details
Build session, 4 hours $1,889 per person Details
Monthly AI plan $1,495 from, per month Details
AI bootcamp, 3 days $15,000 fixed Details
A scoped custom build $15k to $250k+ fixed at scoping Details
Uplift work, hourly $269 per hour Details
One thing worth saying plainly. AI work is not covered by a general IT support agreement. Not by a per-user plan, not by a per-device plan, not by a site fee. Building agents, running them, fixing them and answering questions about them sits under an AI plan or is billed as time, and that is deliberate rather than an oversight. It keeps the cost of AI visible to the person paying for it instead of buried in a support line that was never priced for it.

Every figure on this page is in New Zealand dollars. Third-party prices were checked in August 2026: Microsoft’s are its own published NZ list prices, and the rest are converted from USD at NZ$1.69 as at 28 August 2026, so those move with the exchange rate and are still charged to you in USD. Our own prices exclude GST. Usage-based lines vary with how much work the agent does, which is the honest position rather than a flat number that would have to be padded to be safe.

How it actually goes

Five steps, in the order they really happen.

Step two is the one people skip
Step 01

Pick a job that is already annoying someone

Not the most impressive job, the most repetitive one with a clear right answer. If nobody can describe what a good outcome looks like, an agent cannot either, and that is a finding worth having before you spend anything.

You, in an afternoon
Step 02

Find out what it is allowed to see

An agent inherits the permissions of whoever runs it, which means an over-shared SharePoint becomes an over-sharing agent on day one. The permissions problems that trip up Copilot trip up everything else pointed at the same files.

Readiness assessment
Step 03

Build the smallest version that could possibly work

One job, one data source, one person using it. The point is to find out where the real difficulty is, which is almost never where it looked from the outside.

Build session or plan month
Step 04

Put a human in the loop, on purpose

The agent proposes, a person approves, and the system records who approved what. This is the difference between an agent you can defend in an audit and one you quietly turn off after an incident.

Designed in, not bolted on
Step 05

Decide who runs it on the Monday after

Something built and then orphaned is worse than nothing, because people start relying on it. Name the owner before you build, and be honest if the answer is that nobody has the time.

Your team, or a plan
The part that keeps you out of trouble

It proposes. A person approves.

Every agent, every time
The rule

Nothing goes out on its own

An agent drafts, suggests, flags and queues. Sending a customer an email, posting to the ledger, changing an access right or deleting anything stays with a person. The agent makes the work cheap. It does not make the decision.
The record

Who approved what, and when

Every approval is written down, because the first serious question after anything goes wrong is who authorised it. An agent without an audit trail is one you will have to switch off at exactly the moment you most need to explain it.
The boundary

It sees what its owner sees

An agent inherits permissions. Point one at a file store that has been quietly over-shared for six years and you have not created a new problem, you have made an old one instant and searchable. That is why readiness comes before building.
Book it

Book an agent build session.

We reply within one business hour
Where this usually starts
  • AI readiness assessment $1,499
  • Build session, 4 hours $1,889
  • Monthly AI plan $1,495
  • AI bootcamp, 3 days $15,000
Step 1
A short call, no charge
Enough to work out whether there is an agent here or an automation, which are different bills.
Step 2
The smallest useful version
One job, one data source, one person. Built where you can watch it work.
Step 3
You decide whether it earns its keep
Stopping is a legitimate outcome, and it costs a pilot rather than a project.

By submitting this form you agree to our Privacy Policy.

Or, much faster

One idea, one call.

If you already know the job and just want a straight answer on whether it is worth building, this is the shorter road. Two fields and the idea. We will come back with a yes, a no, or the cheaper thing you should do instead. No obligation and no sequence of follow-up emails.

Straight answers

Agent questions, answered.

FAQ

It depends almost entirely on how much you send it, not on which vendor you picked. A small internal agent answering a few dozen questions a day generally sits low enough that the platform seat is the bigger line. One reading long documents all day is the opposite, and the usage becomes the main cost. That is why the running figure is worked out at scoping and given to you as a monthly number with a ceiling, rather than left to be discovered on an invoice.

If the work lives inside Microsoft 365 and the agent mostly needs your SharePoint, Teams and Graph data with the permissions you already run, Copilot Studio is the shorter path. If the work is reading and reasoning over long material, or it does not fit inside one suite, Claude usually handles it better. Plenty of businesses end up with both, and the deciding question is where your data already lives rather than which model reviews better.

On business and enterprise tiers, generally not by default, and that is one of the real reasons to move a team off personal accounts onto a business plan. The important part is that this is a contractual question with a written answer per vendor and per tier, so it belongs in the scoping document rather than in a reassurance. We will show you the terms rather than summarise them.

If the agent will touch your document estate or Microsoft 365 data, usually yes. An agent inherits the permissions of whoever runs it, so existing over-sharing becomes visible the moment you point something at it. If the agent only touches one tightly held system, it often does not apply. Readiness is the cheaper thing to find out first either way.

No, and that is deliberate. General support agreements, whether per user, per device or per site, exclude AI tooling, agents and automations. AI work sits under an AI plan or is billed as time. The reason is honesty about cost: absorbing AI support into a plan that was never priced for it hides a growing bill inside a line item you thought you understood.

Models are replaced regularly and the good ones behave slightly differently when they are. An agent built as a single enormous instruction tends to break quietly at that point. Built properly, with the job broken into checkable steps, moving to a newer model is a test run rather than a rebuild. If we build it, that is our problem to manage on a plan. If your team builds it, it is one of the things the bootcamp exists to teach.

Yes, and for a lot of businesses that is the better answer. The three day bootcamp exists precisely to leave the capability with your people rather than with us, and the ideas on this page are a reasonable backlog to walk in with. If you would rather own the outcome than the skill, a scoped build is the shorter road.

Pick one job.
Build the small version first.

The businesses getting value out of agents did not start with a strategy. They started with one annoying, repetitive job and a person who was glad to see the back of it.

And relax

Getting started is the easy part.

Onboarding without drama

We do the switch: your current provider, the migration, the handover, all of it. Most teams barely notice the cutover happened.

Everything looked after

On the right plan, compliance, reporting and budgets are handled inside the partnership. You run the business; we run the IT underneath it.

Your QBR writes itself

Quarterly business reviews are generated automatically from your live environment: spend, posture, recommendations and roadmap, ready for the board, reviewed with your account manager.

The honest bit: the full looked-after experience comes with the right plan. We charge fairly for what we take on, and when costs step up it's because you are taking on more, always moving in the right direction.

Sovereign by design

New Zealand owned and operated.

Sovereign data centres across New Zealand and Australia, with your data kept onshore wherever it's required. Our team understands New Zealand, and our leaders have built, scaled and secured businesses right across the New Zealand landscape.

Sovereign data centres · New Zealand & Australia
  • Auckland
  • Christchurch
  • Sydney
  • Melbourne
  • Brisbane
  • Perth
International data-centre operations
  • Singapore
  • Germany
  • Netherlands
  • USA

Servers available in minutes, not days.

Explore data centres & hosting →
Accreditation

Microsoft Solutions Partner in both Modern Work and Security: the two designations covering the platform your business runs on and the security that protects it.

Microsoft Solutions Partner, Modern Work Microsoft Solutions Partner, Security
Fortinet Partner Veeam Partner Lenovo Partner HP Partner SentinelOne Partner Microsoft Azure Microsoft Copilot Claude
Get in touch Book your free discovery & security session