30 Claude Prompts That Write White Papers

You are a technical writer and solutions architect who explains complex technology to a technical buying committee. <context> I need a technical white paper that explains how our technology works and why the approach is sound, built as one self-contained HTML document with inline CSS, a title page, and clean code/diagram blocks, previewable instantly as an artifact. </context> <inputs> - The technology / system: [WHAT IT IS] - The technical problem it solves: [THE CHALLENGE] - How it works at a high level: [ARCHITECTURE OR APPROACH] - Key technical differentiators: [WHAT IS NOVEL OR HARD] - Audience and their depth: [E.G. ENGINEERS, CTOS, ARCHITECTS] - Proof points: [BENCHMARKS, RESULTS, STANDARDS] </inputs> <task> Write a 1,800-2,600 word technical white paper with: a title page, an abstract, a problem statement with the technical constraints, an architecture/approach section with a described diagram and labeled components, a section on the key mechanisms and why they work, a performance or results section with data callouts, a security/reliability or limitations section, and a conclusion with next steps. Keep it precise and jargon-appropriate for the audience. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Describe diagrams as labeled boxes/flows in styled blocks; format any code or config in monospace blocks. - Accurate, specific technical claims; mark anything I must verify; accessible contrast. </constraints> <format> Return the technical white paper as an artifact, then list the diagrams it references so I can have them produced. </format>

You are a B2B solutions marketer who writes problem-solution white papers that move buyers toward a decision. <context> I need a problem-solution white paper that walks from a costly problem to our solution without sounding like an ad, built as one self-contained HTML document with inline CSS and a title page, previewable instantly as an artifact. </context> <inputs> - The expensive problem: [WHAT IS BROKEN AND WHAT IT COSTS] - Who suffers from it: [ROLE / TEAM] - Why existing approaches fall short: [STATUS-QUO GAPS] - Our solution approach: [HOW WE SOLVE IT, VENDOR-NEUTRAL FIRST] - Results or proof: [METRICS, OUTCOMES] - Brand and CTA: [WHO WE ARE, NEXT STEP] </inputs> <task> Write a 1,600-2,200 word problem-solution white paper with: a title page, an executive summary, a problem section that quantifies the cost of inaction, a section on why current approaches fail, a vendor-neutral framework for the right solution, a section showing how our approach fits that framework, a results/proof section with data callouts, and a CTA. Lead with the buyer's problem, earn the solution. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Spend most of the paper on the problem and the neutral framework before naming the product; no hard sell. - Use a cost-of-inaction callout box; accessible contrast and real specifics. </constraints> <format> Return the problem-solution paper as an artifact, then point out where the pitch starts and whether it arrives too early. </format>

You are a principal engineer who documents system architecture for technical evaluators. <context> I need an architecture deep-dive white paper that lets a technical evaluator understand and trust our design, built as one self-contained HTML document with inline CSS, a title page, and clean diagram/code blocks, previewable instantly as an artifact. </context> <inputs> - System name and purpose: [WHAT IT DOES] - Core components: [LIST THE MAJOR PIECES] - How data and requests flow: [THE PATH] - Key design decisions and trade-offs: [WHY BUILT THIS WAY] - Scale / reliability characteristics: [NUMBERS OR GUARANTEES] - Audience: [ENGINEERS, SECURITY, PLATFORM TEAMS] </inputs> <task> Write a 1,800-2,600 word architecture deep-dive with: a title page, an overview, a described system diagram with labeled components, a component-by-component breakdown, a data-flow walkthrough, a design-decisions section that names each trade-off honestly, a scalability and reliability section with figures in callouts, a security model section, and a conclusion. Be candid about trade-offs. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Render diagrams as labeled box-and-arrow blocks in CSS; code/config in monospace blocks. - State trade-offs explicitly rather than claiming the design has no downsides; accessible contrast. </constraints> <format> Return the architecture deep-dive as an artifact, then summarize the three diagrams it needs and the riskiest design choice it documents. </format>

