The Four Lenses: How We Evaluate Whether Automation Is Worth It

Most automation ROI calculations look at one number: how much time does this save, times an hourly rate. That's the easy math. It's also incomplete, and it's the reason a lot of automation projects either get approved when they shouldn't, or get rejected when they should have been built.

Over the projects we've evaluated, we've settled on a four-lens framework that captures the value automation actually creates. Two of the lenses produce dollar figures. Two of them don't, and trying to force them into dollars is what makes the standard ROI story unreliable. This article walks through each lens, why it's there, and how we use them together.

If you want to run a project through the framework yourself, our Is This Worth Automating? tool uses these four lenses to produce a written brief. The article below explains the thinking underneath it.

Why four lenses, not one ROI number

Single-number ROI is appealing because it's decisive. But it has two failure modes we see constantly.

The first failure mode is rejecting projects that are obviously worth doing. The classic version: a business owner says "I just hate doing invoices every month." The pure time-savings math comes out to maybe $8,000 a year, which doesn't clear most internal thresholds for a build. The project gets shelved. What the math missed is that the owner is the only person who knows how to do invoices, the process has compliance exposure if it slips, and the owner's actual constraint is energy, not money. The real value of automating this is somewhere between three and five times what the time-savings number shows.

The second failure mode is approving projects that shouldn't be done. A team adds up theoretical hours saved, multiplies by a loaded rate, and gets a big number. Nobody asks whether those hours actually free up anything useful, whether the process is stable enough to automate, or whether the team will trust the result. The project ships, the savings never materialize on the P&L, and the team learns the wrong lesson about automation.

Four lenses force the conversation to consider all the value, not just the part that's easy to quantify.

Lens 1: Hard cost savings (dollars out)

This is the lens everyone starts with, and it's the most rigorous one. The math is simple: how many hours per week does this work consume across the team, times a fully-loaded cost per hour, times 52. That's an annual dollar figure of time being spent on the work today.

"Fully-loaded" matters. If you pay someone $40 an hour in wages, their actual cost to the business is closer to $55-$65 once you include benefits, taxes, overhead, and the share of management time spent on them. Using the wage-only number underestimates the savings by 30-50%.

We also push for honest hour estimates. People consistently underestimate how long repetitive work actually takes because they only count the "doing" part. The right number includes context-switching, checking whether the work is done, fixing the inevitable mistakes, and the cognitive overhead of remembering it needs to happen at all. We typically ask for an estimate, then ask the person to track it for a week. The tracked number is almost always larger.

This lens produces the most defensible dollar figure in the framework, but it's only one part of the picture.

Lens 2: Revenue gains (dollars in)

Some processes don't just cost time, they cost deals. Lead follow-up is the obvious example. If leads sit unanswered for two days and the average lost deal is worth $5,000, then the cost of a slow process isn't just the salesperson's time, it's the deals slipping out the bottom.

When a prospect can name a specific frequency of misses (deals lost per month, leads that went cold, customers who churned because of slow response), we can quantify this. Misses per month times 12 times the value of each miss gives an annual revenue figure that adds to the hard cost savings number.

When they can't name a frequency, we still capture the lens qualitatively. "We know we're losing some deals to slow follow-up but we don't know how many" is honest and useful information, even though it doesn't produce a number. We document it as exposure without forcing a fake estimate.

The discipline here is not making up numbers. If a prospect doesn't know their miss rate, we don't invent one. Inflated revenue assumptions are how automation projects get approved on paper and disappoint in practice.

Lens 3: Risk reduction

This is the lens that doesn't produce a dollar figure, and the one most ROI calculators ignore entirely. But it's often the lens that makes or breaks an automation decision.

We focus on a few specific risk patterns:

Key-person dependency. When one person is the only one who knows how to do something, the business carries the risk of that person being unavailable. Automation that documents and executes the process turns tribal knowledge into a system.

Compliance and audit exposure. Manual processes produce inconsistent records. If your business has any kind of regulatory, contractual, or audit obligation, automated processes produce the consistent trail that those obligations require. The cost of a failed audit, a compliance finding, or a contract dispute is rarely budgeted for, but it's real.

Error rates with consequences. Some errors are cheap (a typo in an internal report). Others are expensive (sending the wrong invoice to a customer, missing a regulatory filing date). When the error frequency is meaningful and the error cost is high, automation that enforces consistency has value that doesn't show up in time savings.

Security exposure. Manual processes often involve shared credentials, spreadsheets with sensitive data, or workarounds that create security gaps. Automation can close those.

We don't try to assign a dollar figure to risk reduction. The numbers would be made up. Instead, we report it as a qualitative read of the exposure profile, and we name the specific risks. That gives the prospect what they actually need: a clear picture of what they're carrying and what would change.

Lens 4: Team and quality of life

This is the lens that the standard ROI math treats as worthless because it can't be quantified, and that the people doing the work treat as the most important thing in their day. Both are partially right.

What this lens captures: how the work feels, what people would do with the time they get back, and what the cost of frustration actually is.

The reason this matters isn't soft sentiment. Frustrating, repetitive work has real business consequences. Good employees leave businesses where the work is grinding. New hires take longer to ramp on processes that are unpleasant. The people who stay invest less energy. And the leadership team spends an outsized portion of their attention on processes that are constantly almost-failing.

We capture this lens by asking what makes the current work annoying, risky, or expensive (the prospect's own words usually capture the essence) and what they would do with the time and energy back. We mirror their answers in the final brief. The point isn't to assign a number, it's to make sure the decision-maker remembers why the project mattered when the math gets debated later.

How the lenses work together

The framework isn't four separate scores. It's one decision, viewed from four angles. Here's how we use them in practice.

The hard cost savings number anchors the financial conversation. It's the most defensible figure, and it's what a CFO will ask about first. If this number is too small, the project usually doesn't survive even if the other lenses are strong, because the math doesn't justify the build cost.

The revenue gains number, when we can produce one, often dominates the financial story. Time savings rarely produces enough dollar value on its own for a small business; the deals saved is what makes the math work. When revenue gains are unquantified, we note that the financial story is conservative, anchored only by the time savings.

The risk lens is the swing factor. A project with modest financial returns but meaningful risk exposure (compliance, key-person dependency) often gets approved because the alternative is worse than the cost. A project with strong financial returns but no risk story is fine, just less urgent.

The quality-of-life lens is the tiebreaker, and sometimes the lead. For owner-operators especially, this lens is the actual reason they want to do the project, and pretending otherwise is dishonest. We name it explicitly so it doesn't get dismissed.

The verdict at the end isn't "the number cleared a threshold." It's whether the four lenses together tell a coherent story about why this project is worth doing now, worth doing eventually, or not worth doing.

Why this matters for your decision

If you're evaluating an automation project, the four lenses give you a framework that doesn't lie to you in either direction. It won't talk you into a project the math doesn't support, and it won't let you walk away from one where the time savings alone underestimate the real value by 3x.

You can apply the framework informally just by asking the four questions about any project you're considering. Or you can run a specific project through our Is This Worth Automating? tool, which uses this exact framework to produce a written brief with the math and the recommendation.

Want help thinking through your own project?

Run it through our free assessment tool: Is This Worth Automating?

Or if you'd rather just talk it through: Book a 30-minute call