B2B referrals: what a partner needs to be able to say about your company
Prepare a B2B referral: customer situation, service scope, evidence, limits on promises and a clear route to a conversation.
Article language: English

In this article
A partner recommends your company with the best intentions: “They'll do everything, very quickly, and I'm sure you'll get along.” The customer arrives expecting a complete delivery next week. Your company offers a preparatory stage, and the next available date still needs checking. The referral opened a door, but there is already a promise on the other side that nobody put in the materials.
A good referral partnership starts with a simpler task than teaching a partner the entire offer. The partner needs to recognise the right situation, explain the useful scope briefly and point to a way to start a conversation. They also need to know what they cannot confirm on the company's behalf. That helps a customer take a useful next step rather than simply carrying enthusiasm between two inboxes.
Consider a fictional partnership between a studio that designs spaces and a company that makes websites for such projects. The studio often hears that a client cannot explain the scope and outcome of its work online. It can recognise that moment without knowing web technology. What it does need is a precise description of the situations in which a referral would help.
A partner hears the situation before learning the service name
Start with a few sentences people might actually say: “We have good projects, but our website doesn't explain them.” “Customers ask how two scopes differ.” “An old description is still circulating after the offer changed.” These are signs a partner can recognise. A general statement such as “someone needs marketing” is usually too broad to support a useful referral.
For each sign, state which problem the company can discuss further. Do not turn it into a guaranteed diagnosis. A weak website may be one cause of confusion, but the partner has not yet seen the materials, process or expectations. Their job is to identify a sensible entry point, not settle the entire scope from one customer sentence.
Microsoft's co-sell documentation describes the Customer need field for identifying the customer's specific problem and the help required. It is an example from a particular partner programme. The narrower principle is useful in your own partnership: pass on the need, not just the name of a prospective customer.
In the fictional example, a partner could say: “This company helps organise the content and customer journey on a website. It would be useful to show them your two scopes and the questions that keep coming up.” That offers a concrete next step. It does not establish a price, date or solution that has not been checked.
Distinguish a referral for a particular service from a general recommendation of the company. A partner may know one kind of work well without experience of the others. On the referral card, identify the scope covered by the example and what the project shown actually demonstrates. Trust earned on one task then does not accidentally extend to every possible service.
Consider a borderline situation too. The customer says, “We need a new website,” but further discussion reveals that the company has not decided what it wants to offer. The partner can suggest a conversation about the readiness of the materials instead of promising immediate delivery. An example like this is useful on the card because a list of sectors alone will not identify the stage of the need.
In a second example, the scope is clear, but the customer only wants a small update to an existing site. Do not assume that every website need calls for a full project. The partner should be able to convey that distinction, and the company can assess the right scope once it has seen the materials. A good match may lead to a smaller conversation than the general name of a service suggests.
Also identify situations that do not fit. If a customer needs a service outside the scope, the partner should recognise that without feeling an opportunity has been wasted. Declining a B2B engagement is part of honest matching. The article on when to decline a B2B engagement (in Polish) discusses that decision. A partnership that directs every need to the same company quickly creates conversations both sides could have avoided.
Materials should help a conversation, not test presentation skills
Prepare one short card for the partner. Include customer situations, a simple description of the scope, an example of an outcome and the appropriate link. Add two or three boundaries most likely to be extended accidentally. In our example, that could mean distinguishing a website project from managing the company's entire communications, or explaining that materials must be agreed before a date can be given.
The whole documentation does not need to fit in one file. A partner needs to be able to use the card in a real conversation. If they must scroll through a dozen slides to find one sentence, the material probably serves a company presentation rather than a referral. A longer explanation can be available through a link for an interested reader.
The B2B service page should continue the same description. After clicking through to the company's page, the customer should recognise the problem, scope and way to begin a conversation. A guide to the structure and evidence of a B2B service page (in Polish) can help prepare such a page. If the partner card speaks about organising an offer while the page opens with a general claim about business transformation, the reader has to connect two stories alone.
Choose appropriate evidence for each claim. The guide to evidence behind offer promises (in Polish) helps distinguish a demonstrated result from a broad declaration. A partner can point to a particular project or an example of the working method. They should not add results the company has not confirmed, even with friendly intentions.
Look at the material in the form the partner actually uses. A short message may hold one sentence and a link; a conversation allows a fuller example; a slide needs a legible name for the scope. Keep the meaning consistent across each version. Shortening must not remove a condition that determines whether the need fits the service.