You are a compliance and governance writer who explains how a product meets a standard or regulation. <context> I need a compliance white paper that explains how we satisfy a specific standard or regulation, built as one self-contained HTML document with inline CSS and a title page, previewable instantly as an artifact. </context> <inputs> - The standard or regulation: [E.G. SOC 2, ISO 27001, GDPR, HIPAA] - Who needs assurance: [SECURITY, LEGAL, PROCUREMENT] - The key requirements to address: [LIST THE CONTROL AREAS] - How we meet each: [OUR CONTROLS OR PRACTICES] - Evidence available: [AUDITS, CERTIFICATIONS, REPORTS] - Brand and contact: [WHO WE ARE, WHO TO ASK] </inputs> <task> Write a 1,500-2,200 word compliance white paper with: a title page, a scope statement, a plain-language overview of the standard and why it matters, a requirements-mapping section as a table pairing each control area with how we satisfy it, a section on evidence and audit posture, a shared-responsibility note where relevant, and a contact-for-due-diligence close. Keep it factual and disclaimer-aware. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Use a clean two-column requirements-to-controls table; do not overstate certification status, mark gaps as [VERIFY]. - Include a note that this is informational and not legal advice; accessible contrast. </constraints> <format> Return the compliance white paper as an artifact, then flag any control claim that needs sign-off from legal or security before publishing. </format>

You are a technical product marketer who writes integration and migration white papers for technical buyers. <context> I need a white paper that shows how to integrate with or migrate to our platform with minimal risk, built as one self-contained HTML document with inline CSS, a title page, and clean step blocks, previewable instantly as an artifact. </context> <inputs> - Platform or product: [WHAT THEY ADOPT] - The starting state: [WHAT THEY MIGRATE FROM OR INTEGRATE WITH] - The main risks or fears: [DOWNTIME, DATA LOSS, EFFORT] - The phased approach: [STAGES OR STEPS] - Proof it works: [CUSTOMER EXAMPLES, METRICS] - Audience: [ENGINEERS, IT LEADERS, ARCHITECTS] </inputs> <task> Write a 1,600-2,200 word integration/migration white paper with: a title page, an executive summary, a section framing the risks of the current state, a recommended phased approach broken into numbered stages with what happens and how risk is contained at each, a rollback and validation section, an effort-and-timeline callout, a customer-proof vignette, and a getting-started CTA. Make the path feel safe and concrete. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Present phases as clearly numbered, scannable blocks; include a risk-mitigation note per phase. - Realistic effort and timeline ranges, not best-case fantasy; accessible contrast. </constraints> <format> Return the migration white paper as an artifact, then summarize the phase plan in one line each and flag the riskiest step. </format>

You are a research analyst who turns findings into a credible, well-structured research white paper. <context> I have research findings and need them shaped into a formal research-backed white paper, built as one self-contained HTML document with inline CSS, a title page, and styled charts/tables, previewable instantly as an artifact. </context> <inputs> - Research question: [WHAT WE STUDIED] - Method and sample: [HOW, HOW MANY, WHEN] - Key findings: [3-6 RESULTS WITH NUMBERS] - What the findings mean: [INTERPRETATION] - Audience: [WHO WILL USE THIS] - Brand and CTA: [WHO WE ARE, NEXT STEP] </inputs> <task> Write a 1,800-2,600 word research white paper with: a title page, an abstract, a methodology section stating method and sample honestly, a findings section with one subsection per result plus a styled data callout or simple bar representation for each, a discussion section interpreting the results, a limitations section, practical implications, and a conclusion with CTA. Present only the numbers I provide; mark any missing figure as [DATA NEEDED]. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Never invent statistics; use only my figures and label gaps clearly. - Use clean tables and CSS bar callouts for data; state limitations honestly; accessible contrast. </constraints> <format> Return the research white paper as an artifact, then list any place it needed a number you did not supply. </format>

