imady helps you to build enterprise software, web systems, immersive applications and practical AI for New Zealand businesses — designed and delivered by an engineer with twenty years behind him.
The problems we solve
You don't own your data — a platform does
Your customers. Your jobs. Your history. All of it sits in a third party's database, behind an Excel export. You signed away your data sovereignty, and you are still paying rent on it.
You changed your business to fit the software
The platform will not be rebuilt for one company, so you bent your process to fit it. The parts that did not fit are now done by hand — and those are usually the parts that win you the work.
Your AI has nothing to work with
AI needs a clean record of what your business has done. That record is locked in a platform you do not control, or spread across spreadsheets and paper. Building it is the first step, not the last.
The choice is not whether to keep paying. It is whether the system is yours. We migrate your data out, build what fits your business, and hand over the source code.
What we do
What we do
Two lines of the same work. We build the system you own, and we connect it to the Chinese platforms that will not connect themselves.
Software Development
Enterprise applications, web development and maintenance, VR and 3D, and AI built into the systems you already run.
- Enterprise software development
- Web development & maintenance
- VR / AR / 3D applications
- AI application integration
China Platform Integration
The technical work of connecting a New Zealand system to WeChat, Alipay and Chinese business platforms. Documentation in Chinese, entity requirements that assume a Chinese company, integration patterns your developers have not seen before.
- WeChat Official Accounts & Mini Programs
- WeChat, Alipay and Chinese payments integration
- Chinese SaaS / ERP integration and data extraction
- ICT & Software Project Management
Built with
The risk was never the technology.
Small software projects rarely fail because someone picked the wrong framework. They fail because nobody wrote down what the thing was supposed to do, because the person who understood it left, or because it was built three times larger than the business needed. We work the way we do to remove those failures first.
We agree what finished means, first.
Most of what goes wrong was decided before anyone opened an editor. So we settle what the system must do, what it will not do, and how we will both know it is done — in enough detail to price it, not so much that it cannot change.
One engineer, accountable end to end.
You speak to the person who designs the system and writes the code. Nothing is lost in a handover, because there is no handover.
Right-sized architecture.
Most businesses your size need one well-built application, not a microservice estate. We will tell you so, even though the smaller project is worth less to us.
It is yours when we finish.
Source code, data and documentation are handed over. Nothing depends on a framework only we can maintain. If you decide to work with someone else next year, you can.
Both the first conversation and the assessment are free. A clear starting point is worth as much to us as it is to you.
How we work
Nothing here requires a leap of faith.
First conversation — free
Thirty minutes. You describe the problem. We tell you honestly whether we are the right people to solve it.
Assessment — free
Most firms charge for this, and it is worth charging for. We would rather spend that week showing you we understand your business than writing a proposal about ourselves. Our time is free; travel and any third-party costs are agreed with you first.
Case study: how we scoped a 220kV training systemSpec & Design
Enough written down to price the work and to know when it is finished — not a specification frozen before reality arrives. Whether the build then runs in fixed stages or in iterations is a decision about your project, not our doctrine.
Build in stages, & handover
Each stage delivers something usable. You approve the next one, send this one back for changes, or stop. At the end the source code, the data and the documentation are yours.
Proof, not promises.
What we can show you is what we build with, and how we build.
Technology we work in
This site, built twice
The page you are reading exists in two independent implementations — a hand-built WordPress theme and a React application with a .NET service layer — driven by one shared content model.
Why that matters to you
It is the same discipline we bring to your project: content separated from presentation, nothing hard-coded, and a system that can be rebuilt on different foundations without rewriting the words.
More case studies and live demos are published as clients allow.
Thirty minutes. No obligation. No sales script.
Tell us what is not working. If we can help, we will say how. If we cannot, we will say who might.
Start a conversationOr email fs@imady.co.nz