Who you're actually hiring

15 years of shipping other people's production software

Before Avokodo, Chris Greeff spent 15 years building software that real businesses depend on daily — most of it in New Zealand's tech sector.

Xero

Cloud accounting used by millions of small businesses worldwide.

Vend

Retail point-of-sale software, later acquired by Lightspeed.

First AML

Anti-money-laundering compliance software for financial services, law and accounting firms.

Cotiss

Procurement and tender management software.

CoachMate

The grassroots coaching platform for Golf NZ, Basketball NZ and NZ Football.

That is the experience an Avokodo build draws on: production systems with real users, real data and real consequences when they go wrong — not weekend projects.

How this actually works

Avokodo is deliberately part-time and deliberately small. Chris Greeff takes a limited number of projects at a time, which is exactly why the scope is fixed before work starts and why builds are sized to go live in 2–4 weeks rather than running for six months.

That constraint is the reason the price works. A NZ$1,000–NZ$5,000 build is only possible because there is no bench to fill, no discovery phase to bill, and no layer of people between you and the code. It also means Avokodo says no to work that does not fit — which is better for both sides than saying yes and delivering late.

What happens if I get busy, or get hit by a bus

This is the real question when you hire one person part-time to build something your business will depend on, and it deserves a straight answer rather than a reassuring noise. Avokodo is set up so that the answer is "you are fine", and here is specifically why.

You own the code, from day one

Not a licence, not a seat, not access while you keep paying. The repository and the source are yours, and you can take a copy at any point without asking.

Nothing exotic in the stack

Builds use mainstream, widely known tools. Any competent developer can read the code and continue it — there is no bespoke framework or private library that only Avokodo understands.

The monthly is cancellable, always

It buys hosting, monitoring and upkeep. It is not a licence for software you already paid to have built, and stopping it does not switch anything off that you own.

Handover is written down, not in someone’s head

How it runs, where it is deployed and how to change it are documented as part of the build, so a new developer starts from notes rather than from archaeology.

The honest version: hiring a small operation means accepting a smaller team, and the right way to de-risk that is ownership and portability rather than promises. That is why every point above is about what you keep if Avokodo stops, not about assurances that it won't.

When Avokodo is the wrong choice

Saying this on a sales page is unusual, but a project that was never a fit helps nobody.

• →You need a team of several people working in parallel to a deadline.
• →The system is safety-critical or falls under a formal compliance regime needing audited processes.
• →You want a consumer product, a mobile app or a marketing website rather than an internal tool.
• →You need guaranteed same-day response or on-call cover outside business hours.
• →The work genuinely needs a full-time partner embedded in your business for months.

In any of those cases Chris Greeff will say so on the first call and, where possible, point you at someone who does fit.

Where Avokodo is

Avokodo is based in Tauranga, New Zealand, and works remotely with teams anywhere. Quotes and invoices are in New Zealand dollars. Most projects run over a handful of calls plus written updates, so time zones have not been a problem — but if your team needs frequent live overlap outside New Zealand hours, say so on the first call.

Chris Greeff on LinkedIn — the work history above is checkable there.