You are a market research lead who writes annual State-of-the-Industry trend reports. <context> I need a polished industry-trends report that reads like a flagship annual study, built as one self-contained HTML document with inline CSS, a title page, a contents list, and styled charts, previewable instantly as an artifact. </context> <inputs> - Industry and report title: [E.G. STATE OF X 2026] - Data sources: [SURVEY, MARKET DATA, INTERNAL DATA] - Headline numbers: [KEY STATS WITH VALUES] - The major trends: [3-6 THEMES] - Audience: [WHO READS THIS REPORT] - Sponsor / brand and CTA: [WHO WE ARE, NEXT STEP] </inputs> <task> Write a 2,000-3,000 word industry-trends report with: a title page, a table of contents, an executive summary with the headline numbers in stat callouts, a methodology note, one chapter per major trend each containing the data, the interpretation, and a quoted-expert placeholder, a "key takeaways" recap, a predictions section, and a sponsor CTA. Use only the figures I provide and mark gaps as [DATA NEEDED]. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Big stat callouts and clean tables/CSS bars for charts; do not invent numbers. - Magazine-grade structure with anchored sections and contents links; accessible contrast. </constraints> <format> Return the trends report as an artifact, then list the charts it references and the stats still marked [DATA NEEDED]. </format>

You are a data storyteller who turns survey results into a shareable white paper. <context> I ran a survey and need the results packaged as a clear, visual white paper, built as one self-contained HTML document with inline CSS, a title page, and styled result blocks, previewable instantly as an artifact. </context> <inputs> - Survey topic and goal: [WHAT WE WANTED TO LEARN] - Respondent profile and count: [WHO, HOW MANY] - Key result percentages: [QUESTION: RESULT PAIRS] - The most surprising finding: [THE HEADLINE] - Audience: [WHO SHOULD READ THIS] - Brand and CTA: [WHO WE ARE, NEXT STEP] </inputs> <task> Write a 1,500-2,200 word survey white paper with: a title page, a respondent-profile box, an at-a-glance key-findings panel with the top stats as callouts, a section per major question showing the result, a styled bar/percentage visual, and a one-line interpretation, a "what surprised us" highlight, a recommendations section, and a CTA. Use only my percentages and mark any missing one as [DATA NEEDED]. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Render results as CSS percentage bars and stat callouts; never invent figures. - Skimmable, visual layout; respondent count visible up front; accessible contrast. </constraints> <format> Return the survey white paper as an artifact, then suggest the single chart that should become the social-share image. </format>

You are an analyst who writes rigorous, fair benchmark and comparison reports. <context> I need a benchmark report that compares options on objective criteria, built as one self-contained HTML document with inline CSS, a title page, and a clean comparison table, previewable instantly as an artifact. </context> <inputs> - What is being compared: [OPTIONS / APPROACHES / VENDORS] - The evaluation criteria: [4-8 DIMENSIONS] - The scores or data per option: [VALUES OR RATINGS] - The methodology: [HOW SCORED] - Audience and decision they face: [WHO, WHAT CHOICE] - Any disclosure: [SPONSORSHIP OR NEUTRALITY NOTE] </inputs> <task> Write a 1,600-2,300 word benchmark report with: a title page, an executive summary of the verdict, a methodology section stating criteria and scoring honestly, a master comparison table scoring each option across the criteria, a section per criterion explaining the differences, a "best for" recommendation matrix mapping use cases to options, a limitations/disclosure note, and a conclusion. Be fair and transparent; use only my data. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Build a readable scored comparison table; disclose methodology and any bias; do not invent scores. - Provide a "best for X" matrix, not a single forced winner; accessible contrast. </constraints> <format> Return the benchmark report as an artifact, then note where the methodology is weakest and how a skeptic might contest the scores. </format>

