A reference conversation with a supplier's customer: what can their experience tell you?
Prepare a supplier reference conversation that distinguishes a specific customer experience from a guarantee of future results.
Article language: English

In this article
"Would you recommend this company?" can receive a polite answer that explains almost nothing. Imagine an office-space operator choosing a room-booking system supplier. They speak with an existing customer and hear that the collaboration went well. They still do not know how data was prepared, who handled changes or what happened after launch.
A reference conversation explores one customer's experience with a supplier. It can help before purchase when questions concern a similar task and the relevant stage of work. It is not a forecast for your assignment. Leave with a description of conditions and ordinary work, rather than another vote for a choice the team already likes.
First name the experience you need
In the fictional example, the operator has several locations. They want to understand how the supplier prepares a move from the old booking method to a new one, not the entire software market. Before the conversation they record three unknowns: preparing information, their own team's participation and handling changes after launch. Each can be explained by someone familiar with that work.
Business Queensland's guide to finding suppliers suggests checking whether other businesses recommend the supplier as part of broader supplier research. That is practical advice, not an assurance that a recommendation alone is enough to assess a particular service. Your conversation should address the task that still needs clarification.
Ask the supplier with a named scope. If you need information about maintenance, someone who only chose the company may not have answers. If you ask about launch preparation, someone who started using the system recently may not know its beginning. Match the role, not the most recognisable brand in a portfolio.
A B2B service supplier selection brief (in Polish) can identify which unknowns concern your own requirements. The reference conversation should help you understand them, not necessarily settle everything. Some questions remain for the supplier; others belong to people on your side who will do the future work.
Also establish when the customer used the service. They may describe a different team or an earlier version of the solution. That does not make their account worthless, but you need its time frame. If delivery conditions have changed materially, put the follow-up question to the supplier who can relate it to the current proposal.
Similar companies do not necessarily place similar orders
A long list of shared features in a presentation can mislead. Two organisations have several offices, but one prepared all room information itself while the other expected the provider to organise it. A similar final screen does not show that difference. In our fictional example it may determine the scope of cooperation needed.
Ask what condition the materials and the company were in at the start. What did it already know and have? Who made decisions on its side? Do not request confidential files or details of someone else's contract. A description of the task and division of work is often enough for your question. The interviewee should be able to keep the boundary of what they want and are allowed to share.
Jaakkola and Aarikka-Stenroos's research on B2B customer referencing considered three parties: the supplier, the customer giving a reference and the prospective buyer. Its field research concerned knowledge-intensive business services. The authors identified benefits and possible burdens in the relationship. The interviewee brings experience but also spends resources on the contact.
Do not treat them as an additional unpaid purchasing committee. Prepare questions they can actually answer and agree a reasonable scope. Do not expect them to assess your full specification or choose for you. They can describe what happened in their case. That is useful material when you preserve its source and limits.
The match may be partial. The interviewee may know launch preparation but not later maintenance. Keep the answer about the beginning and record the missing later knowledge. Do not infer a positive view of the entire collaboration from one well-described stage. Equally, one difficulty does not automatically settle every other part of the service.
Record your comparison specifically: same kind of task, similar customer participation, different amount of material. This makes the experience useful without erasing differences. "A company like ours" is convenient but does not explain which conditions matter for the new order.
Ask about the ordinary process, not just an overall rating
"How was the first launch prepared?" gives the interviewee room to describe work. Follow up on what their team supplied and what it received from the provider. You need not start by asking whether the collaboration was excellent. Our office operator wants to understand its own future contribution, not award a medal for appearing in someone's story.
An ordinary post-launch change is useful too. Suppose the reference customer describes adding a location. Who prepared the data? How was scope agreed? What depended on the customer? These are questions about experience. They do not require detailed commercial terms to reveal the division of work.

