Give the buying team evidence it can use

Map decisions rather than job titles alone

Identify the questions that must be answered for the purchase to move forward. A user may ask whether the product fits daily work, an operator whether it can be implemented, a budget owner whether the value justifies the cost and a security reviewer whether the risks are acceptable. One person can hold several roles. Do not assume every organization uses the same sequence or that a senior title reveals the real approval process.

Ask sales what happens after the first enthusiastic meeting. Which person receives the material next, what do they challenge and what evidence is missing? Use documented objections and recent opportunities rather than inventing a generic committee. Record unknowns honestly. The output should be a set of decision questions and evidence needs, not a persona poster filled with confident claims about what finance or IT always wants.

Build a claim register before making the deck

For each important claim, record the exact wording, product version, scope, source, owner and review date. Separate demonstrated capability, observed customer outcome and projected benefit. A feature working in a controlled demonstration is not a promise about every customer environment. A customer quotation is evidence of that person’s experience, not automatic substantiation of a universal performance claim. Preserve the conditions that make the evidence meaningful.

The FTC’s US advertising guidance calls for truthful, non-deceptive and evidence-based claims, with additional rules for some categories. Treat that as a jurisdiction-specific starting point for review, not a complete global compliance rule. Have specialists approve technical, security, financial or regulated assertions. Avoid allowing a marketing shorthand to grow stronger each time it is copied into a slide, email or sales script.

Match the format to the doubt

A workflow doubt may need a demonstration. An integration doubt may need architecture notes and a qualified technical conversation. A value doubt may need a transparent calculator with customer-controlled inputs. A change-management doubt may need a realistic implementation plan. Choose the smallest useful artifact that answers the question, including what it does not cover. Sending a long deck in place of a clear answer makes the buyer do unnecessary interpretation.

Slack’s creator account describes turning actual workplace use into a relatable story, while Volvo’s Epic Split makes a truck capability visually memorable. Both can open a conversation about a product. Neither replaces the evidence required to select, integrate or safely operate it. Use the campaign as an entry point and provide the next layer of detail for the particular buying decision instead of expecting one hero film to carry every burden.

Design for the person who was not in the meeting

Give each artifact enough context to stand alone: the problem, the supported claim, the conditions, the source and the next useful question. Buyers often forward material without the salesperson’s explanation. A screenshot stripped of footnotes or a calculator with hidden assumptions can become misleading in that handoff. Put material qualifications beside the claim and label illustrative figures clearly, even when that makes the page less dramatic.

Provide a short summary for navigation and a deeper evidence layer for review. Keep version control and a clear owner so obsolete specifications do not circulate indefinitely. Avoid collecting confidential customer data merely to personalize a proposal when a range or a customer-run worksheet would work. Obtain proper permission before using customer names, logos, quotations or non-public results. A polished document is not a reason to relax evidence or confidentiality standards.

Measure usefulness in the sales conversation

Ask which decision the artifact helped resolve, what questions remained and whether the next step was appropriate. Downloads and opens measure access, not buyer confidence or sales impact. Opportunity progression can provide a useful signal, but stronger deals may also receive more material. Do not infer that a document caused a win merely because it was present. Combine usage information with structured feedback and suitable testing where practical.

Review lost and stalled opportunities as well as wins. Sometimes the correct conclusion is that the product does not fit, the evidence is insufficient or the purchase is not a priority. Good enablement helps both sides discover that efficiently. Update the claim register when the product, evidence or requirements change. Retire material whose support has expired instead of allowing a once-convincing number to become a permanent sales legend.

Make the reasoning concrete.

A scheduling-software vendor says its product saves ten hours a week, but the number comes from one small team using an early version.

Replace the universal claim with a scoped description of that observed case if permission and evidence support it. Offer an illustrative worksheet that lets another buyer estimate their own task volume and time assumptions.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Buying decision

   What must be resolved, by whom and at what stage?

2. Supported claim

   What exactly can be said about the current product?

3. Evidence conditions

   Which version, customer context and measurement limits apply?

4. Useful artifact

   What format answers the question with the least ambiguity?

5. Internal handoff

   Would the artifact remain accurate when forwarded without explanation?

6. Review owner

   Who updates, approves and retires the evidence?

Read with a question in mind.

Watch for the wrong conclusion.

• Giving every decision-maker the same generic deck.
• Turning one customer’s outcome into an unconditional claim.
• Hiding assumptions or qualifications in a separate document.
• Calling a content-assisted opportunity a content-caused sale.

Sources & scope

Original editorial synthesis with linked campaign evidence. Exercises and calculations are hypothetical, not historical campaign facts. No named human author or reviewer is claimed.

• FTC: Advertising and Marketing Basics →Primary regulator guidance · Supports: US truth-in-advertising principle that claims should be truthful, non-deceptive and evidence-based; specialized products may have additional rules.
• Sandwich: Slack →Primary creator case study · Supports: Initial scepticism, actual use, documentary-style production, staff casting and reported internal-sharing anecdotes.
• Volvo Trucks: Viral marketing huge success, 11 December 2013 →Primary brand release via Cision · Supports: 14 November 2013 launch and original campaign context.