You are an academic-style writer who synthesizes existing research into a literature-review white paper. <context> I need a literature-review white paper that synthesizes what is known about a topic into a structured overview, built as one self-contained HTML document with inline CSS, a title page, and a references list, previewable instantly as an artifact. </context> <inputs> - The topic / question: [WHAT THE REVIEW COVERS] - Key themes or schools of thought: [3-6 STRANDS] - Sources I have: [STUDIES, REPORTS, AUTHORS] - Where the field agrees and disagrees: [CONSENSUS AND DEBATE] - The gap or open question: [WHAT IS UNRESOLVED] - Audience: [WHO WILL USE THIS] </inputs> <task> Write a 1,700-2,500 word literature-review white paper with: a title page, an introduction framing the question, a thematic structure with one section per theme synthesizing the sources I provide, a section on points of consensus and ongoing debate, a clearly stated research gap, implications, and a references list using only the sources I supply. Synthesize across sources rather than summarizing each in isolation; mark any citation I must add as [SOURCE NEEDED]. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Use only the sources I provide; never fabricate citations or findings. - Organize by theme, not by paper; clean references list; accessible contrast. </constraints> <format> Return the literature review as an artifact, then list any claim that still needs a citation marked [SOURCE NEEDED]. </format>

You are a chief-of-staff writer who distills complex material into a tight executive brief. <context> I need a one-to-two page executive brief that gives leaders the decision and the reasoning fast, built as one self-contained HTML document with inline CSS and a clean header, previewable instantly as an artifact. </context> <inputs> - The topic or decision: [WHAT THIS IS ABOUT] - The recommendation: [WHAT YOU WANT THEM TO DO] - The key reasons: [2-4 SUPPORTING POINTS] - The risks or trade-offs: [WHAT COULD GO WRONG] - Supporting data: [KEY NUMBERS] - Audience and decision needed: [WHO, WHAT THEY DECIDE] </inputs> <task> Write a 600-900 word executive brief with: a header (title, date, prepared-for/by line), a bottom-line-up-front recommendation in bold, a context paragraph, a reasons section with 2-4 crisp supporting points each in a line or two, a risks/trade-offs box, a key-data callout, and a single clear ask or next step. Lead with the answer, then justify it. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Bottom-line-up-front; ruthlessly concise, no padding; scannable in under two minutes. - One data callout and one risks box; accessible contrast. </constraints> <format> Return the executive brief as an artifact, then state the single sentence a busy executive would remember. </format>

You are an executive communications specialist who prepares board-ready one-pagers. <context> I need a single-page board document that updates the board on a topic and frames any decision, built as one self-contained HTML document with inline CSS and a structured layout, previewable instantly as an artifact. </context> <inputs> - The subject: [WHAT THE BOARD NEEDS TO KNOW] - Status / progress: [WHERE THINGS STAND] - Key metrics: [THE NUMBERS THAT MATTER] - The decision or approval requested: [WHAT YOU NEED FROM THEM] - Risks and mitigations: [WHAT TO FLAG] - Period and presenter: [DATE, WHO] </inputs> <task> Write a one-page board document with: a clean header (subject, period, presenter), a one-line summary, a metrics strip with 3-5 KPIs as callouts, a short status narrative, a risks-and-mitigations table, a clearly boxed "decision requested" section, and a tight next-steps list. Keep it to a single printed page of dense, scannable information. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Fits one page; KPI callout strip and a two-column risk/mitigation table; no fluff. - The decision requested is visually unmissable; accessible contrast. </constraints> <format> Return the board one-pager as an artifact, then note which metric the board will fixate on and whether it is framed well. </format>

You are a policy advisor who writes neutral issue briefs that inform a decision. <context> I need an issue briefing memo that lays out a topic objectively so a decision-maker can act, built as one self-contained HTML document with inline CSS and a memo header, previewable instantly as an artifact. </context> <inputs> - The issue: [WHAT IS AT STAKE] - Background a reader needs: [CONTEXT] - The options on the table: [2-4 CHOICES] - Pros and cons of each: [TRADE-OFFS] - Relevant data or precedent: [EVIDENCE] - Decision-maker and timeframe: [WHO, BY WHEN] </inputs> <task> Write an 800-1,200 word briefing memo with: a memo header (to, from, date, re), a one-paragraph summary of the issue, a background section, an options section presenting each choice with balanced pros and cons in a comparison block, a key-considerations callout, and a recommendation or "decision points" close. Stay even-handed; present options fairly before any recommendation. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Neutral tone; each option gets a fair pros/cons treatment; clearly separate facts from recommendation. - Use a comparison block for the options; accessible contrast. </constraints> <format> Return the briefing memo as an artifact, then flag any place your own bias may have leaked into a supposedly neutral section. </format>

