Remote consulting vs local: does it matter for NZ product work?

For NZ product work, location matters in exactly one phase: discovery. Being in the building while you map a business surfaces what no video call can. After that, delivery is genuinely location-neutral, and limiting your search to consultants in your own city shrinks an already small national talent pool to a puddle.

Discovery is embodied. Delivery isn't.

Here's the distinction the remote-versus-local debate keeps missing: it argues about the engagement as if it were one kind of work. It's two.

Discovery is about finding out how a business actually runs, and businesses don't run the way anyone describes them on a call. They run in the workaround the ops person does every morning without thinking about it. The sticky note on the second monitor. The spreadsheet someone built in 2019 that turns out to be load-bearing. You find these by being there, watching work happen, and asking "what's that?" at the right moment. A video call shows you what people say they do. A room shows you what they do.

Delivery is different. Once the map exists and the priorities are agreed, the work is building, measuring, and iterating, and none of that improves because the person doing it is nearby. What predicts delivery quality is cadence: something shipped or learned every week, numbers you can both see, and a rhythm that doesn't depend on anyone's calendar aligning with a drive across town.

So the honest answer to "remote or local?" is: local where it pays, remote where it doesn't. In practice that's local discovery, remote delivery, and it's exactly how I run my own engagements.

The local-comfort tax

Now the uncomfortable part. New Zealand has a little over five million people. The number of consultants here who genuinely span product, engineering, and growth at once is small. The number in your specific town might be zero, and it's certainly not guaranteed to include the best match for your problem.

When a business insists on someone local, it isn't really buying better work. It's buying the comfort of a face across a café table, and it pays for that comfort with a smaller pool, a weaker match, and often a higher price, because local-only sellers know the buyer has already narrowed the field for them.

We already know this trade isn't necessary. Most NZ SMEs happily run their accounting through a Xero advisor they rarely meet and their legal work through someone they see once a year. The work is judged on outputs. Product and growth work deserves the same standard.

The proof case: Himalayan Trust

The engagement that settled this for me runs between New Zealand and Nepal. The Himalayan Trust's operations and automation work, like donation flows through Raisely and supporter journeys through ActiveCampaign and Klaviyo, serves people working in two countries, several time zones apart, with field teams that are sometimes days from reliable connectivity.

By the local-comfort logic, that engagement shouldn't function at all. It's been running for years. What makes it work has nothing to do with geography: a clear view of what the systems need to do, automation that keeps working between check-ins, and a steady rhythm of visible improvements. The distance never turned out to be the constraint. The systems and the cadence were always the thing.

If product and operations work can run NZ-to-Nepal, it can run Auckland-to-Queenstown without drama.

/ From the workshop · Ski-rental delivery · New Zealand / Japan

Snopro: 33x return on ad spend in the first Japan season.

Read the case study →

Better questions than "where are you based?"

If you're evaluating a consultant for NZ product work, geography is the least predictive thing you can ask about. Ask these instead:

• What will I see every week? The answer should be shipped work and real numbers, not a status report.
• When do you want to be on-site, and why? A good answer names discovery and specific leverage moments. A vague answer means they haven't thought about it.
• What does done look like? If there's no definition of done and no North Star metric, proximity won't save the engagement.

The takeaway

Pay for presence where it earns something: in the room during discovery, when watching the work beats hearing about it. Everywhere else, hire from the whole pool and judge on cadence and outcomes. The question was never remote versus local. It's whether you can see the work, and good work is visible from anywhere.