An Australian company building product-grade software for NZ Government agencies, fintechs around Xero, the Wētā ecosystem, and the panel suppliers that serve them. NZISM-aware, accessibility-by-default, and on the same working day as the Beehive.
The honest version. We are not pretending to have a Lambton Quay office. We are an Australian engineering and product consultancy with senior staff who travel for the days that matter, ship the rest from a shared working day, and know what NZ public-sector procurement expects.
Wellington sits broadly two hours ahead of AEST — sometimes three during the DST changeover weeks. The working day overlaps in full from Wellington morning standup through mid-afternoon. We are upfront about the changeover weeks rather than pretending it never happens.
Wellington is the capital and that is where the work concentrates. We design and build to the NZ Information Security Manual (NZISM), the All-of-Government cloud panels, and the NZ Government Web Accessibility Standard 1.1 from the start — not as a bolt-on at handover.
Every engagement is staffed by senior engineers and designers who have shipped product before. We do not subcontract, offshore, or rotate junior staff in once the statement of work is signed.
We work in your Slack, your Linear, your repos, and your sprint cadence. Our engineers show up to your standups under their own names — not as a vendor pool you have to coordinate around.
Code, infrastructure, designs, and documentation are yours from day one. No vendor lock-in, no licensing tail, and no surprise retainers if you choose to bring the work in-house later.
Eaglum is an Australian company. We invoice in NZD where it helps, are familiar with the NZ Privacy Act 2020 and NZ public-sector procurement frameworks, and treat Wellington engagements as their own context — not an Australian engagement with a different postcode.
Six services covering the surface area Wellington buyers actually ask us about. The per-stack engineering pages (Laravel, React, Node) live separately for the buyers who think about the build at that level.
Designers and engineers working as one team to deliver Wellington-grade product — accessible, documented, and ready for an All-of-Government assessment from day one.
Learn more
Versioned, documented APIs that integrate with whole-of-government NZ platforms (RealMe, NZ Business Number) and the agency systems that surround them.
Learn more
Tokens, components, and governance aligned with NZ Government accessibility expectations. WCAG 2.2 AA / Web Accessibility Standard 1.1 baked in, not bolted on.
Learn more
Fast, testable prototypes that let you validate a service with real Wellington users — citizens, agency staff, or panel-procured suppliers — before engineering spend compounds.
Learn more
Research, journey mapping, and usability testing aligned with NZ public-sector service-design expectations. Findings land in your sprint, sized against what your stack can ship.
Learn more
Senior engineers embedded into your agency or panel-supplier team, accountable to your lead. Same standup, same repo, same sprint — no body-shop framing.
Learn more
Wellington is government-heavy by design. Our work centres on NZ Government, fintech, the Wētā ecosystem, and the supplier ecosystem that serves them.
The Beehive, Treasury, MBIE, IRD, MSD, and DIA anchor an overwhelmingly government-heavy Wellington economy. We build the operational, citizen-facing, and internal-staff platforms that surround the policy work — sized to NZISM and Web Accessibility Standard 1.1.
Xero is global-headquartered in Wellington and the surrounding fintech and B2B SaaS density is real. We work alongside teams shipping into ANZ and global enterprise — onboarding, billing, integrations, and the regulated platforms behind them.
Wētā FX, Park Road Post, Stone Street Studios, and the Lord-of-the-Rings ecosystem concentrate film, animation, and VFX talent in Miramar. We work on production-tooling, post-production workflows, and the operational software that surrounds the work — not VFX itself.
Trade Me and a smaller-than-Auckland-but-real B2B SaaS cluster. We work with scale-ups shipping into ANZ enterprise — the platform work that earns the next round.
The advisory, legal, audit, and consulting firms that orbit NZ Government procurement. We build the case-management, billing, and regulated-data platforms behind the partner-letterhead work.
Victoria University of Wellington and Massey Wellington run student, research, and admin platforms that need engineering depth. We build admin systems, research portals, and student-experience products with public-sector-grade documentation.
Four steps from first call to running software. Procurement evidence, accessibility audits, and exit handover are part of the slice — not a separate line item invoiced at the end.
Read the system, the dashboards and the on-call history. Talk to your engineers and the people closest to your users.
Agree the first slice on a single page — scope, success metric, Definition of Done, risks. Reviewed with your team, not handed to them.
Pair, review, test, deploy. The slice goes to production behind a feature flag with the observability and runbook your team will need.
Walk your team through the code, infrastructure and runbook. Decide together whether to scope the next slice — no contract pressure either way.
Wellington concentrates work along the waterfront and into Te Aro, with the Hutt Valley engineering belt across the harbour and the Wētā cluster at Miramar. These are the rooms we plan our visits around.
The CBD and government core — the Beehive, Treasury, and the head-office cluster for NZ ministries and agencies. Where stakeholder workshops and exec presentations land.
Wellington's creative and start-up belt. Tech, design, and a long tail of independent studios that shape Wellington's product culture. Default for embedded-team work and showcase weeks.
Adjacent to Wellington Hospital and Victoria University — research, healthcare, and a residential-creative tenant base. Where clinical and research-platform work gets validated.
Wellington's tech-and-engineering belt across the harbour — Datacom, a long list of B2B SaaS scale-ups, and a real engineering culture. Comfortable for embedded-team work over longer engagements.
The Wētā FX cluster and the surrounding film, animation, and post-production ecosystem. Where studio-pipeline and licensing-platform work gets validated.
A surprising amount of operations density around the airport — logistics, government operations, and a long tail of mid-market businesses. Comfortable for kick-off blocks when the rest of the team is interstate.
No — we are based in Melbourne and we are honest about that. We travel to Wellington for the days that matter (kickoffs, agency workshops, panel-supplier reviews, and milestone showcases) and run the rest async on a two-hour offset that gives us full working-day overlap.
Wellington is broadly two hours ahead of AEST. During the DST changeover weeks (NZ DST starts late September, AU DST starts first week of October) it is briefly three hours ahead. The working day overlaps in full from Wellington morning standup through mid-afternoon — better than a lot of intra-Australian timezone pairings.
Two-to-three day blocks at the start of an engagement and at major milestones. We come to your office, your end-users, or the precinct that matters — Lambton, Te Aro, the Hutt Valley, or Miramar. Single-day visits do not earn the flight; we plan blocks that do.
NZ Government (the dominant one), fintech (Xero and the surrounding SaaS density), film, animation, and VFX (Wētā FX, Park Road, Stone Street), tech and SaaS more broadly, public-sector adjacent professional services, and Victoria University of Wellington and Massey Wellington.
Yes. Our engineers join your standup, your repo, and your sprint cadence under their own names. They report to your lead, not a vendor account manager. We are familiar with both direct-to-agency engagement and the prime/sub model that NZ panel suppliers operate under.
Laravel, Node.js, and Python on the server. React, TypeScript, and Inertia on the client. Postgres and SQLite where it fits. We meet your stack rather than imposing one — and we are also comfortable working inside agency-mandated stacks (.NET, Java, Drupal).
Discovery typically starts within two to three weeks of signing — assuming your procurement instrument is in place. We are familiar with the All-of-Government cloud and digital-services panel patterns and we plan around them, not around them.
Yes — the operational, non-classified surface area. We are familiar with the NZ Information Security Manual (NZISM), the NZ Government Chief Digital Officer's All-of-Government cloud panels, the NZ Government Web Accessibility Standard 1.1 (which is equivalent to WCAG 2.2 AA), the NZ Privacy Act 2020, and the documentation NZ public-sector buyers expect at handover.
You do — code, designs, infrastructure, and documentation, from day one. Repositories live in your GitHub or Azure DevOps org. Cloud infrastructure runs in your AWS, Azure, or All-of-Government-panelled account. There is no vendor lock-in tail and exit handover is part of the engagement, not an afterthought.
Tell us where the work is and we'll figure out the right shape. NZISM-aware, accessibility-by-default, and the same Slice-based delivery on either side of the Tasman.