You are an editor who writes standalone executive summaries that make people read the full document. <context> I have a longer report or white paper and need a sharp standalone executive summary, built as one self-contained HTML document with inline CSS and a clean header, previewable instantly as an artifact. </context> <inputs> - The full document's topic: [WHAT IT COVERS] - The single most important conclusion: [THE TAKEAWAY] - The key supporting points: [3-5 POINTS] - The most compelling data: [KEY NUMBERS] - The recommended action: [WHAT THE READER SHOULD DO] - Audience: [WHO] </inputs> <task> Write a one-page standalone executive summary with: a title and subtitle, an opening that states the central conclusion immediately, a short "why it matters" line, a bulleted key-findings list with 3-5 points, a highlighted data callout, a recommended-action block, and a one-line pointer to the full document. Make it complete enough to act on alone, compelling enough to drive the full read. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Lead with the conclusion; every line earns its place; one data callout. - Reads in under 90 seconds; accessible contrast. </constraints> <format> Return the executive summary as an artifact, then state the hook line that should make a reader open the full report. </format>

You are a sales-enablement writer who turns a market insight into a brief reps can use in conversations. <context> I need a short insight brief that arms sales reps with a credible point of view to share with prospects, built as one self-contained HTML document with inline CSS and a clean header, previewable instantly as an artifact. </context> <inputs> - The insight or trend: [WHAT REPS SHOULD KNOW] - Why prospects should care: [THE RELEVANCE] - Supporting evidence: [STATS, EXAMPLES] - The implication for the buyer: [WHAT IT MEANS FOR THEM] - How it connects to our value: [SOFT BRIDGE, NOT A PITCH] - Talk-track or question reps can use: [CONVERSATION STARTER] </inputs> <task> Write a 700-1,000 word insight brief with: a header, a one-line insight statement, a "why this matters now" section with the evidence in a callout, an "implications for you" section framed around the buyer, a short bridge to our perspective without pitching, a suggested talk-track box with a question reps can open with, and a recap. Make it genuinely useful to a prospect, not a disguised ad. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Insight-first, value-second; the product bridge is soft and late; one evidence callout. - Include a usable talk-track box for reps; accessible contrast. </constraints> <format> Return the insight brief as an artifact, then suggest the one question a rep should lead the conversation with. </format>

You are a demand-generation strategist who writes premium gated white papers that justify an email exchange. <context> I need a high-value gated lead-magnet white paper plus its gate copy, built as one self-contained HTML document with inline CSS, a title page, and a download landing block, previewable instantly as an artifact. </context> <inputs> - The promise / title: [WHAT THE READER WILL LEARN] - The audience and their goal: [WHO, WHAT THEY WANT] - The substance inside: [FRAMEWORKS, DATA, STEPS] - Proof of expertise: [RESULTS, CREDENTIALS] - The offer after reading: [NEXT STEP / CTA] - Brand and tone: [WHO WE ARE, VOICE] </inputs> <task> Write a 1,600-2,400 word gated white paper with: a title page, an executive summary, three to four substantive chapters delivering genuinely useful frameworks and data callouts, a worked example, a practical checklist or template section the reader can act on, and a soft CTA chapter. Then add a separate landing-page block with the gate: a benefit-led headline, three bullets on what is inside, and a placeholder email form. Make the content good enough that the email feels like a fair trade. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - The white paper must deliver real value, not a teaser; include at least one usable checklist or template. - Keep the landing-gate block visually distinct from the paper itself; accessible contrast. </constraints> <format> Return the gated white paper and its landing block as an artifact, then explain why the value justifies the gate and what to test on the form. </format>

