Follow-through
Every promise stays on the list until it is done.
For fractional CMOs and account teams making promises on every client call. Commitments from calls and notes stay tied to the client until marked done. Ask any time which ones are at risk.
- Granola
- Fathom
- ClickUp
The grind
Small promises are the ones that get dropped.
'I'll send that over Friday.' 'Let me check with the team.' You say it on a call and mean it, and then three more calls happen. The client remembers. You find out when they ask where it is.
- Promises live in transcripts nobody rereads.
- Client promises get forgotten too, blocking your work.
- You only learn a promise slipped when the client brings it up.
The flow
From 'I'll get back to you' to done
Promises are caught on the call
When a transcript comes in from Granola or Fathom (Fathom needs a paid Fathom plan), Armbrain pulls out the commitments: who promised what, and by when.
ingesttranscriptOr say it in plain words
Made a promise in a hallway or by text? Tell Armbrain, like 'Remember I owe Jordan the launch budget by Thursday', and it is saved as a commitment for that client.
store_memoryAsk what is at risk
Ask which commitments are at risk. Armbrain sweeps the client's mind for promises that are in trouble and shows where each one came from.
briefingcommitment_auditTurn promises into tasks
Add an owner and due date to create a task. If you use ClickUp, it syncs there.
workcreate_taskClose the loop
Check the open list before each call. When something is done, tell Armbrain. It stays on record so the next brief shows what was delivered.
worklist_tasks
The payoff
What you promised stays in front of you between calls.
Know what you owe and what you are owed before every call. Handle risky promises on Tuesday instead of explaining them on Friday. Next briefs show what was delivered.
Change these first:
CLIENTCOMPANY = Tidewater Logistics Armbrain, help me check my promises to CLIENTCOMPANY. 1. Switch to the CLIENTCOMPANY mind. 2. List every open commitment on both sides: what was promised, who owns it, who it was promised to, and the due date if there is one. 3. Tell me which commitments are at risk and why: late, close to due, or no clear owner. 4. For each at-risk item I own, suggest a next step and a task with a due date. Show me the list before you create any tasks. 5. Tell me anything the client is likely to ask about that I have not answered yet. Show where each commitment came from, with the meeting or note and its date. If a commitment has no due date or owner, flag it instead of guessing.
Example prompt. The client and people in it are fictional; replace them with your own.
Before you rely on it: A commitment list only knows the promises that reached the mind. If something was agreed by phone or in a hallway, save it yourself. Mark finished promises done so briefs stay accurate.
More use cases
- Meetings
Turn a meeting into decisions and tasks
Every call yields saved decisions, owned tasks, and a recap under the right client.
Read - Follow-through
Follow-up email in your voice
A follow-up that sounds like you and knows the call, waiting for your OK by default.
Read - Team
Hand work to your team or VA
Give your team the client context and a clear task, without the long briefing.
Read
Give your next client conversation a head start.
Start with one client's mind and one real question. 30 days free, no card to start.