An Auckland engineering practice.
We design, build and operate the systems small and mid-sized New Zealand businesses run on. The website and what makes it findable, the agents that carry defined work, and the data moving between the tools you already pay for.
The work that consumes a small team is rarely the skilled work. It is re-entry, chasing, and moving information between systems that were never designed to exchange it.
Large organisations addressed this a decade ago, with budgets that were never available further down the market. The tooling has since become inexpensive enough that a well scoped build returns its cost within weeks. What remains scarce is the willingness to establish how a job is actually done before building anything for it. That is where an engagement with us begins.
How we work.
The same five commitments apply to every engagement, whatever is being built.
Process before product
We establish how the work runs today, including the steps people carry out from memory, before proposing anything to replace it.
Live before large
A narrow working version goes into production early. Every decision after that is made against evidence rather than against a document.
Inside your accounts
Infrastructure, domains, analytics and repositories are provisioned in your name from the outset, not migrated to you at the end.
Fixed scope, fixed price
Both are agreed in writing after the first conversation, with the boundary of what is included recorded alongside the number.
Handover, not dependency
Code, credentials and documentation transfer at the end of every engagement, whether or not we continue to operate the system afterwards.
Where we will disagree with you.
Most of what goes wrong on projects of this kind is organisational rather than technical, and most of it is visible early to somebody prepared to raise it. We would rather raise it before a quote than explain it afterwards.
- When the work should not be undertaken yet.
- When an off-the-shelf product would do the job for less.
- When a process needs correcting before it is automated.
- When we are not the right firm for the piece of work in front of us.
- What a system will cost to run, before you commit to building it.
How the practice is set up.
Deliberately small at the centre, with the depth brought in where a build requires it.
Direct access
You deal with the people building the system. There is no account layer relaying what you said.
Sized to the work
The team is assembled around the project, rather than the project being shaped to keep a standing team occupied.
Specialists where they matter
Brought in where a build genuinely calls for them, with senior engineering on the parts that carry operational risk.
One point of accountability
The same person is answerable from the first conversation through to handover and beyond it.
Tell us the idea.
You do not need a spec. Tell us what you want the business to do and we will tell you whether it is worth building, including when the honest answer is not yet.
Based
Auckland, New Zealand. Working wherever your systems are.
Reply
Within one business day. No sales sequence, no newsletter.
Direct
+64 21 048 4586
hello@adagradit.com
What it costs
The first conversation costs nothing, and you keep what comes out of it either way.