Design, develop, secure, deliver.
Four stages, in order. You know what is being built before it is built, and you own it at the end.
Map how the work runs today; agree in writing what the system will do, every screen, rule and edge case, before anything is built.
The mapping is done with the people who do the work, not only with management, because the workarounds are where the real process lives. What comes out is a specification you read and approve: the screens, who can see what, what happens at each decision, and what the system deliberately will not do.
What you see and sign off
A written specification in plain language, a walkthrough of every screen, and the scope of the block it becomes. You approve the specification before any build work starts, and you keep it either way.
Built to that specification and shown to you as it goes, so what arrives is what was agreed.
You see working software early and often, on your own data where that is sensible. Changes are welcome; anything that widens a block's scope is agreed in writing before it is built, so scope never grows quietly.
What you see and sign off
Regular working demonstrations, a running list of decisions taken, and written agreement on anything that widens a block's scope.
Your data is safe, and not by assumption: permissions, identity and logging are set correctly and checked before anything goes live.
Access is granted by role and tied to your existing logins, so starting and finishing staff is one action in a system you already run. Sensitive actions are recorded. The testing is done by an independent party, and you receive the findings.
What you see and sign off
A written list of roles and what each can reach, confirmation that access runs through your own identity provider, and the penetration test report with anything found and fixed.
A live job runs alongside the old process, then documentation, admin access and the code hand over. Running it afterwards does not depend on us.
Running both ways at once for a short period is the only honest test: if the new system disagrees with the spreadsheet, that gets resolved before the spreadsheet is retired. Then your team is trained on it and the keys change hands.
What you see and sign off
Documentation written for your team, administrator access in your own accounts, the source code in a repository your business owns, and a training session for the people using it.
The last stage is a handover, not a renegotiation.
No build fee, no lock-in, yours.
A block is one working part of your operation — capacity planning, the job register, approvals, a connector to a system you already run. Each one is specified, built and put to work on its own. Blocks are how the work is delivered and how it is charged: you commission the first, then another once the first has earned its keep.
Charged from the day work on that block starts, not on handover. Building and billing begin together, so you are never paying for something you cannot yet use.
Named users with access, not headcount. Provisioning a person starts their charge; removing them ends it.
No project fee, no deposit, nothing capitalised up front. The cost of starting is a month.
Month to month. No lock-in and no buyout clause, because a system you own is not something you can be locked out of.
Designed to scale with you.
The monthly charge is not a licence — nothing here is licensed to you. It covers running the system: hosting and its administration, monitoring and incident response, security patching, dependency upgrades, keeping integrations working when a vendor changes an API, user administration, support, and continued development within the block's scope.
Support, monitoring and continued development inside a block's scope are part of the monthly charge, not a separate retainer. The repository, the data, the cloud accounts, the tenancy, the admin access and the intellectual property are yours throughout, so nothing about this arrangement is required to keep your system running.
All figures are in New Zealand dollars and exclude GST.
Ready to build?
A short call about your systems, and what they could be doing for you.
Book a conversation