All articles

Your Contact Has to Sell the Idea When You’re Not in the Room

Help your contact explain the proposal internally with a clear problem, relevant evidence, open risks and a specific decision, not another product deck.

Help your contact carry a decision brief, not just a shorter product presentation. It should explain the buyer’s problem, distinguish evidence from assumptions, expose open risks and alternatives, and name the next commitment colleagues are being asked to consider. Let the contact correct it in their own terms. A useful note does not establish authority, budget or agreement.

AI-generated buyer enablement scene: an operations contact prepares a business case note for colleagues beside an inspection sensor

Table of contents

  1. 1. The people reading the forward missed the meeting

  2. 2. Give the internal reader a case they can examine

  3. 3. Let your contact correct the case before using it

  4. 4. What the forwarded note could actually say

  5. 5. Frequently asked questions

The people reading the forward missed the meeting

The colleagues who receive your proposal were not necessarily on the call. They may see a supplier’s name, an attachment and a short message from someone they trust. They haven't heard which questions were answered, which claims were qualified or what the demonstration actually showed. We need to start with that missing context.

Your contact says, “Send something over and I’ll discuss it with the team.” A product deck is a reasonable response: it preserves the technical explanation. But the contact may still have to construct the reason for discussing it, separate the supplier’s claims from their own observations and decide what they want colleagues to approve.

Consider a hypothetical manufacturer exploring a camera-based inspection sensor. Its quality lead has watched the supplier demonstrate a visible mark on a sample. The supplier sends a recap about flexible configuration, integration support and the product range. In this illustrative scenario, the lead still has no agreed account of the plant’s problem or what a technical check would require. No actual demonstration result or customer is being reported.

A supplier observation, buyer-owned problem and explicit unknowns support a next-decision discussion without turning assumptions into verified results

Information to carry into the hypothetical discussion, not evidence of internal approval.

A short note can ask for a small decision

We don't need to turn that conversation into a complete purchase justification immediately. The first internal question might be whether production and quality should help scope an off-line feasibility check. A note for that decision can be short while leaving the work of a later investment case unfinished.

HM Treasury’s Green Book, checked on November 12, 2026, describes proportional business cases as providing sufficient detail for sound decisions without unnecessary effort, taking account of scale, cost, complexity and risk. That is UK public-spending guidance, not this private buyer’s procurement procedure. The useful analogy is to match the detail to the commitment under discussion, not to skip necessary reviews.

Give the internal reader a case they can examine

An internal business case serves a different reading situation from a supplier presentation. We're helping someone who missed the meeting understand a proposed change and judge a commitment. Reducing the slide count won't necessarily provide the missing information. A short discussion note needs a reason to exist outside the sales conversation.

Start with the buyer’s problem and the purpose of bringing it up now. Use a description your contact recognises, including what remains uncertain. “Our product improves inspection” is a supplier proposition. “We want to understand whether this kind of inspection could address the issue quality has raised” leaves the application and the evidence open for colleagues to examine.

Then distinguish what is known from what is being proposed. What did the buyer report? What did the demonstration actually show? Which claimed benefit still needs checking in the buyer’s conditions? Without those distinctions, a forwarded summary can make a supplier’s possibility sound like an internally verified conclusion.

Name the decision the note requests. Is it permission to involve an engineer, to prepare a test plan or to consider spending? What work would a yes authorise, and what would it leave undecided? “Please review the proposal” gives the reader less to judge than a request with a clear scope and an owner who can confirm it.

Leave room for alternatives and unresolved costs or risks. Continuing the current approach, revising an existing check or gathering more information may be relevant options. If you don't know what would make one preferable, state the missing question. The note should help colleagues disagree usefully, not make your preferred option look inevitable.

Borrow the questions, not someone else’s approval process

HM Treasury’s published summary business-case guidance, also checked on November 12, 2026, brings together the reason for change, options, costs, benefits, risks, funding assumptions and delivery arrangements. We are borrowing those kinds of questions as an editorial analogy. Private buyers are not being told to adopt a government model or compress a formal appraisal onto a page.

For your contact, the practical structure can be simple: why discuss this, what supports it, what remains unresolved, which alternatives deserve attention and what decision is requested. Put the supporting technical material behind that account. The first reader should not have to reconstruct the argument from a catalogue.

Let your contact correct the case before using it

