Value Communication & Business Case Questions

Direct answer

Build one story with a spine all three share, then give each executive a short section in their own measure, and move depth into an appendix so the main deck stays short. The CFO (chief financial officer) gets money and payback (the month when cumulative savings first cover the cost), the CIO (chief information officer) gets architecture and risk, and the Head of Operations gets rollout and day-to-day impact.

Main deck: 8 slides, one visual each

Each slide has one visual because a CFO and an operations lead will each study only the visual that matters to them.

What the key slides actually say (illustrative figures: $150,000 first-year cost, $216,000 yearly benefit, so $18,000 a month)

• Slide 1 headline: "Approve $150,000 to remove $216,000 a year of manual order-handling cost; payback in month 9."
• Slide 4 cumulative cash (cumulative cash is the running total of money in minus money out): month 0 is -$150,000, month 4 is -$78,000, month 8 is -$6,000, month 9 is +$12,000. The curve crosses zero in month 9, and that crossing is the point marked on the chart.
• Slide 5 three-year TCO: status quo $1,578,000 ($526,000 a year: $310,000 of current systems and support plus the $216,000 of manual order handling) against proposed $1,080,000 ($310,000 a year of running cost that stays, plus the $150,000 one-time cost). The $498,000 gap equals 3 x $216,000 - $150,000, so the TCO bars reconcile with the payback curve on slide 4.
• Slide 6 risk table, one sample row: Risk: data migration overruns by 4 weeks. Likelihood: medium. Mitigation: migrate in two phases against a fixed-scope plan. Owner: Head of Operations.

What each executive gets in the main story

