Build vs buy: when a custom internal tool is actually the right call

The five real options

Every internal-tooling decision comes down to five choices. Most comparisons skip the first one, which is a mistake — it is often the right answer.

1. Keep doing it by hand

A spreadsheet and a person. Genuinely correct when the volume is low and the process is still changing shape every month. Automating a process you have not settled yet just locks in the wrong version of it.

2. Buy off-the-shelf SaaS

Someone has already built your process as a product. Cheapest and fastest by a wide margin when it fits — and you should look hard before concluding it does not.

3. Glue it together with Zapier or Make

Connect the tools you already pay for. Excellent for linear, low-volume flows: when this happens, do that. Costs rise with task volume rather than with value.

4. Build on Retool or another low-code platform

Assemble internal screens over your existing databases and APIs, quickly. Powerful, and priced per builder seat forever.

5. Commission a custom build

Software shaped to your process that you own outright. Highest upfront cost, no per-seat or per-task ceiling, and the only option where the asset is yours.

Side by side

Vendor figures are USD list prices as published in August 2026. Avokodo prices are in New Zealand dollars.

Zapier counts a task as each successful action step; triggers and filters are free, and overages bill at 1.25× your effective rate. Retool counts builder seats separately from end users.

When off-the-shelf wins — and you should not hire anyone

If a product already does 80% of what you need and the missing 20% is preference rather than necessity, buy the product. It will be cheaper than any custom build, it is maintained by a company whose entire business is maintaining it, and it works on Monday.

The trap is the reverse: bending a genuinely specific process to fit a product because the product was cheaper, then paying for that mismatch in staff time every week for three years. The question is not "does this tool do the job" but "what does my team have to do differently to make it fit, and what does that cost annually".

When Zapier or Make wins

Zapier is the right answer for linear, low-volume connective work: a form submission creates a CRM record, a payment posts to a channel, a signed document files itself. Set up in an afternoon, no developer needed, and on the free or Professional tier it costs less than lunch.

It stops being the right answer at volume and at complexity. Pricing runs per task — each successful action step — so cost scales with how much work it does rather than how much value it creates. Once a flow needs real branching, retries that mean something, or a decision that depends on three systems agreeing, you are building software in a tool not designed for building software. That is usually where the maintenance pain starts.

The honest rule: if your monthly task count is stable and modest, keep Zapier. Avokodo will say so.

When Retool or low-code wins

Retool is genuinely good, and it wins when you have a technical person in-house who will own the tool long-term. If someone on your team can and will maintain it, a low-code platform gets you internal screens fast and keeps the changes in your hands.

Two things eventually bite. The first is seat pricing — the Business plan runs about USD $50 per builder per month billed annually, and that is a bill with no end date. The second is the ceiling: low-code platforms are excellent right up to the point where you need something the platform does not do, and then you are stuck in a way that is expensive to undo.

If you have no in-house technical owner, low-code tends to become the thing nobody maintains — which is worse than either buying or building.

When a custom build wins

Custom is right when the process is the point. If how your business handles orders, claims, jobs or approvals is genuinely specific — and especially if that specificity is part of why customers choose you — bending it to fit a product costs you the thing that made it worth having.

It also wins on arithmetic once rented pricing compounds, and on ownership. You get the code, you can hand it to any developer, and the bill does not grow because you hired three more people.

It is the wrong call when your process is ordinary, your volumes are small, or nobody on your side can make decisions about scope. Custom software needs someone who knows how the work actually happens.

The rented-versus-owned arithmetic

Subscription pricing looks small monthly and large in aggregate. Three years is a fair window for an internal tool. Vendor figures below are USD list converted at roughly 1 USD ≈ 1.7 NZD, rounded, for comparison against Avokodo's New Zealand dollar pricing.

Read that honestly: Zapier is genuinely cheaper over three years, and if a Zapier flow does the job you should keep it. The custom build beats the low-code seat model at five builders, and unlike both it leaves you owning an asset rather than a renewal date. Task volume and seat count are what move these numbers, so run them with your own.

How to decide in ten minutes

Answer these six honestly. They are ordered so the cheapest answers come first.

1. 01Has the process stopped changing shape? If not, do not automate it yet.
2. 02Have you actually trialled two off-the-shelf products? If not, do that first.
3. 03Could a linear "when this, then that" flow cover it? If yes, try Zapier.
4. 04Is your monthly task volume small and stable? If yes, stay on Zapier.
5. 05Do you have someone in-house who will own a low-code tool for years? If yes, Retool is viable.
6. 06Is the process specific to how your business works, and does per-seat or per-task pricing already hurt? If yes, build.

If you answered your way to the bottom, a custom build is probably right. If you stopped earlier, the cheaper answer is the correct one, and Chris Greeff would rather tell you that on a call than sell you a build you did not need.

Common questions

Full pricing detail is on the pricing page.