How long should a white paper be?

Ten to twenty pages suits most B2B and technical topics. Shorter briefs of six to eight pages work for a single objection; industry playbooks run twenty to thirty pages.

What tone should a white paper use?

Neutral, specific, and evidence-led. Avoid superlatives and product language in the body; the argument should hold even if the vendor's name were removed.

Should a white paper mention the product?

Yes, but late and briefly. Establish the problem and the general approach first, then show how your implementation fits. Product-first white papers get discarded as sales collateral.

How many sources does a white paper need?

Enough that every factual claim is checkable — typically eight to twenty references. Prefer standards bodies, regulators, and peer-reviewed or analyst research over vendor blogs.

How to Write a White Paper: A Step-by-Step Process

Most failed white papers fail before a word is written — no named reader, no single claim, no evidence plan. Here is the sequence that avoids that.

August 10, 2026 · 10 min read

Quick answer

To write a white paper: name one reader and the decision they own, write the single claim the paper proves, build an evidence plan with cited sources, get the outline approved, draft the executive summary first, include an honest limitations section, then lock text before design. Ten to twenty pages is standard.

A white paper is an argument supported by evidence, written for one identified reader who has a decision to make. Everything in the process below exists to protect those three constraints. Skip the first two steps and the draft will be a brochure with footnotes.

Step 1 — Name the reader and the decision

Write down one job title and one decision. 'A VP of Engineering deciding whether to allow autonomous agents write-access to production systems' is a reader. 'Enterprise decision-makers' is not. The reader determines vocabulary, evidence type, and length.

Step 2 — Write the single claim

One sentence that the paper proves. If you cannot write it, you are not ready to outline. Every section should either establish the claim, support it with evidence, or address the strongest objection to it.

Step 3 — Build the evidence plan

Primary standards and regulator guidance where relevant
Independent analyst or academic data for market claims
Your own measured results, with the baseline stated
Expert interviews, quoted and attributed with permission
A named source for every number that appears in the document

Step 4 — Outline before drafting

Get the outline approved by every stakeholder who will later review the draft. This single step removes most late-stage rewrites, because structural disagreement is cheap to resolve at the bullet stage and expensive at the paragraph stage.

Step 5 — Draft to the summary first

Write the executive summary first, as if the reader will read nothing else — because many will. Then write the body to support it. Revisit the summary at the end so it matches what the paper actually proves.

Step 6 — Include the limitations

A section that names what the approach does not do, and under what conditions it underperforms, raises credibility more than any claim of superiority. Reviewers are trained to look for it and distrust documents that lack it.

Step 7 — Review, then design

Lock the text before design. Then design for scanning: a summary box, clear headings, one chart per key claim, a comparison table, and a references list. Deliver a print-ready PDF — enterprise reviewers still print.

Write the executive summary as though the reader will read nothing else. Many will.

The seven-step process at a glance

Step	Output	Who is involved
Name the reader	One job title and one decision	Marketing and sales
Write the claim	A single provable sentence	Author and sponsor
Evidence plan	Source list and interview schedule	Author and SMEs
Outline approval	Signed-off section structure	All reviewers
Draft	Executive summary first, then body	Author
Review	Technical, legal, and editorial passes	SMEs, legal, editor
Design	Print-ready tagged PDF	Designer

Sources & further reading

Primary standards, official documentation, and research referenced in this article.

FAQ

How long should a white paper be?: Ten to twenty pages suits most B2B and technical topics. Shorter briefs of six to eight pages work for a single objection; industry playbooks run twenty to thirty pages.
What tone should a white paper use?: Neutral, specific, and evidence-led. Avoid superlatives and product language in the body; the argument should hold even if the vendor's name were removed.
Should a white paper mention the product?: Yes, but late and briefly. Establish the problem and the general approach first, then show how your implementation fits. Product-first white papers get discarded as sales collateral.
How many sources does a white paper need?: Enough that every factual claim is checkable — typically eight to twenty references. Prefer standards bodies, regulators, and peer-reviewed or analyst research over vendor blogs.