B2B AI DirectoryB2B AI Directory
White Paperspro

White papers

Technical evaluator white paper from product documentation and SME interviews

Create a technically credible paper for architects, engineers, security, IT, or operations evaluators using verified documentation and SME evidence.

Output
white paper package
Inputs
9 required
Prompt depth
766 words

Copy-paste prompt

Replace the bracketed inputs with your real material.

You are a senior B2B research editor and white paper strategist. Produce a practitioner-ready deliverable for: Technical evaluator white paper from product documentation and SME interviews.

Objective
Create a technically credible paper for architects, engineers, security, IT, or operations evaluators using verified documentation and SME evidence.

Required practitioner depth
The reader needs architecture, constraints, deployment, tradeoffs, and validation. The work enforces terminology consistency and separates supported capability from roadmap or assumption.
Do not collapse this assignment into a generic summary, brainstorm, or list of...

[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 and reader decision
  • Point of view
  • Source pack
  • Methodology and evidence rules
  • Product context
  • Format and distribution
  • Editorial constraints
  • Task-specific evidence
  • Transcripts and notes

What you receive

  • Primary deliverable that fully executes this job: Create a technically credible paper for architects, engineers, security, IT, or operations evaluators using verified documentation and SME evidence.
  • Practitioner-depth requirements: The reader needs architecture, constraints, deployment, tradeoffs, and validation. The work enforces terminology consistency and separates supported capability from roadmap or assumption.
  • Claim-level evidence ledger with source, strength, limitation, and citation status.
  • Reader-centered thesis, methodology, outline, framework, visual, and activation package.
  • Red-team findings for claims, originality, methodology, usefulness, and unsupported promotion.

Quality checks

  • Do not invent citations, statistics, customer evidence, survey findings, or methodological certainty.
  • Mark VERIFIED, PARTIAL, HYPOTHESIS, CONFLICT, and SOURCE REQUIRED clearly.
  • Keep the paper useful to a reader who never buys the product.
  • Ensure every chart, claim, and conclusion traces to evidence and its limitations.
  • Missing or conflicting inputs are surfaced rather than silently resolved.
  • Every material recommendation has evidence, confidence, owner, and a validation or reversal condition.