← Back to Field Notes

December 8, 2025 · The Bloomfield Team

How to Build a Business Case for Technology Investment

Sixty-seven percent of proposed manufacturing technology investments never make it past the initial approval meeting. The operations manager knows the problem. The shop floor team knows the problem. The numbers support a fix. The proposal lands on the owner's desk and dies there, not because the investment is wrong but because the case was built wrong.

The issue is framing. Most technology proposals in manufacturing are built around what the technology does. The proposals that get funded are built around what the business loses by not having it.

For a deeper look at how these ideas connect across the shop floor, see our complete guide to AI in manufacturing.

Start With the Cost of the Current State

Every technology investment proposal should open with a number: the annualized cost of the problem you are solving. This number needs to be specific, defensible, and drawn from your own data.

If you are proposing a quoting automation tool, the cost of the current state is calculable. Take your average quote turnaround time. Look at your win rate. Apply the documented relationship between response time and win rate. Multiply the difference in wins by your average job value. That is the revenue your current quoting process leaves on the table every year.

If you are proposing a knowledge management system, the cost is the ramp time for new hires multiplied by annual turnover, plus the margin impact of errors during the learning period, plus the cost of the next retirement that takes twenty years of institutional knowledge out the door. We have seen this number exceed $500,000 for a single departure at shops running specialized work.

The goal is to make the current state expensive in the listener's mind before introducing the proposed change. If the problem costs $400,000 per year and the solution costs $120,000, the conversation shifts from "can we afford this" to "can we afford to wait."

Define the Scope Tightly

Proposals that try to solve everything get funded last. The business cases that move forward target a single, well-defined process with a measurable outcome.

Bad scope: "We need to modernize our technology infrastructure." Good scope: "We need to reduce our average quote turnaround from 4.2 days to 1.5 days, which our data shows will increase our win rate from 14% to approximately 30%, generating an estimated $960,000 in additional annual revenue."

Tight scope also makes the project easier to evaluate after implementation. If you promised a specific improvement to a specific metric, you either hit it or you did not. That accountability makes leadership more willing to approve the next investment.

Use Your Own Numbers

Industry benchmarks are useful for context. They are not useful as the foundation of a business case. When a CFO sees "industry average" in a proposal, they mentally discount everything that follows. When they see their own ERP data, their own quoting metrics, their own reject rates, the conversation changes.

Pull six months of data from your ERP. Calculate your actual quote-to-win conversion rate. Measure the actual hours your estimators spend on research versus decision-making. Count the actual number of jobs that shipped late due to material delays that could have been flagged earlier. These are the metrics your CFO already understands, and presenting them with precision demonstrates that the proposal is grounded in your operation's reality.

Address the Real Objections Early

Technology proposals at manufacturing companies face three consistent objections, and the best business cases address all three before they are raised.

"We tried something like this before and it did not work." Acknowledge the history directly. Name the previous project, identify why it failed (typically scope creep, poor data preparation, or lack of adoption support), and explain specifically how this proposal addresses those failures. If your shop had a bad ERP implementation in 2018, say so. Then show why starting with a focused pilot avoids the same pattern.

"Our people will not use it." Show that the proposed tool integrates into existing workflows rather than replacing them. Describe how your team was involved in defining the requirements. If possible, reference a conversation with the estimator, scheduler, or supervisor who will use the tool daily and their specific feedback on the proposed approach.

"What happens if the vendor goes away?" Address data ownership, system portability, and ongoing maintenance requirements. Manufacturers have been burned by vendors who disappeared or pivoted. Show that your data stays yours and the system can be maintained independently if needed.

Build the Timeline Around Quick Wins

A 12-month implementation timeline with benefits starting in month 10 is a hard sell. A 90-day phase one that delivers measurable improvement, followed by planned expansions, is a much easier conversation.

Structure the proposal so that the first value delivery happens within 60 to 90 days. For a quoting tool, that might mean connecting to the ERP and surfacing historical job data for new quotes. Not the full vision. A working piece that your team uses daily and that produces data showing improvement. That data becomes the business case for phase two.

Present the Decision as Timing, Not Whether

The best business cases position the investment decision as a question of when, not whether. If your competitors are quoting in half the time, the market pressure will eventually force the investment regardless. If retirements are accelerating, the knowledge capture challenge only gets worse with each passing quarter. If data connectivity is already limiting your ability to grow, adding volume without fixing the infrastructure will amplify the problem.

The question for leadership is whether they want to make this investment from a position of strength, with time to implement thoughtfully, or from a position of urgency when the cost of waiting becomes undeniable.

Present the data. Show the cost of the current state. Define a tight scope with measurable outcomes. Let the numbers carry the argument.