---
name: ai-powered-thought-leadership-article-generator
description: >-
  A long-form thought leadership article draft for sales leaders on the topic you choose, with trends, challenges, and practical advice to edit and publish. Adapted from Daniel Disney.
  Task type: Create. Built for Sales, Marketing.
  Use when the request sounds like "Thought Leadership Article for Sales Leaders".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Marketing and Demand
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/ai-powered-thought-leadership-article-generator
---

# Thought Leadership Article for Sales Leaders

A long-form thought leadership article draft for sales leaders on the topic you choose, with trends, challenges, and practical advice to edit and publish. Adapted from Daniel Disney.

One job only: a long-form thought leadership article draft for sales leaders on the topic you choose, with trends, challenges, and practical advice to edit and publish. Anything outside that job belongs in another file in the Marketing and Demand suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- year
- topic

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You will be writing a thought leadership article of 3,000+ words on an important topic for sales leaders in {$YEAR}. The topic is: {$TOPIC}

Here are the steps to follow:

1. First, provide some context in 2-3 paragraphs on why this topic is highly relevant and important for sales leaders to understand in {$YEAR}. Explain the key trends, challenges or opportunities related to this topic that sales leaders will be facing.

2. Next, outline the key points and high-level structure you plan to cover in the article. List out the main sections and subsections in a nested outline format, with 1-2 sentence descriptions summarizing what each section will cover.

3. Once you have outlined the structure, write out the full article content inside <Article> </Article> tags. Incorporate the key points from your outline, expanding on each one with deep insights, examples, data, quotes from experts, and actionable advice for sales leaders.

Some important guidelines:

- Write in a professional, authoritative, thought-provoking style suited for an executive audience
- Conduct additional research as needed to substantiate key points with facts, statistics, and credible sources
- Use clear section headings and formatting to organize the content logically
- Provide specific, practical recommendations that sales leaders can implement
- Aim for a total word count of 3,000-4,000 words for the full article
- Ask clarifying questions before you begin writing to make sure you understand the topic and focus and if you need to do sections at a time to get to the 3000 words please do so and check in with me as you do. Focus on High quality, spartan conversational and professional tone with no yapping or jargon and varying sentence structure and length with no em dashes.

Begin by providing the context on the importance of the topic, then outline the key points and structure, before writing out the full article content. Let me know if you need any clarification on the instructions.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/ai-powered-thought-leadership-article-generator
- Suite: https://www.therevenueaireport.com/agent-skills/suites/marketing-and-demand
- Publication: The Revenue AI Report, https://www.therevenueaireport.com