White Paper Copywriting: How to Write One for a Client

A B2B software company has hired you to write a 12-page white paper. They want it to drive pipeline. They have a product, a sales team's pitch deck, and three months of analyst calls you can listen to. The client has a date in mind for publication and a vague idea of what the paper should argue.

That is the freelance white paper copywriting job, and it is significantly harder than writing a sales page. You have to synthesize a client's proprietary knowledge, find credible third-party data, structure an argument that earns trust, and write in a voice that sounds authoritative without sounding like a vendor pitch. Most white paper guides are written for B2B marketers planning the channel. This one is for the writer who has to deliver the document.

Here is how to do that work.

What a White Paper Actually Is

A white paper is an argument. A long one. Sophisticated buyers read it because they have a decision to make and the paper helps them think through it. The paper does not sell explicitly. It earns trust by answering the question the buyer is actually asking.

Three things separate a white paper from a long blog post or a report.

• It argues for a position. A blog post can be informative and end. A report can be data and end. A white paper takes a side and defends it with evidence. If you finish reading without knowing what the author thinks, the paper failed.
• The reader is sophisticated. White paper readers are usually directors, VPs, or above. They are not looking for definitions. They want to know if the position holds up to their existing knowledge.
• The format is built for skim-then-read. The executive summary delivers the full argument in 300 words because half the audience reads only that. The body delivers the evidence for the half that goes deeper.

McKinsey publishes white papers as the gold standard of this format. Their pieces (research notes, perspectives, insights articles) all run the same arc: a thesis stated up front, evidence layered behind it, a conclusion that names the implication. The writing is dense without being academic, which is the bar to aim for.

The Research Job: Finding the Right Question

The single most common reason white papers fail is that they answer the wrong question. The client thinks the audience is asking "why should I buy software like ours?" The audience is actually asking "is the problem this software solves a priority for me right now?" Those are completely different questions. Answering the first one when the audience is asking the second one wastes 12 pages.

Three steps to find the right question:

1. Read the audience's own words on the problem. Before you read a single sales call recording, find Reddit threads where the audience talks about this problem when no vendor is in the room. r/devops, r/sysadmin, r/sales, r/procurement. The way a VP of engineering frames a build-vs-buy decision in a Reddit thread is different from the way they frame it on a sales call. The Reddit version is usually closer to the truth.
2. Then listen to the sales calls. Listen for what the prospect asks before the salesperson answers. Those questions are usually the real ones. The objections that come up after the demo are the questions you have to address in the white paper to move the buyer.
3. Compare what the client thinks the audience asks to what the audience actually asks. Almost always, there is a gap. The client believes the audience asks one thing. The Reddit threads and sales calls show the audience asks something else. Bridging that gap is where the right white paper question lives.

PhraseMine is built for that first source. Paste a brief about the audience and the problem, and it returns the Reddit conversations where this audience talks about the issue without a vendor present. The way they articulate the problem in those threads is what should anchor the executive summary.

For a fuller breakdown of the two research tracks every B2B copywriter runs, see customer research questions for copywriters.

The White Paper Structure That Earns the Read

Every credible white paper uses roughly the same five-part structure. The order is not negotiable.

Part 1: Executive summary. 300 words. Stands alone. Half your readers will only read this. It must deliver the full argument: the problem, your position, the key evidence, the implication.

Part 2: Problem framing. What the problem is, why it is a problem now, and how the audience currently experiences it. Evidence supports every claim here. This is where the audience decides whether to keep reading or not. If the framing matches what they already feel, they keep reading.

Part 3: The argument. Your thesis, stated clearly. One sentence the reader can quote back. The argument should be specific enough to be wrong. If the position is so vague that no one could disagree, it carries no weight.

Part 4: The evidence stack. Third-party research, primary data the client owns, customer case studies, expert interviews. Each piece of evidence reinforces a specific part of the argument. Hubspot's State of Marketing report is a good model here: their argument is anchored by survey data they ran themselves, then layered with third-party research that contextualizes their findings.

Part 5: Conclusion and next step. What the implication is, what the reader should do, and (lightly) how the client helps. The CTA at the end of a white paper is the softest CTA in B2B marketing. "Talk to our team" is enough. Hard sales asks at the end of a white paper undo the trust the rest of the paper just built.

Salesforce's State of Sales report, an enterprise-level annual white paper, runs this exact arc across 80 pages. The executive summary holds the full thesis. The body delivers the data. The conclusion implies the client without selling.