You are a content marketer who writes definitive, rank-worthy ultimate-guide white papers. <context> I need a comprehensive ultimate-guide white paper that becomes the reference on a topic, built as one self-contained HTML document with inline CSS, a title page, a table of contents, and anchored sections, previewable instantly as an artifact. </context> <inputs> - The topic: [WHAT THE GUIDE COVERS COMPLETELY] - Who it is for and their level: [BEGINNER / PRO] - The subtopics to cover: [LIST THE PARTS] - Practical takeaways per section: [WHAT THEY DO WITH IT] - Proof or examples I can use: [CASES, DATA] - Brand and CTA: [WHO WE ARE, NEXT STEP] </inputs> <task> Write a 2,200-3,200 word ultimate guide with: a title page, a clickable table of contents, an introduction on who it is for and what they will gain, one thorough chapter per subtopic each with explanation, a concrete example, and an actionable takeaway, a common-mistakes section, a quick-reference summary or checklist, an FAQ, and a CTA. Be genuinely comprehensive and practical, not padded. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Anchored contents links and clear chapter structure; every section ends with a usable takeaway. - Depth over word-count padding; one FAQ block; accessible contrast. </constraints> <format> Return the ultimate guide as an artifact, then list the chapters and which one is strongest for a standalone blog excerpt. </format>

You are a B2B content strategist who writes neutral-feeling buyer's guides that help and convert. <context> I need a buyer's guide white paper that helps someone choose the right solution in our category, built as one self-contained HTML document with inline CSS, a title page, and an evaluation checklist, previewable instantly as an artifact. </context> <inputs> - The category being evaluated: [WHAT THEY ARE BUYING] - The buyer and their context: [WHO, WHAT SITUATION] - The key evaluation criteria: [WHAT MATTERS WHEN CHOOSING] - Common pitfalls in buying: [MISTAKES TO AVOID] - Where we genuinely excel: [OUR STRENGTH, HONESTLY] - Brand and CTA: [WHO WE ARE, NEXT STEP] </inputs> <task> Write a 1,700-2,400 word buyer's guide with: a title page, an introduction on how to approach the decision, a section defining the must-have criteria, a vendor-neutral evaluation checklist the reader can score against, a common-pitfalls section, a section on questions to ask any provider, an honest "where different approaches fit" comparison, a soft section on our strengths, and a CTA. Stay genuinely helpful first. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Most of the guide must be useful regardless of vendor; the self-promotion is honest and late. - Include a scorable evaluation checklist; accessible contrast. </constraints> <format> Return the buyer's guide as an artifact, then point out where it becomes self-serving and whether that arrives too soon. </format>

You are a value-engineering writer who builds ROI and business-case white papers for budget holders. <context> I need an ROI white paper that helps a champion justify the investment internally, built as one self-contained HTML document with inline CSS, a title page, and a styled ROI model table, previewable instantly as an artifact. </context> <inputs> - The investment / solution: [WHAT THEY ARE BUYING INTO] - The costs it replaces or reduces: [CURRENT SPEND OR WASTE] - The value drivers: [TIME SAVED, REVENUE, RISK AVOIDED] - Sample numbers to model: [ASSUMPTIONS, RATES, VOLUMES] - The payback expectation: [TIMEFRAME] - Audience: [CFO, FINANCE, BUDGET OWNER] </inputs> <task> Write a 1,500-2,200 word ROI white paper with: a title page, an executive summary stating the headline return, a section framing the cost of the status quo, a value-drivers section, a transparent ROI model presented as a table with the assumptions I provide and the resulting payback and return callouts, a sensitivity note showing conservative vs optimistic cases, a risk-and-assumptions section, and a CTA. Use only my numbers and mark missing inputs as [ASSUMPTION NEEDED]. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Show the math transparently in a table; never invent financial figures; label every assumption. - Include conservative and optimistic scenarios; accessible contrast. </constraints> <format> Return the ROI white paper as an artifact, then summarize the headline return and flag the assumption the whole case hinges on. </format>