If someone says "the supplier responded quickly", ask for context. Was it acknowledgement of a message, explanation of a problem or execution of a change? Establish which kind of response is being assessed; you need not collect exact times for every ticket. Otherwise two people may use "quickly" for different events.
Ask about incomplete information too. How did the parties clarify it? Who knew what had to be supplied? The aim is not an embarrassing story but understanding work under conditions less convenient than complete material and agreement by everyone. A good answer can show the ordinary handling of a case.
For evidence behind promises in a B2B offer (in Polish), a claim must relate to its basis. Apply the same discipline here. "The supplier organised data for our first site" differs from "the supplier will organise all our data". The latter concerns future scope and needs its own confirmation.
A customer and a specialist have different sources of knowledge
An existing customer may know the effects of using a service but not every technical cause. If they say a fix solved a problem, record their experience; do not automatically turn it into a universal diagnosis. A similar symptom in a new project may need different investigation. Ask the appropriate person about current application.
Involving an expert in a B2B sales conversation (in Polish) helps clarify a particular specialist unknown. The two accounts can work together: the customer describes their case and the supplier relates the question to planned scope. A positive opinion cannot replace evaluation of conditions that differ in your company.
In our example the reference customer had one person coordinating all locations. The new buyer knows decisions are distributed on its side. This does not invalidate the previous experience. It creates a question for the next conversation: how will the proposed supplier work with a different division of responsibility?
The discussion may also show that part of the result came from the customer's own team. Preserve that contribution instead of attributing everything to the provider. It helps assess your own preparation: under which conditions did the result arise, and what must the new organisation provide itself?
A public B2B case study (in Polish) can start these questions. A direct conversation allows context to be clarified, but need not explain the entire project. In your notes distinguish what the interviewee knew personally, heard second-hand and did not discuss.
A recommendation has value, and selection of the interviewee has limits
When the supplier names the interviewee, you know how they were selected. That is ordinary source information worth retaining. One positive story is not a random sample of all customers. You need not call it unreliable; use it for questions the person can actually answer.
Do not try to balance the conversation by forcing a story about the worst project. A reference need not be an interrogation. Ask what the person would prepare differently next time or what condition should be agreed earlier. The answer can reveal work required on both sides without judging everyone involved in someone else's project.
With a customer advisory council (in Polish), it also matters who contributes experience and in what role. A reference conversation has a different purpose: helping one buyer understand an earlier collaboration. It does not replace ongoing collection of customer voices or justify diagnosing the supplier's whole customer base.
After the conversation our fictional office operator prepares a short note for those choosing the service. It does not give the supplier stars. It records an answer, its source and the action arising from it. Three excerpts from that fictional summary follow:
- Data preparation: the interviewee personally collected room names and descriptions; the supplier provided a template. In that project the customer supplied organised material. Our coordinator should find who can do that in each office. The offer needs clarification if we expect the provider to do it.
- Post-launch change: the interviewee reported adding a location, but another person handled later arrangements. We know her own part in reporting it, not the whole delivery. Ask the supplier how a similar expansion would be handled; do not record that the previous customer confirmed every stage.
- Coordination: one person approved information from all locations. Our room descriptions are agreed by separate owners. Before comparing offers, decide whether we can name one contact or need cooperation with several participants. The reference will not make this organisational decision for us.
Each point contributes something different: described experience, a limit of knowledge or a buyer-side task. The note also separates no answer from an unfavourable one. The interviewee did not know about maintenance after a team change, so it remains open. We do not enter "maintenance problems". Silence in the material does not become an event because a spreadsheet dislikes blank cells.
The next message to the supplier can use a concrete point: "We understand from the conversation that the customer collected data in that project. Please specify in our proposal who organises room descriptions and how they are sent for agreement." There is no need to forward the entire prior customer's account or attribute an opinion about the new offer to them. We refer to the observed division of work and address the future supplier.
If the answer changes scope, return to the offer comparison. If it confirms a condition already described, add it to the selection material. The reference conversation has then provided useful knowledge even without a striking verdict. The team knows what it understands better and what remains to be agreed.
Aeneia Design can turn actual experience into a clear presentation of services and projects on a website. The page should show the company's contribution and context that lets a prospective customer ask the right question. References still belong to particular people and cases. They are most useful when they explain work instead of merely decorating a decision with a satisfied customer's logo.






