A developer’s quote
We read it line by line: what is fair, what is padded and what is missing, such as testing or handover.
Software consulting · New Zealand
Before you pay for a custom build or one more subscription, we look at what you already run and say what to build, what to buy and what to leave alone.
The most expensive software is the kind that gets built and then ignored. We start by asking whether you need it at all.
Where we start
Bring a developer’s quote, or the list of tools you pay for. Either gives us enough to start.
We read it line by line: what is fair, what is padded and what is missing, such as testing or handover.
We check which ones anyone opens, and which two do the same job.
How we decide
We ask them in this order for every job on your list, and write down the answer with the reason.
| Compared on | Buy | Build | Leave alone |
|---|---|---|---|
| Up front | A subscription, then set-up | Biggest cost, quoted in stages | Nothing |
| Each month | Licences per user | Hosting and care | Nothing |
| Fit | Close, and you adapt | Exact, until you change | As it is today |
| Best when | Many firms do this job | The job is how you win | It is rare or painless |
What you get
One line per system: keep, buy, build or retire, with the effort beside it and the order to act in. Take it to anyone, us included. For the whole business, start with an automation audit.
We would rather say so than quote you for it.
Questions
Open any question
Buy when many firms do the same job, such as invoicing, bookings or email. Build when the job is how you win and nothing on the market fits. Often it is a mix, with a little glue between the two. We decide job by job and write down the reason.
A software consultant looks at what you run, what it costs and where people lose time, then tells you what to keep, buy, build or drop. You get the answer in writing, so you can act on it with us, with another firm or on your own.
Jobs run from about $500 to $200,000 and up. You get a written scope and one price before anything starts. A review of what you run moves with the number of systems and how well they are documented. See how we price a job.
A written review. It lists every system you run, a verdict on each, the effort beside it and the order to act in. It is yours to keep, and any developer or vendor can work from it.
Yes. Send the quote and what you asked for. We read it line by line and tell you what is fair, what looks padded and what is missing, such as testing, hosting or a handover. You get our answer in writing.
Sometimes. It pays when the job is how you win, nothing on the market fits and someone will look after it. It does not pay for common jobs like invoicing. We price a care plan alongside the build, so you see the true cost before you commit.
Yes, when building is the answer. Small builds use n8n and AI. Larger ones are custom code, delivered in stages with a fixed price for each. If someone else is better placed to build it, we say so and help you brief them.
Only when it fits. We’re a Zoho Partner, so we know it well. If something else fits better, we’ll say so. If you already use it, see our Zoho pages.
Yes, and we start there. The cheapest fix is often a setting you have not switched on, or two tools that need joining. We check what you own before we recommend buying anything new.
You decide. Take the review to us, to another firm, or do it yourself. If we build, the scope and price come first and nothing starts until you say yes. Not sure where to begin? An automation audit covers the whole business, and how we work shows each step.
A few lines is plenty. We reply within 2 business days with a couple of questions and an honest view on whether to build, buy or leave it.