Free tool

Business Value Assessment template

A Business Value Assessment in sales uses stakeholder interviews to establish what a proposed software purchase needs to achieve. Plan the interviews here, record each one, then check what the business case still needs.

If the customer already understands the problem, has credible figures and knows who can decide, a shorter working session may be enough to establish the case.

Nothing you write here is sent or saved. Print the page to keep it.

Plan the interviews

Choose the people who can answer the open questions. Include the economic buyer, who needs to agree which business outcomes the investment is meant to deliver, and people whose work will change. They help establish whether those outcomes are realistic and how to measure them.

Before each interview, fill in the person's role and the question they can answer.

In each interview

For example, if the customer is considering a customer service platform, ask people to take you through the work:

  • Where does a case wait?
  • What gets entered twice?
  • Who picks it up when the first person cannot resolve it?
  • Which part would actually change if the company bought the product?

For every number, note which task it refers to, how often it happens and what the estimate is based on. When a manager and someone doing the work describe it differently, record both.

Record each interview

One block per interview. For more interviews, print the page or copy your text before you start a fresh one.

Interview 1

Interview 2

Interview 3

Interview 4

After the interviews

The case should make it possible to challenge the assumptions and still understand why the investment is being proposed. Tick each item once you have checked it.

Business outcomes agreed by the economic buyer

Ask: Has the economic buyer agreed which business outcomes the investment is meant to deliver?

Check: An outcome the economic buyer has not agreed is unresolved.

Assumptions behind the business case

Ask: Does every number say which task it refers to, how often it happens and what the estimate is based on?

Check: An estimate should remain recognisable as an estimate when it reaches the business case.

Where accounts differ

Ask: Where two people described the work differently, is it recorded what the difference changes in scope or value?

Check: A case built from one person's account is weak.

Changes needed in the roadmap

Ask: Which changes are needed to reach the desired state?

Proof of Value criteria

Ask: Which capabilities and outcomes need demonstrating before the customer can decide?

Check: Proof criteria that do not trace to an agreed outcome should be questioned.

Decisions still open

Ask: Is any business outcome still unresolved after the interviews?

Check: Starting the proof will not settle it. Take it back to the customer and agree what the evidence should help them decide.

Sources

The fields and questions come from the article on what stakeholder interviews add to a Business Value Assessment.

In Value and proof for senior Sales Engineers, participants learn to plan and run a Business Value Assessment.

If you think I could help, write to me or give me a call.