Product engineering
When the package does not fit, build the product
Custom enterprise software is not a failure of procurement. It is how Australian operators get software that matches the work.
There is a particular meeting where a vendor map is on the wall and everyone agrees the last package “almost” did it. Almost is how you accumulate five systems of record and a team of people who copy values between them.
Custom enterprise software is not a personality trait. It is the honest response when the domain is the business.
What we will build
- Internal platforms: case, quoting, partner, operations consoles.
- The APIs those products need so they are not another silo.
- Strangler patterns around the package you cannot turn off this year.
What we will not build: a rewrite of SAP because someone liked a Figma file.
How it should feel to your team
The repo is yours. The first pull request from your people happens in week two, not at “handover.” AI-assisted coding is on, with the same standards as our own work. Tests are not a phase.
If a firm will not work that way, they are selling a black box with a nicer font.
Integration is part of the product
A beautiful portal that cannot write to the core is a brochure. We design the product and the contracts together. That is why this practice still contains MuleSoft people and product people in the same squad.
Sydney delivery means we can sit with the operations lead who will actually use the thing. That still beats a thousand user stories written in another timezone.
