Build a Business Case Without Inventing ROI

A prospect asks for a business case before their team has measured time, cost, or operational risk. The request is reasonable. Leaders often need a clear picture before they assign people to an evaluation. Trouble starts when a seller fills gaps with a polished return on investment claim. A business case should organize known evidence, identify missing evidence, and set out assumptions for validation.

Start with observed work. Ask a buyer to describe one recurring task from beginning to end. Who performs the task? What starts the work? Which systems or files do people open? Where does a handoff occur? What happens when information is missing? These questions produce a useful record without forcing a number into an early conversation.

Suppose a fictional support organization says supervisors spend part of every Friday reconciling three reports before a weekly meeting. Do not turn this statement into annual savings. Ask which reports exist, who produces each report, and what supervisors seek during reconciliation. The buyer might explain one report tracks open cases, another shows escalations, and a third lists staffing changes. A mismatch might signal a data issue, a reporting habit, or a leadership question. Detail matters before anyone assigns financial value.

Ask what evidence the buyer already trusts. Evidence might include a calendar entry, process document, system report, sample file, or direct observation from a manager. Record the source beside every statement. If a supervisor says reconciliation usually takes two hours, name the supervisor and label the source as an observation. If an operations analyst supplies a report, record its date and owner. This discipline keeps facts separate from early impressions.

Use clear labels for each kind of information. An observation describes work someone sees today. An assumption fills a gap awaiting verification. A question identifies information nobody has supplied. A decision records a buyer choice. These labels stop a spreadsheet from turning guesses into accepted facts. They also help finance, operations, and leadership review a case without arguing about the origin of each line.

An assumptions sheet needs no complex formula. Start with item, description, source, owner, confidence, validation date, and notes. For the fictional Friday reconciliation example, one row reads, “Supervisor review time. Operations manager reports roughly two hours each Friday. Source: manager observation during a 3 September discussion. Owner: operations manager. Confidence: preliminary. Validation date: 17 September.” The row does not claim a result. The row identifies work for the buyer to check.

Confidence does not measure optimism. Use simple labels such as observed, preliminary, or pending review. Avoid artificial precision for a number nobody has tested. A buyer might prefer a range when schedules vary. Record why variation occurs. Month end often requires more review, or one team might handle more complex cases. A range with an owner and reason serves a discussion better than one figure presented as settled.

Keep a hypothesis separate from a committed outcome. A hypothesis might state a shared record might reduce repeated report reconciliation. Such a statement opens a question for the buyer. A committed outcome would state supervisors will save a fixed number of hours. Do not write the second statement without buyer evidence and buyer approval. Your role involves structuring a discussion, not supplying an outcome for someone else.

When a buyer asks, “What return do other customers get?” acknowledge the question without borrowing another organization’s circumstances. Say, “I do not want to present another team’s experience as your forecast. Which part of your current process would you like to measure first?” This response returns attention to their data, people, and decisions. A buyer seeking a comparison might explain which cost category leadership expects to see. Ask who owns those numbers and how they normally review them.

Consider a fictional practice situation with Aisha, an account executive, and Leo, a service director. Leo wants material for a budget meeting in ten days. He believes supervisors spend too much time combining reports, yet he has no reliable baseline. Aisha asks Leo to describe last Friday. He says two supervisors reviewed three reports from 1:00 p.m. until roughly 3:30 p.m. before their staff meeting. Leo is unsure whether this occurs every week.

Aisha does not annualize the observation. She asks who has access to recent meeting records and which supervisor participated. Leo names Tessa, who leads one supervisor group. Aisha writes an observation: “Two supervisors reconciled three reports for roughly two and a half hours on Friday. Source: Leo’s recollection. Confidence: preliminary.” She writes a validation item: “Tessa will review the next two Friday sessions and note start time, end time, report names, and unresolved differences.” Leo agrees, though his budget meeting arrives after only one session.

Leo then asks whether Aisha’s company typically promises a certain return. Aisha says, “We should build your meeting material from evidence your leaders recognize. Which choice does your budget group need to make?” Leo says he needs approval for a deeper evaluation, not approval for a purchase. This distinction changes the business case. The document now needs to explain why measuring reconciliation work deserves staff time. No purchase forecast belongs in this early record.

Together, they select a small scope. Tessa will track one Friday process before the meeting. Leo will ask an analyst for copies of the three reports used during review. Aisha will prepare a one page record with observations, open questions, and a proposed next step. The proposed next step is a focused review with Leo, Tessa, and the analyst. They will compare report fields and identify differences needing manual investigation.

Business cases often mix cost, risk, and service quality in one discussion. Keep these categories separate. Some managers say delays affect customer experience. Ask for an observed example instead of translating concern into revenue or retention. An operations owner might worry about errors. Ask which errors occur, how people notice them, and what work follows. A finance partner might need a cost view. Ask which internal source they use and which assumptions they require. Place each answer beside its source.

Review wording before sending anything. Remove phrases such as will save, will reduce, or proven impact unless the buyer supplied supported language for their own decision record. Check each number against its source. Check each source for an owner. If an assumption lacks a validation date, ask whether a date belongs there or whether the line should remain an open question. In the fictional situation, Aisha sends Leo the one page record. Its final line schedules a twenty minute meeting for 18 September. Leo, Tessa, and the analyst place the three report copies side by side, mark each field needing manual reconciliation, and assign Tessa to record the next review start time before they leave.