One-Source Content Engine

Goal

Turn one real source — a customer call, a support thread you are allowed to use, or a 20-minute expert voice note — into a week of specific posts, a newsletter, and one page section, without inventing expertise you did not record.

Tools required

Direct is the vendor's public site. Affiliate appears only when ShipPlays is enrolled in that program.

• A recorder you already use

  Direct

  Zoom, Meet, or a voice memo. The recording is the source of truth.

• Notion

  Direct

  One page per source: quotes, numbers, and a do-not-claim list. A Google Doc works too.

• Beehiiv

  Direct

  Where the newsletter actually goes, once you have signed the draft.

• Buffer

  Direct

  Schedule only after the human pass. Native scheduling is fine if you already have it.

Step-by-step setup

1. Name the reader in one sentence

   Example: ops managers at 30–200 person shops who reorder by gut feel and are tired of stockouts. Every asset has to be useful to that person. If the same paragraph would also work for a dentist, it is too abstract. Write the sentence at the top of the source template.

2. Make the source page boring and strict

   Fields: recording link, 8–12 exact quotes with ids (Q1, Q2), numbers the speaker actually said, stories, opinions, and a do-not-claim list. You fill the quotes. The model does not invent them. If a number is not on the page, it cannot appear in the package.

3. Capture one source a week

   A 25-minute call is enough. Paste the transcript under the template and run the extraction prompt. You delete anything the speaker did not say. You fix quotes that the transcript mangled. This edit is the quality bar. Skipping it is how you publish someone else's mouth wrong.

4. Package only from the edited page

   The package prompt receives the edited source page and nothing else. It produces one newsletter (about 600–900 words), four short posts, one thread outline, and one landing-page section. Each item cites a quote id. An item with no quote id gets cut.

5. Rewrite the openings yourself

   Models bury the point under a warm-up. Your pass is the first two sentences and the delete. Cut about one sentence in three. Schedule only what you would sign. For the first four weeks, ship the newsletter plus one social surface. Add a channel only after the source habit is boring.

6. File three lines of truth on the source page

   What shipped, what got a real reply or a sale, what you will not repeat. Next week's extraction prompt includes those three lines. The library becomes the advantage. The prompt does not.

Exact prompts

Extract a source page from this transcript. Do not write posts. Do not smooth the speaker into a brand voice. Do not add facts that are not in the transcript.

Reader:
{READER_SENTENCE}

Transcript:
{TRANSCRIPT}

Return markdown with these headings only:
- Quotes: 8 to 12 short quotes, each with an id (Q1…) and a timestamp or paragraph hint if you can see one. Exact words. If you are unsure of a word, mark it [unclear].
- Numbers: only figures the speaker said. If they said "about," keep the hedge.
- Stories: 2 to 4, two sentences each, tied to a quote id.
- Opinions: what they believe, tied to a quote id. Do not upgrade a hedge into a rule.
- Do not claim: topics they joked about, half-finished thoughts, and anything that would be advice they did not mean to give.

If the transcript does not support 8 quotes, return fewer. Never pad.

Build one week's package from this edited source page only. Every claim must cite a quote id from the page. If a sentence cannot cite one, delete the sentence.

Reader:
{READER_SENTENCE}

Source page:
{EDITED_SOURCE_PAGE}

Last week's lesson, if any:
{THREE_LINES_OR_NONE}

Return exactly these parts:
1. Newsletter, 600–900 words. Open with the sharpest specific fact. No "in today's world." No invented customer. End with one question the reader can answer from their own shop.
2. Four short posts. Each is under 70 words, cites a quote id, and can stand alone.
3. Thread outline: 6 beats, not full prose. Each beat has a quote id.
4. Landing section: 120 words a stranger could read and know who this is for. Cites at least two quote ids.
5. Cut list: lines you almost wrote that the source page does not support.

Do not add statistics, studies, or quotes that are not on the page.

Expected results

• One source produces a week of assets without a second research hole.
• Every published claim traces to a quote id on the source page.
• A library you can respin next quarter without starting from a blank topic.
• A voice that still sounds like the person who was on the call.

Guardrails

• No fabricated quotes, customers, or numbers.
• Do not turn a casual remark into medical, financial, or legal advice. If the source was careful, you may keep their wording. If it was casual, label it as experience.
• Get a yes before you use a customer's name or company. Anonymize by default.
• The scheduler does not post without the human pass. The pass is the product.
• Do not upload a call the other party did not agree could be processed this way.

Common mistakes

Related

• Search-Intent Brief Factory
• Outbound Account Research Sprint