Solo AI Club
the sample · read a real issue

A real issue, start to finish.

This is exactly what lands in your inbox — no teaser, no paywall. Read it, run it, then get one like this twice a week.

Free forever. Unsubscribe anytime.

solo ai club · issue 01 · [date]

Turn a 40-minute call into a client-ready recap in 5 minutes.

You finished the call. The notes are a mess, the client wants a recap today, and you're the whole team. Here's the exact workflow I use to turn raw call notes into a clean, client-ready one-pager — in about five minutes, start to finish.

01 · one workflow to run today

The five-minute recap.

  1. 1

    Drop your transcript or rough notes into a folder, or paste them straight into Claude.

  2. 2

    Run this prompt:

    prompt 
    You are my client-communications assistant. Here are my raw notes from a call: <notes>{{PASTE YOUR NOTES}}</notes>. In <recap> tags, write a one-page client recap with (1) what we agreed, (2) open questions, (3) next steps with owners and dates. Keep it under 250 words, plain and warm, no jargon. Then list any details you had to assume so I can correct them.
  3. 3

    Review the assumptions Claude lists, and correct anything wrong in one reply.

  4. 4

    Ask Claude to save it as a .docx, or drop it straight into your email.

recap.docx
Client recap — Northwind
What we agreed
Open questions
Next steps
why it works

The <notes> tags isolate your messy input so Claude knows exactly what to work on.

The numbered structure forces a format you can actually send.

And asking Claude to surface its assumptions catches errors before the client sees them.

stylized result · run the live version below to watch it stream.

02 · one tool, decoded

Chat vs Cowork vs Claude Code — which one for this?

Chat Cowork Claude Code
best for quick questions, drafts, one-off rewrites multi-step work on your own files building and shipping software (and sites — this one)
what it does answers in the chat window; doesn't touch your files plans, then delivers after you approve reads a codebase, edits files, opens PRs
where it falls short won't act across your files or apps overkill for a one-liner it's a coding tool, not where you'd draft an email
plan needed works on Free paid desktop app paid
solo verdict your everyday default your "do it for me" mode when "make me a tool" becomes "ship me a product"

no star ratings — honest qualitative notes only.

03 · one prompt worth stealing

The grounded proposal.

prompt 
Read every file in this folder first. Using my tone from about-me.md, draft a one-page proposal for {{PROJECT}}. Ask me up to 3 clarifying questions before you start. When it's done, save it as a .docx.
why it works

"Read first" grounds Claude in your real context, the tone file keeps it sounding like you, and capping it at three questions stops it guessing.

04 · one move for the week

In Cowork, set one recurring task — "Every Friday at 9am, pull this week's numbers from my sheet and send me a 5-bullet summary." You just hired a Monday-morning analyst that costs nothing.

That's one workflow. You'll get two like this a week — one to run today, one tool decoded, one prompt worth stealing.

— [Founder name placeholder]

forward this to a solo operator who needs it →
go deeper · hands-on

Play with the tools from this issue.

Run the recap live

Pick a task and watch Claude stream a realistic response. Scripted preview — no data leaves your browser.

claude
your prompt 
You are my client-communications assistant. Here are my raw notes from a call: <notes>{{PASTE}}</notes>. Draft a one-page client recap with (1) what we agreed, (2) open questions, (3) next steps with owners and dates. Keep it under 250 words, plain and warm. Then list any details you had to assume so I can correct them.
claude

i'll structure this as a one-page recap, then flag what i assumed.

client recap — draft

what we agreed

  • scope is the landing page plus two inner pages
  • launch target is the end of the month

open questions

  • do you want a blog section in v1, or later?
  • who is providing the final photography?

next steps

  • you: send logo files and brand colors — by friday
  • me: share the first layout for review — early next week

assumptions i made (correct anything wrong):

  • "the site" means a marketing site, not a web app
  • "soon" for launch means this month
📄recap.docxsaved

Messy in, clean out

Claude for Excel, before and after. Drag the toggle.

messy.csv · mixed dates, dupes, currencies
date
client
amount
3/2/26
acme co
€980
2026-02-03
Acme Co
980 eur
14 Jan
northwind
$1,250
19/02/26
Bluefin
£1,900
clean.xlsx · standardized + summary
date
client
amount (usd)
2026-01-14
Northwind
1,250.00
2026-02-03
Acme Co
1,058.00
2026-02-19
Bluefin
2,400.00
jan
feb
mar

illustrative data · the real edits stay formula-safe in your sheet.

What's your time worth?

A working Artifact — real in-browser math.

17.3
hours / month
$1,039
reclaimable / month

a working Artifact — and yes, this one actually does the math.

coming up · more issues

What's already in the queue.

issue 02
The five-minute competitor teardown
  • a Cowork research workflow
  • ChatGPT vs Claude for research
  • the teardown prompt
issue 03
Stop rewriting the same email
  • a reusable email-system workflow
  • the snippets approach
  • a tone-match prompt
issue 04
Your spreadsheet can do more than you think
  • Claude for Excel
  • formula-safe cleanups
  • a pivot prompt

Get the next issue free.

Free forever. Unsubscribe anytime.