When should a NZ startup hire a product consultant vs a developer?
Map your own coverage across engineering, product, and growth, then hire the gap. Most early-stage problems need 10 hours of product thinking before they need 400 hours of development.
Hire a developer when you know exactly what to build and why: validated demand, a tight spec, and you're confident owning the product decisions yourself. Hire a product consultant when any of that is fuzzy. The honest way to decide is to map your own coverage across engineering, product, and growth, and hire the gap.
The question is a false binary
"Consultant or developer" assumes your problem belongs to one discipline. It almost never does.
Every early-stage company is running three problems at once: what to build (product), how to get it built (engineering), and how to get people finding and buying it (growth). These are usually three separate hires, and the seams between them are where startups leak money. The growth person inherits a product they can't change, the developer builds a spec nobody validated, and the product thinker hands over slide decks that don't survive contact with the codebase.
So flip the question. Don't ask which title to hire. Ask which of the three you genuinely cover yourself, and hire whatever's missing.
Run the coverage map on yourself
Three questions, answered honestly:
Product: Can you decide what to build next, and what not to, based on evidence rather than enthusiasm? Have you killed a feature you loved?
Growth: Can you read your own funnel? If revenue dipped next month, would you know where to look first?
Engineering: Can you get it shipped, and judge whether what's being shipped is any good?
A technical founder with product instincts needs build capacity, and a developer is the right, cheaper answer. A domain-expert founder with deep customer knowledge but no funnel literacy doesn't need 400 hours of development. They usually need about 10 hours of sharp product and growth thinking first, because the most expensive thing a developer can do is faithfully build the wrong spec at speed.
What the gap looks like in practice: Bikeaholic
Bikeaholic, a mountain-bike retail and hire business in Queenstown, came to me growth-shaped: return on ad spend was declining, and the reflex answers were the usual two. The marketing answer, spend more on ads. The development answer, rebuild the website.
Neither survived contact with the data. A proper dig through GA4 showed who was actually using the site, what each audience wanted, and where they were trying to go. The ad spend wasn't the problem. The journeys were.
So the work crossed all three disciplines at once. We rebuilt the homepage around what the audiences were actually there to do. We rebuilt the Shopping, Performance Max, and search campaigns from the ground up. We optimised the email journeys in Klaviyo so the traffic we'd already paid for kept working. The result: less ad spend per month, more results out the other end.
Now run the hiring question against that engagement. A developer would have rebuilt the homepage to the old assumptions. A media buyer would have tuned campaigns pointing at broken journeys. The leverage was only visible to someone holding the growth data, the product decisions, and the build in the same head. That's the gap most NZ startups are actually trying to hire for, whether they name it that way or not.
When a developer is genuinely the right call
This cuts both ways, so here's the honest boundary. Hire a straight developer, not a consultant, when:
- The spec is proven and tight. Demand is validated, the definition of done is clear, and you own the product decisions with confidence.
- You're product-strong yourself. If you genuinely cover product and growth, buying strategy you already have is waste. Buy hands.
- You're past MVP and scaling. Product-market fit exists and the job is throughput, reliability, and speed. That's a developer's home ground, and a consultant hovering over it adds cost, not clarity.
A consultant who can't name these cases for you is selling, not advising.
The takeaway
Stop choosing between titles. Map your own coverage across product, engineering, and growth, be brutal about what you actually hold, and hire the gap. And before you sign off on 400 hours of development, spend 10 making sure they're pointed at the right thing.
/ From the workshop · Health platform · Queenstown
My Wellness: 10+ admin hours saved per practitioner every week.
Read the case study →
Frequently asked questions
- What does a product consultant cost compared to a developer in New Zealand?
- Contract developers in NZ typically run $80 to $150 NZD per hour. Independent product and growth consultants run $150 to $250 per hour, or $4,000 to $8,000 a month on retainer. The hourly gap looks like the consultant is dearer, but the comparison that matters is total spend to the right outcome, and wrong-direction development hours are the most expensive line item in any startup budget.
- Can't a good full-stack developer do the product thinking too?
- Some genuinely can, and they're worth holding onto. The test isn't whether they say yes to product questions, it's whether they push back on scope. Ask what they'd cut from your spec and why. A builder who has never talked you out of a feature is executing, not thinking, and you still own every product decision whether you realise it or not.
- What if my startup can't afford to hire either yet?
- Then don't hire, validate. A two-week demand test costs under $1,000 NZD and a scoped discovery under $4,000, and either will teach you more than a premature hire. Most early hiring mistakes happen because founders bought capacity before they knew what the capacity was for.
- Is there a middle option between a consultant and a developer?
- Yes, and for early-stage NZ companies it's often the right one: a builder who spans product, engineering, and growth in one head. You get the strategy and the shipping from the same person, with no handoff between the thinking and the build. The trade-off is that one person doesn't scale forever, which is fine, because neither does your stage.
- How does Garage 30 fit into this decision?
- Garage 30 sits deliberately in the overlap: engineering depth, product thinking, and growth instinct in one engagement. That suits founders who need the gaps covered rather than a single discipline. If you're weighing this exact hire, book a 30-minute call at cal.com/casey-hemingway/30min and we'll map your coverage honestly, including the cases where a straight developer is the better call.