explain-like-pro

Explainer Newsletter

This skill produces explainer pieces in a specific voice: warm, plain-spoken, curiosity-driven, and built around a single clear story arc. The reader is smart but busy, and has zero patience for jargon. The goal of every piece is the same — take one thing the reader half-understands and leave them genuinely getting it, while enjoying the ride.

The voice works for any subject. The examples here often draw on business and tech because that's the source material, but the same moves explain a science paper, a court ruling, a sports trade, or a new law. Don't let the subject change the voice.

The core operating principle

Anticipate the reader's mind and stay one step ahead of it. Almost everything good about this voice flows from this. You're not lecturing — you're having a conversation where you keep guessing the reader's next question and answering it before they ask. That's why the writing feels effortless: it never leaves the reader stranded.

Before drafting, write down (for yourself) the 4–6 questions a curious newcomer would ask about this topic, in the order they'd naturally occur. That ordered list is your outline. The piece is just those questions, answered one at a time, with a hook on the front and a reframe on the back.

Research the facts before you write a word

A confident, plain-spoken voice only works if what it says is true. Never write this kind of piece from memory alone — memory drifts, numbers go stale, and a single wrong figure quietly poisons the reader's trust in the whole thing. Search the web first, then write.

When to search (basically always for a real topic):

• Anything time-sensitive: prices, valuations, who currently holds a role, the status of a deal, recent events, "latest" anything.
• Every specific number, date, name, quote, or statistic you plan to put on the page.
• Any surprising or counterintuitive claim — the thing that makes the story is exactly the thing most worth verifying.
• The mechanics of how something works, when you're explaining a concept you don't have rock-solid command of.

How to source well:

• Go to the origin. Prefer primary and authoritative sources over aggregators: company filings and investor presentations, official press releases, government and regulator sites, court documents, peer-reviewed papers, original data, and the reporting of established outlets. Treat random blogs, forums, and SEO content farms as leads to verify, not as citations.
• Cross-check the load-bearing facts. If a claim anchors the story (the headline number, the central twist), confirm it in at least two independent reliable sources. If reputable sources disagree, say so in the piece rather than picking one silently.
• Search per fact, not in one giant query. Look up each figure or claim separately so you get specific, current results.
• Date-check. Note when a figure is from ("…as of [period]") and don't present an old number as today's.
• If you can't verify it, don't assert it. Either leave it out, or hedge honestly ("reports suggest," "the company hasn't confirmed"). Never invent a source, a number, or an attribution to make a sentence sound more authoritative.

Attribute the way this voice does — lightly, in prose. No footnotes or academic citations. Fold the source into the sentence the way a smart friend would: "According to its latest filing…" "Reuters reported that…" "The company itself has said…" "Regulators have flagged…"

Hyperlink the load-bearing claims so the reader can verify them. This is how Finshots itself works — specific facts, figures, and surprising assertions are turned into inline links to the source they came from. Do the same: for any strong, checkable statement — a specific date or number, a named study or standard, a direct factual claim a skeptical reader might want to confirm — embed a hyperlink on the natural anchor phrase, pointing to the reliable source you actually drew it from. Rules of thumb:

• Link the claim, not the whole sentence. Anchor the few words that carry the fact ("finalised the first three standards"), so the prose still reads naturally.
• Link primary/authoritative sources — official bodies, filings, regulators, peer-reviewed papers, established outlets — over SEO blogs and aggregators. Link the source you verified the fact against, not just the first result.
• Don't over-link. Skip common knowledge and your own connective reasoning. If everything is linked, nothing stands out — aim to link the facts that genuinely matter or that a reader would reasonably want to check.
• One link per claim. Don't stack multiple links on the same fact, and don't re-link the same source repeatedly in adjacent sentences.
• The links serve the reader's trust, not decoration. The voice stays conversational; the links just sit quietly underneath the strong statements.

This research step feeds directly into the question-outline above: as you verify facts, you'll discover what the reader's real questions are and where the genuine surprise lives.

Structure of a full issue

Produce these parts in order. Keep the body roughly 700–1,200 words.

1. Subject line — a curiosity gap, not a summary. Withhold the punchline. Use a quiet emphasis word that signals there's a twist: "The chipmaker Apple suddenly needs," "The pivot nobody saw coming," "Reading between the lines of the report." Avoid clickbait that overpromises; the tension should be real.
2. One-line promise (italic) — "In today's issue, we explain why ___ ." Tell the reader exactly what they'll walk away understanding. One sentence.
3. The Story (the body) — opens human, builds question by question, ends on a reframe. Detailed below.
4. Sign-off — a short, warm, slightly self-aware closing line, then "Until then…" or "Until next time…"

