# Customer Reference Calls for B2B Software: Ask About the Work After Purchase

<a id="main-content"></a>

B2B Strategy

October 28, 2026  ·  8 min read  ·  Victor Valentine Romo

On this page

1. [Decide What the Call Must Resolve](<#decide-what-the-call-must-resolve>)
2. [Map the Reference Before Comparing Experiences](<#map-the-reference-before-comparing-experiences>)
3. [Build a Neutral Discussion Guide](<#build-a-neutral-discussion-guide>)
4. [Ask About Support and Maintenance as Work](<#ask-about-support-and-maintenance-as-work>)
5. [Mark Firsthand Accounts and Secondhand Claims](<#mark-firsthand-accounts-and-secondhand-claims>)
6. [Work Through a Fictional Reference Worksheet](<#work-through-a-fictional-reference-worksheet>)
7. [Keep the Sample Limitation in the Decision Record](<#keep-the-sample-limitation-in-the-decision-record>)
8. [Protect the Participant's Words and Identity](<#protect-the-participant-s-words-and-identity>)
9. [Turn the Call Into Follow-Up Evidence](<#turn-the-call-into-follow-up-evidence>)
10. [Sources](<#sources>)

A customer reference can describe work your software demonstration never reaches.

Ask who configured the workflow. Ask what happened when the normal path broke. Ask who maintains the configuration after the implementation team leaves.

Keep each answer attached to the customer's operating conditions. A reference can describe a useful experience without establishing how your team would fare.

[GitLab's reference program manager description](<https://handbook.gitlab.com/job-description-library/marketing/reference-program-manager/>) includes identifying and engaging reference customers across sales, customer success, product, and marketing. That describes one company's managed program. When a vendor selects your reference, treat the conversation as a selected example with explicit limits.

The worksheet below proposes a buyer interview method. Every worked answer is fictional. It contains no completed customer call, endorsement, or prediction of buyer results.

<a id="decide-what-the-call-must-resolve"></a>

## Decide What the Call Must Resolve

Start with unanswered questions from your evaluation. “Would you recommend the product?” is too broad to establish whether your team can operate the proposed workflow.

Write a narrower question: what does a coordinator need when a service request arrives without its required location? Or ask which person restores an assignment rule after the organization changes its staffing structure.

Separate product questions from operating questions. A reference might describe how its coordinator handles an exception. The supplier still needs to establish whether the configuration proposed for your team supports that behavior.

Use a [buyer business case](</articles/b2b-business-case-decision-memo/>) to identify which unknowns affect the next decision. Prioritize questions that could change the scope, implementation plan, or willingness to continue evaluation.

Do not turn the reference into an unpaid consultant. Send the topics in advance, agree on a bounded conversation, and leave space to decline. Ask for descriptions of work rather than confidential documents or commercial details.

<a id="map-the-reference-before-comparing-experiences"></a>

## Map the Reference Before Comparing Experiences

Begin by learning where the participant stands in the workflow. A sponsor can explain the purchase decision. A coordinator can explain daily use. An administrator can explain configuration. Ask which work the participant performs firsthand.

Record the implementation stage. Separate initial setup, a limited rollout, and ongoing operation. Ask when the described event occurred relative to those stages. A setup problem may have been resolved before the current workflow began.

Capture the product version or release period, hosting arrangement, enabled modules, and relevant configuration if the participant knows them. Write “unknown” when they do not. Ask the supplier to confirm technical details separately.

Map team constraints with the same care. Ask whether a dedicated administrator, implementation partner, or internal technical team supports the workflow. Identify who owns maintenance [when that person is unavailable](</articles/business-continuity-tabletop-small-team/>).

Use this opening worksheet:

| Context field | What to establish | Why the comparison needs it |
| --- | --- | --- |
| Workflow | Work entering the system and the result leaving it | Similar product use can hide different tasks |
| Participant role | Steps performed personally and decisions owned | Establishes the boundary of firsthand experience |
| Stage | Setup, rollout, or ongoing use | Distinguishes implementation from current operation |
| Product conditions | Version, modules, configuration, or unknown | Defines the technical conditions behind the account |
| Team constraints | Available administrators, partners, and reviewers | Exposes support work your team would need to assign |

This map establishes applicability. It does not require an identical company or make one account [representative of every customer](</articles/small-b2b-customer-survey-interpretation/>).

<a id="build-a-neutral-discussion-guide"></a>

## Build a Neutral Discussion Guide

[GOV.UK's in-depth interview guidance](<https://www.gov.uk/service-manual/user-research/using-in-depth-interviews>) recommends a discussion guide, [open and neutral questions](</articles/win-loss-interview-guide-b2b/>), and follow-ups focused on concrete experiences. Apply those practices to the conversation. The guidance does not certify a vendor-selected reference sample as representative.

Order the topics from context to setup, routine work, exceptions, support, and maintenance. Use the same core topics across references while allowing follow-up questions to reflect each participant's experience.

For setup, ask: “Walk me through the work between choosing the product and using it for this workflow.” Follow with: “Which steps did your team own?” and “What setup work, if any, remained unresolved when the workflow first went into use?”

For routine operation, ask: “Describe a recent request from receipt through handoff.” Ask which steps happen outside the software. Keep those steps in the notes rather than treating the product boundary as the workflow boundary.

For exceptions, ask: “Tell me about a request that [could not follow the usual path](</articles/process-variant-analysis-small-team/>).” Follow the sequence. Ask who noticed, what they could see, and which action returned the work to a usable state.

Avoid [supplying the answer inside the question](</articles/b2b-customer-survey-question-design/>). “Was setup easy?” asks for an adjective. “Walk me through the setup steps your team handled” invites a sequence. Then ask whether any step needed outside help. Allow an answer of none.

<a id="ask-about-support-and-maintenance-as-work"></a>

## Ask About Support and Maintenance as Work

Keep support questions concrete. Ask the participant to describe one issue they personally raised and the steps that followed. Ask what they provided, how they tracked the issue, and what they did while it remained open.

Distinguish the customer's recollection from the supplier's contractual commitments. A useful account of one support interaction does not establish the support terms available to your proposed purchase.

For maintenance, ask what changed after initial setup. Did the team add a request field, alter an assignment rule, or replace an integration? Ask who made the change and how the team checked the result.

[Ask what remains manual](</articles/operations-automation-audit/>). Keep the wording neutral: “Which parts of the handoff do people still prepare outside the system?” The answer may describe a deliberate operating choice. Do not label every manual step a product defect.

Close this topic with a backward-looking question: “Given what you know now, what would you verify before setting up this workflow again?” Ask for the condition behind each answer. Keep [hypothetical wishes](</articles/b2b-usability-findings-triage/>) separate from events the participant experienced.

<a id="mark-firsthand-accounts-and-secondhand-claims"></a>

## Mark Firsthand Accounts and Secondhand Claims

Use an evidence label in your notes. “Firsthand account” means the participant describes work they performed or observed. It remains an account unless you separately inspect an approved artifact or demonstration.

Use “secondhand claim” when the participant reports something another team told them. Record the stated origin without turning it into a verified fact. Ask who could answer the question directly, subject to permission.

Use “opinion” for judgments such as satisfaction or preference. Preserve the judgment as that participant's view. Ask which event explains it when more detail would help your decision.

Use “unknown” when neither the participant nor available evidence resolves the question. Do not fill a missing version number from the current vendor website. The reference may describe a different release or configuration.

[Record conflicts intact](</articles/conflicting-client-feedback-consulting/>). A participant may recall that assignment changes were automatic while an administrator's approved explanation describes a manual step. Identify the gap and request clarification. Avoid blending the accounts into a smoother story.

<a id="work-through-a-fictional-reference-worksheet"></a>

## Work Through a Fictional Reference Worksheet

Imagine a buyer evaluating software for a service-request workflow. The buyer has coordinators and specialists but no dedicated product administrator. Every condition and answer below is invented for the exercise.

The fictional reference participant is a coordinator in ongoing operation after a staged rollout. The participant handles intake and handoff. An internal administrator manages rules, while a partner handled part of the original setup.

The participant knows which modules the team uses but cannot confirm the exact release. That uncertainty stays in the context map. Neither this reference nor its answers stands for a real customer.

| Topic | Fictional answer summary | Applicability limit | Unanswered question and next evidence |
| --- | --- | --- | --- |
| Setup | Participant checked sample requests; partner configured fields | Participant did not perform configuration | Supplier to describe setup tasks and proposed owner |
| Missing input | Coordinator returns incomplete requests to the sender | Describes current local procedure | Confirm whether the proposed configuration blocks assignment |
| Exception | Administrator adjusts rules when a specialist changes role | Buyer has no dedicated administrator | Show which role can maintain the rule and how changes are checked |
| Support | Participant filed one issue and used a manual handoff while waiting | One firsthand account, no contract reviewed | Obtain applicable support terms and define the buyer's fallback |
| Export | Coordinator prepares the weekly file; finance describes it as usable | Finance opinion is secondhand | Ask an authorized reviewer to inspect a synthetic sample export |
| Verify again | Participant would clarify maintenance ownership earlier | Advice reflects this team's staffing | Assign a buyer owner before considering an implementation plan |

The worksheet produces a specific mismatch: the reference has administrative support the buyer has not assigned. It does not prove the product is unsuitable. It identifies work the buyer must understand before proceeding.

For the export question, preserve both parts of the answer. File preparation is firsthand. Finance's view is secondhand. Ask for a permitted synthetic example rather than a real finance export.

<a id="keep-the-sample-limitation-in-the-decision-record"></a>

## Keep the Sample Limitation in the Decision Record

Ask the supplier why it proposed this reference and which conditions it considers comparable. Record that explanation as the supplier's view. Compare it with the context you established directly.

A vendor-selected conversation provides access to one account under its particular conditions. Do not calculate satisfaction rates, expected implementation effort, or a probability of success from the worksheet.

When the reference differs from your team, identify the consequence for evidence. Different staffing may require [a configuration demonstration](</articles/b2b-software-demo-evaluation-script/>). A different version may require current documentation. A different workflow may leave the original question unanswered.

Request another relevant conversation only when it would resolve a defined gap. More calls without a question create more notes. Keep unavailable perspectives visible if a suitable reference cannot be arranged.

The same listening discipline belongs in [consultative selling](</articles/consultative-selling-b2b/>). Here the buyer owns the investigation. The call explores operating conditions; it does not ask the reference to sell or approve the purchase.

<a id="protect-the-participant-s-words-and-identity"></a>

## Protect the Participant's Words and Identity

Before the call, explain who will receive the notes and whether recording is proposed. [Obtain permission before recording](</articles/b2b-research-consent-recording-scope/>). Agree on any limits the participant requests before proceeding.

Keep names and direct quotations private unless permission covers the intended use and audience. Permission to speak with a buyer does not establish permission to publish an endorsement.

Prefer a bounded internal summary where direct quotation adds nothing to the decision. Identify the participant by an agreed role label. [Restrict the detailed record](</articles/small-team-access-review-evidence/>) to the people who need it for evaluation.

If someone shares confidential information, stop copying it into the worksheet. Ask for a non-sensitive explanation or leave the point unresolved. A reference call needs no customer records to produce a useful next question.

When preparing an outward-facing summary, confirm the allowed wording and identity details first. Do not convert private evaluation notes into marketing material.

<a id="turn-the-call-into-follow-up-evidence"></a>

## Turn the Call Into Follow-Up Evidence

Finish with a buyer-owned summary: relevant conditions, firsthand accounts, secondhand claims, opinions, unanswered questions, and applicability limits. Give each unresolved item an owner and a next evidence request.

Use a [mutual action plan](</articles/mutual-action-plan-b2b-services/>) to coordinate supplier follow-up. Keep the interview notes in their controlled location. The plan needs the question and its owner, not the participant's private words.

For the fictional buyer, the next task is establishing maintenance ownership and reviewing a synthetic export. Another general recommendation would leave both questions open.

Return the findings to the internal decision memo. State whether they change a requirement, reveal [an implementation dependency](</articles/business-system-dependency-map/>), or leave the next decision blocked. Keep product verification and purchase approval with their authorized owners.

Carry the conditions forward with the answer.

<a id="sources"></a>

## Sources

- [GitLab: Reference Program Manager](<https://handbook.gitlab.com/job-description-library/marketing/reference-program-manager/>). A documented example of managed reference-customer engagement. Checked 2026.10.28.
- [GOV.UK Service Manual: Using In-Depth Interviews](<https://www.gov.uk/service-manual/user-research/using-in-depth-interviews>). Discussion guides, neutral questions, and concrete [follow-ups](</articles/b2b-follow-up-sequences/>). Checked 2026.10.28.
