Aotearoa New ZealandEst. 2021
Software woven aroundthe way you already work
Custom software, automation and AI — built in New Zealand, for New Zealand businesses.
01Services
What we build, and why you would ask us to
Described plainly, without categories invented to look impressive. If your problem is not on this list it is still worth a conversation — the list is where we have done it before, not the limit of what we do.
02Why local matters
A New Zealand company, building for New Zealand conditions
Most of the software sold to Kiwi businesses was designed for somewhere else, then translated. GST is bolted on, the address form wants a state, the support desk opens when you are going to bed. We start from how the work is actually done here — and you can ring the people who wrote the code.
- 01
LoomInfo Limited is registered and operating in New Zealand
- 02
Your data is hosted in New Zealand or Australian regions, not offshore by default
- 03
Built to the Privacy Act 2020 from the first line, not retrofitted
- 04
GST, IRD, NZBN and e-invoicing handled properly, not approximated
- 05
Fixed prices quoted in New Zealand dollars
- 06
You own the code, the repository and the hosting accounts outright
Same time zone as you. Not a ticket queue in another hemisphere.
Mon–Fri, 8am–6pm NZST
03Automation & AI
Most of what gets sold as AI is a rule in a nice jacket
There is a great deal of enthusiasm about AI in New Zealand business right now, and a fair amount of money being spent on it badly. Our position is unfashionable and has saved our clients a lot: use the simplest thing that solves the problem. Sometimes that is a language model. Far more often it is a rule, a connection between two systems, or a form that stops someone typing the same thing twice.
- 01
Connect
Cheapest · most reliable
Two systems that both hold the same information, joined so a change in one appears correctly in the other. No intelligence required, and no intelligence wanted — this layer should be boring and utterly predictable.
- 02
Decide by rule
Cheap · fully auditable
The decisions your team makes the same way every time, written down as rules and executed by software. If you can explain the rule to a new starter in a sentence, it does not need a model — and a rule can be audited, which a model cannot.
- 03
Read and extract
Moderate · needs checking
Where the input is unstructured — a PDF, an email, a photograph, a scrawled docket — a model reads it and turns it into structured data. Then deterministic code checks that data before anything acts on it. The model reads; it does not decide.
- 04
Assist and converse
Highest · needs guardrails
A genuine assistant: answering from your own material, citing where each answer came from, and handing over to a person when it is not confident. This rung is worth it when the questions are genuinely varied. When they are not, rung one or two does the job for a fraction of the running cost.
04Sectors
We work where New Zealand actually earns its living
Primary industry, trades, tourism and the services around them. Knowing a sector means knowing which corners cannot be cut in it — the audit, the season, the compliance file — and that is most of what makes a build succeed.
ObservedEvery engagement
Nearly every business we meet has one process held together by a spreadsheet and a person who remembers how it works.
That person is the most expensive integration in the building
05Case studies
Work we have shipped, described honestly
Most of our work sits under a confidentiality agreement, so these are described by category rather than by client — what the problem was, what was built, and what changed.
06Approach
Six stages, and you can stop after any of them
Each stage produces something you own and could take elsewhere. That is deliberate: a process you can leave partway through is the only honest kind.
- 01
Scoping call
45 minutes · free
A conversation with the person who would actually run the build, not an account manager. We want to understand the process that hurts, what you have already tried, and what "fixed" would look like. If software is not the answer, we will say so on this call.
- 02
Discovery
1–2 weeks · fixed price
We spend time with the people doing the work — not just the person who signs off — and map how it really runs, including the workarounds. Workarounds are the most valuable thing in the room: each one marks a place the current system fails.
- 03
Blueprint
3–5 days
Scope, sequence and a fixed price in New Zealand dollars. You get a plan specific enough to hold us to, and a recommendation on what to build first — which is usually less than you expect, because the first release should prove the idea rather than complete it.
- 04
Build
2-week cycles
Working software every fortnight, on a test environment you can log into and use. No reveal at the end. You see it as it is made, which is the only reliable way to find out that something was misunderstood while there is still time to change it.
- 05
Go live
1–2 weeks
Data migrated and checked, staff trained in sessions we record, and a cutover with a rollback path that has been tested rather than assumed. We are on hand through the first week, because week one is when the real edge cases arrive.
- 06
Care
Ongoing · cancel any time
Hosting, monitoring, backups, security patching and a response time in writing. Plus an allowance of small changes each month, because the requests that arrive after launch are usually the most valuable ones — they come from real use.
At a glanceHow we work
- New Zealand regions worked in
- 14
- From Northland to Southland, remote-first with on-site time where it earns its keep.
- of code owned by the client
- 100%
- Repository, hosting accounts and documentation, in your name from the first commit.
- hosting regions only
- NZ + AU
- Data residency stated in writing, region by region, for your privacy officer.
- between working releases
- 2 weeks
- Software you can log into and use, every fortnight, from the start of the build.
- first, on every field app
- Offline
- Designed for the paddock, the packhouse and the rural run — not for the office fibre.
- support hours
- NZST
- Rung, answered and fixed by the people who wrote the code, in your own time zone.
07Questions
The things people ask on the first call
Answered here so you do not have to spend the call asking them.
Yes. LoomInfo Limited is registered in New Zealand and operates here, with a New Zealand Business Number you can look up on the Companies Office register. That matters more than it used to: a great deal of software sold into this market is resold from offshore with a local phone number attached, and you usually find out which is which at the point something breaks.
Next stepFree · no obligation
Tell us about the part of your week that should not be manual
Free 45-minute call with the person who would run the build. No sales script, no obligation.
- 01
You tell us what hurts
Forty-five minutes, no preparation needed. Bring the process that is costing you time.
- 02
We tell you what we think
Including when the answer is a setting in software you already own, or nothing at all.
- 03
You decide, in your own time
No follow-up sequence, no pressure. If it is worth doing, we will scope it properly.
Free 45-min
scoping call