Writing & strategy samples

How I think, shown in full.

Five pieces, in full. The first is an essay on how I review AI drafts, written from the workflow I use every day. The four after it are spec, built for a hypothetical brand to show method: the plan, the post, the sequence, and the briefs I'd hand a writer. The real client programs, with real numbers, are in case studies.

Essay How I work

The first draft always reads finished

The three-pass review I run on every AI draft, and what it catches.

EssaySeptember 2026 · Written from the workflow I built and use daily

At WB Games Boston I wrote launch email for Lord of the Rings Online and Dungeons & Dragons Online. The job's core mechanism was catching copy promising something beyond the game's reality. A sentence would drift through one too many people in different parts of marketing and production, and what started as a clear product description would become a grand abstracted promise we couldn't quite deliver.

Where the drafts break

A bad forgery gets stopped at the counter. A good one? It can circulate for years. The cost hits the center of whoever holds that forgery when an authority finally verifies its authenticity.

AI drafts fail by sounding right. It just takes a while after you hit publish.

A model will write “cuts research time per prospect from 20 to 2 minutes” because that sentence has the shape of a claim a buyer responds to, and shape is what AI is good at. The problem is that shape tends to be the same one over and over and over. It fits a true number and a made-up one equally well.

The EBU and the BBC had journalists at 22 public broadcasters grade more than 3,000 AI answers about the news. 45% carried at least one significant issue, and 20% had major accuracy problems including invented details. And that's the easy version of the job. The model had the article sitting right there.

The draft also arrives with evened out paragraphs, like a wax cake, with a confident topic sentence at the head of every section. Those top-level sentences used to mean somebody spent time, effort, and mental focus. Now they cost little to nothing.

Why the model can't check itself

Ask the model to check its own claims. It'll tell you they're fine.

Somebody actually tested this.

Language models “struggle to self-correct their responses without external feedback, and at times, their performance even degrades after self-correction.”
Huang et al., Google DeepMind and the University of Illinois · ICLR 2024

The model has no way of knowing whether a claim is true. Ask it to grade its own work and you get a second confident answer, not a check.

Somebody has to walk in with what the model doesn't have: the source document, the pricing page, the product philosophy, the emotional center of audience knowledge.

Before I prompt

More than half the work happens before a draft. I ask myself: Who is this for? What does it have to do? I'll gather sources. I'll search for the product's limits. This typically means features hiding behind a higher pricing tier and features where the product is very weak. Then I tell the model to flag what's missing instead of filling the gap.

That last instruction helps, but it's not enough. A model told to flag gaps will still write a confident sentence followed by another sentence telling you why that previous sentence is so important.

What I check, and in what order

The review pass

  1. Pass 1 · Check the evidence

    Open the sources. Check whether the claims hold up. A number like 20 to 2 minutes usually traces back to one customer on one call. One customer's result isn't what everyone should expect, so I narrow the claim to what the evidence actually supports, or I cut it.

  2. Pass 2 · Check the promise

    A promise has to describe what the product actually does, even if that promise is adorned with the wings of high emotion.

  3. Pass 3 · Check the claim, then the prose

    Do the facts support the claim? Have I left out anything the reader needs? Then rhythm and specificity, including whether a competitor could use the same sentence unchanged. All this helps rank what words get higher priority, what becomes a header, and what words and even whole paragraphs get cut.

Claims come first: removing one will often change everything around it.

Overclaiming is the obvious failure; hedging is the quiet one. “Can help reduce X” can't be proven wrong, which means it isn't really a claim, and readers price it that way. If the evidence supports “does,” then write “does.” The sentence gets shorter, its promise gets stronger, and now it's something a customer could hold you to. If you deliver? That's a win on brand prestige, repeat customers, and word of mouth.

Then I read the finished copy once more for accuracy and overall flow, headline included. Headlines are where claims get compressed hardest and checked least. That flow portion is more of a feeling, less of an intellectual decision. Great writing is like great music. There are trends, there are fundamentals, and there are rules to know so we know when to bend or break them for maximum results.

What it costs, and what it misses

The whole pass takes time and energy, both mental and emotional. On a long piece it can take longer than the draft did, because checking a source is slower than reading a sentence. Weighing a feeling is slower than drafting a hopeful promise. The speed AI gives you is real, and some of it leaks through the cracks inherent to the AI limitations. What's left is still faster than writing without AI involved, but intuition cannot be modeled by AI. Intuition is where the best writers thrive.

The pass doesn't catch a piece that's accurate and boring, a claim built on the wrong premise, or a subject nobody should have written up in the first place. Those are earlier problems, avoided through intuition and context clues wrapped up in the white-water rapids of human emotion.

Why it holds

Prompts, even agentic workflows, are easy to write and easy to copy. Anyone can re-use a prompt, a workflow. Nobody can repurpose that intangible intuition we all have inside, where I open the pricing page, read it, and silently reflect until that brilliant eureka moment.

Sample 01 Content strategy

"Cadence," a two-quarter organic plan

How I decide what's worth publishing before anyone writes it, and how I'd know whether it moved anything.

SpecContent-operations SaaS · Goal: qualified trial signups from organic, no added paid spend

The problem we solve for the buyer

Marketing teams don't search for "content operations software." They search the pain: missed deadlines, scattered calendars, approvals stuck in DMs. So the plan buys the problem language first and introduces the product second, usually in the last third of the piece.

Audience and intent

