agentleFS
jacobtop-tcgjacobtop-tcg/sales-engineering-skills/skills/business-value-assessment-interviews/SKILL.md

business-value-assessment-interviews

Skill0 starsChanged 13 days agoMITView on GitHub

Plans and runs a Business Value Assessment as a set of stakeholder interviews, then turns the findings into a business case, a roadmap and focused Proof of Value criteria. Use when a B2B software deal needs a business case and the problem, the figures or the decision are spread across several people at the customer, or when deciding whether such an assessment is worth the customer's time.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the customer already understands the problem, has credible figures and knows who can decide, recommend a shorter working session.

    line 24
  2. Distinctive:

    Do not size the interview count by what the method allows.

    line 27
  3. Distinctive:

    Look for consequences a vendor's calculation of time saved would miss: faster handling in one team moving follow-up work to another …

    line 42
  4. Distinctive:

    When a manager describes the intended process and someone doing the work describes what happens when information is missing, record both.

    line 47
  5. Distinctive:

    If the interviews leave the business outcome unresolved, record it as an open decision and take it back to the customer.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Business Value Assessment interviews

A Business Value Assessment uses stakeholder interviews to establish what a proposed software purchase needs to achieve. The interviews cover the customer's current tools and problems, the state they want to reach, the capabilities that would require and how they would judge success. The output is a business case, a roadmap and a more focused set of criteria for a Proof of Value.

The reason for interviewing several people: the people involved can be describing different problems even when they appear to agree on the solution. A case built with one person can miss work, consequences and objections that become obvious when you speak to the people around them.

Ask for these inputs

  1. The proposed purchase and the goals stated so far, with who stated each.
  2. Whether the customer already understands the problem, has credible figures and knows who can decide.
  3. Who the economic buyer is, and whether they have agreed what would make the investment worthwhile.
  4. Which departments carry the benefits and which carry the work.
  5. Whether a proof is about to be scoped, and what business outcome it is meant to demonstrate.

Step 1: Decide whether the interviews are worth it

An assessment of this kind is a substantial commitment from the customer. It has to give them something they could not get from a quick conversation about return on investment.

  • If the customer already understands the problem, has credible figures and knows who can decide, recommend a shorter working session.
  • Recommend the fuller interview set when important parts of the decision are still spread across the organization: the benefits sit in one department and the work in another, the economic buyer has not agreed what would make the investment worthwhile, or the team is about to scope a proof without knowing which business outcome it must demonstrate.

Do not size the interview count by what the method allows. Choose the people who can answer the open questions. The count follows the work needed to understand the decision.

Step 2: Plan the interview list

For each interviewee, record the role, the open question they can answer and why their view might differ from others. Include the economic buyer, who must agree which business outcomes the investment is meant to deliver, and the people whose work will change, who help establish whether those outcomes are realistic and how to measure them.

Step 3: Ask about the work

Goals that sound compatible can still pull the work in different directions. Investigate how they fit. 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?

Look for consequences a vendor's calculation of time saved would miss: faster handling in one team moving follow-up work to another department, or removing a system that a team relies on.

Step 4: Treat numbers and disagreements as findings

  • For every number, record which task it refers to, how often it happens and what the estimate is based on. Keep estimates labelled as estimates all the way into the business case.
  • When a manager describes the intended process and someone doing the work describes what happens when information is missing, record both. The difference can change the scope or the value attributed to the project.
  • Allow the assessment to expose a problem with the proposed solution. If that outcome is ruled out, you are asking the customer to justify a conclusion already reached.

Step 5: Write the outputs

  • Business case: the proposed investment and its assumptions, written so the customer's people can challenge the assumptions and still understand why the investment is proposed. Do not fill it with supportive quotations.
  • Roadmap: the changes needed to reach the desired state.
  • Proof of Value criteria: the capabilities and outcomes that need demonstrating before the customer can decide, chosen before the sales engineer starts building the environment.

If the interviews leave the business outcome unresolved, record it as an open decision and take it back to the customer. Starting the proof will not settle it.

Output template

Interviewee (role)Open question they answerWhat they describedNumbers given (task, frequency, basis)Differs fromEffect on scope or value

Followed by: agreed business outcomes (with economic buyer confirmation), assumptions list, roadmap changes, Proof of Value criteria, open decisions.

Checks

  • A case built from one person's account is weak.
  • A number with no task, frequency or basis is unsupported.
  • An outcome the economic buyer has not agreed is unresolved.
  • Proof criteria that do not trace to an agreed outcome should be questioned.

A browser version of the same template, for people without an agent: Business Value Assessment template.

Based on: What stakeholder interviews add to a Business Value Assessment

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.