How to Write the Executive Summary

The executive summary is the hardest single piece of writing in a white paper. Many B2B readers (CFOs, board members, the executive sponsor of the buying decision) only read this. The 300 words have to do all the work.

Three things that make an executive summary land.

1. State the problem in the audience's words. If you wrote the problem framing using language from the client's deck, rewrite it using language from your audience research. The summary should make the reader think "yes, this is exactly the problem I am dealing with" in the first paragraph.

2. State the position clearly. Not "this paper explores the topic of X." Not "we believe several factors contribute to Y." A clear sentence: "The conventional approach to X is now wrong. Here is why and what to do instead." If the reader cannot summarize your position in one sentence after the executive summary, the summary failed.

3. Name the implication. What changes for the reader if they accept your argument? A budget reallocation? A hiring decision? A vendor swap? Naming the implication is what makes the summary memorable. Vague summaries get skimmed. Specific summaries get forwarded.

Before

“This white paper explores the evolving landscape of customer support technology and examines how organizations can prepare for the next generation of support tools. We discuss several key trends and offer recommendations for technology leaders.”

After

Most enterprise support teams are paying for automation that does not get used. The reason is not the technology. It is the workflow handoff between automation and human agents, which has not been redesigned for the AI-assisted era. This paper argues that the next 18 months will separate teams that fix the handoff from teams that keep paying for tools their agents work around.

What Counts as Credible Evidence

White paper evidence has a hierarchy. Some sources earn trust. Some break it. Get the wrong source mix and the paper reads as marketing.

Strongest evidence:

• Independent third-party research from named institutions (Gartner, Forrester, McKinsey, IDC, university research labs).
• Primary data the client owns (anonymized customer data, internal usage data, original survey research).
• Named expert interviews from people the audience would recognize as authorities.

Weak evidence:

• The client's own marketing claims with no source citation.
• Industry "studies" published by competitors trying to sell the same thing.
• Single anecdotes presented as trends.
• Quotes from anonymous customers without role or industry context.

The fastest test: would a skeptical buyer accept this evidence in a board meeting? If no, do not use it. White papers get forwarded internally and one weak citation undermines the rest of the document.

If the client wants to include their own customer success metrics, frame them as case study data with full context (industry, company size, time period, what they measured). Stripped of context, the same numbers read as marketing.

Writing the Tone: Authoritative Without Stiff

White paper voice is harder than blog voice because the register is higher but the writing still has to read. Three things keep authority readable.

1. Short sentences after long ones. Academic writing fails because every sentence is dense. Strong white paper writing alternates. A long sentence that carries an argument followed by a short sentence that lands the point. The rhythm is what keeps a 12-page paper readable.

2. Concrete examples in every section. Abstract argument plus concrete example is the rhythm. If a section runs three pages without a named company, a specific number, or a real scenario, the reader checks out. Even McKinsey, which is the most abstract of the major B2B publishers, breaks every long argument with a concrete reference.

3. Active voice. "We found that 60% of teams" beats "It was found that 60% of teams." White paper writers slip into passive voice trying to sound objective. The result reads as bureaucratic. Authority comes from the strength of the argument, not the distance of the writing.

For the broader frame on writing in a voice that is not your own, see voice of customer research for copywriters.

How to Deliver a White Paper to a Client

A white paper handoff has more moving parts than most copy projects. The document goes through copy, design, legal, and sometimes a sales review before it ships. Three things to include in the deliverable.

1. The full document in a Google Doc with section headings. Executive summary, problem framing, argument, evidence sections, conclusion. Each section labelled and structured so the design team can lay it out without guessing.

2. The evidence appendix. A separate doc listing every source you cited, with links, dates, and the specific data point pulled from each one. The legal review uses this. The design team uses it for footnotes. The client uses it when prospects ask "where did you get that number?"

3. The design brief one-pager. Suggested pull quotes (the lines you want highlighted), the visualizations the data supports, and the tone reference (other white papers in the same neighborhood). The design team will lay it out faster and better with this in hand.

If the client is also producing a sales page or one-pager from the white paper, see sales page examples that convert for how the same research feeds into shorter formats.

White paper copywriting fails when it sounds like a vendor pitch dressed up in a serious format. It works when it answers a question the audience genuinely has and earns the trust to be forwarded inside an organization. PhraseMine gives you the audience's actual framing of the problem before you write the executive summary, which is the difference between a white paper that gets read and one that gets archived.