Your best thinking is probably trapped in a notes app. Half-finished bullets from a coaching session, a line you scribbled after a client breakthrough, a voice memo you never transcribed. The ideas are good. The problem is the gap between raw notes and something you’d actually publish.

This prompt closes that gap. It’s built for thought leadership for coaches who have the insight but not the hours to shape it. You hand the AI your messy notes and your core argument; it returns a structured, human-sounding essay that makes one clear point and uses your real examples as evidence. And by the end of this page you’ll understand the prompting principles that make it work, so your next draft is sharper too.

When to use this

• You have pages of session notes or voice-memo transcripts and a point you want to make, but no draft.
• You want to publish on LinkedIn, Substack, Medium, or your own blog without it sounding AI-generated.
• You keep starting essays and abandoning them at paragraph two.
• You want to turn a recurring theme you see across clients into a credibility-building piece.
• You’re repurposing a talk, a podcast riff, or a newsletter into a longer signature essay.

The prompt

Copy this whole block into ChatGPT, Claude, or Gemini:

You are an expert essay editor and ghostwriter who turns a coach's raw, messy notes into a polished thought-leadership essay that reads like it came from a credible expert.

Before writing, ask me up to 3 clarifying questions if anything below is unclear or missing. Otherwise, proceed.

CONTEXT
- My coaching niche: {{NICHE}}
- Who I want this essay to reach: {{IDEAL_READER}}
- The core argument or belief I want to make: {{CORE_ARGUMENT}}
- My raw notes (bullet points, half-sentences, client moments, anything): {{RAW_NOTES}}
- Where this will be published: {{PUBLICATION}}
- My tone: {{TONE}}
- The action I want the reader to take at the end: {{CTA}}

TASK
Turn my raw notes into ONE finished thought-leadership essay that:
1. Opens with a specific, concrete hook (a scene, a question, or a sharp claim) - not a generic windup.
2. Makes ONE clear argument: {{CORE_ARGUMENT}}. Every section must support it.
3. Organizes my messy notes into a logical flow with 3-5 short sections, each with a plain-language subheading.
4. Uses my real examples and client moments from the notes as evidence. Do not invent new ones.
5. Sounds like a human expert in my tone. Short paragraphs. No corporate buzzwords, no 'in today's fast-paced world'.
6. Ends with a takeaway the reader can act on, then a soft call to action: {{CTA}}.

CONSTRAINTS
- 700-1000 words.
- Do not invent statistics, client results, or quotes that are not in my notes.
- If a claim in my notes needs a supporting detail I did not give you, flag it in [brackets] rather than making it up.
- Keep subheadings concrete, not clever.

After the essay, give me:
- A 1-line summary I can use as the standfirst/excerpt.
- 3 alternative titles.
- A note on any [bracketed] gaps I should fill before publishing.

How to customize it

Replace the seven {{VARIABLES}} before you send it:

The most important box is {{RAW_NOTES}}. Don’t tidy it first. The model’s job is to do the tidying; the raw texture is where your real voice and your best examples live.

See it in action (full example)

Here is the exact prompt, filled in for a career coach. This is the whole input, nothing hidden:

You are an expert essay editor and ghostwriter who turns a coach's raw, messy notes into a polished thought-leadership essay that reads like it came from a credible expert.

Before writing, ask me up to 3 clarifying questions if anything below is unclear or missing. Otherwise, proceed.

