A meeting can go well and leave the sale dependent on a conversation you will not attend. The marketing manager understands the problem, sees value in the service and wants to present it to management. From that point, what you prepare needs to help other people understand the need, the conditions and the work the choice involves.
The person you spoke to remains important. They know the business, have a need and may influence the evaluation, even without authority to hire a supplier. Working on that relationship means understanding where they can move forward and where they need support, rather than expecting them to repeat an entire sales presentation from memory.

Understand how that business decides a purchase
Ask how a similar need normally moves from an initial conversation to a purchase and who participates at each stage. Distinguish who uses the service, who evaluates its conditions and who authorises proceeding. Job titles help orient the conversation, but you need to confirm people's actual roles and the decisions each can make for that particular project.
A simple question can open up that context: “If we agree this proposal makes sense, what needs to happen internally for us to move forward?” The answer shows whether there is a joint evaluation, a budget approval or a dependency still unknown. Ask to prepare the next work, without turning the conversation into an interrogation about the organisation.
In a hypothetical example, the marketing manager wants to improve the response to website enquiries. They may understand the difficulty and coordinate daily work, while management decides the investment and operations needs to confirm availability. Each person participates in part of the choice, without any one of them having to know every detail of the whole project.
Do not conclude that the most senior title is always the best entry point. A manager may authorise spending while depending on the assessment of the people who will use the service. If that team does not yet understand the need, going directly to authorisation can leave an important condition for delivery unresolved inside the business.
It also matters whether there is a defined process or the business is still deciding how to evaluate this purchase. A new service may not have an established path. In that case, help identify what needs to be clarified, leaving internal choices with the people who know and manage the organisation and its priorities.
Within the B2B sales process, understanding these participants helps select the next information and contact. You do not need to draw a complete hierarchy. You need to know who has a relevant question, who can answer it and which condition allows the evaluation to move towards a concrete commitment between the two parties involved.
Record what has been confirmed and retain the gaps. “Management needs to evaluate it” may still leave unclear what will be evaluated and with which information. That missing detail is a question for the next conversation, without inventing a date, decision maker or process merely to complete the sales record and make the opportunity look clearer.
Find out what each participant needs to evaluate
Connect the people involved with questions that could change the decision, avoiding assumptions about interests based solely on job titles. Ask which concerns have already arisen and what information is usually needed. A proposal becomes useful when it answers those questions clearly, maintaining a consistent explanation of the need without promising different, incompatible advantages to each recipient.
Management may want to understand the investment's priority, but may also need clarification about an operational dependency. The team using the service may be concerned about the effort of change or delivery quality. These are possibilities to investigate, rather than fixed profiles you can assign without listening to the people who will participate in the purchase.
Ask your contact for examples of questions they expect to receive. “Which question do you think will arise when you show this proposal?” is more useful than asking only whether the document looks good. The answer may reveal a missing explanation of the current problem, the work required from the client or why the solution deserves evaluation now.
In the fictional example, management might ask why organising enquiries deserves priority over other initiatives. Operations may want to know who will update statuses and handle exceptions. Answering only with a feature list would leave both without the context they need, even though the service appears to be described thoroughly from a technical perspective.
Distinguish known questions from your contact's expectations. If they believe somebody will reject the proposal for lack of time, check where that interpretation comes from. There may be an objection already expressed or merely concern about bringing another issue to management; each situation calls for a different way to clarify the capacity available for the work.
The diagnosis before a marketing plan helps connect an intervention to how the business actually operates. Use that understanding to answer purchase questions. Do not add a layer of vague language when what is missing is an explanation of which current work could improve and what participation that requires from the client and its team.
When incompatible priorities appear, make the difference visible. If one person expects speed and another requires a more extensive integration, a sequence must be chosen or the scope revised. The proposal should not present both expectations as simultaneously guaranteed; it should help discuss the commitment the business can realistically make and what that commitment requires.
Prepare a summary that works without your presence
Write a summary that explains the current situation, proposed intervention, conditions and decision requested without requiring attendance at the original meeting. Use language your contact recognises and confirms. The document should retain essential context as it circulates internally, distinguishing what was observed, what was agreed and what still depends on evaluation by the people involved in the purchase.
Start with the need as it was understood together. In the hypothetical example, enquiries arrive through the website, but the team cannot always tell who is handling each one. The proposal aims to organise that handover and follow-up; this description is more useful than opening with a page about every capability the supplier has to offer.
Then explain the intervention and its purpose. If you propose organising enquiries in a shared system, describe which information becomes available and which decisions it supports. Do not turn that operational improvement into an automatic sales promise: the commercial outcome still depends on factors that the proposed work may not be able to control by itself.
Present scope and conditions close to that explanation. Who provides information, who approves it and which access is required? The document's recipient needs to understand the effort on their side so approval is not based on an incomplete picture of what delivery will require from the organisation and the people who will participate in it.
State clearly which decision is being requested. It might be authorising a diagnostic phase, confirming availability for a demonstration or evaluating an implementation proposal. Mixing these stages makes responding difficult: somebody may agree to investigate the problem while still lacking the conditions to purchase the solution being presented and commit resources to the work.
Review the summary with your contact before treating it as final. Ask whether it correctly represents the need and contains any assumptions about the business. This review reduces the risk of the document circulating with an error that is then repeated in internal conversations and forces everybody to reconstruct the original understanding before moving forward.
Keep an identifiable version that is easy to consult. If you change scope or conditions after a meeting, explain what changed and which document is current. The aim is to let different people evaluate the same proposal, without inadvertently comparing versions whose price, deliverables or responsibilities already differ from the conditions that are now being discussed.
Choose evidence that answers questions about the decision
Select examples, demonstrations or explanations that help evaluate the proposed delivery and reduce a specific uncertainty. Use only materials you may share and describe the context in which they were produced. Evidence should support the reasoning behind the purchase, without turning a previous result into a prediction for this client or an illustrative example into an actual experience.
A short demonstration can show how an enquiry passes from one person to another and what information remains available. That helps evaluate the intended operation. It does not need to simulate sales, savings or execution times you have not measured; showing a relevant part of the process may be enough to clarify an operational question.
If you use a fictional example, identify it within the material itself. Someone who missed the meeting needs to recognise its nature without relying on an oral explanation. An invented name and a realistic interface can look like a client case when the document is forwarded, even if you never intended to create that impression.
Where authorised real work exists, select the part matching the question being evaluated. Explain the context needed to understand what you are showing and its limitations. A project of a different size or with different conditions may demonstrate competence, but it does not prove that the same intervention will produce the same result in this business.
You can also make quality observable through how you verify a deliverable. Which information must be present, which journey will be tested and who confirms that the work matches the agreement? These criteria help people without technical expertise evaluate the service without having to rely solely on the confidence with which the sales presentation is delivered.
Real client objections can guide reusable explanations. If several people ask how work will be monitored, prepare a clear answer about that process. Then check whether the answer fits the specific situation, rather than automatically sending a collection of materials that forces the client to search for the point they actually need to evaluate.
Choose the amount of evidence according to the question to resolve. Adding files without explaining their purpose can increase internal effort and scatter the evaluation. A summary with a relevant demonstration and understandable delivery criteria may enable a better conversation than an extensive folder that nobody can connect to the decision that is still pending.