SegmentWhat they searchWhat we publish
IC marketer (drowning)"content calendar template"Templates and how-to guides
Marketing manager (evaluating)"content workflow tools"Comparison and use-case content
Head of marketing (deciding)"content operations ROI"Case studies and ROI breakdowns

Content pillars

Three pillars, deliberately uneven. Most of the volume goes to planning, because that's where the search demand actually is: calendars, briefs, templates. A smaller run covers production speed and approvals, aimed at people already using a tool and unhappy with it. The thinnest pillar is measurement and ROI, which almost nobody searches for and every head of marketing asks about on the call.

Channel logic

Search does the compounding, which is why the pillar pages get the budget even though they show nothing for a full quarter. YouTube is here because the product is a workflow, and a workflow is faster to show than to describe. Email is the only channel with a conversion job, turning template downloaders into trials. One production pass feeds all three.

How we measure it

Leading: organic sessions, video watch time, template downloads. Lagging: organic-attributed trial signups, trial-to-paid rate. Monthly review, and any format that hasn't moved a leading indicator in two cycles comes out of the calendar.

Sample 02 Writing

An SEO blog post, top of funnel

Written for a keyword, and still worth reading if you found it some other way.

SpecKeyword: how to plan a content calendar · Informational · CTA: free template to trial

The post

How to Plan a Content Calendar That Actually Survives Q4

Every content calendar looks great in January. The test is October, when three launches collide, two people are out sick, and the tidy doc you built in a quiet week is the only thing between you and a missed quarter. The planning was fine. It was done in a quiet week, for a quiet week.

Start with the goal, not the grid. Write down the one number this quarter has to move, then make every slot trace back to it. If a planned piece can't name the metric it serves, it comes out of the calendar.

Build in slack before you need it. A calendar packed to 100% breaks on contact with reality. Leave one open slot per cycle on purpose. Something unplanned lands every quarter. The open slot is where it goes.

Make the handoff visible. Most of the delay in a content calendar happens in the gap between two people, where nothing is anyone's job yet. Put the handoff on the calendar as its own row, with a name on it.

The version I build from is one tab, three columns, and a name on every row. It's free. Take it, delete what you don't use, and keep the goal cell.

Why it ranks. Answers the query in the first 40 words, uses the keyword naturally in the H1, the intro, and the close, and earns the link with a genuine template.

Sample 03 Writing

A four-email nurture sequence

Lifecycle copy with the branching and the exit condition specified, so someone could actually go build it.

SpecTrigger: downloaded the calendar template · Goal: start a trial · Exit: trial starts

The sequence

  1. Email 1 · immediately

    Deliver the file, no fluff. One line on the single best way to use it: fill the goal cell first, everything else hangs off it.

  2. Email 2 · day 2

    Lead with the pain: calendars die in the handoff gaps, usually between the person who wrote the brief and the person who owns the deadline. Teach the ownership-column fix. No pitch in this one.

  3. Email 3 · day 4

    Bridge from template to product. The same plan, but with approvals and status live. Soft CTA to start a trial.

  4. Email 4 · day 7 · branch: no trial yet

    A before and after, one line from a customer, and the ask. If a trial starts at any point, exit into onboarding.

Email 1, written out

Subject: Your calendar template (start with cell B2)

Here's the file.

One thing before you start filling it in. Cell B2 is the number this quarter has to move. Fill that one first. Every row underneath has to trace back to it, and the rows that can't are the rows you cut.

That's the whole trick. The rest is formatting.

What I'd test. Email 1 subject line, Email 3 CTA wording, day-2 send time. Benchmarked against a 45 to 55% open and 3 to 5% CTR for warm template leads.

Sample 04 Briefs

SEO and AI-search (GEO) briefs

The brief a freelance writer would actually receive from me, for the blue links and for the AI answer box.

SpecTwo briefs · Pillar and cluster, then citation in AI answers · Written September 2026

Pillar brief: the "content calendar" topic cluster

Primary keyword: content calendar. The person searching it has a spreadsheet that fell apart in Q3 and wants to see what the working version looks like. The pillar has to answer that on one page: the definition box, the five components, a step-by-step build, a gated template, common mistakes, and a measurement section, with the cluster linked underneath it.

On-page: keyword in the H1, the first 100 words, one H2, and the metadata. A snippet-targeted definition block. FAQ schema. An original template asset to earn links.

What to skip: the history-of-content-calendars section. Every competing pillar page has one, it's there to hit a word count, and nobody reads past the H2. Those words go to the mistakes section instead, which is the part people screenshot and send to a coworker.

GEO brief: getting cited by AI answers

Some buyers now open an assistant before they open a single link, and the ones who do show up with a shortlist already made. SEO gets you the click. GEO gets you named inside the answer, whether or not anyone clicks at all.

Open with a direct answer, 40 to 55 words, liftable whole. Then give it a reason to lift yours instead of someone else's: original data, or a framework with a name on it. Write the H2s as the questions people actually type, and keep the paragraphs short enough that a model can lift one whole without trimming it. Schema tells the model where to look. The slow part is entity authority, which is mostly naming the brand and the author the same way everywhere until the models connect the two.

Measure it by running the target prompts across ChatGPT, Claude, Gemini, and Perplexity on a schedule and logging every time the brand gets named. Share of voice against the competitors named alongside you is the number worth reporting. AI-referral traffic needs its own tag or it disappears into direct.

Why this brief exists. The SEO brief above stopped being enough on its own. Same page, same research, one more surface it has to win.

Want a sample written for your category? Ask me.
Get in touch