You are a lead-gen content designer who pairs a short white paper with an actionable checklist as one downloadable asset. <context> I need a combo lead magnet: a concise white paper plus a tear-off checklist, built as one self-contained HTML document with inline CSS, a title page, and a distinct checklist section, previewable instantly as an artifact. </context> <inputs> - The topic and outcome: [WHAT THE READER ACHIEVES] - Audience: [WHO IT HELPS] - The core method or framework: [THE APPROACH] - The steps that become the checklist: [ACTIONABLE ITEMS] - Proof or example: [CASE OR DATA] - Brand and CTA: [WHO WE ARE, NEXT STEP] </inputs> <task> Write a combo lead magnet (1,200-1,800 words) with: a title page, a short framing section on why the outcome matters, a concise explanation of the method with a worked example and one data callout, a clearly separated "your checklist" section formatted as printable checkbox items the reader can act on immediately, a tips-for-using-it note, and a CTA. The white paper sets up the why; the checklist delivers the how. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - The checklist must be genuinely actionable and visually distinct with real checkbox styling. - Keep prose tight; the asset's value is the checklist; accessible contrast. </constraints> <format> Return the combo lead magnet as an artifact, then suggest the headline that would make this the highest-converting download. </format>

You are a proposal writer who produces formal white papers for government and enterprise procurement. <context> I need a formal capabilities white paper suited to a government or enterprise RFP context, built as one self-contained HTML document with inline CSS, a title page, and a structured, compliant layout, previewable instantly as an artifact. </context> <inputs> - The requirement or problem the buyer has: [THEIR NEED] - Our capability and approach: [WHAT WE OFFER] - Relevant qualifications: [PAST PERFORMANCE, CERTIFICATIONS, COMPLIANCE] - Key differentiators: [WHY US] - Constraints to acknowledge: [BUDGET, TIMELINE, REGULATION] - Audience: [PROCUREMENT, EVALUATORS] </inputs> <task> Write a 1,800-2,500 word capabilities white paper with: a formal title page, an executive summary, an understanding-of-the-requirement section that proves you grasp their need, a technical approach section, a past-performance/qualifications section, a compliance-and-standards section, a risk-management section, and a clear point of contact. Use formal, precise, evaluator-friendly language. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Formal structure with numbered sections; demonstrate understanding before pitching capability. - Do not overstate qualifications; mark any unverified claim as [VERIFY]; accessible contrast. </constraints> <format> Return the capabilities white paper as an artifact, then note where an evaluator would deduct points and how to strengthen it. </format>

You are a regulated-industry writer who produces careful, claims-aware white papers for healthcare or finance audiences. <context> I need a white paper for a regulated industry that informs without overclaiming, built as one self-contained HTML document with inline CSS, a title page, and clear disclosure blocks, previewable instantly as an artifact. </context> <inputs> - The topic and clinical/financial context: [WHAT IT COVERS] - The audience: [CLINICIANS, ADMINISTRATORS, ADVISORS] - The evidence available: [STUDIES, DATA, GUIDELINES] - The claim I can responsibly make: [SUPPORTED ASSERTION] - Required disclaimers: [REGULATORY OR LEGAL NOTES] - Brand and contact: [WHO WE ARE, WHO TO ASK] </inputs> <task> Write a 1,600-2,300 word regulated-industry white paper with: a title page, a scope-and-disclaimer note up front, an executive summary, a background section grounded in the evidence I provide, an analysis section that states only supported claims, a section on considerations and limitations, an implications-for-practice section, and a contact close. Be conservative with claims; mark anything needing review as [COMPLIANCE REVIEW]. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Make no medical or financial claim beyond the evidence I supply; include the required disclaimers prominently. - Flag every assertion that needs compliance sign-off; accessible contrast. </constraints> <format> Return the regulated-industry white paper as an artifact, then list every claim marked [COMPLIANCE REVIEW] for legal to check. </format>

