1. Regions
  2. New Zealand
  3. Christchurch

Software engineering and product design for Christchurch businesses

An Australian company building product-grade software for Christchurch teams across agritech, aerospace, manufacturing, B2B SaaS, and the regional public sector. NZ-aware delivery, on the ground when it matters, and on the same working day as your team.

Why Christchurch teams work with us

The honest version. We are not pretending to have a Cashel Street office. We are an Australian engineering and product consultancy with senior staff who travel for the days that matter and ship the rest with full working-day overlap.

Across the Tasman, in your day

Christchurch sits broadly two hours ahead of AEST — sometimes three during the DST changeover weeks. Working day overlaps from morning standup through mid-afternoon Christchurch time.

On the ground when it matters

We are based in Melbourne and travel to Christchurch for the days that earn it — kickoffs, Lincoln agritech sessions, aerospace partner reviews, and milestone showcases. Two-to-three day blocks, not single coffees.

Senior engineers, no body-shopping

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.

Embedded in your team

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.

You own everything

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.

Australian business, NZ-aware delivery

Eaglum is an Australian company. We invoice in NZD where it helps, are familiar with the NZ Privacy Act 2020 and the operating reality of post-quake Christchurch business, and treat South Island engagements as their own context.

What we do for Christchurch teams

Six services covering the surface area Christchurch 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.

Industries we work with in Christchurch

Christchurch concentrates a small number of sectors disproportionately well — agritech, aerospace, manufacturing, and a real engineering-flavoured tech scene. We have shipped product across all of them.

Agritech

AgResearch, Lincoln University, DairyNZ adjacency, and the Halter and broader Agri-tech NZ cluster make Christchurch and Lincoln a globally significant agritech hub. We build farm-management, traceability, and supply-chain platforms — the systems behind the paddock.

Aerospace & space

Rocket Lab's origin city. Pyper Vision, Dawn Aerospace, and a growing aerospace ecosystem — globalised now, but the engineering culture is still Christchurch. We build the operational software, supplier portals, and integration layers around the work, not propulsion.

Tech & SaaS

Trimble (with significant Christchurch presence) and Tait Communications anchor a real engineering-focused tech cluster. We work alongside scale-ups shipping into ANZ and global enterprise — the platform work behind the product.

Manufacturing

Scott Technology and a manufacturing tail that matured in the post-quake rebuild. We build operations platforms, quality-management systems, and the digital infrastructure behind manufacturing scale-ups.

Universities & research

University of Canterbury and Lincoln University concentrate engineering, agritech, and life-sciences research. We build admin systems, research portals, and student-experience products with public-sector-grade documentation.

Public sector

Regional NZ Government, Christchurch City Council, and the post-earthquake recovery agencies (Ōtākaro adjacent). We deliver work shaped to NZ public-sector accessibility expectations and the documentation buyers expect at handover.

How we work

Four steps from first call to running software. The same method we use everywhere — the Christchurch variant just adds a Tasman crossing.

01

Discovery

Read the system, the dashboards and the on-call history. Talk to your engineers and the people closest to your users.

02

Slice definition

Agree the first slice on a single page — scope, success metric, Definition of Done, risks. Reviewed with your team, not handed to them.

03

Build the slice

Pair, review, test, deploy. The slice goes to production behind a feature flag with the observability and runbook your team will need.

04

Hand it over

Walk your team through the code, infrastructure and runbook. Decide together whether to scope the next slice — no contract pressure either way.

Where work happens in Christchurch

Christchurch concentrates work in a rebuilt CBD, around the universities at Riccarton and Lincoln, and in the start-up belt at Addington. The agritech work happens out beyond the Port Hills — we travel for it.

Christchurch CBD

The rebuilt central city — High Street, Cashel Mall, and the head-office cluster for a long tail of professional services, government regional offices, and corporate businesses. Where stakeholder workshops and exec presentations land.

Riccarton

Adjacent to the University of Canterbury and a long-running technology and professional-services belt. Comfortable for embedded-team work and longer engagements.

Addington

Christchurch's start-up and SaaS belt, immediately south-west of the CBD. Comfortable for studio-sized team engagements.

Lincoln

Lincoln University and the surrounding agritech cluster. Where farm-management and agribusiness product gets validated by the people running the science and the paddock.

Christchurch Innovation Precinct

The post-quake innovation precinct — anchored by tertiary, research, and start-up tenants. Aerospace and engineering scale-ups concentrate here.

Tūranga & central library precinct

The cultural and civic heart of the rebuilt city. A surprising amount of community-facing service-design and accessibility work centres around this precinct.

Frequently asked questions

Are your engineers based in Christchurch?

No — we are based in Melbourne and we are honest about that. We travel to Christchurch and Lincoln for the days that matter (kickoffs, agritech workshops, aerospace partner reviews, and milestone showcases) and run the rest async with full working-day overlap.

How do you handle the NZ-AU timezone difference?

Christchurch 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 Christchurch morning standup through mid-afternoon — better than a lot of intra-Australian timezone pairings.

How does on-site work happen?

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 — the CBD, Riccarton, Addington, Lincoln, or further afield to a Canterbury farm. Single-day visits do not earn the flight; we plan blocks that do.

What industries do you work with in Christchurch?

Agritech (AgResearch, Lincoln University, Halter, the wider Agri-tech NZ cluster), aerospace and space (Rocket Lab origin city, Pyper Vision, Dawn Aerospace), tech and SaaS (Trimble, Tait), manufacturing, universities, and the regional public sector. We avoid sectors where we cannot bring real depth.

Can you embed engineers into our Christchurch team?

Yes. Our engineers join your standup, your repo, and your sprint cadence under their own names. They report to your tech lead, not a vendor account manager. The two-hour offset is more than workable — many Christchurch engineering teams already work cross-Tasman.

What technologies do you work with?

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 comfortable working alongside C++ and embedded-adjacent stacks where the agritech and aerospace work demands it.

How fast can you start?

Discovery typically starts within two to three weeks of signing. The Slice — your first piece of shipped product — usually lands four to six weeks after that. We are deliberate about not over-committing; we would rather move the start date than ship a slice with the wrong people on it.

How does the post-quake context shape things?

Christchurch has rebuilt — and the tech ecosystem that emerged from the rebuild is more concentrated and more deliberate than it was pre-2011. Engineering culture is real, the precincts are walkable, and the businesses that survived are typically run by people who think in terms of resilience by default. We treat that as an asset, not a footnote.

Who owns the IP?

You do — code, designs, infrastructure, and documentation, from day one. Repositories live in your GitHub org. Cloud infrastructure runs in your AWS, GCP, or Azure account. There is no vendor lock-in tail, no licensing surprise, and no retainer required to keep using what we built.

Got a Christchurch product on your desk?

Tell us where the work is and we'll figure out the right shape. Agritech, aerospace, manufacturing — the Slice scales to the question on your desk.

Send an email