Note: Finshots issues also carry business inserts (subscribe nudges, "Finshots Family" insurance-masterclass blocks, mailing address). Those are house ads, not part of the writing voice — leave them out unless the user explicitly wants their own CTA.

How to write the Story body

Open on something small and human

Never open on the macro news. Open on a person, a small scene, a memory, a tiny moment — then widen to the big thing. A friend eyeing a laptop. A kid begging for a SIM card. Millions of people opening an app out of habit. The mundane detail is the doorways; the reader walks through it into the larger topic without noticing the transition. If a first-person anecdote fits, use it ("I still remember the time I…"). If not, open on a vivid, concrete second-person moment ("Think about the last time you…").

Build by answering the reader's questions in sequence

This is the engine. Surface each likely objection or curiosity as a question, then answer it. Make the questions explicit on the page:

• "Now I know what you're probably thinking: why can't they just ___?"
• "So why does ___ seem so desperate to ___, you ask?"
• "Which brings us to another question: ___?"
• "And before you ask — no, ___ ."

Each answered question hands off to the next. The reader never feels lectured; they feel accompanied.

Kill the jargon on contact

The instant a technical term appears, define it in plain words, in line, then move on — no glossary, no condescension. "DRAM chips temporarily store data while your phone is running — different from the chips that permanently hold your photos and apps." If you can avoid the term entirely, do. If you can't, demystify it the moment it lands.

Reach for one clean analogy per hard idea

Map the unfamiliar onto something the reader already lives with. A subscription business: "today's billings become tomorrow's revenue." A state-funded company: think of how a government sometimes seeds a company it believes in.

Control the rhythm

Vary sentence length deliberately. Long, explanatory sentences should be interrupted by short punches that land a beat. Give the punch its own paragraph:

The catch?

And that could change everything.

But here's what most people missed.

These one-liners are the heartbeat of the voice. Use them to mark turns in the argument and to let a big idea breathe.

Use the conversational connective tissue

Light, spoken transitions keep momentum: "Here's the thing." "Well, actually…" "Now…" "So yeah." "And there you have it." A tag question now and then ("…no?") pulls the reader in. Use sparingly — seasoning, not the meal.

Land on a reframe, not a recap

The payoff is the strongest move in the whole format. Don't summarize what you said — flip how the reader sees it. "What if [the company] was never really in the [obvious] business at all? What if it was always in the business of ___?" "The real question was never X. It's Y." State the one idea you want them to keep, then close warm.

Keep it human — avoid the AI tells

This voice dies the instant it smells machine-generated. Actively avoid:

• Listicle-brain. This is flowing prose with a narrative spine, not a bulleted "key takeaways" dump. (Lists are fine inside the story when a source genuinely has, say, three numbered findings — but the piece is a story, not a slide.)
• Hedging mush — "it's important to note," "it's worth considering," "in today's fast-paced world." Cut all of it.
• Symmetrical, over-balanced sentences and tidy "Firstly/Secondly/In conclusion" scaffolding. Real writers are lumpier.
• Em-dash overload and the "not just X, but Y" construction on repeat. Use them once if earned.
• Throat-clearing. Start where the energy is.
• Vocabulary inflation — "utilize," "leverage," "myriad," "delve." Use the word a smart friend would say out loud.

Read the draft aloud in your head. If a sentence sounds like a press release or a textbook, rewrite it the way you'd actually say it to a curious friend across a table. That table-talk test is the whole game.

Workflow

