Admin Army is a team working across New Zealand, Fiji, and India. Every one of them is named below.
The team is organised across three service lines: Payroll, Bookkeeping, and Accounting Practice Support. Each has its own leadership and accountability chain. That separation exists so that quality is governed within each function, not blurred across them.
Within each service line, senior NZ-based specialists set standards and make judgement calls. Trained operators execute delivery inside documented processes. Leadership is embedded in the workflow. The people making decisions about quality, escalation, and client outcomes are operationally current. They review live work, maintain SOP oversight, and sign off on delivery. They do not manage from a distance.
Service line managers own their delivery engines. They are responsible for quality, capacity, SOP currency, and escalation within their function. Accountability is distributed and specific. No one person carries everything. No one function depends on a single individual.
The team operates from New Zealand, Fiji, and India. That is not a split between a core team and a support function. It is a single operation designed to run across all three locations inside the same governance structure, the same documented processes, and the same escalation paths.
Fiji-based team members work in real-time alignment with New Zealand hours, enabling direct collaboration and oversight within the same working day. India-based team members extend operational coverage across time zones, with capability aligned to Western Australian business hours as that market develops.
Every person on this page, regardless of where they sit, operates under the same standards, the same quality gates, and the same accountability. The bios below are presented with equal visibility because that reflects how the team actually works. There is no B-team.
This is what it takes to run the model properly.
The depth you see below means cross-trained coverage. When someone is on leave, the work continues without disruption because the knowledge is in the system, not in one person’s head. It means service line separation is possible without stretching people across functions. It means capacity buffers exist so that volume increases do not require heroics.
You will have a primary point of contact who knows your business and becomes your client expert. But your work does not depend on one individual being available, being healthy, or staying in the role. The knowledge sits in the system, not in a single person’s head.
The system does not depend on any one of them. But it is made real, trustworthy, and human by all of them being visible and named.
You have now seen the system, the controls, and the people.
If you want to understand how the operating model itself is structured.
If your concern is data access, security, and risk governance.
If you have seen enough and your systems are ready.