Bringing an expert to a sales meeting: answer the question, not every possible question
Prepare the expert for a B2B sales meeting, distinguish explanation from diagnosis and record what remains uncertain.
Article language: English

In this article
“We'll bring an expert to the next meeting” can be good news. At a fictional firm producing industry reports, though, the customer has to explain their work all over again and then listen to a lecture on what language models can do. The salesperson already had notes from the previous conversation. The specialist never received them. An hour later, the customer's one question remains unanswered.
Start by identifying the question the specialist is there to address. What do you already know about the need? Why is the answer so far insufficient? What can the expert explain in the meeting, and what needs proper investigation afterwards? Sales and the specialist need to work on this together. An extra person should contribute the knowledge the conversation needs, not become a more impressive version of the company catalogue.
Name the question before inviting the expert
In our fictional example, a customer is considering AI for an initial review of product descriptions supplied by partners. They are not asking about every use of artificial intelligence. They want to establish what part of the preliminary work can meaningfully be assessed before the material reaches an industry specialist. The salesperson should pass on that context instead of inviting an expert to a general conversation about innovation.
GitLab's own rules for involving Solutions Architects link their participation to prior business discovery and readiness to scope a solution for evaluation. Solutions Architects support technical assessment. These are one company's rules, not a universal sales stage every small organisation should copy or evidence that meetings automatically become more effective.
In our example, it helps to look at what is handed over between people. The salesperson knows the customer's goal, the current way of working and the reason for another meeting. The expert should be able to see those points and say what is still missing for them to contribute usefully. There is no need for a lengthy document. There is a need to avoid an invitation containing only the customer's name and the words “AI potential”.
Put the question briefly in your own words and check it with the customer. “Can we discuss an initial review of the descriptions while leaving the industry assessment with your specialist?” establishes a scope. “Can AI help us?” permits almost any answer. Clarifying the question does not have to decide the solution. It should help you bring the right expertise into the next conversation.
Record separately what the customer is not trying to change. In the fictional case, the team still wants to assess the substance of each description. This guards against a demonstration in which the model produces a final recommendation on its own and answers a question nobody asked. An impressive feature does not necessarily bring you closer to understanding the task.
The six Signal articles linked below are in Polish.
Before the meeting, the expert may ask for an ordinary example permitted for that use, or for a description of the current task. Materials for an AI audit (in Polish) can help identify a useful starting point, but they do not mean everything must be sent before the first conversation. The material requested should fit the agreed stage and the company's rules.
If the question falls outside the invited person's speciality, it is better to notice early. A tools expert may be able to explain the kind of trial needed without knowing the content of every industry document. The salesperson should preserve that boundary when describing their role. The broad word “expert” is not a substitute qualification in everything that might appear in an attachment.
An expert answer starts with the customer's situation
A qualitative study of expectations for initial B2B sales meetings used 46 interviews with salespeople and buyers. The authors found differences, including in how the customer's situation was understood. They analysed participants' accounts of experiences and expectations, not direct observations of the meetings themselves.
The study is not a reason to promise that simply bringing in a specialist will improve sales results. In our case, check a simpler point: are both people from the supplier addressing the task the customer brought? If the expert starts with the entire technology, the salesperson can return to the agreed question. They do not have to pretend to know the technical answer better.
At the start, confirm the shared purpose. The customer may clarify that they do not want to compare tools yet. First they want to consider what a sound initial review would look like. That changes the expert's contribution. A prepared demonstration may be premature; a discussion of the type of material and how the result will be checked may be needed instead.
The specialist should be able to ask a question of their own, including one that challenges the first account of the problem. Suppose some descriptions are not available in their current version. Summarising them may then be less important than that underlying uncertainty. The expert can explain the dependency without diagnosing the entire document workflow from a single statement.
The salesperson remains responsible for continuity. They can recall the previously confirmed goal, mark a new question and help establish the next step. They should not immediately turn a cautious expert statement into a commitment. “We can consider that after reviewing the material” does not mean “we will do it in the standard package”.
A map of people involved in the purchase (in Polish) helps when someone on the customer's side who knows a particular part of the work is needed. The person leading procurement cannot always answer how a document is normally assessed. A missing answer is not necessarily a lack of interest. It may point to the right participant for the next conversation.
Keep the different perspectives in the notes too. A manager wants to reduce the wait for a report, while an industry specialist worries about the extra work of checking poor material. These needs need not conflict. But they should not be reduced to one sentence saying that the company wants automation. The expert needs to understand how the proposed task connects to both people's work.