• CFO: slides 4 and 5: payback, three-year TCO, the two assumptions the result depends on.
• CIO: slides 3 and 6: how it fits the current estate (the customer's existing systems), integration effort, security and resilience.
• Head of Operations: slides 6 and 7: what changes for their teams, phasing, rollback.

Appendix for the deeper questions

Appendix slides are not presented; they sit ready for the follow-up question. If time is short, build A1, A6 and A7 first, because finance and risk questions come up in almost every review:

• A1: Calculation detail and every assumption with its source (for the CFO and procurement)
• A2: Decision drivers (the criteria the buyers will score the options on) and approvals required (for the people who sign off)
• A3: Benchmarks (measured results from comparable customers) against comparable deployments (for a high-cost, high-reliability solution)
• A4: Compliance attestations (formal statements by an auditor that a standard is met) and certifications
• A5: Operational runbooks (step-by-step procedures for running the system): failure handling, escalation and rollback
• A6: Risk register with owners
• A7: Sensitivity analysis (how the result changes when one assumption changes, for example payback if the benefit is 20% lower)

Shorter forms of the same story

The 8-slide main deck above is the core. The three forms below are cut-downs for specific slots, not alternatives to design first.

• 3-slide CFO pitch: (1) cost reduction, (2) implementation risk and vendor credibility, (3) ROI (return on investment) and payback. Each slide ends with one line of evidence, such as a customer reference or the audited baseline.
• One-page value summary: per stakeholder, a headline metric, one supporting data point and one or two sentences of message.
• 10-slide funding deck (12-month expansion): the 8 slides above plus a slide on the 12-month milestones and one on the funding request by phase.

Pitfalls

• A single deck that tries to answer every question; put it in the appendix.
• Metrics owned by nobody in the room. If the Head of Operations has no number on any slide, they will vote against.
• Showing the CFO a feature list. They need the chart that explains when the money returns.

Direct answer

I would run the CFO conversation in the CFO's own frame: cash, accounting treatment and risk, with outcomes on the same page as cost. The one-page comparison puts options in columns (managed service, self-hosted, or a cheaper competitor) and puts cost lines and outcome lines in rows, so total cost of ownership (TCO: every cost of owning the solution over a set period, not just the price) sits next to what the spend buys. Capex (capital expenditure, a large up-front purchase that is depreciated, meaning its cost is spread across its useful years in the accounts instead of hitting one budget at once) and opex (operating expenditure, an ongoing expense in the period it occurs) are shown separately so finance can place each correctly.

How I structure the conversation

1. Confirm the decision and horizon. "Are we comparing over three years, and which budget does each option draw on?"
2. Show the cost side by type. Up-front (capex or one-off), recurring (opex), and hidden costs (staff time, implementation, support).
3. Show the outcome side. What each option does for recovery time, risk and benefit realisation, valued in dollars where I can defend it.
4. Show the risk side. Where operational expense and risk fall: with the vendor under the managed option, with the customer's team under self-hosted.
5. Land the recommendation in one line.

The one-page comparison (illustrative figures, three years)

Two things to know before reading the table. First, present value at 8%: money paid in later years is worth less than money today, so each year's cost is divided by 1.08 for every year of delay (8% is an assumed cost of capital, the return the company could earn on the money elsewhere, which finance should supply). For example, managed year 1 is 240,000 / 1.08 = 222,222. Second, the last two rows rest on this assumption: recovery time is the contractual target for how fast service returns after an outage (often called the RTO, recovery time objective), and each option has 2 incidents a year at $25,000 per hour of downtime. So managed is 1 hour x 2 x 25,000 = $50,000 and self-hosted is 4 x 2 x 25,000 = $200,000.

RATE = 0.08  # assumed discount rate

def pv(amount_by_year):
    return sum(a / (1 + RATE) ** t for t, a in enumerate(amount_by_year))

managed = {
    "Setup and migration (one-off)": [60_000, 0, 0, 0],
    "Subscription": [0, 180_000, 180_000, 180_000],
    "Staff time (0.5 engineer)": [0, 60_000, 60_000, 60_000],
}
selfhosted = {
    "Hardware and licences (capex)": [220_000, 0, 0, 0],
    "Implementation (one-off)": [90_000, 0, 0, 0],
    "Support contract and power": [0, 50_000, 50_000, 50_000],
    "Staff time (1.5 engineers)": [0, 180_000, 180_000, 180_000],
}
def total(opt):
    return [sum(v[t] for v in opt.values()) for t in range(4)]
for name, opt in [("Managed", managed), ("Self-hosted", selfhosted)]:
    t = total(opt)
    print(f"{name:12s} by year={t} 3yr total={sum(t):,} PV@8%={pv(t):,.0f}")

COST_PER_HOUR = 25_000
for name, rto_hours, incidents in [("Managed", 1.0, 2), ("Self-hosted", 4.0, 2)]:
    print(f"{name:12s} expected downtime cost/yr = {rto_hours*incidents*COST_PER_HOUR:,}")

Output:

Managed      by year=[60000, 240000, 240000, 240000] 3yr total=780,000 PV@8%=678,503
Self-hosted  by year=[310000, 230000, 230000, 230000] 3yr total=1,000,000 PV@8%=902,732
Managed      expected downtime cost/yr = 50,000.0
Self-hosted  expected downtime cost/yr = 200,000.0

Adding expected downtime (3 years undiscounted: managed $150,000, self-hosted $600,000), risk-adjusted totals are $930,000 vs $1,600,000. The three metrics I would put in the headline of the narrative are recovery time (1 hour vs 4 hours), three-year TCO ($780,000 vs $1,000,000), and staff cost ($60,000 vs $180,000 per year). The downtime assumption (2 incidents per year at $25,000 per hour of downtime, recovery targets as stated) is the most sensitive input and must come from the customer's own incident history.

Cheaper-competitor version of the template

Same rows, and the competitor goes in a third column. The cheaper licence will show on the subscription row, so I would add rows for what is not in their price (integration work, extra staff, outage exposure) and fill each from evidence, not assertion. If the evidence does not support the extra cost, I concede that the competitor is cheaper on cost and lead with outcomes.

Explaining it to a non-technical procurement stakeholder (short slide structure)

1. Decision and horizon (one sentence).
2. What each option is, in plain terms ("we run it" or "you run it").
3. Three-year cost, one bar per option.
4. Three headline metrics: recovery time, three-year TCO, staff cost.
5. Where the risk sits (who gets the call at 2 a.m.).
6. One-line recommendation: "Choose the managed service: about $220,000 lower over three years and recovery in 1 hour, assuming the outage history we used."

Trade-offs and pitfalls

• Capex vs opex: self-hosted looks cheaper per year ($230,000 vs $240,000 recurring) but needs $310,000 on day one. Whether capex is worth it depends on the customer's cost of capital and how finance treats depreciation, so ask them.
• Do not hide the managed option's weakness: lock-in and a recurring bill that never ends. Say it.
• Benefit realisation (checking after go-live that the promised benefit really arrived): say who owns tracking it, or the CFO will assume nobody does. Here the benefit is avoided downtime of about $150,000 a year (200,000 minus 50,000) plus $120,000 a year of staff time (180,000 minus 60,000). The customer's operations lead would report both quarterly from the incident log and the timesheets, against these targets.

Direct answer

Before a renewal, the CFO wants one thing from the deck: evidence that the money spent returned what was promised, in numbers Finance can audit. I would build an eight-slide deck that opens with the answer, shows realized value against projected value line by line, says how every number was measured, shows risk reduction separately and conservatively, admits the gaps, and ends with the renewal in terms of the next twelve months. The CFO (chief financial officer) is the audience; a QBR (quarterly business review) deck, which normally covers usage, support tickets and roadmap and says little about money, would be too soft for this audience. The brief is about presenting the numbers, not building the model, so the structure below assumes a value model already exists.

Terms: a baseline is the "before" number a benefit is measured against (for example, the cost per invoice in the three months before the product). Go-live is the day a team starts using the product for real work. Hard savings are cash that actually leaves the budget (a cancelled licence); productivity is capacity released, not cash. The counterfactual is what would have happened without the product. Re-baselining is changing the baseline after the fact, which is why it must be visible. Recurring benefits repeat every year; one-time benefits (a one-off clean-up) do not. ROI (return on investment) is net benefit divided by cost. Causal attribution means showing the product, not something else, caused the change.

Slide-by-slide structure and the data behind each

Worked numbers for slides 3, 6 and 7 (illustrative)

Realized share: 780,000 / 1,000,000 = 78%. Gap: $220,000. Drivers on slide 7: two of five business units went live a quarter late, worth about $120,000 this year and recoverable next year; the remaining $100,000 is lower per-transaction savings than the model assumed, which is a model correction, not a delay.

ROI on slide 6. With subscription and services cost of $400,000 for the year: realized ROI = (780,000 - 400,000) / 400,000 = 95%, against 150% projected ((1,000,000 - 400,000) / 400,000). ROI is net benefit divided by cost.

Showing risk reduction credibly (slide 5)

Risk benefits are the first thing a CFO discounts, so I present them as a separate line, never inside the $780,000. The method is expected loss avoided: the number of incidents multiplied by the average cost per incident, taken from the customer's own log, not an industry average. Example: the customer's log shows 3 serious incidents a year before at an average of $90,000 each ($270,000), and 1 this year ($90,000). Two avoided incidents at $90,000 is $180,000. I label it "indicative: one year of data, causal attribution is partial", and I show the incident count so the CFO can judge whether two avoided incidents is signal or luck. I do not add it to ROI.

Finance questions I would prepare for

1. "Is the $160,000 of productivity real cash?" No: it is capacity, not budget released. I show where the hours went (for example, more audits done) and let the CFO decide how to treat it. I never present it as savings that reduce headcount unless it did.
2. "What baseline did you use and who agreed it?" Point to slide 4 and the sign-off. In words: "The baseline is your own cost per invoice for the three months before go-live, pulled from your finance system and signed off by your controller on the date shown on slide 4. If you want a different baseline, I will show both."
3. "What would have happened without the product?" The counterfactual: I show the trend before go-live and any other change in the period, and say what I cannot separate. In words: "Invoice volume was already flat before go-live, and the hiring freeze in the third quarter also reduced effort. I show both on slide 4. What I cannot cleanly separate is the freeze's effect on the productivity line, which is why that line is tagged estimated."
4. "Why 78% and not 100%?" Slide 7, with the $120,000 timing and $100,000 model correction.
5. "What does next year look like and what are you assuming?" Slide 8, with the same baseline, the late units' benefit now arriving and no new promises.
6. "What are the total costs, including our internal time?" I include customer-side effort in the cost line so the ROI is not flattering.
7. "How much of this is one-off?" Separate recurring from one-time lines, and say so. In words: "All $780,000 is recurring: the licence retirements and invoice savings repeat every year, and I expect the productivity line to as well. If there were a one-off item, such as a one-time data clean-up saving, I would show it on its own row so year two is not overstated."
8. "What if we do not renew?" Answer honestly with the costs of leaving, kept factual and short. A CFO who senses a threat stops listening.

Trade-offs and pitfalls

• Realized and projected must sit side by side. Showing only realized hides the gap and the CFO will find it.
• Never re-baseline quietly. If the baseline changed, say when and why, and show both.
• Estimated numbers wear a label. Mixing estimated and measured values without tags makes the audited number look like the guessed one.
• What I would change by customer: with a sceptical CFO I would put slide 4 (method) before slide 3 (results), so the method is accepted before the number arrives.

Direct answer

Do not defend the price or discount to match. Move the comparison from price per licence to cost and outcome over the life of the deal, in three steps: (1) agree what exactly is being compared, (2) put the whole cost of each option on the table, and (3) offer a test that settles "feature parity" on the buyer's own requirements instead of on a datasheet (the vendor's own marketing summary of what the product does). The two pieces of evidence I would bring are a requirement-by-requirement parity test (a side-by-side check that the rival really does everything the buyer needs) on the buyer's own data and a reference customer's measured outcome and total cost.