1. Clarify the topic and, if not obvious, the angle (what's the surprising or under-noticed thing here?).
2. Research first. Search the web for current, reliable sources; verify every number, name, date, and surprising claim; cross-check the load-bearing facts; note how recent each figure is. Don't draft from memory.
3. List the reader's 4–6 natural questions in order — that's the outline. (Your research will have shown you what those questions really are.)
4. Find the human opening — the small scene or memory that leads into the topic.
5. Draft the body, answering questions in sequence, defining jargon on contact, one analogy per hard idea, rhythm punches at the turns, and light in-prose attribution for sourced facts — with inline hyperlinks on the load-bearing claims so the reader can verify them.
6. Write the reframe ending and the warm sign-off.
7. Write the subject line and one-line italic promise last, once you know where the piece actually lands.
8. Run the table-talk test, strip any AI tells, and do a final fact pass — is anything asserted that you didn't verify, and does every load-bearing claim carry a link to a reliable source?

References

• references/patterns.md — phrase banks, opening-hook types, transition library, and question-framing templates pulled from the style. Read it when you want concrete language to reach for.
• references/worked-example.md — a full sample issue on a non-finance topic, annotated to show each move in action. Read it when you want to see the structure assembled end to end.

Patterns & phrase bank

Concrete language to reach for. These are moves, not mandatory fill-ins — pick what fits and rephrase freely. Overusing any single phrase is itself an AI tell, so rotate them.

Opening-hook types

Pick the one that best leads into the topic. Always start small, then widen.

1. First-person memory — "I still remember the time I…" Works when you can credibly tie a personal moment to the topic.
2. The small recent scene — "Last week, a friend and I…" / "A couple of days ago I…" A tiny, concrete event that turns out to connect to something big.
3. The ordinary mass moment — "On [specific date], around [number] people opened [thing] out of habit." Anchors an abstract story to a real instant in time.
4. Direct second-person — "Think about the last time you [did everyday thing]." Pulls the reader into their own experience before introducing the concept.
5. The standing puzzle — "For years, [subject] has occupied a strange place…" Opens on a question the reader has quietly wondered about.
6. The "here's the gist" — "If you haven't had the chance to read [thing], here's the gist." For reacting to a document, report, or announcement.

Question-framing templates (the engine)

Use these to surface the reader's next thought on the page. Rotate the phrasing.

• "Now I know what you're probably thinking: why can't they just ___?"
• "So why does ___ seem so keen to ___, you ask?"
• "Which brings us to another question: ___?"
• "And before you ask — no, ___ can't simply ___ either."
• "But here's what you probably missed."
• "But the [rising prices / obvious part] isn't the most interesting bit. It's what happened next."
• "At first glance, this sounds [bizarre/impossible]. But what if we flip the question?"

The reframe ending

The payoff flips the reader's mental model. Patterns:

• "What if [subject] was never really in the [obvious] business at all? What if it was always in the business of ___?"
• "Earlier, the question was ___. Tomorrow, the bigger question may be ___."
• "The real test isn't whether ___. It's whether ___."
• "And surprisingly, the answer had very little to do with [the obvious culprit] itself."

Then state the single keep-this idea plainly, and close warm.

One-line punch paragraphs

Drop these on their own line to mark a turn or let an idea breathe. Keep them short.

• "The catch?"
• "And that could change everything."
• "But here's the twist."
• "Then came an unexpected helping hand."
• "And this isn't just theoretical."
• "But there's a catch."
• "And that's where the problem lies."

Conversational connectives

Seasoning to keep it spoken, not written. Use lightly.

• "Here's the thing."
• "Well, actually…"
• "You see…"
• "Now…" / "So…" / "And so…"
• "So yeah."
• "And there you have it."
• "…no?" (tag question, occasional)
• "folks" (warm direct address, rare)

Handling numbers

• Always contextualize a number, never strand it. "The notice was for roughly 150x that." "Less than 0.4% of the country's transactions." "Below its usual intake of around 40,000."
• Convert the abstract into the relatable: a giant figure becomes "the size of [familiar thing]," a percentage becomes "more than four out of every five."
• Round in prose; precision is for the rare moment it matters.

Attributing sources (light, in prose)

Once a fact is researched and verified, fold the source into the sentence — no footnotes, no "[1]". Rotate these so it never reads like a template:

• "According to its latest [filing / report / presentation]…"
• "[Outlet] reported that…" / "As [outlet] first reported…"
• "The company itself has said…" / "In a statement, they said…"
• "Regulators have flagged…" / "Official data shows…"
• "Reports suggest…" (use only when the claim genuinely isn't confirmed)
• "Back in [month/year], we / they…"

Hyperlink the strong claims. Turn the few words carrying a checkable fact into an inline link to the source — e.g. "NIST finalised the first three standards" or "intelligence officials have said openly that…" Link the anchor phrase, not the whole sentence; prefer primary/authoritative sources; link the genuinely load-bearing facts rather than everything; one link per fact.

Calibrate certainty honestly: "confirmed," "announced," "said" for solid facts; "reportedly," "reports suggest," "is said to" for unconfirmed ones. If two reliable sources disagree, name the disagreement instead of hiding it: "Estimates vary — [source A] puts it at X, while [source B] says Y."

Defining jargon in line

Pattern: term → plain-words definition → contrast with the thing it's often confused with → move on.

• "DRAM chips temporarily store data while your device is running — unlike the chips that permanently hold your photos and apps."
• "Billings are what a customer pays upfront for a subscription period; revenue is recognized gradually over the life of that contract. In other words, today's billings become tomorrow's revenue."

Sign-offs

• A small self-aware line that ties back to the human opening, then:
• "Until then…" or "Until next time…"

Sentence-rhythm checklist

• Did a long explanatory sentence get followed by a short punch?
• Is there at least one one-line paragraph at a turning point?
• Are paragraphs mostly 1–3 sentences? (This format runs short and airy.)
• Read it aloud in your head: does any sentence sound like a textbook or a press release? Rewrite it as table talk.

Worked example (annotated)

A full sample issue written in the voice, on a deliberately non-finance topic to show the method travels anywhere. Annotations in [brackets] point out the move being made — they are not part of the piece.

---

Subject line: The slow death your phone hides from you

[Curiosity gap. "Slow death" + "hides from you" promises a twist without revealing it. Not "Why phone batteries degrade."]

In today's issue, we explain why your phone's battery quietly gets worse every year — and why the fix isn't the one you've been told.

[One-line italic promise. The reader knows exactly what they'll understand by the end.]

The Story

A few months ago, my phone died at 38%.

[Human opening — a tiny, concrete, slightly absurd personal moment. No "batteries are a complex electrochemical system" throat-clearing.]

Not 2%. Not 5%. Thirty-eight. One minute it was fine, the next the screen went black in the middle of a text. I assumed the phone was broken. It wasn't. The battery was just old — and old batteries lie about how much they have left.

[Widens from the scene to the real subject. The last line is a small hook that plants the central mystery.]

Here's the thing. Every rechargeable battery is dying from the day you buy it. Not because the makers cut corners, but because of what a battery physically is.

[Conversational connective ("Here's the thing"), then reframes the problem as inevitable, which raises the obvious question — answered next.]

A lithium-ion battery — the kind in basically every phone — works by shuffling tiny charged particles back and forth between two sides every time you charge and drain it. Think of it like a crowd moving between two rooms through a doorway, over and over. Do that enough times, and the doorway gets scuffed, the rooms get cluttered, and fewer people make the trip. That "trip" is your charge. Fewer trips means less battery.

[Jargon ("lithium-ion") defined in plain words on contact. Then one clean, globally legible analogy — a crowd through a doorway — for an idea most people never actually understood.]

Now I know what you're probably thinking: so why not just build a bigger battery that lasts for years?

[The engine. Surfaces the reader's exact next question, in their voice.]

Well, makers could. But a bigger battery means a thicker, heavier phone — and every survey for two decades says people pick thin and light over long-lasting almost every time. So phones are designed for the showroom, not for year three.

[Answers the question, and sneaks in a second insight — the incentive behind the design.]

But the battery wearing out isn't the most interesting part. It's what your phone does about it.

[One-line-style turn that redirects from the obvious story to the surprising one — classic structure.]

As the battery ages, your phone quietly starts protecting itself. It slows the processor down so it never asks the tired battery for more power than it can safely give. That's why an old phone feels sluggish and dies early — same root cause. The slowdown isn't a glitch. It's a feature you were never told about.

[Payoff-building reveal. Connects two things the reader experienced separately — slowness and short battery life — into one cause.]

So what actually helps?

[Another reader question, teeing up the practical part.]

Mostly, it's heat and extremes. Charging to 100% and draining to 0% every day is the doorway-scuffing at its worst. Leaving the phone baking in a hot car is worse still. Keeping it loosely topped up, somewhere in the middle, and cool — that's the boring, unglamorous secret. No app required.

[Practical answer, kept plain. Resists the urge to list ten tips — gives the one principle that matters.]

And there you have it. The reason your phone feels old isn't that you've outgrown it or that some company flipped a switch to make you buy a new one. It's a doorway, scuffed by a few hundred ordinary days, doing exactly what physics says it must.

[Reframe ending: flips the reader's instinctive story ("they're sabotaging me to sell phones") to the truer, quieter one. States the single keep-this idea.]

So yeah, mine still dies at 38%. But at least now I know it's not lying to spite me — it's just tired.

[Warm, self-aware sign-off that loops back to the opening scene.]

Until then…

---

Why this works (quick recap of the moves)

• Opened human (phone dying at 38%), never on "batteries are electrochemical cells."
• Ran on questions the reader actually has — why not a bigger battery? what helps? — answered in order.
• Defined the one piece of jargon (lithium-ion) instantly, then dropped it.
• One analogy, globally legible (a crowd through a doorway), reused as a through-line.
• Marked the turns with short redirect sentences ("But the battery wearing out isn't the most interesting part").
• Reframed at the end instead of recapping, and tied the close back to the opening.
• No listicle, no hedging, no inflated words. Reads like table talk.

This example uses evergreen science, so it needs no citations. For a topical piece — a deal, a number, a recent event — you'd research and verify each fact first, then weave in light attribution with an inline link on the load-bearing claims ("NIST finalised the first three standards", "Reuters reported". The voice stays the same; it just rests on checked, linked facts.