Blog
When a prospect says, “Send me something”, they are rarely asking for a generic company brochure. They are usually asking for help with a specific decision: whether the problem is worth solving, whether your approach will work, whether the change is manageable, or whether they can defend the purchase internally.
A strong B2B sales follow up gives the buyer exactly what they need for that next decision. Instead of writing “just checking in”, identify the unresolved question from discovery and send one useful asset with one clear sales next step.
Many sales professionals hear this phrase and immediately send a pitch deck, product brochure, website link and case study. It feels responsive. In reality, it puts work back on the prospect. They must work out what matters, what to forward, and how to explain your relevance to others.
That is not decision enablement. It is content dumping.
In B2B selling, a buyer is often managing several concerns at the same time. A business leader may want commercial impact. An operations leader may worry about disruption. IT may want security and integration clarity. Finance may ask whether the return justifies the spend. Procurement may compare alternatives after the business case is already taking shape.
Your follow up after sales meeting should help the prospect handle one of these conversations. If you cannot identify which conversation comes next, you have not completed discovery.
“Sales is not about selling anymore, but about building trust and educating.”— Siva Devaki, sales thought leader
The practical implication is simple: your deal follow-up should educate the buyer towards a decision, not educate them about every feature you offer.
Before you send anything, review your meeting notes and ask: what was unresolved when the call ended? The answer determines the asset.
Listen for the language buyers use. If they say, “We need to show leadership that this is worth prioritising”, they need a quantified business case. If they say, “My team will ask how long this will take”, they need an implementation plan. If they say, “We are looking at a few options”, they need a comparison guide.
There are six common decision questions behind “send me something”.
| Buyer’s unresolved question | Best follow-up asset | Your objective |
|---|---|---|
| Is this problem costly enough to act on? | Quantified business case | Create urgency and commercial logic |
| Can we implement this without disruption? | Implementation plan | Reduce delivery and adoption risk |
| How does this compare with our alternatives? | Comparison guide | Shape evaluation criteria |
| How do I explain this to my leadership team? | Stakeholder brief | Help the champion build internal alignment |
| Has this worked for a company like ours? | Relevant proof point | Build credibility and lower perceived risk |
| What exactly should happen next? | Next-step email | Secure a committed action and date |
Send a business case when the buyer accepts the problem but has not yet made it important enough to fund. This is common when a functional manager likes your solution but needs approval from a CFO, founder, regional leader or business head.
A useful business case is not a fabricated ROI calculator. It uses the buyer’s own inputs from discovery, clearly labels assumptions, and shows the operational consequence of doing nothing.
For example, if a sales leader told you their team loses time building manual reports, do not claim a precise saving without evidence. Write: “Based on the reporting process you described, the proposed approach is designed to reduce manual consolidation and give managers earlier visibility into stalled deals. The commercial case will depend on the time recovered, adoption by managers, and the value of improved conversion.”
Then list the inputs you need to complete the case. This gives the champion a practical reason to engage again.
A business case should be short enough to forward. One or two pages is often more useful than a detailed spreadsheet that no one opens.
Implementation anxiety kills deals that appear healthy in pipeline reviews. A prospect may agree with your value proposition and still pause because they fear internal disruption, technical dependencies, training effort or a failed rollout.
Send an implementation plan when the buyer asks about timelines, onboarding, integrations, adoption, data migration, governance or support. This asset should make the first phase feel controlled, not effortless. Experienced buyers do not trust “seamless implementation” language. They want to know what is required from both sides.
If you sell into regulated sectors, implementation detail is even more important. A banking, financial services or insurance buyer may need clarity on controls, information handling and ownership before product capability becomes relevant. Teams selling into these environments should build this into their sales training for BFSI, rather than leaving it to late-stage solution consultants.
When a buyer says they are evaluating alternatives, do not send a competitor-bashing document. It makes you look defensive and is unlikely to be forwarded internally.
Instead, send a comparison guide that helps the prospect evaluate options fairly. The guide can compare approaches, not named competitors: build versus buy, point solution versus integrated platform, local support versus remote support, or standard deployment versus customised deployment.
The purpose is to influence the evaluation criteria before the buyer reduces the decision to price or feature checklists.
A practical guide might include questions such as: What internal capability is needed to make each option work? Who owns ongoing administration? What is the cost of delayed adoption? How easily can the solution support additional teams or markets? What evidence should a vendor provide before selection?
This approach is particularly useful in SaaS deals, where buyers may see several products with apparently similar feature sets. The seller who clarifies the operational trade-offs often earns more trust than the seller who claims to be best. For stronger capability here, explore sales training for SaaS companies.
A stakeholder brief is the most underused asset in a B2B follow-up strategy. Your main contact may understand your solution, but they still need to bring in leadership, finance, IT, operations, procurement or a country head. If they cannot explain the proposal simply, the deal loses momentum between meetings.
Create a one-page brief they can forward without rewriting. It should not look like a marketing flyer. It should read like an internal note prepared for a decision discussion.
Do not make the champion hunt through a deck for this information. Make them look prepared in front of their colleagues.
Proof is needed when the buyer’s concern is credibility. They may like your approach but wonder whether you understand their sector, company size, regional context or specific use case.
The most useful proof point is narrow and relevant. A two-paragraph mini case is often stronger than a glossy collection of logos. Describe the starting problem, the work done, the conditions that made it successful and the outcome observed. Keep customer confidentiality intact where required.
Do not send a case study because it is the only asset available. Send it because it answers a live doubt. If the buyer is concerned about manager adoption, send proof about manager adoption. If they are worried about multi-market rollout, send proof about coordinating stakeholders across markets.
For buyers increasingly using AI to validate vendor claims before or after a meeting, vague proof will not survive scrutiny. Your follow-up needs clear claims, clear scope and no inflated language. This is especially important in complex deals, as discussed in how B2B buyers use AI for validation, discovery and proof.
Not every follow-up needs an attachment. If the prospect is already aligned on the problem, value and approach, adding more content can create delay. Send a concise next-step email that confirms what was agreed and makes the next action easy to accept.
This is the right move when the meeting ended with a specific commitment, such as bringing in the IT lead, validating commercial inputs, reviewing a proposal or scheduling a product workshop.
Subject: Next step on [priority discussed]
Hi [Name],
Thanks for the discussion today. My understanding is that the immediate priority is [problem/outcome in their words], particularly because [business context they shared].
We agreed that the next useful step is [specific action] with [stakeholder names or roles]. I suggest we use that session to validate [two or three open items] and decide whether it makes sense to progress.
I have held [two time options]. Please let me know which works, or send a suitable alternative.
Regards, [Your name]
This format is simple, but it does three important things. It proves you listened, creates a shared record of the agreement, and asks for a decision rather than a vague response.
A good deal follow-up is rarely one email. It is a sequence that moves the buyer from interest to internal alignment to a committed decision process. The sequence should change based on what happens, not run automatically regardless of buyer behaviour.
Send the asset while the meeting context is fresh. Open with the issue discussed, not an introduction to your company. Explain why you chose this asset and what you want the buyer to do with it.
If there is no response, do not write “just checking in”. Offer a version designed for a specific internal audience. For example: “You mentioned your operations head will be involved. I have condensed the rollout approach into a one-page brief that may be easier to share.”
If the deal remains quiet, ask a direct but respectful question. “To make this useful, which area needs more work before you can decide whether to proceed: business case, implementation effort, stakeholder alignment or commercial terms?”
This question gives the buyer a low-effort way to explain the stall. It also tells you which asset to send next.
When you have made several useful attempts and there is still no engagement, close the loop without resentment. State the original priority, acknowledge that timing may have changed, and ask whether to pause, revisit in a defined period, or close the conversation.
A respectful close-the-loop message protects your time and often gets a more honest response than another chase email.
Sending a generic deck. A corporate deck may be useful later, but it rarely addresses a live buying concern. Lead with the decision asset, then include a company overview only if needed.
Using urgency that belongs to you, not the buyer. “Can we connect this week?” is not a reason to act. Tie urgency to the buyer’s planning cycle, operational problem, internal meeting or stated target.
Asking for a call without explaining its purpose. Every meeting request should state what will be decided or validated. Buyers accept working sessions more readily than vague catch-ups.
Overloading the champion. Your contact is not your content distribution team. Give them one clear item and a simple explanation of where it fits.
Failing to inspect follow-up quality. Managers often inspect call volume and email activity, but not whether reps are sending decision-enabling material. Better deal inspection should examine the buyer’s next decision, stakeholder gaps and agreed sales next steps. That discipline supports stronger sales coaching and more reliable pipeline conversations.
Simpli5Sales helps B2B teams improve discovery, stakeholder conversations, business-case selling and disciplined deal follow-up. Our corporate sales training and sales consulting work focus on the practical behaviours that help reps move opportunities forward without relying on generic sequences or discount-led pressure.
If your team has active opportunities stuck after good first meetings, start by reviewing the last ten follow-up emails. Identify the decision each buyer needed to make, the asset sent, and the next step requested. Then build the missing assets and coach the team to use them consistently. Talk to Simpli5Sales about strengthening your B2B follow-up strategy.
Loading comments…
Tell us where revenue is leaking. We'll show you what a working sales system looks like for your team.