Terms: procurement is the team that negotiates price and terms; TCO (total cost of ownership) is all costs over the life of the purchase; list price is the published price before discount; feature parity is the rival's claim that its product does everything yours does, so the lower price is a free saving.

The three-point response, with live phrasing

1. Agree the basis of comparison. "Fair point, and I want to make sure we compare the same things. What does the 15% include? Does their quote cover the integration work, support level and the two requirements your team listed as critical?"

2. Move to cost and outcome over three years. "Price per licence is one line. What your business pays is licence plus the people and time to run it, plus what happens when it falls short. Can we put both options side by side over three years, using your numbers?"

3. Offer a test that proves or disproves parity. "You say feature parity. Let's test it. Pick your three hardest requirements and let us run both against a sample of your own data, with your team scoring the result. If they match, you have saved 15%. If they do not, you have avoided paying for the gap later."

If you only get a few sentences live, use: "Understood. Before we compare price, can we compare what you'd get for it? Let's test the three requirements that matter most to you, and put total cost over three years next to the licence number."

Illustrative arithmetic (replace with the buyer's real data)

The assumed run costs are, for example, ours: $25,000 of admin time plus $15,000 of tooling and support; rival: $45,000 of admin time, $25,000 of extra tooling and $15,000 of manual workarounds for the gap. On these assumptions the rival costs $15,000 a year more. The assumption that decides the outcome is the rival's added run cost: it breaks even at $70,000 ($240,000 minus $170,000). Below that, the rival is cheaper, and I should say so rather than hide it. That is why the number must come from the buyer's data or a parity test, not from my slide.

The two pieces of evidence

1. A parity test on the buyer's data (a proof of concept: a short, time-boxed trial of the product on real data, scored against criteria agreed in advance). It converts "feature parity" from a claim into a result. A scored sheet might look like this: Requirement 1, bulk import of 50,000 records: ours pass, rival pass with manual clean-up (partial). Requirement 2, role-based approval workflow: ours pass, rival fail. Requirement 3, report in the buyer's format: ours pass, rival pass. Each row is scored by the buyer's team, not by us, against a pass criterion written down before the test.
2. A reference customer with a measured outcome and full cost, ideally of similar size: "they chose us over a cheaper option and saw X, at a total cost of Y over three years". Get permission and exact figures; do not paraphrase.

Trade-offs and pitfalls

• Discounting first teaches procurement that price is the lever. If the price must move, trade it for something (term length, volume, or reference rights, meaning the buyer agrees to act as a reference customer that you may name publicly or let other prospects call), do not give it away.
• Procurement is measured on price, so attacking their frame fails. Give them a defensible rationale to take to the budget owner.
• If the test shows the rival really is equivalent for this buyer, say so and negotiate on terms; trust is worth more than one deal.

Direct answer

My approach is: treat the pushback as information, not as an attack. I find out which part of the ROI claim is really being challenged (the inputs, the logic, the ownership, or the risk), test that part with the buyer's own data, and adjust the proposal rather than defend the number. I would answer this question with a story in this shape; the specifics below are an illustrative skeleton to copy the shape of, not a script to memorise; in an interview you should use a real example with real figures.

Terms: ROI (return on investment) is benefit relative to cost; a pilot is a small time-boxed trial; champion is an internal advocate; deflection means a support ticket that customers resolve without a human agent; payback (payback period) is how many months of benefit it takes to earn back the price paid.

Story skeleton (Situation, Task, Action, Result)

Situation. I was the Solutions Architect (the pre-sales technical expert) on a customer-support automation deal. Our business case said 30% of 20,000 monthly tickets would be deflected, at $6 per ticket handled, which is $36,000 a month. The price was $96,000 for the first year. The head of finance said, "I don't believe the 30%."

Finding the real objection. I did not argue the number. I asked three questions: "Which part feels least believable?", "What number would you be comfortable defending to your own boss?", and "Who would be on the hook if it came in lower?" The answers separated three of the four possible targets (nobody was challenging the logic of the calculation itself, only its inputs, its ownership and the risk):

1. The input is wrong: their tickets are mostly complex billing disputes, so deflection would be lower.
2. Nobody owns the result: the support director had not been in the conversation.
3. Risk tolerance: they did not want to commit a full year's budget on a vendor estimate.

It turned out to be a mix of the first and third. Quote the exact words the buyer used; it makes the story credible.

Action. I proposed a four-week pilot on live tickets, with the support director as co-owner and the success threshold agreed in writing beforehand (we set it at a minimum of 15% deflection, roughly half our claim, which the finance head said she could defend to her own boss). The pilot measured 18% deflection, not 30%.

Result (worked out from the measured figures). Recomputing with the measured figure: 20,000 x 0.18 x $6 = $21,600 a month. Payback on the $96,000 price moved from $96,000 / $36,000 = about 2.7 months to $96,000 / $21,600 = about 4.4 months. That is still acceptable, and the number was now the customer's own. We restructured the first year as a phased contract. For example: a $48,000 first phase covering the two highest-volume ticket queues for six months, with expansion to the full $96,000 scope triggered if deflection stayed at or above 15% for eight consecutive weeks. The commercial outcome: a signed deal at a smaller first phase and a clear path to expansion, instead of a stalled negotiation over a number nobody believed.

What interviewers listen for

• Diagnosis before response: you separated the types of objection instead of repeating the claim louder.
• A specific action (the pilot, the shared owner, the written threshold), not "I built trust".
• A measurable, honest result, including the part that went against you (18%, not 30%).
• What you changed afterwards, for example: start every business case from the buyer's own baseline and show a low, expected and high case. For this deal that would have been 12%, 18% and 30% deflection: $14,400, $21,600 and $36,000 a month, or payback of about 6.7, 4.4 and 2.7 months on the $96,000 price.

Pitfalls

• Cleaning the story so the number was right all along. Strong candidates show the claim was adjusted.
• An outcome with no commercial detail ("they were happy"). State what was signed, at what scope.
• Inventing precise figures. If you cannot recall exact numbers, give ranges and say so.