Why deals stall at the end
Most business-to-business marketing and most sales content are built for the start and middle of a deal: the problem, the category, the product, the comparison. By the time a champion has chosen, the people who must approve the choice start asking their own questions, and they are different people with different concerns. The diagnosis of a lengthening sales cycle finds that time often accumulates in approval and procurement, and names the fix: security and architecture documentation, standard terms and data-processing pages, a business case template and reference customers by sector. This guide covers how to build that material and keep it working.
The stall happens because each late question is answered from scratch. A seller forwards a security questionnaire to whoever seems likely to know, a finance director's request for a business case becomes a weekend's work for the champion, and procurement waits for company details that exist somewhere in the business but not in one place. Each answer takes time, the buyer waits, and the momentum built during the evaluation fades. Some deals die there, not because the buyer changed their mind but because something else took the champion's attention. Sales cycle lengthAverage time from opportunity creation to a closed deal. grows, and the cause is invisible in a report that only shows stages.
The business-to-business content guide maps content by role and stage and points out that the procurement, legal and security columns are usually the empty ones. A late-stage library fills them before they are needed, so that the answer to a late question is a matter of finding and adapting rather than writing. The sales content and training guide lists a security and compliance pack, an implementation plan and contract summaries among the risk and procurement assets sales needs; this guide is about building and running those assets, and the pipeline section places them beside the guides on stages, alignment and measurement.
Who asks what in the last stages
Strategyzer's Value Proposition Canvas, listed in this page's sources, describes customers in terms of the jobs they are trying to do, the pains that get in the way and the gains they hope for. The sales cycle troubleshooting page applies it to the buying committeeThe group of people in an organisation who influence, evaluate and approve a purchase.: each role has its own jobs, pains and gains, and proof for the champion does nothing for procurement. The value proposition canvas framework page shows how to draw it; drawing one for each late-stage role is a quick way to see what the library is missing.
| Role | The job they are doing | What worries them | What they ask for |
|---|---|---|---|
| Champion | Getting the decision approved without damage to their standing | Being unable to answer a colleague's question | A business case they can present as their own; answers they can forward |
| Finance | Deciding whether the spend is justified against other uses of the money | Costs that grow after signature; benefits that never arrive | Total cost over the contract; how pricing changes; the assumptions behind the benefits |
| Procurement | Running a fair, documented purchase on acceptable terms | Non-standard terms; a supplier that cannot be compared or onboarded | Company details, standard terms, references, pricing logic |
| Security | Making sure the purchase does not create unmanaged risk | Unknown handling of systems and data | Completed questionnaires; documentation of how the product is built and run |
| Legal | Agreeing a contract the organisation can live with | Liability, obligations on data, terms that conflict with policy | Standard terms; data protection terms; a named contact for negotiation |
| IT | Fitting the product into what already exists | Integration effort; support burden after go-live | Architecture and integration documentation; an implementation plan |
The table is a starting point. Draw it again for each segment, because a regulated buyer, a public body and a small firm ask very different questions, and ask sellers which roles appear in their recent deals.
A business case kit for the champion
The champion is the person who has to make the case internally, and most champions have never written one for a purchase like this. A kit makes their job easier without writing the case for them.
A useful kit contains the problem stated in the buyer's terms; the options, including doing nothing and building something in-house; the costs of each option over the period the buyer cares about; the benefits, which the buyer estimates from their own figures; the risks of each option and how they are handled; and an implementation plan with the buyer's effort as well as the vendor's. It is editable, in a format the buyer's organisation uses, because the champion will present it under their own name. Every assumption is labelled as an assumption, with a space for the buyer's own figure.
The temptation is to fill the benefits with the vendor's estimates of what the buyer will save. Finance reviewers dismiss vendor-supplied savings quickly, and a case that collapses under one question damages the champion. A kit that asks the buyer for their own baseline figures and shows how to calculate the effect produces a case the buyer believes, because it is built from their numbers. Customer outcomes belong in the kit as evidence of what is possible, not as a promise of what this buyer will get.
Pricing in the kit should follow the logic the pricing and packaging guide describes, so that finance can see what is included, how the bill grows and what the alternatives cost.
Security and data protection answers
Security and data protection questions arrive as questionnaires, documents to review or calls with the buyer's specialists. They vary in format, but the underlying questions repeat across buyers, which is what makes an answer library worth building.
Ownership is the most important design decision. The substance of each answer belongs to the person accountable for it: the security lead for how systems are built, accessed and monitored, legal for terms and obligations, and whoever owns privacy for how personal data is handled. Buyers ask how the vendor processes personal data about their staff or customers, and where the GDPR applies it governs that processing, so those answers come from the privacy owner and are never written by marketing alone. Marketing's part is the structure of the library, the plain-language versions of technical answers, consistency between the library and what the website says, and the reminders that keep answers reviewed.
Build the library from the questionnaires the business has already answered. Group the questions by topic, write one approved answer for each, and record against every answer its owner, the date it was last reviewed and the date of the next review. Note which answers can be shared freely, which need a confidentiality agreement first, and which must be written fresh for each buyer. Store it where sellers and solution engineers can search it, and route every new question that is not in the library to the right owner rather than letting a seller improvise.
Publish what can be published. An overview of how the product handles security and personal data, written for the reviewer who will read it first, answers many questions before they are asked and shortens the questionnaire that follows.
The procurement pack
Procurement teams need information they can process quickly and compare across suppliers. A pack assembled once and kept current saves days of back and forth in each deal. A procurement packThe documents a vendor assembles once for buyers' procurement teams: company facts, standard terms, references, pricing logic, and implementation and support. is therefore maintained material rather than work done afresh for every buyer.
- Company facts. Legal entity name, registration details, addresses, ownership, the contacts for contracts, invoicing and support.
- Standard terms. The contract the vendor offers by default, with any data protection terms, so that negotiation starts from a known document. Legal owns these; the pack only makes them easy to find.
- References. Comparable customers who have agreed to speak or be named, drawn from the reference pool that the customer references and advocacy guide describes, matched to the buyer's sector and size.
- Pricing logic. How the price is built, what each option includes and how it changes with volume or term, consistent with the pricing and packaging guide.
- Implementation and support. What happens after signature, who does what, and how support works.
Keep one version of each document, with an owner and a review date, and keep the pack where any seller can send it. Procurement questionnaires vary in format; answers drawn from the pack and the security library fill most of them.
Responding to a request for proposal
A request for proposal turns the end of a deal into a formal comparison, and it can arrive with little warning. The agency request for proposal template shows the process from the buyer's side: what the buyer asks, how answers are scored and why a structured request makes responses comparable. Seeing it from that side is the best preparation for answering one.
Decide whether to bid. Write bid or no-bid criteria in advance and apply them every time: fit with the ideal profile, whether the requirements match what the product actually does, whether anyone had a conversation with the buyer before the request arrived, whether the request appears to be written around another vendor's product, and whether the team has the capacity to answer well. A request that fails several criteria is usually better declined politely than answered badly.
Build the answer from the library. Reuse approved answers from the security library and the procurement pack, and write fresh only what is specific to this buyer. A requirement-by-requirement compliance table, one row per requirement with the answer and any condition, shows the evaluator exactly where the product meets the need. Answer honestly, including "not supported" where that is the truth; an evaluator who discovers an overstated answer later stops trusting the rest. Where a requirement can only be met by planned work, the guide to talking about the roadmap covers approved roadmap wording and who must agree before a future capability is written into a response.
Bring the win themes. The competitive battlecards guide covers the honest differences against each rival; the battlecardA short internal document that tells salespeople how to position against one named competitor in a deal. for any competitor known to be bidding supplies the themes the response should prove, not just claim.
Approve before sending. A proposal makes commitments on behalf of the company, so it passes through the reviews the approvals and compliance guide describes, with legal, security and finance signing the parts they own.
Debrief either way. Ask the buyer for feedback whether the bid won or lost, record the outcome and the reasons in the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it., and feed both into the library and the bid criteria. Over time the win rateShare of closed sales opportunities that were won. on bids that met the criteria, against those that did not, tests whether the criteria are right.
Keeping the library current
A late-stage library goes stale quietly. A product changes, a policy is updated, a new type of buyer asks a question nobody has answered, and the old answer keeps being sent. Three habits keep it current.
The first is collecting the late questions. The sales cycle troubleshooting page recommends asking sales regularly which questions arrived late in deals and adding the answer to the library promptly. The weekly pipeline review is a natural place to capture them, because stuck deals surface there with the question that stalled them. The sales and marketing alignment guide makes content for sales a commitment in the agreement between the teams, and late-stage material belongs in that commitment.
The second is owners and review dates on every item, with reminders that reach the owner before the date passes. The third is planning late-stage material into named-account programmes. For target accounts, the ABM account plan template includes plays for the opportunity stage, and the account-based marketing on LinkedIn guide plans content by buying role; putting the security overview or the business case kit in front of the roles that will need them, before they ask, moves the late questions earlier.
| Item | Owner | What triggers an update |
|---|---|---|
| Business case kit | Product marketing, with finance input | Pricing or packaging change; new customer evidence |
| Security answers | Security lead | Product or infrastructure change; review date |
| Data protection answers | Privacy owner | Change in how personal data is handled; review date |
| Standard terms | Legal | Policy or contract change |
| Procurement pack | Sales operations or marketing | Company detail change; new references |
| Bid criteria | Sales and marketing leads | Debrief findings |
An analytics vendor's late-stage library (illustrative)
Hushfinch Analytics stops answering from scratch
Hushfinch Analytics is an invented vendor of footfall and sales analytics software for retail chains. Its sales team asks marketing why so many deals seem to stall after the champion has chosen. The marketing lead reviews the 22 deals closed or lost over the past two quarters with the sellers and lists every question that arrived after the product demonstration. There are 140, and most fall into a few groups: how the product handles shoppers' and staff personal data, how the business would justify the spend, and procurement's requests for company details and terms.
The team builds three things. A business case kit sets out the problem, the options including doing nothing, the costs and a benefits section where the buyer enters their own figures for store hours and stock losses, with every assumption labelled. An answer library of 85 approved answers is owned by the security lead and the data protection officer, with marketing writing the plain-language versions and every answer carrying a review date six months ahead. A procurement pack gathers company details, standard terms, pricing logic and three references from the reference pool.
Hushfinch also adopts a bid or no-bid rule after a debrief on a lost bid reveals that the requirements had been copied from a competitor's product sheet. Of the next seven requests for proposal, it declines three that fail the rule, including two that list features only one rival offers, and answers the other four from the library. Sellers report that the security and procurement questions in the following quarter are answered in days rather than weeks, and the questions that are not in the library are routed to their owners and added.
If sellers still improvise late answers once the library exists, the guide to sales not using marketing content checks whether the problem is findability, proof that fits the buyer or training on when to use each item.
Common mistakes
- Writing every late answer from scratch. The same questions recur across buyers; answer them once, properly, and reuse.
- Marketing writing security or privacy answers alone. The substance belongs to the people accountable for it; marketing supplies structure and plain language.
- A business case built on the vendor's estimates. Finance trusts figures from its own organisation; give the champion a kit that uses them.
- Answers without owners or review dates. A library nobody reviews becomes a source of confident, out of date answers.
- Bidding on every request for proposal. A request written around another product is usually lost before it starts; criteria free the time to answer good ones well.
- Overstating compliance with requirements. "Not supported" is an answer; an overstated one is a problem waiting for implementation.
- Ignoring the questions sellers report. The late questions from this quarter's deals are next quarter's library entries.