Agree how to involve others without bypassing your contact
Suggest involving other people when that would clarify a question your contact cannot resolve alone. Explain the purpose of the contact and agree an appropriate format with them. The commercial relationship should gain information and coordination, preserving the context already built without turning access to a decision maker into an attempt to bypass the person who started the conversation.
You can explain that a particular question requires the person overseeing the operational process and suggest a conversation focused on that point. The meeting then has a concrete reason. Immediately requesting a meeting with the entire management team, without explaining what needs deciding, may add work without improving the evaluation of the proposal or its relevance.
Respect how the business prefers to organise contact. Your contact may want to present the need first or gather questions before scheduling a joint session. That choice does not prove a lack of interest; ask what you can prepare to make the step useful and agree how relevant information will return so the conversation can continue.
When a joint conversation happens, start by confirming the understanding instead of repeating the entire presentation. New people may bring a priority or restriction you did not know about. Allow space for that information and check whether it changes the proposed work, without treating their arrival as an obstacle to a sale you considered already resolved.
In the hypothetical example, operations may explain that the current system already records some information and the difficulty lies in handing over responsibility. That could reduce or change the necessary intervention. Listening to this contribution protects the proposal's quality and avoids selling a solution to a problem that had been described only partially in the initial conversation.
If there is no direct access to other people, prepare specific questions your contact can take to them. Avoid asking them to defend technical details they do not understand or negotiate conditions that have not been discussed. Offer a clear written explanation and availability to answer questions in a format that respects the business's own internal process.
Keep all relevant participants informed about decisions that change the work. A condition agreed in a later conversation needs to return to the document and to the people affected. Commercial coordination also prevents somebody approving one version while another team prepares to deliver an expectation that differs from what was agreed between the parties involved.
Follow up on the internal step with specific questions
Agree what will happen after sending the proposal, which information the client needs to gather and when it makes sense to talk again. Follow-up should help resolve the pending decision while respecting the business's time and conditions. Specific questions about the agreed step provide more context than repeated messages that simply ask whether an answer is available yet.
If the proposal was due to be presented at an internal meeting, check afterwards whether that evaluation happened and which questions arose. The meeting may have been postponed or addressed only part of the issue. Knowing what occurred helps select the next work, rather than interpreting every delay as a price objection or lack of interest.
When your contact says more information is needed, ask them to identify the question. Perhaps a technical condition, the team's effort or the starting sequence needs explaining. Answer the point preventing evaluation; forwarding the same presentation with extra pages may leave the main question exactly where it was, despite creating more material for the recipient to read.
If an objection appears, distinguish who raised it, in what context and what was actually said. You do not need names when the person's role and question are sufficient. The aim is to respond accurately, without turning your contact's brief summary into a stronger statement than the internal conversation supports or using it to assume an unconfirmed refusal.
A change of priority may mean the purchase no longer makes sense now. In that case, find out whether there is a concrete condition for resuming or whether the opportunity should end. Continuing to insist without new information occupies both parties and may weaken a relationship that could still have value in a different future situation.
The work of turning leads into service clients requires continuity between diagnosis, proposal and decision. That continuity does not mean pressuring every contact until you obtain a yes. It means knowing which need you are working on, which step was agreed and whether the opportunity still matches the buyer's actual situation and priorities.
End each interaction with an updated understanding. There may be a question to clarify, another person to involve or a decision not to proceed. Record the outcome factually so the next contact does not restart the conversation or present as pending a choice the business has already communicated clearly to the people handling the opportunity.
Confirm the commitment before preparing the start
When a positive indication arrives, confirm what was actually approved, by whom and under which conditions. Distinguish agreement with the approach from authorisation to purchase and start. Preparing the start should rest on a shared understanding of scope, responsibilities and next steps, including the people who will participate in delivery and the resources on which the work depends.
“They liked the proposal” may mean management recognises the need but still has to approve the investment. “We can proceed” may also depend on a condition not mentioned in the first contact. Ask for clarity about the commitment so delivery can be prepared responsibly, without using an isolated phrase as confirmation of everything you hoped would happen.
Review the document on which the decision was based. If changes were made during internal circulation, confirm that price, scope, schedule and client participation remain consistent with each other. An improvement requested by one team may affect another team's work; that effect needs to be discussed before it silently becomes part of the delivery expected from the supplier.
Include the people who will oversee execution in the handover. The person who approved may not be the one gathering materials, approving content or using the result. Explain the original need and agreed conditions so the project team does not have to reconstruct everything from a proposal received without the context that informed the purchase.
In the fictional example, starting may depend on identifying who receives enquiries, who monitors statuses and who approves the configuration. These responsibilities need to exist for the solution to be used. Investment authorisation is relevant, but it does not replace the operational preparation that allows the chosen work to be put into practice by the business.
If a condition remains open, present it as such and agree how it will be resolved. It may be possible to prepare part of the work while another part awaits information, provided that has been agreed. Avoid turning the desire to begin into a promised schedule that depends on people or resources whose availability remains unconfirmed.
A sale with several participants becomes more solid when everyone can understand the decision in which they participate. Your work is to help that understanding circulate faithfully, answer the right questions and make clear commitments. Your contact then stops carrying the explanation of the service alone, and delivery begins with less room for incompatible interpretations of what was agreed.