The price is fixed at scoping, and it does not move.
Two ways to do something substantial. Either we turn your own team into the AI capability over three intensive days, or we build a specific thing for you at a price agreed in writing before a line of it exists. Both start with scoping, both pilot before they scale, and both leave the capability with you.
Two routes, and they suit different businesses.
Capability, or a delivered thingThe bootcamp is an enablement investment: your people do the work and keep the capability. A custom build is a delivered outcome: we build it, you own it. Plenty of clients do the bootcamp first and a build afterwards. All prices are NZD and exclude GST.
The AI Documentation & Control Bootcamp
- Runs on your tenancy, your keys, nothing leaves
- Every agent change is a proposal a human approves
- Extension, 2 further days, $10,000 + GST
- Enablement hours, 150-hour package, $40,350 + GST
A specific build
- Fixed price set at scoping, and it does not move
- Every hosting and running cost itemised up front
- Staged against milestones you have seen demonstrated
- Six phases, two decision points, both of them yours
Where the money is protected.
Three commitments, in writingScoping is its own step
You see it before you pay for it
The running cost is not a surprise
Tell us what you are trying to change.
We reply within one business hour- Bootcamp, 3 days $15,000
- Extension, 2 more days $10,000
- Enablement, 150 hours $40,350
- Custom build $15k to $250k+
By submitting this form you agree to our Privacy Policy.
Project questions, answered.
FAQAsk who you want holding the capability afterwards. The bootcamp trains your team to run an agent fleet themselves, so the skill stays in your business and you are not dependent on us. A custom build hands you a finished thing. If you have people with the appetite to run it, the bootcamp compounds further. If you need a specific outcome by a specific date, the build is the shorter road.
The price is set at the end of scoping, in writing, and it does not move for the scope described. If you change the scope, that is a new conversation and a new number, and we will say so at the time rather than absorbing it quietly and finding it later. Hosting and running costs are itemised in the same document.
For the bootcamp, no. The agents run on your AI subscriptions inside your own tenancy, your people hold the keys and your data stays where it lives today. For a custom build it depends on what you are building, and the answer is written into the scoping document before you commit, not assumed.
Then it is not worth doing, and stopping there is a successful outcome rather than a failure. The pilot exists precisely so that finding out costs a pilot rather than a full build. We would rather lose the back half of a project than deliver something that quietly does not earn its keep.
For a build touching your document estate or Microsoft 365 data, usually yes, because the same permissions problems that trip up Copilot will trip up anything else pointed at those files. Scoping will tell you if it applies. If it does, readiness is the cheaper thing to do first.
Your team, us on a monthly plan, or a third party. All three are legitimate and we price the option openly rather than making the handover awkward. A build that only we can maintain is a build we have done badly.
Where this fits.
Assess, train, run, buildPriced before it is built,
piloted before it scales.
Scoping is a real step with a document at the end of it. Read the client guide first if you would rather see how the whole thing runs before you talk to anyone.
