Back to database

Josh Belanger's AI use case

Financial entrepreneur and newsletter writer at Belanger Trading

Finance newsletter editing workflow where human-written market thoughts are streamlined with ChatGPT, copyedited with Claude, and refined with custom GPTs to preserve trading-specific language.

The problem

What was broken before AI

A finance newsletter draft can start as a messy pile of market observations, research notes, trade context, caveats, and jargon. Before AI, turning that into readable copy likely required more manual rewriting and copyediting, especially when the language had to stay precise enough for a trading audience.

What changed

What the use case made possible

AI became a production layer between Belanger’s human market thinking and the final newsletter: ChatGPT streamlines the draft, Claude helps copyedit, and custom GPTs are used to handle technical language with fewer unwanted substitutions or hallucinated phrasing.

Why this matters

Why this use case is worth studying

This case sits in the uncomfortable but important middle ground of AI-assisted publishing. The workflow still depends on the writer’s own research, judgment, and accountability, but it uses AI to reduce the drag between having a market take and shipping a polished issue. For specialist creators, the lesson is that generic AI editing can be too generic; the system needs domain vocabulary, house style, and clear boundaries around what it is allowed to change.

Use this when

When this pattern applies

Use this when you already have the expertise and raw material, but the editing and production process slows you down.

Exponential Builder analysis

01

Domain language is part of the product

In specialist media, the reader is paying for judgment and fluency. A useful AI workflow protects the words that signal expertise instead of smoothing everything into generic prose.

02

AI editing works best as a chain

Belanger’s reported setup separates streamlining, copyediting, and jargon handling. Splitting those jobs makes the workflow easier to inspect and less likely to bury a bad change.

03

The human source of truth still matters

The workflow starts with the writer’s own thoughts and research. That matters more in finance, where a polished sentence can create misplaced confidence if the underlying claim is wrong or overstated.

Who this is for

Best fit

Newsletter writers in technical or regulated-adjacent niches

Finance, trading, crypto, and market commentators who need careful wording

Solo creators who write from notes and want a repeatable editing system

Operators building a house-style assistant for specialist content

Writers who want AI help without handing off the core argument

What to avoid

Mistakes and warnings

Where this pattern can go wrong if you copy it too literally.

Do not let AI generate market claims, trade recommendations, or performance expectations without human verification.

Watch for softened caveats; finance writing often needs uncertainty and risk language to remain explicit.

Generic copyediting can remove useful jargon or replace precise trading language with vague business prose.

AI detectors are imperfect, so do not treat detection scores as proof of quality or misconduct.

If you publish financial content, consider disclosure, compliance, and reader-suitability issues before scaling this workflow.

Custom GPTs can still hallucinate; domain instructions reduce risk but do not remove the need for review.

Public workflow preview

The shape of the workflow

A high-level look at how the use case works, with the reusable pattern made clear.

01

Start with human notes

Write the market thoughts, research points, and details that must appear in the newsletter.

02

Streamline with ChatGPT

Use ChatGPT to shape the rough material into a cleaner draft without asking it to invent the investment thesis.

03

Copyedit with Claude

Run the draft through Claude for clarity, grammar, flow, and readability.

04

Use custom GPTs for jargon

Create task-specific GPTs that understand the newsletter’s trading terminology and preferred phrasing.

05

Final human review

Check every market claim, trade detail, and risk-sensitive sentence before publishing.

Copy the pattern

The reusable idea

Pattern in one sentence

Write the expert draft yourself, then use AI as a structured editing chain that tightens the prose while protecting the niche vocabulary and factual claims.

Reusable idea

If you write in a technical niche, don’t start by asking AI to create the piece from scratch. Start by writing the raw material yourself, then make the model act like a production assistant: organize, tighten, copyedit, and flag unclear language. The more specialized your field, the more useful it becomes to keep a reusable style-and-jargon assistant rather than prompting from zero every time.

Steal this workflow

Finance-newsletter editing recipe:

1

Draft: Write your raw market note in bullets, including thesis, evidence, caveats, and reader takeaway.

2

Lock: Add a section called “Do not change” with tickers, numbers, trade mechanics, and required disclaimers.

3

Streamline: Ask ChatGPT to turn the notes into your usual newsletter structure.

4

Copyedit: Ask Claude to improve clarity and flow without adding new facts.

5

Jargon pass: Run technical sections through a custom GPT that has your glossary and sample phrasing.

6

Risk pass: Ask AI to flag overconfident language, then make the final call yourself.

7

Publish: Only after checking every claim against your own research.

Suggested prompt

“You are editing a finance newsletter draft. Use only the information I provide. Do not add market claims, trade recommendations, tickers, prices, performance expectations, or sources. Preserve the meaning of all technical trading language. First, reorganize the draft for clarity and remove repetition. Second, improve sentence flow while keeping my direct, specialist tone. Third, flag any sentence that sounds overly certain, promotional, or like personalized financial advice. Here are my locked facts and phrases: [paste]. Here is the draft: [paste].”

Field notes

Get new AI use cases in your inbox

A short weekly note on how real people are using AI to save time, make money, build tools, and run their lives.

No spam. Just useful AI use cases.

Related use cases

Keep exploring nearby systems.

Browse all