AI knowledge base for optometrists.
Internal AI knowledge base, built around how an optometry practice actually works.
Eye test recalls, bookings and patient messages handled automatically, with patient information protected under the Privacy Act 2020.
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.
How it works in New Zealand
We find the one workflow costing optometry practices the most hours, ship a working slice into production in weeks, prove it pays for itself, then harden it and hand it over.
Made for New Zealand paperwork.
Policies, job manuals and compliance records in one place staff can ask, including Records of Building Work for restricted work.
- Restricted work needs an LBP
- Serious breaches get reported
- Government work is tendered on GETS
Optometry practices run their businesses unlike anyone else.
Optometrists balance eye tests, recalls, and frame sales, with recall reminders often the first thing to slip.
Recall reminders and insurance or funding queries are the recurring admin load behind every optometry front desk.
The shape of the result for optometry practices: New staff get to productive 3x faster - less senior-team interruption. Built on Claude, hardened with the rest of the stack as it scales. Kiwi Dynamics
Questions optometry practices ask
Who owns the code and the model setup?
You do, on delivery. We deploy AI knowledge base into your own cloud account where possible, with the model setup, prompts, evals and integration code all checked into a repo you own. Claude sits in your account too - we don't operate it from ours.
How long does AI knowledge base take to ship for optometry practices?
We aim for a working pilot inside 4-6 weeks - narrow scope, real optometry practices data, measurable outcome. From there it's another 6-8 weeks of hardening before you'd consider it production. Full rollouts (multiple sites, multiple teams) typically land in 3-4 months.
Are there hidden costs we should plan for?
Three to know about: model/API spend (which we set up under your own account, not ours, so you see and control it), any new SaaS subscriptions we recommend, and your team's time during rollout. We surface all three in the quote so there are no surprises.
Can AI help with payday filing?
It can prepare it. Employers file employment information every payday, within 2 working days when filing electronically, and automation can have it ready for a person to check.
Can you work to the NZISM?
The NZISM is the government's information security manual and is written for vendors serving agencies as well as the agencies themselves, so government-adjacent work should be built to it.
Let's chat
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.


