The Real ROI of Custom Tools: A Simple Framework for the Build-vs-Buy Decision

A back-of-the-envelope way to evaluate whether a bespoke build pays off, using the hours-saved model and client outcomes.

“Should we build this or just live with the workaround?” is one of the most common questions growing businesses face — and most answer it by gut feel. There's a simpler, more honest way.

Here's a framework you can run on the back of a napkin before you commission anything.

The cost of the status quo: manual work, every week

Start by pricing what you already do. Take the task you're considering automating and estimate the hours it consumes each week, then multiply by a loaded hourly cost for whoever does it. That weekly number, annualized, is the true price of the status quo.

Most people underestimate it badly, because manual work hides in fifteen-minute increments scattered across the week. Add them up honestly and the figure is usually larger than expected.

The build-vs-buy framework in three numbers

You only need three numbers. First, the annual cost of the status quo. Second, the cost to build the tool. Third, the cost to maintain it. If the first comfortably exceeds the sum of the other two within a reasonable payback window, building is the rational call.

What's changed is the second number. When a build takes an afternoon instead of a quarter, the math tips toward “build” far more often than it used to.

Worked example: 20 deliverables a month

Say a recurring deliverable takes eight hours at a $100 loaded rate — $800 each. A vibe-coded version takes two hours, or $200. That's $600 saved per deliverable. Across 20 a month, that's $12,000 in monthly capacity reclaimed.

Even if the tool took a full day to build and needs occasional upkeep, the payback period is measured in days, not years.

When custom isn't the right call

Custom isn't always the answer. If a task happens rarely, changes constantly, or is handled well by an existing tool you already pay for, building adds complexity for little gain. The framework protects you from over-building as much as under-building.

The goal isn't to build everything. It's to build the things where the status quo quietly costs more than the fix.

Run the three numbers on the task that annoys your team most. If the math says build, we can have a working version in front of you within the week.