You are a sustainability communications writer who produces credible, greenwash-free ESG white papers. <context> I need an ESG or sustainability white paper that reports progress and commitments honestly, built as one self-contained HTML document with inline CSS, a title page, and styled metric callouts, previewable instantly as an artifact. </context> <inputs> - The focus area: [E.G. EMISSIONS, SUPPLY CHAIN, GOVERNANCE] - Our commitments and targets: [GOALS WITH DATES] - Progress and metrics so far: [ACTUAL NUMBERS] - Initiatives underway: [WHAT WE ARE DOING] - Honest gaps or challenges: [WHERE WE FALL SHORT] - Audience: [INVESTORS, CUSTOMERS, REGULATORS] </inputs> <task> Write a 1,600-2,300 word ESG white paper with: a title page, a CEO-style commitment statement, an executive summary, a targets-and-progress section with metric callouts using my real numbers, an initiatives section, an honest "where we have further to go" section, a governance-and-methodology note, and a forward commitments close. Substantiate every claim; mark missing figures as [DATA NEEDED] and avoid vague green language. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Use only my metrics; include a methodology note; acknowledge gaps to avoid greenwashing. - Concrete targets with dates, not vague aspirations; accessible contrast. </constraints> <format> Return the ESG white paper as an artifact, then flag any statement that could read as greenwashing and how to make it defensible. </format>

You are a customer-marketing writer who builds white papers anchored on a real customer outcome. <context> I need a case-led white paper that uses a customer's journey to teach a broader lesson, built as one self-contained HTML document with inline CSS, a title page, and a results callout panel, previewable instantly as an artifact. </context> <inputs> - The customer and their situation: [WHO, WHAT THEY FACED] - The challenge in detail: [THE PROBLEM] - The approach they took: [WHAT THEY DID] - The results with numbers: [OUTCOMES] - The transferable lesson: [WHAT OTHERS CAN LEARN] - Brand and CTA: [WHO WE ARE, NEXT STEP] </inputs> <task> Write a 1,500-2,200 word case-led white paper with: a title page, an executive summary with the headline result, a section setting up the customer's challenge, an approach section explaining what they did and why, a results section with a prominent metrics callout panel, a "lessons for others" section that generalizes beyond this one customer, a short methodology/quote placeholder, and a CTA. Make it teach, not just brag. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Use only the customer numbers I provide; keep the lesson generalizable, not a pure testimonial. - Prominent results callout panel and a quote placeholder; accessible contrast. </constraints> <format> Return the case-led white paper as an artifact, then state the transferable lesson and whether it stands without the brand mention. </format>

You are an explanatory writer who makes a complex concept genuinely understandable in a white paper. <context> I need an educational white paper that explains how something works clearly enough to build trust and authority, built as one self-contained HTML document with inline CSS, a title page, and described diagrams, previewable instantly as an artifact. </context> <inputs> - The concept to explain: [WHAT IT IS] - Why the reader should understand it: [THE RELEVANCE] - The core mechanism in plain terms: [HOW IT WORKS] - Common misconceptions: [WHAT PEOPLE GET WRONG] - A useful analogy or example: [TO ANCHOR IT] - Audience and their level: [WHO, HOW EXPERT] </inputs> <task> Write a 1,500-2,200 word educational white paper with: a title page, an introduction on why this matters to the reader, a plain-language explanation of the concept, a described step-by-step diagram of how it works, a section debunking common misconceptions, a concrete worked example or analogy, a "what this means for you" section, and a further-reading or CTA close. Prioritize clarity over completeness; teach like a great mentor. </task> <constraints> - One self-contained, print-friendly HTML file; Google Fonts only. - Plain language calibrated to the audience; render the process as a labeled CSS diagram/flow. - One anchoring analogy or worked example; accessible contrast; no jargon without explanation. </constraints> <format> Return the educational white paper as an artifact, then name the diagram it relies on and the misconception it corrects best. </format>