Built for the parts of the information technology project managers job that eat a Tuesday.
Every information technology project managers team we've worked with has a different definition of "broken".
0.07% of all Claude.ai conversations map to this kind of work (Anthropic Economic Index, March 2026).
We'd call the engagement a success when Information Technology Project Managers are using the system without thinking about us. 0.07% of all Claude.ai conversations map to this kind of work (Anthropic Economic Index, March 2026) Kiwi Dynamics
An AI agency, minus the theatre.
*Every engagement is scoped and quoted up front. Results vary by workflow and business.
On the tools or running at scale, the admin still eats the week :)
The questions a public sector buyer asks, answered up front: privacy impact, the NZISM, where the data lives and how an algorithm is held to account.
*Illustrative example based on nine hours a week of admin. Actual results vary by workflow and business.
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.
What changes for information technology project managers week to week
Information Technology Project Managers sits within Computer & Software, one of the sectors we build production AI for.
- Draft, review and refactor code
- Turn tickets into tested changes
- Document systems and write runbooks
- Triage logs and incidents
How the work runs
We find the one workflow costing Information Technology Project Managers the most hours, ship a working slice into production in weeks, prove it pays for itself, then harden it and hand it over.
Straight answers
What's a typical engagement length for Information Technology Project Managers?
Six to twelve weeks for the build, then a short managed-services month while the system goes from "shipped" to "owned by your team". After that you keep us on retainer if you want, or take it from there yourself.
Do you do hourly billing or fixed price?
Fixed price for the pilot, every time. After that it's your call - fixed price per milestone or a small monthly retainer for ongoing iteration. We don't run open-ended T&M because it disincentivises us from finishing.
Can you work with our existing systems?
Yes. The default AI stack we reach for is Draft, review and refactor code, Turn tickets into tested changes, Document systems and write runbooks, Triage logs and incidents, but we'll bend it around whatever you already run - Xero, HubSpot, Shopify, Cin7, your own in-house apps. The discovery week maps every data source before any build starts.
Do you work with Xero?
Yes. Xero is one of the systems we build around, and we connect to the other tools you already run rather than asking you to switch.
How does this fit the Public Service AI Framework?
The framework, led by the Government Chief Digital Officer, asks for safe, transparent and accountable AI. Agencies that sign the Algorithm Charter also commit to transparency in how they use algorithms.
Get started in 5 minutes
StartContact us
Tell us what you're trying to do and we'll reply with how we'd build it, no obligation.
Was this helpful?
Thanks, your comment is with our team.