Business Strategy & ROIRole-Specific

Using Claude for writing and editing

In brief

Claude is most useful for writing not as a ghostwriter, but as a collaborator. The right workflow produces output that sounds like you — and is better than what you would have written alone.

7 min read·AI Augmentation

Contents

♡Sign in to save

Most people use Claude wrong for writing. They describe what they want and expect it to produce a finished piece. The result feels generic, loses their voice, and needs so much editing it barely saved time.

The better approach: use Claude as a thinking partner and first-draft engine, then edit into your own voice. This produces work that is genuinely better than what you would have written alone — while still sounding like you.

Where Claude helps most

First drafts when you are starting from nothing. The blank page problem is real. A rough Claude draft gives you something to react to, which is far easier than generating from scratch. Even if you rewrite most of it, you have a structure and the key points laid out.

Editing and tightening. Paste in a draft and ask Claude to make it more direct, cut it by 30%, or fix the structure. It is surprisingly good at identifying where pieces are too wordy or where the argument is muddled.

Matching a specific tone. Give Claude an example of writing you like and ask it to write in that style. Or describe the tone: "write like a senior director briefing executives — direct, no unnecessary context."

Adapting one piece into many formats. Long-form article → LinkedIn post → email newsletter → slide deck summary. This is mechanical work. Claude handles it well once you have the source material.

Research synthesis. Paste in several sources and ask Claude to synthesize the key points into a coherent summary with your editorial framing. This is not plagiarism — you are using it to structure and organize information you sourced yourself.

A workflow that actually works

Here is a pattern that produces good output consistently:

Step 1: Brief Claude properly.
Tell it: who the audience is, what you want them to think or do after reading, the format, the tone, and any constraints. The more context, the better the first draft.

Step 2: Get a rough draft.
Do not overthink the prompt. You are looking for raw material, not a finished piece. Even a mediocre first draft gives you structure to work with.

Step 3: Edit into your voice.
This is where your judgment matters. Cut what does not sound like you. Add your specific examples, opinions, and experiences. Claude cannot know what you know — only you can.

Step 4: Use Claude for refinements.
Paste in your revised draft and ask for specific improvements: "tighten the conclusion," "this paragraph is unclear — rewrite it," "does the structure make sense?"

Step 5: Final read yourself.
Always do a final read. Claude does not know your audience the way you do, and it can miss the one sentence that will land wrong with a specific reader.

What to keep in your own voice

Claude is better than most people at producing grammatically clean, coherent text. But it does not know:

Your specific examples and stories
Your opinions and the reasoning behind them
The precise tone of your relationship with your reader
What your audience has already heard and does not need explained

These are what make writing interesting. Claude can structure and draft; you provide the substance.

Practical prompts that work

For a first draft:
"Write a [type of piece] for [audience]. The main point is [your point]. Tone should be [description]. Length: [rough word count or format]. Here are the key things to include: [your list]."

For editing:
"Edit this for clarity and directness. Cut anything that is not essential. Keep my voice — do not make it sound more formal."

For tone matching:
"Here is an example of writing I like: [paste example]. Write [new piece] in this style."

For adapting:
"Turn this [long piece] into a [LinkedIn post / email / set of slides]. Keep the main argument. Match this length: [target]."

The test for whether Claude improved your writing

The simplest test: does the final output sound like you at your best, or does it sound like something a committee wrote? If it sounds like you, the process worked. If it does not, you edited too little, or you asked Claude to do too much without enough context.

Writing that sounds like Claude — hedged, corporate, structured to a fault — is worse than writing that sounds a bit rough but genuine. Always edit toward your own voice.