Prepare short answers to common questions. “How much does it cost?” can lead to an explanation of what determines the scope. “When can they start?” can lead to a check of availability. A partner does not need a rehearsed evasion. They need to recognise the limits of their information and point to a person or place that can confirm it.
The guide to demonstrating a service without a staged ideal (in Polish) can also help. A small example lets the partner understand what the recipient would actually receive. It should remain clearly an example, so one impressive project does not automatically become a promise of the same result every time.
Someone must own the handoff
Agree the simplest next step for the customer. It might be visiting a particular page and describing the need themselves. In another process, the parties might arrange a joint conversation. The choice should reflect how the companies actually work. “We'll connect you” alone does not explain who acts next or where to return if nothing happens.
A partner does not need the customer's entire documentation. At first, a recognisable situation and a route the interested person can choose may be enough. Questions about data, authority to share it and terms of cooperation must be settled in the appropriate process. Referral material should explain the service, not replace those decisions.
HubSpot's shared partner deals documentation describes assigning a sales contact who receives certain notifications, including partner matching opportunities and assisted deal creation. This is a feature of a particular environment, but it illustrates identifiable responsibility at the point of entry. A partnership likewise needs someone who knows what to do with interest after a referral.
Agree how to recognise that contact has been made without automatically giving the partner access to the whole conversation. The scope of feedback should be agreed. To improve the materials it may be enough to indicate whether the need fitted the offer and which part of the description was missing. Not every lesson requires sharing the details of a case.
A customer can use the guide to preparing a B2B service-provider selection brief (in Polish) to organise the scope before a conversation. The referral should make that step easier, not suggest the partner has already agreed everything. The company still needs to understand the task and confirm whether it can take it on.
Aeneia Design: discuss organising an offer and materials so a partner can recognise a suitable need and point to a next step. The scope, evidence and possible work require agreement. The existing service description and the sentences partners already use can be a starting point. Comparing them can reveal where useful detail disappears and where a promise needs correction. The parties settle any referral compensation separately. View the service scope
Check what the partner actually says next
Walk through the journey of a reader who knows only the short referral. Ask them to open the link and explain what the company does and what materials would be useful to prepare. If they need another explanation from the partner, check whether it is missing from the page. A referral can start a conversation; it should not have to serve as instructions for an incomprehensible offer.
Give the partner three short situations: a fit, a non-fit and an ambiguous case. Ask them to explain in their own words whether they would refer the customer and what they would say about the service. Do not show the ready answer beforehand. Compare their reasoning with the scope, the stated need, promised outcome and proposed next step.
Record differences in the description. Does the partner omit the condition that materials must be prepared? Do they present a narrower scope as full delivery? Do they promise a date? Return to the specific sentence on the card or page that may have prompted that interpretation. “Refer more accurately” does not fix material that still encourages the same reading.
If conversations after referrals do not progress, investigate the reason instead of judging only the number of contacts. A guide to analysing lost B2B offers (in Polish) helps distinguish a poor fit, a lack of readiness and problems with the proposal itself. A partnership can work well even when it honestly filters out situations outside the scope.
When the same mismatch recurs, compare the timing of the referral. The material may be clear but reach a customer only when they need urgent delivery, while the service requires the scope to be organised first. That is a reason to change the signal the partner looks for and the first sentence of the conversation. Do not repair the difference by adding an even broader promise of speed.
With several partners, compare their descriptions of the same need. One may hear a content issue, another a technology issue and another a sales issue. Keep the useful context of each referral, but check that all point to the same confirmed scope. A shared card may need examples from different conversations instead of one sentence so broad that it stops distinguishing anything.
Provide a place to report unclear material. When a partner encounters a question they cannot explain, they should know whom to ask for an addition. Those questions help update the card and page. Without that route, everyone supplies their own explanation, and after a few months the company receives several versions of the same offer.
When the service changes, update the card and identify the current link. A partner does not need to track every editorial change to the page, but should know about a change that affects whom they refer and why. A short record of the date and material owner helps maintain a consistent description without multiplying presentation versions. For a larger set of files, use the guide to organising a materials library by version and intended use (in Polish) to prepare the library, so the partner can obtain the current description of the right scope.
A good referral leaves the customer with a clear thought: this company may be able to help in this situation, and the first step is to show it the relevant material. The partner does not need to become a spokesperson for every possible service. It is enough to open the right door without imagining a delivery date has already been signed.