CONTEXT
- My coaching niche: career coaching for mid-career women in tech
- Who I want this essay to reach: a senior engineer who keeps getting nudged toward management but isn't sure she wants it
- The core argument or belief I want to make: chasing the next title is the wrong goal; choosing which problems you want to own is the right one
- My raw notes (bullet points, half-sentences, client moments, anything): - client "Maya", staff engineer, got offered EM role, panicked, came to me - she kept saying "I should want this" - asked her: what did you actually enjoy this quarter? answer = the gnarly migration nobody else would touch - the title ladder is a default, not a decision - most of my clients optimize for the next rung without asking what's on it - "owning problems" framing landed for her - she turned down EM, negotiated a principal track instead, now happier - my own story: I took a director role I hated for 2 years bc it was "the path" - the question that cracks it open: what problems do you want to be the person people bring? - warning: this is not anti-management, management is a great choice IF the problems excite you
- Where this will be published: my LinkedIn and my Substack
- My tone: direct, warm, a little contrarian
- The action I want the reader to take at the end: reply and tell me the problem they actually want to own

TASK
Turn my raw notes into ONE finished thought-leadership essay that:
1. Opens with a specific, concrete hook (a scene, a question, or a sharp claim) - not a generic windup.
2. Makes ONE clear argument: chasing the next title is the wrong goal; choosing which problems you want to own is the right one. Every section must support it.
3. Organizes my messy notes into a logical flow with 3-5 short sections, each with a plain-language subheading.
4. Uses my real examples and client moments from the notes as evidence. Do not invent new ones.
5. Sounds like a human expert in my tone. Short paragraphs. No corporate buzzwords, no 'in today's fast-paced world'.
6. Ends with a takeaway the reader can act on, then a soft call to action: reply and tell me the problem they actually want to own.

CONSTRAINTS
- 700-1000 words.
- Do not invent statistics, client results, or quotes that are not in my notes.
- If a claim in my notes needs a supporting detail I did not give you, flag it in [brackets] rather than making it up.
- Keep subheadings concrete, not clever.

After the essay, give me:
- A 1-line summary I can use as the standfirst/excerpt.
- 3 alternative titles.
- A note on any [bracketed] gaps I should fill before publishing.

And here is the complete output the model returns:

Stop Climbing the Ladder. Start Choosing Your Problems.

A staff engineer I’ll call Maya sat across from me and said the most honest thing I’d heard all week: “I should want this.”

She’d just been offered an engineering manager role. By every visible measure, she should have been thrilled. More scope, more money, the next rung. And yet she’d booked an emergency session because the offer made her stomach drop.

“I should want this” is not the same sentence as “I want this.” Most of the careers I see stall in that exact gap.

The ladder is a default, not a decision

Here’s what almost nobody says out loud: the title ladder is the path of least resistance. It’s pre-built. Someone else decided the rungs, the order, and what counts as “up.” When you climb it, you’re not making a choice so much as accepting a default.

Most of my clients optimize for the next rung without ever asking what’s actually on it. They want the promotion the way you want the next level in a video game – because it’s there, and because stopping feels like failing.

But a rung isn’t a reason. “Manager” is a title. It is not a description of how you’ll spend your Tuesday.

The question that changes the conversation

So I didn’t ask Maya whether she wanted to be a manager. I asked her a different question: what did you actually enjoy this quarter?

She didn’t hesitate. It was the gnarly data migration nobody else would touch – the messy, high-stakes one with no clean answer. She’d loved it.

That told us everything. Maya doesn’t light up running one-on-ones and managing a roadmap. She lights up owning hard technical problems other people avoid. The EM role would have moved her away from the exact work that energizes her.

The better question isn’t “what’s the next title?” It’s this: what problems do you want to be the person people bring you?

Answer that, and the title takes care of itself.

What Maya did instead

Maya turned down the EM offer. Instead, she negotiated onto a principal engineering track – one built around owning the gnarliest technical problems in the org. Same seniority. Completely different daily life.

She’s happier. Not because she “won” a title, but because she chose the problems she wanted to own and then found the role that let her own them. The title followed the work, instead of the work following the title.

I learned this the slow, expensive way

I’m not preaching from theory here. I once took a director role I hated and kept for two years – purely because it was “the path.” It was the right rung and the wrong life. Two years is a long time to spend climbing toward something you never wanted to stand on.

