Your system · after every call

Your call notes become the record, the draft, the next step

An add-on for the half hour of admin that follows a client call. Paste your raw notes or the transcript, and one command turns them into an update to that person's file, a follow-up draft in your voice waiting for your yes, and the promises captured where they will be seen again. One plain file per person, on your machine, and the sending stays yours.

Add it to your system

It reads the system you already built and slots in. No full system yet? It brings a small starter and runs on its own.

See the difference

The same call, two endings

The version where the admin swallows your evening, and the version where the record does the holding. Flip between them.

The 30 minutes after
TUESDAY, 4:32PM. GOOD CALL WITH ANA.

Now the rest: the notes are half in a notebook and half in a doc called notes-final-2, the record has not been touched since May, and the follow-up should go out today. It goes out at 10pm, written from memory, and you lie awake wondering whether you promised her the worksheet or the workbook.

By Thursday the call is a blur. The work was good; the holding of it leaked.

The 3 minutes after

You say "I just finished a call with Ana" and paste the notes. Ana's file gets a new entry, with her words kept exactly as she said them. The two promises land on their own dated lines: the worksheet is yours, the numbers she owes you are hers.

A follow-up draft appears in your voice, ending in your sign-off, and waits for your yes. You change one line and send it yourself, while the call is still warm.

Thursday, before her next session, "where do things stand with Ana" is one screen.

The draft is built from your notes and your sign-off, so what goes out is your follow-up in your words, and the sending stays yours.

The whole loop

From raw notes to a record that holds

Six moves that live inside your own system. You bring the notes; the pack keeps the thread.

1
End

The call ends, you grab what you have

Typed notes, a voice memo transcript, scribbles on paper. The pack starts where the call ends and works with whatever you already do.

2
Paste

One line and the notes

Say "I just finished a call with Ana" and paste. Claude reads Ana's file first, so today's update lands against the whole history instead of a blank page.

3
Record

The person's file updates

A new entry, newest first: a plain summary, her words quoted verbatim where the exact words matter, where things stand refreshed. You see the full update before it saves.

4
Promises

Each promise gets its own line

What you promised and what they promised, dated and kept separate. A promise stays visible until it is kept or released, and kept ones get marked, never deleted.

5
Draft

The follow-up appears and waits

Built from your notes, in plain words, ending in your sign-off. It is shown to you in full, and it goes nowhere until you say so.

6
Send

You send it, from your own email

Copy, tweak, send. The pack has no way to send anything, by design, so the follow-up your client receives is one you read and chose.

On Friday, ask it what you have promised

There is a sweep inside: ask "what have I promised" and every open promise across all your people comes back on one screen, by person, oldest first, with the date it was made. Yours and theirs. Two minutes, and nothing said on a call is quietly gone.

❤️

The record is the point

A fresh chat forgets the call by tomorrow. Ana's file holds what she said in May, what you promised her, and where things stand, so the next call starts where the last one ended. It is a Heart practice, and it lives in a system that is yours.

The part that makes it yours

It holds your actual clients

Generic CRM fields fit a client who exists on average. Yours said something specific on that call, and the record keeps it.

Their words, kept verbatim

"I want this year to feel lighter" never becomes "client expressed a desire for reduced workload." The exact words are what you build the next call on, and the file keeps them as said.

Promises never get lost

A promise made on a call gets its own dated line, marked whose it is, and it stays until kept or released. The weekly sweep reads them all back, oldest first, no judgment.

The draft waits for you

Every follow-up is a draft in your voice with your sign-off, shown in full. You approve it and send it yourself, so nothing reaches a client without passing through your hands.

What it will honestly tell you it cannot do

It cannot join or record your calls: you bring the notes or a transcript from whatever you already use, and the pack starts where the call ends. It cannot send email, by design: every follow-up is a draft that waits for your yes, and it will never tell you something went out. And the record is only as complete as what you feed it after each call: skip five calls and the file has a five-call gap, which it will say plainly instead of papering over, because a record you cannot trust is worse than no record.

A peek inside

What you are adding

Plain files that drop into your root system, in folders you own and can open in anything.

# after-every-call/ drops into .claude/commands/ and your root
after-a-call.mdthe main move: paste the notes, the record updates, the promises land, the draft appears
person-page.template.mdone file per person: who they are, where things stand, promises, call history
follow-up.template.mdthe draft email shape: what you talked about, what happens next, your sign-off
CLAUDE.md (starter)a minimal root, so it runs standalone if you do not have the full system, with the promise sweep and the one-screen read-back built in as rules
README.md + SETUP-GUIDE.mdthe overview and the install, add-on or standalone

The promises

The rules it never breaks

Built the same way as the rest of your system, because your client relationships are on the line.

The follow-up is always a draft

It writes, shows, and waits. You approve it and send it from your own email. The pack has no way to send anything, and it will never claim it did.

Your client's words stay verbatim

It cleans an obvious typo and touches nothing else. What they said, as they said it, is the material the next call is built on.

Promises made on calls are sacred

Each one gets its own dated line and never disappears: kept gets marked kept, released gets marked released. Nothing you said to a client gets lost or reworded.

It is yours, on your machine

Your clients live in plain markdown files you can open, read, and edit yourself, in a folder you own rather than on a platform you rent by the month.

How to use it

Drop it in, then bring it one real call

Install takes about 5 minutes. The after-a-call run takes about 3 once the notes are pasted.

1

Drop it into your system

Download and unzip into your root folder. The skill joins your existing skills and the people folder gets a home. No full system yet? It brings a small starter so it runs on its own.

2

Finish a call, paste the notes

Say "I just finished a call with..." and paste whatever you have, messy is fine. The file update shows in full before it saves, and the draft waits for your yes.

3

Then it is call, paste, send

Ask what you have promised on Fridays, and ask where things stand with anyone before you write to them. The record does the holding, so your head does not have to.

# one line in your root CLAUDE.md, once - After every call: when I say "I just finished a call" or paste call notes, read after-every-call's skill and run it. When I ask what I have promised or where things stand, answer from the people/ files.

The next follow-up goes out while the call is still warm.

Paste the notes from your next client call, read the draft, change one line, and send it yourself: three minutes instead of thirty, with the promises captured where you will see them again. Your record starts holding tonight.

Add it to your system

Want to build it live with us instead? Come to the next live session.