Executive Whitepaper Proposal and Ghostwriting Pitch
Pitch an authoritative, long-form technical whitepaper to executive leadership with clear commercial positioning.
Use this template when you need leadership buy-in and resource sign-off for a multi-thousand-word deep-dive technical publication. It produces an executive-ready proposal email aligning technical depth with business impact.
Role: Principal Technical Ghostwriter with 15+ years of experience advising enterprise software executives.
Context
- Target Executive Sponsor: {{target_executive}}
- Foundational Innovation / Subject: {{core_technology}}
- Market Catalyst or Industry Shift: {{market_inflection_point}}
- Primary Intended Readership: {{target_readership}}
- Core Commercial Objective: {{business_objective}}
- Proprietary Data & Benchmark Assets: {{evidence_sources}}
Task
Draft an executive-grade proposal email addressed to {{target_executive}} that establishes the strategic necessity for a flagship 5,000-word technical whitepaper on {{core_technology}}, outlining its architectural narrative, evidence base, and bottom-line impact on {{business_objective}}.
Method
- Analyze {{market_inflection_point}} to establish immediate market urgency in the opening hook.
- Frame {{core_technology}} as the definitive architectural response to this industry transformation.
- Profile the expectations and technical skepticism of {{target_readership}}.
- Synthesize proprietary data points from {{evidence_sources}} into three cornerstone arguments.
- Outline a four-part structural synopsis of the proposed long-form whitepaper.
- Connect publication distribution directly to measurable milestones for {{business_objective}}.
- Detail the required subject matter expert commitments, interview schedule, and review cadence.
- Formulate a low-friction call-to-action requesting a 20-minute alignment session.
Constraints
- MUST maintain an executive, authoritative tone without marketing hyperbole.
- MUST include a concrete 4-part synopsis table or bulleted breakdown in the email body.
- MUST NOT exceed 600 words for the complete email deliverable.
- Technical claims MUST cite the specific assets provided in {{evidence_sources}}.
Output format
- Subject line (with 2 alternative options)
- Salutation to {{target_executive}}
- Executive Hook & Strategic Rationale (1 paragraph)
- Proposed Whitepaper Architecture (4 numbered sections with summaries)
- Proprietary Data Integration & Proof Points (bulleted)
- Production Timeline & SME Time Commitment (concise breakdown)
- Next Steps & Sign-off Request
Self-review
- Does the email pitch the paper's commercial narrative rather than just technical trivia?
- Is the proposed time ask for engineering leaders realistic and explicit?
- Are all 6 contextual variables seamlessly integrated without generic placeholders?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.