HomeServicesSoftware Consulting
Software Consulting in New Zealand
Consulting buys you an opinion before you commit to a build: an architecture review, a technical audit of something you are about to acquire, or a plan that turns a vague idea into a scope. Cheaper than discovering the same thing halfway through a project.
$5k+
Typical project value
2 min
To post a project
What do you need built?
Start here and add detail as you go.
Free - No obligation - Your details stay private
What people usually mean by software consulting
Consulting is the cheapest thing on this site and the easiest to waste money on. The difference is whether you are buying a decision or buying a document. A $12,000 review that stops a $200,000 project going the wrong way is the best money you will spend; a $12,000 report that sits in a drawer is a donation.
A second opinion before you commit
You have quotes that disagree, or a proposal you cannot evaluate. A few days of independent review before signing.
Turning an idea into a scope
You know the problem but not the shape of the solution. Discovery produces something developers can quote consistently.
Checking what you are about to buy
Technical due diligence on a business, product or codebase you are acquiring. What is really there, and what it will cost to keep.
Senior help without a hire
A fractional CTO a day or two a week: making technical decisions, managing suppliers and hiring, without a six-figure salary.
What it costs
Indicative ranges from projects posted here. Use them to sense-check a quote, not to budget precisely.
Focused review
A few days on a specific question: is this architecture sound, is this quote reasonable, why is this system slow.
$3k – $12k
Discovery or audit
Two to four weeks producing a scope developers can quote against, or a full assessment of an existing system.
$12k – $40k
Ongoing technical leadership
A fractional CTO or architect engaged regularly, accountable for decisions rather than advice.
$4k – $15k/month
Questions worth asking a provider
·What decision will I be able to make at the end of this that I cannot make now?
·Do you build as well as advise, and would you be quoting on the work you recommend?
·What does the deliverable look like — can I send it to three developers and get comparable quotes?
·Who exactly does the work, and how much of it is the person in this meeting?
·Have you told a client not to build something? What happened?
Common questions
What does software consulting cost in New Zealand?
A focused review answering a specific question is $3,000 to $12,000. Discovery or a full system audit is $12,000 to $40,000 over two to four weeks. Ongoing fractional CTO work runs $4,000 to $15,000 a month depending on days. Day rates cluster between $1,200 and $2,500, and the senior person's involvement matters more than the rate.
Is discovery worth paying for?
It is when the brief is genuinely unclear and the build is large — a well-run discovery is the cheapest way to avoid building the wrong thing. It is not when the brief is already clear, or when the discovery is really a sales exercise ending in a proposal from the same firm. Ask whether they would quote the build, and whether the output is portable to other developers.
Should the consultant also build it?
There are real advantages — continuity, accountability, no handover. The conflict is equally real: a firm that recommends a large custom build and then bids for it was never a neutral adviser. Either use someone who does not build, or accept the conflict openly and get a second opinion on the recommendation.
What is a fractional CTO?
An experienced technical leader for a day or two a week, making decisions and holding suppliers to account. It suits businesses spending real money on software without anyone senior enough to judge it, and it is far cheaper than a wrong hire. Agree what they are accountable for, not just what they will advise on.
What should I get at the end?
Something usable, not a slide deck. For discovery: a scope three developers could quote from and produce comparable numbers. For an audit: findings ranked by risk with an estimated cost to fix each. For a review: a recommendation with reasoning. If you cannot act on it on Monday, you bought a document rather than a decision.
Software Consulting by city: Adelaide · Auckland · Australia · Brisbane · Canberra · Christchurch · Dunedin · Gold Coast · Hamilton · Melbourne · New Zealand · Perth
Software Consulting projects open right now
Titles and categories are public. Full briefs, budgets, regions and buyer detail are visible to approved providers only.
Updated daily
No open projects in this category right now. New briefs are posted every week.
Buy a decision, not a document
The test for any consulting engagement is simple: what will you be able to decide at the end that you cannot decide now?
"Whether to build or buy, with numbers behind it." "Which of these three quotes is realistic." "Whether the system we are acquiring is worth what they are asking." Those are decisions. "A digital strategy" is not, and engagements that promise one tend to end in a well-formatted restatement of what you already knew.
Write the question down before you brief anyone. It is the single most effective way to make consulting money well spent.
The four things worth buying
A second opinion. You have quotes ranging from $40,000 to $180,000 and no way to judge them. A few days of independent review costs a fraction of the gap and often explains it entirely.
Discovery. You know the problem but not the shape of the solution. Done properly, this produces something three developers can quote from and return comparable numbers — which is worth far more than the document itself.
Due diligence. You are buying a business, a product or a codebase. What is actually there, what state it is in, who understands it, and what it will cost to keep running. This is where consulting most reliably pays for itself, because the findings change the price you pay.
Fractional leadership. You are spending real money on software and nobody in the business is senior enough to judge it. A day or two a week of experienced technical leadership costs less than a wrong hire and far less than a wrong build.
The conflict to name out loud
Most consultants also build. That brings genuine advantages — continuity, accountability, no handover gap — and one obvious problem: a firm that recommends a large custom build and then bids to deliver it was never neutral.
You have two honest options. Use someone who does not build, and accept that they will hand off. Or use someone who does, name the conflict at the start, and get a second opinion on the recommendation before you commit.
What you should not do is assume the advice is disinterested because it came with a fee attached. Ask directly: would you be quoting on this work?
Ask who actually does it
The most common disappointment in consulting is not bad advice. It is meeting an experienced principal during the sale and getting a junior for the delivery.
Ask who will do the work, how many days each person is on it, and how much of that is the person in front of you. Rates of $1,200 to $2,500 a day are normal for genuinely senior people in New Zealand; the same rate for someone two years out is not, and you will only find out afterwards if you did not ask.
What good output looks like
- Discovery: a scope with enough detail that three independent developers produce quotes within a sensible range of each other. If the quotes still vary 4x, the discovery did not do its job.
- Audit: findings ranked by risk, each with a rough cost to fix, so you can decide what to do this quarter and what to live with.
- Review: a recommendation with the reasoning shown, in language you can defend to a board.
- Due diligence: what you are buying, what is missing, key person risk, and the number you should adjust the offer by.
In every case: portable. If the deliverable is only usable by the firm that wrote it, you bought a sales document.
When not to buy consulting
If the project is small — under about $30,000 — the review can cost a meaningful share of the build. Ask two or three developers for their approach instead; the disagreements between them are free consulting.
If your brief is already clear and specific, discovery adds cost without adding certainty. And if you are looking for someone to confirm a decision you have already made, save the money: you will get the confirmation and none of the value.
The most useful question you can ask
Ask when they last told a client not to build something, and what happened.
Consultants who have never advised against a project have either been extraordinarily lucky in their clients or have never risked the fee. The answer tells you whether you are buying judgement or agreement.
Describe the decision you are facing
You do not need to specify the engagement. Describe the decision in front of you, what you have already been told, who disagrees, and what happens if you get it wrong. Consultants worth hiring will tell you whether you need them at all — and the ones who say the answer is a fortnight rather than a quarter are usually the ones to take seriously.
Get up to 5 quotes for your software consulting project
You choose who may contact you. Free to use, no obligation.