- Home
- Services
Product engineering, from first commit to launch.
Software development from architecture and build through cloud, security, release and handover, for new products going from zero to one and for the systems you already run on.
Launch a new product
Turn your idea into a product people can use, and a system your team can keep building on.
We start by working out what the first release needs and what can wait. Then we handle the architecture, the build, cloud infrastructure, security, automated deployment and monitoring.
When it ships you have a production system with documentation. We can keep looking after it, or hand it over to your own engineers.
Modernise an existing system
Upgrade, rebuild or move a system your business already runs on.
We start by understanding what the system does today and who relies on it. Then we agree what needs to change, and in what order.
The changes go out in small releases, so the business keeps using the system throughout. GenTwo is an example: we are replacing a venue display platform in stages without interrupting daily operations.
Add engineering capacity
Experienced engineers for a roadmap with more work than people.
We join your delivery workflow and take a defined piece of the work. That might be a new feature, a first release, a prototype to test an idea, or bringing the engineering up to modern standards. We agree what done looks like up front, deliver it, and hand it back documented.
We also work as the engineering partner on builds that a design agency leads.
Not sure which of the three you need? Talk to us and we will help you work it out.
What an engagement gives you
A shippable v1, not a prototype
Tests, monitoring, security and documentation are built in from the start, so the first release is ready for real users.
Experienced judgement from day one
The engineers who scope your project also build it, and stay on it through delivery and handover. They own the important decisions and review the design and code.
Code your team can own
The code lives in a repository in your organisation from the first commit. Cloud accounts are in your name, so we have access and you have ownership. The intellectual property is yours, third-party dependencies are listed with their licences, and documentation is written as we go.
Progress you can see
You see working software within the first few weeks, and a working demo every week or two after that.
How we work
Agree the outcome
Before writing code we agree what success looks like. The work then runs as tickets on a board you can see at any time.
Build for production from the start
Every change is reviewed and tested as we go. A prototype is an option when it answers a specific question.
Release early and often
Small, frequent releases mean decisions rest on how the software behaves, and priorities can change without waste.
Measure and improve
Once it is live we watch how it behaves with real users and real load, and adjust. Regular progress reviews run through the whole engagement.
Where AI fits
We use AI tools every day and they make us considerably faster. They also produce mistakes that look correct. Experience is what tells us when to rein a tool back in and how to get its best work out. An experienced engineer reviews the design and code, owns the important decisions, and remains accountable for what ships.
What we build with
We pick the best tool for the job and are happy to work in any stack, especially when a project already has one. Our experience spans front end, back end, cloud hosting and infrastructure. Recent projects have included .NET and C#, Node, TypeScript, React, React Native, Electron, PostgreSQL, AWS, Azure, Terraform and GitHub.
Support and handover
Software needs looking after once it is live. Some teams want a clean handover and take it from there. Others want us to stay on.
Keeping things running
Consequential changes are reviewed by a second engineer. Automated tests run on every change. Monitoring and alerting are set up as part of the build, and the infrastructure is defined as code so an environment can be rebuilt if it needs to be.
When the work finishes
You get a running system, the code, the infrastructure definitions, the deployment process and a written record of the main decisions. We walk your team through it and stay available while they settle in.
Ongoing support
If you want us to keep looking after it, we set aside time each month and agree response times for urgent issues. The arrangement is shaped around how your product is used.
Specialists
Years in this industry come with people we trust. Where a project needs specialist design, user research or penetration testing, we bring in people we have worked with before and introduce them to you by name.
Questions
Do we need a finished specification?
No. A conversation about the product and what it has to fit around is a good place to start. We agree the scope and next steps together before any build begins.
Can you work on our existing codebase, alongside our team?
Yes. We work in your codebase and your delivery workflow, next to your engineers. We agree which piece we take on and how it fits your process first, then hand it back documented.
Can you work with our design agency on a build?
Yes. We can be the engineering partner on a build your agency leads. How that works with your team and your client depends on the project, and we work it out with you first.
Do you work with teams outside New Zealand?
Yes. We are used to working remotely, and we work well with teams in Australia and elsewhere where our working hours overlap.
Tell us what you are working on.
Whether you know exactly what you need or you are still weighing it up, tell us about the problem and we will suggest a starting point.