An explanation, a demonstration and a diagnosis answer different questions
A brief answer may concern a known feature of a tool. A demonstration shows how it works with particular material. A proper diagnosis requires understanding the actual task and its constraints. These forms can complement one another, but they should not accidentally become one unlimited commitment in a sales conversation.
In our example, the expert can explain the difference between a draft summary and an industry assessment of a product. They can also show an agreed example. Neither confirms that the tool will be useful for all the customer's documents. If results must be compared across the real scope, identify that as separate work and state its result.
The principles of a service demonstration without a staged ending (in Polish) help keep clear what was actually shown. In a sales conversation, also check how the customer understood the demonstration. Did they see an example of a feature, or take it as proof for their own use? Clarify the difference during the discussion, before it enters an internal purchasing recommendation.
If the expert does not know the answer, they should be able to say what is needed to establish it. Identify the specific unknown, the relevant expertise and a possible result of further checking. A general “we need to analyse this” leaves the customer unable to see why another stage is necessary. An improvised answer, meanwhile, can create false certainty.
The distinction described in a paid diagnosis before a service quote (in Polish) is useful here. Not every expert answer needs a separate commission. But if further work has a real scope and outcome, describe it honestly. The customer should know what they will receive for their decision, rather than discover later that a consultation was meant to be a complete project.
The salesperson and expert can agree beforehand on a signal to return to scope. When details arise that require proper material, the person leading the meeting summarises the unknown and proposes agreeing the further work. This is not intended to silence the customer. It distinguishes discussing whether a task can be done from actually doing a new task under unprepared conditions.
In the fictional case, after the explanation the customer may decide to organise the description categories themselves first. That is a concrete meeting result too. There is no need to call it the expert's defeat or rescue it with another demonstration. The conversation was meant to identify a condition for further assessment, not secure a promise to implement at any cost.
Aeneia Audit: Bring a specific AI task and a question the current description of work does not resolve. We can discuss the material needed to agree the scope of a diagnosis of tools, information and result checks. Prepare a question for a conversation about an AI audit.
A short return to the shared thread in that fictional meeting might sound like this. The expert says, “We have not yet checked whether the initial review will be useful to your specialist.” The salesperson adds, “Should the next task be to assess that result on an agreed example?” The customer answers, “First I want to talk with the person who would check it.” Each statement contributes something different: a limit to current knowledge, a proposal for further work and the customer's actual decision.
Do not compress that exchange into the note “customer interested in a pilot”. What was agreed was an earlier conversation that may make it possible to determine whether a trial makes sense. The salesperson preserves the expert's qualification, while the expert does not have to take over the whole relationship. The right next move follows from the customer's answer. It does not come from automatically scheduling another meeting to repeat the same unagreed proposal.
An expert from another company does not automatically expand the proposal
Sometimes a partner with the needed knowledge joins the conversation. The customer should understand their role: are they explaining a particular subject, or taking part in preparing a further proposal? Two companies appearing at a meeting does not by itself establish a shared delivery scope. State that according to the actual arrangements.
A joint offer with a competitor (in Polish) raises separate questions about each company's participation and the limits of permissible cooperation. Here the basic distinction is enough: a specialist's contribution to an explanation does not automatically commit both organisations. Formal terms and the scope of information need their own appropriate assessment.
In our example, the firm might invite someone familiar with the industry's assessment of a description. That person can help explain the task but does not necessarily represent every future user. A single statement should not become approval of a solution by the whole field in the notes. Its value is specific knowledge with a stated scope.
A reference conversation with a supplier's customer (in Polish) provides different evidence from an expert's participation. An existing user can describe their own experience of the relationship. A specialist can explain conditions for use. Neither conversation should be presented as a ready prediction of the outcome for a new customer.
After the meeting, keep the answer and its limits together
The summary should show what was answered and what remains open. For the fictional company, it might say: the possibility of separately assessing an initial review of descriptions was identified; the tool's usefulness for the entire collection has not yet been assessed. Specified material and an agreed way to investigate further are needed. That is different from a confirmed implementation.
Check that summary together before passing it on. The expert may notice that a careful statement has lost its condition. The salesperson may see that the summary omits the customer's decision about the next step. Both corrections matter. A good note preserves technical precision and the meaning of the sales conversation rather than choosing only one perspective.
If the next step needs another participant, explain why. Adding a name to an invitation and restarting the whole history is not enough. Pass on the question and the points already established on a sound basis. Each new person can then contribute the needed knowledge, and the customer does not pay with their time for an internal change of personnel.
At Aeneia Audit, a concrete question about AI use and the material needed to understand current work can be a starting point. The scope of any further diagnosis is agreed against the task, tools and flow of information. An expert does not have to win the meeting by using the most technical terms. It is better if everyone leaves knowing what was explained and what work the next answer requires.









