D://LEAD44AI/ML Implementation
AI applied to
actual work.
Identifying where AI genuinely helps in your business, then implementing it, with the data access, guardrails, and measurement needed to know whether it worked. It is for organisations under pressure to do something with AI who want it tied to a real outcome.
THE PROBLEM
Most AI projects begin with the technology and go looking for a problem. That order is why so many of them quietly stop.
The cost of leaving this alone is rarely one visible failure. It is the slow accumulation: the workaround that became the process, the thing only one person knows, the renewal nobody questioned.
Our starting point is always the same: establish what is actually true today, then decide what to change. Work scoped against an assumption tends to solve a problem you do not have.
- 01Nobody owns itIt sits with whoever touched it last, which is not the same as being managed.
- 02No current pictureWhat you have, what it costs, and who has access are all slightly out of date.
- 03Only handled when it breaksAttention arrives after the disruption rather than before it.
WHAT YOU GET
What the engagement covers
Scoped before it starts, so you know what is included and what is not.
- 01
Opportunity assessment
Where AI would genuinely help, ranked by value and feasibility, including the cases where the honest answer is that it would not.
- 02
Data readiness
Whether your data can actually support it. This is usually the real constraint and rarely the thing being discussed in the meeting.
- 03
Implementation
Delivered into the tools people already use, with guardrails on what information may be involved.
- 04
Measurement
A success measure agreed before the build, so the result can be assessed rather than asserted.
HOW WE WORK
Discover, design, deliver, embed
Four stages with a written output at each one. You always know which stage you are in and what comes next.
- 01Weeks 1 – 2
Discover
We map how the work happens now, including the workarounds people are slightly embarrassed to mention.
- 02Weeks 3 – 4
Design
Options costed against benefit, so the choice is a decision rather than a preference.
- 03Per stage
Deliver
Built in slices that reach production and get used, each with a success measure agreed before it starts.
- 04Post-delivery
Embed
Training, documentation, and a check-in once the novelty has worn off. Adoption is the only measure that counts.
WHAT CHANGES
What you should expect
- Someone other than you owns it, with that written down.
- The current state is documented and stays documented.
- Cost is planned ahead rather than discovered at renewal.
- Decisions are made against evidence rather than assumption.
FAQ
Questions we get asked
01What is AI/ML implementation?
Identifying where AI genuinely helps in your business, then implementing it, with the data access, guardrails, and measurement needed to know whether it worked. It is for organisations under pressure to do something with AI who want it tied to a real outcome.
02Where does AI actually save a business money?
In our experience, in unglamorous places. Drafting and summarising routine documents. Finding information across years of files. Taking a first pass at support enquiries. Extracting data from invoices and forms that someone currently re-keys. Meeting notes and actions. None of these are impressive demonstrations. All of them are hours per week that come back.
03Do we need to train our own AI model?
Almost certainly not, and it is the most common expensive misconception. The overwhelming majority of business use cases are met by a commercial model with your own information supplied as context at the time of the question. Training a bespoke model is slow, costly, needs specialist skills to maintain, and is justified only for genuinely unusual problems.
04Will our data be used to train someone else’s AI?
It depends on the tier and the contract, which is exactly why it needs checking rather than assuming. Consumer tiers have historically used conversations to improve models. Business and enterprise agreements from the major vendors generally commit not to train on your content. We read the terms of whatever you are considering and tell you plainly what they say.
05How do we stop AI giving our staff confidently wrong answers?
You cannot eliminate it, so you design around it. Ground the tool in your own documents so it answers from your material rather than from general knowledge. Require it to cite where an answer came from. Keep a person between the output and any decision or external communication. And pick use cases where a wrong answer is visible and cheap rather than invisible and expensive.
06Should we start with Microsoft Copilot?
Often yes, if you are already on Microsoft 365, because it works with information you already hold and needs no new platform. The one prerequisite people skip is permissions. Copilot respects your existing access controls faithfully, which means if your file permissions are loose it will efficiently surface things to people who were never meant to find them. Getting that right first is not optional.
07How long before we see anything useful?
A focused first use case should show something real within weeks rather than quarters. If a proposed AI project cannot show value inside a quarter, that is usually a sign the problem was chosen to suit the technology rather than the other way round.
08How much does AI/ML implementation cost in New Zealand?
We quote after scoping rather than before. Anyone pricing this work without looking at your environment is guessing, and the guess is rarely in your favour. Scoping itself is quick, and we tell you what it costs before we start it.
09How long does it take to get started with AI/ML implementation?
A first conversation takes about half an hour and costs nothing. Scoping is usually a week or two of our time depending on the size of the environment, and we agree the delivery dates with you before anything is booked in.
10Can you deliver AI/ML implementation alongside our existing IT team or provider?
Yes, and it is common. We are happy to work as an extra pair of hands under your internal team, or alongside an incumbent provider on a defined piece of work. We will set out in writing where the responsibilities split, so nothing falls between us.
11Do we have to be an existing Atlas client to start a project?
No. This can be delivered as a standalone piece of work for an organisation we have never worked with before, or folded into a managed agreement if you already have one with us. Plenty of clients use us for one thing and keep everything else where it is.
12Do you deliver projects outside Auckland?
Our team is based in Auckland and we attend sites across the wider region. Most of this work is delivered remotely, so we support organisations throughout New Zealand, and we will say up front where being on site genuinely matters.
13Who from Atlas will be on the engagement?
Named people, not a queue. You get a lead who knows your environment and stays with it, which is the difference between explaining your business once and explaining it every time you make contact.
14What happens when the engagement ends?
You keep the documentation regardless, and anything registered in your name stays in your name. Whether we stay involved is your call. Some clients take it in house from there, others move it onto an ongoing agreement with us. We would rather you left cleanly than stayed because leaving was difficult.
Start with a conversation.
Tell us what you are dealing with and we will tell you whether this is the right service for it, and what it would take.
← All services