That’s the cost of treating the ladder as the goal: you can be promoted away from everything you’re good at and into a job you’d never have chosen on its own.

To be clear: this isn’t anti-management

Management is a genuinely great choice – if the problems excite you. Coaching a team, untangling people dynamics, building something through others: for the right person, that’s the work, not a detour from it.

The point isn’t “don’t be a manager.” The point is: don’t take any role, IC or management, because it’s the next rung. Take it because the problems it puts in front of you are problems you actually want to spend your days on.

Your move

Before you say yes to the next title, answer one question on paper: what problems do you want to be the person people bring you?

Then look at the role on the table and ask whether it brings you more of those problems or fewer. If it’s fewer, no title is worth it.

Reply and tell me: what’s the problem you actually want to own? I read every response.

---

Standfirst / excerpt: Chasing the next title is a default, not a decision – here’s the better question to ask before you say yes.

3 alternative titles: 1. “I Should Want This” Is Not the Same as “I Want This” 2. The Promotion Trap: Why Your Next Title Might Be the Wrong Goal 3. Choose Your Problems, Not Your Rung

Gaps to fill before publishing: Your notes didn’t mention how long Maya had been a staff engineer or how the principal-track negotiation actually went – adding one concrete detail there would make the turnaround more credible. Everything else is drawn directly from your notes; no invented results.

That’s a publish-ready draft from a pile of bullets. A few minutes of personal edits and it’s live.

Why this works

Four prompting principles are doing the heavy lifting. Learn them and every draft you generate gets better:

1. Role priming. The opening line (“You are an expert essay editor and ghostwriter…”) tells the model which slice of its training to draw from. “Clean up my notes” pulls from the bland average of the web; “act as an expert essay ghostwriter” pulls from the good stuff. Always assign a role before you assign a task.
2. Specificity in, specificity out. The model can only be as concrete as your input. This is why {{RAW_NOTES}} and {{CORE_ARGUMENT}} matter most: the Maya story, the migration detail, the director-role confession – those specifics are what make the essay sound like you and not like anyone. Vague notes produce a vague essay. The output is capped by the quality of what you feed in.
3. Constraints are quality control. The numbered rules and the “do not invent statistics or quotes” line aren’t decoration – each one removes a common failure mode. The single most valuable constraint is the bracket rule: instead of confidently fabricating a detail to fill a gap, the model flags it in [brackets] for you. That one instruction is the difference between a draft you trust and one you have to fact-check line by line.
4. Ask before you guess. The “ask me up to 3 clarifying questions first” line lets the model close gaps by asking rather than inventing. It’s the biggest single fix for generic AI writing: a model that asks “which client moment should anchor this?” writes a far better essay than one that quietly makes something up.

Do this now

1. Copy the prompt above into ChatGPT or Claude.
2. Open your notes app or session notes and paste the raw mess straight into {{RAW_NOTES}} – don’t clean it first.
3. Fill in your niche, reader, core argument, publication, tone, and CTA.
4. Send it. Answer any clarifying questions honestly, then edit the draft in your own voice and publish it this week.

Pro tips

• Feed it more, not less. A long, messy notes dump beats three tidy bullets every time. The texture is the evidence.
• Defend the one argument. If you can’t state your {{CORE_ARGUMENT}} in a single sentence, the essay won’t hold together. Sharpen it first.
• Always check the [brackets]. The gaps it flags are exactly the spots where a lazy writer would have faked it. Fill them with real detail and your credibility climbs.
• Run it twice with two arguments. Sometimes the same notes support a sharper, more contrarian point than your first instinct. Generate both and keep the braver one.

Related

• Long-Form Content Engine: A Reusable System for Coaches Who Want to Publish Weekly
• Write a 2,000-Word SEO Pillar Article That Positions Coaches as Authorities
• Content Repurposing Machine: One Pillar Into 20 Assets for Coaches
• Coaching Session Note-Taker & Theme Tracker (Custom GPT)