Research-backed white paper from a defensible point of view

Use real source material to research-backed white paper from a defensible point of view, with a defined deliverable, evidence controls, and practitioner-level decision rules.

Output

white paper

Inputs

8 required

Prompt depth

320 words

Copy-paste prompt

Replace the bracketed inputs with your real material.

You are a senior B2B research editor who builds white papers around a defensible argument, not a pile of statistics wrapped in formal language.

Topic: [the business question or market issue]
Audience: [role, industry, expertise level, and situation]
Our point of view: [what we believe and why]
Source pack: [upload or paste research reports, interviews, internal data, customer evidence, and approved links]
Product context: [one line, for relevance only]
Target length: [page count or word range]
Brand voice: [direct, technical, practical, provocative, or other]
Claims to avoid: [legal, competitive, confidential, or unproven claims]

Build the white paper:
1. Evidence readiness: separate what...

[Full prompt continues for Pro members.]

Unlock the complete prompt

Pro includes the complete prompt library and every complete workflow.

View Pro options

What you provide

Topic
Audience
Our point of view
Source pack
Product context
Target length
Brand voice
Claims to avoid

What you receive

Evidence readiness: separate what the sources prove, partially support, contradict, or cannot support. List missing evidence that would materially weaken the paper.
Editorial thesis: write the central argument in one sentence. It must explain something important, not merely announce a trend.
Evidence ledger: create a table with claim, source, evidence strength, limitation, and status as VERIFIED, PARTIAL, HYPOTHESIS, or SOURCE REQUIRED.
Narrative structure: organize the paper around the reader's current situation, what changed, why the standard response falls short, what the evidence reveals, a practical framew...
Full draft: write the complete paper in a clear practitioner voice. Use short paragraphs, concrete examples, useful subheads, and varied sentence structure. Avoid corporate fill...
Original framework: create one memorable model or decision tool derived from the evidence. Explain how to use it and where it stops being useful.
Production package: provide an executive summary, pull quotes, chart recommendations, source notes, title options, and a designer-ready page sequence.
Red-team review: flag unsupported claims, weak transitions, repeated ideas, and any section a skeptical reader would challenge.

Quality checks

Do not invent citations, findings, customer evidence, or statistics. Use SOURCE REQUIRED where evidence is missing.
Rule: a white paper earns authority by improving the reader's judgment, not by making the company sound authoritative.