The same Sunday recording that feeds the clip chain feeds this one. You're not making new raw material — you're extracting a second product from something you already made, which is why this costs eight build hours instead of thirty.
The full chain, the restructure prompt, and the editorial pass are all on this page. No email needed for any of it.
Eight modules. Note that it deliberately stops before publishing — the twenty-five minutes in the middle is the part that can't be automated, and the chain is built to enforce that.
Google Drive · Watch Files
The same trigger as the clip chain, fanned out with a Router. Don't build a second watcher on the same folder — you'll pay for the polling twice.
Deepgram or AssemblyAI · transcribe
About $0.25 per hour of audio. At one 25-minute recording a week that's roughly 45¢ a month. The cheapest module in the entire book.
Claude · restructure
The interesting decision, and it gets its own section below. Restructure, not rewrite.
Notion · create page, status Needs Edit
Build a filtered view showing only that status. That view is your writing queue and the only place you should look on writing day.
YOU · twenty-five minutes
The chain stops here on purpose. This is the product; everything else is transport.
Ghost / Framer / Webflow · publish via API
Ghost has the cleanest API. If yours has none, let the chain stop at Notion and paste manually — four minutes a week isn't worth engineering around.
Search Console · request indexing
Small, and it shortens time-to-indexed from weeks to days.
Airtable · log to Content
Same table as the clips, so you can eventually see which recording sessions produced things that worked.
The single most important instruction here is that the model must restructure, not rewrite. Your spoken words contain the specifics — the numbers, the war stories, the opinions. A model asked to "write an article about this" smooths every one of them into competent, sourceless prose, which is what everyone else publishes.
Below is a transcript of me speaking about a topic in my field. Turn it into a first draft of a written article. Your job is to restructure, not to rewrite. - Preserve my specific examples, numbers, names, and dates verbatim. Do not smooth, generalize, or paraphrase them. - Preserve my opinions, including ones stated bluntly. Do not hedge them. - Remove only: filler, false starts, repetition, and things I clearly abandoned mid-sentence. - Reorder for a reader rather than a listener. Spoken tangents that work aloud usually need to move or go. - Add subheadings that describe what the section actually says, not generic labels. Hard rules: - Invent nothing. Add no statistics, studies, examples, or claims not present in the transcript. - If a passage is unclear or a claim seems incomplete, do not fix it — mark it [NEEDS AUTHOR INPUT: what's unclear] and move on. - Do not add an introduction that summarizes what the article will cover. Start with the substance. - Do not add a conclusion that restates the article. Target 1,000-1,400 words. Transcript follows.
[NEEDS AUTHOR INPUT] earns its placeWithout it, a model encountering a gap in your reasoning will fill it — plausibly, fluently, and with something you never said. With it, the gaps come back as a to-do list. Those markers are where the best material ends up, because they're precisely the spots where you assumed knowledge your reader doesn't have.
"Edit the draft" is useless advice and it's where most guidance stops. Set a timer and work in this order.
Resolve every [NEEDS AUTHOR INPUT] marker · 8 min
These come first because they're the highest-value additions in the piece. Each one is a place your expertise skipped a step.
Add one thing only you would know · 5 min
Non-negotiable. A real number, a named form, a specific year, the mistake you watched someone make, the reason the obvious approach fails. If you finish without adding one of these, don't publish — it's a summary of existing consensus, which is exactly what the AI Overview already gave the searcher.
Take one position · 4 min
Find where you're describing a debate and pick a side. Not manufactured contrarianism — an actual opinion, stated plainly. This is the biggest differentiator between content that gets cited and content that gets absorbed, because a summarizer can restate consensus and cannot manufacture a stance with a person behind it.
Fix the opening · 4 min
The first two sentences decide everything. Cut any throat-clearing the model left in and start with the claim.
Read it aloud · 4 min
Anything you'd be embarrassed to say to a smart colleague gets cut. This catches more bad writing than any other technique.
The chain is copyable in an afternoon. Your list of things nobody writes down is not. That's the commercial argument, and it matters more than the search-penalty one: the twenty-five minutes is the only part a competitor can't replicate.
Roughly 60% of searches now end without a click. Being the cited source is worth as much as being the top result — and four habits do the whole job.
Answer the question in the first hundred words
Directly, in a self-contained paragraph. Not "this is a complicated topic with several considerations" — the actual answer. This is what gets lifted into a snippet or summary, and it's also just better writing.
Write subheadings as the questions people ask
"How often should covenants be tested?" beats "Testing Frequency." Both tell a reader what's below; only one matches how anyone searches.
Put specifics in structures a machine can parse
Comparisons in tables, sequences in numbered lists, thresholds in a table with numbers in their own column. The parts most likely to be cited are the data parts.
Say who you are, on the page
One line of credential near the top. It's the trust signal a human needs before believing a number, and the first-person expertise marker that distinguishes a source from a summary.
What you don't need: schema plugins, keyword-density tools, or anything promising to optimize your content. Those four are the whole intervention at your scale, and three of them are just good writing with a different justification.
Everything above builds it from scratch in about eight hours. The blueprint makes it about thirty minutes.
Needs Edit view, pre-filteredIt's a JSON file and a Notion template — tell me where to send them.
One email a week about building things that run without you. Unsubscribe link at the bottom of every one, and it works.
© 2026 Jeff Sheikowitz. All rights reserved.