You can draft a starting point, but your contact must be able to reject its premise. Ask whether it describes the problem accurately and whether it is useful for the discussion they actually plan to have. They may tell you that the issue belongs to another team, the timing is wrong or the proposed check would answer the wrong question.

Those corrections are valuable. Keep the buyer’s account distinct from your proposed language. Don’t place an unconfirmed benefit, a convenient savings estimate or someone else’s supposed support in the contact’s voice. If the economics are unknown, leave them unknown. A polished paragraph isn't a substitute for the buyer’s evidence.

Nor does agreeing to forward the note establish internal advocacy. In MEDDICC’s own framework, a Champion has influence, a stake in the outcome and an active internal selling role. Its distinction, checked on November 12, 2026, is a sales-method definition, not proof of this contact’s position. A friendly response or a well-written document doesn't establish all those conditions.

Keep the request proportionate to the relationship. Your contact may want an explanation they can question, not a script that makes them responsible for closing your deal. An honest internal discussion can end in a request for more evidence, a different option or a decision not to proceed. The material should remain useful in those outcomes too.

What the forwarded note could actually say

Here is a filled-in example for the hypothetical inspection-sensor discussion. The assumed constraints are that quality has raised an issue, production time is limited and no in-plant trial or purchase has been approved. These are invented conditions for explanation, not observations from a real account. The note is written as something the contact would first correct, not send unchanged.

“Purpose: decide whether production and quality should help scope an off-line feasibility check of camera inspection for the issue raised by the quality team. This discussion isn't a request to order a sensor or install it on the line.”

“What we have so far: the quality lead has described a concern about inconsistent inspection. The supplier has demonstrated detection of a visible mark on its sample. We haven't measured the scale of our issue, tested representative retained samples or established performance under our production conditions. No savings figure is included.”

“What needs checking: whether suitable retained samples can be used, what outcomes would matter to quality, which operating conditions need to be represented and who would own the review. We also need to understand what time, equipment and supplier assistance a feasibility check would require before seeking approval to run it.”

“Alternatives: review the current inspection approach, ask for more relevant evidence before committing time, or take no further action if the issue doesn't justify investigation. The supplier’s proposed sensor is one option to examine; the product demonstration has not established which option is best for our use.”

“Decision requested: can production and quality identify the right participants to prepare a feasibility-check outline? If that is not worthwhile now, record what information or priority is missing. A separate decision would be needed on the resources and conditions for any actual test.”

Compare that with the original recap about configuration and product range. The note still doesn't prove technical suitability, but it exposes a question, an evidence gap and a request colleagues can respond to. The observable result of this hypothetical rewrite is a clearer document. No internal agreement, approved test or sale has been demonstrated.

Whether the account started in OKKI Go, at an exhibition or through a referral, keep that distinction intact. Company background can help you prepare a relevant conversation; it cannot tell you what colleagues have accepted inside the buyer’s organisation. Before calling the document ready, ask your contact what they would change and whether this is the decision they want to put in front of the team.

Before you send the deck, ask what the next internal reader needs to decide and what your contact can honestly stand behind. Give that reader enough context to question the proposal, including a reasonable basis for saying no. You are helping the contact carry an account they can defend, not asking them to repeat a pitch they cannot verify.

Frequently asked questions

What should you send when a contact wants to discuss your proposal internally?

Send material matched to the next discussion: a short buyer-relevant explanation of the problem, the evidence available, the important unknowns and the decision being requested. Attach technical detail where needed. Ask the contact to correct the account before using it; do not assume a product recap is already an internal case.

Does a contact who forwards your presentation qualify as a sales champion?

Forwarding alone does not establish influence, advocacy or a stake in the outcome. MEDDICC uses those conditions in its own Champion definition, which is a method rather than a universal rule for buying organisations. Treat the contact’s actual role and actions as questions to understand, not a status a document can create.

Should an early internal business case include ROI or a complete purchase request?

Include economic claims only when there is a defensible basis and the intended decision needs them. An early discussion may instead ask whether to investigate an application or prepare a test plan. State what remains unknown and what a positive response authorises; a short note does not replace any mandatory investment or technical review.

Explore OKKI Go

OKKI Go

Bring prospecting into your AI workflow.

Use AI agents to search companies, find decision-makers and start outreach.

Explore OKKI Go