From client meeting notes to a ready-to-review follow-up.

What this page is

Illustrative example using fictional information—not customer work. It is not a live demo. Nothing here was executed against a real inbox, calendar, or client file. The notes, recap, email, action list, and flags are a synthetic fixture so you can see the shape of the work.

The job is narrow. An independent consultant — Jamie — leaves a client meeting with Sample Studio and needs a recap, a follow-up email, and an action list. The facts are already in the notes. The rewrite is the work.

Illustrative example using fictional information—not customer work.

Client: Sample Studio — Maya Chen, owner
Consultant: Jamie
Date: Tuesday working session

Maya wants a written recap after each Tuesday check-in so her small team knows what changed.

Open items:
- Northline brand-kit proposal. Jamie said a draft can go out Thursday.
- April sprint invoice question. Maya will send the line items.
- Intro to their operations lead. Name was not given.

Budget mention: "$4,800 if the original scope holds." Jamie did not confirm that this is the current number.

Maya asked for a shared folder. Jamie did not confirm which tool — Drive or Dropbox.

Next check-in proposed Thursday 2:00. Maya said she would confirm.

Jamie promised a recap and a follow-up email the same day.

Sample Studio — Tuesday working session recap

Decisions
- Jamie will send a written recap after Tuesday check-ins so the Sample Studio team can see what changed.

Open items
- Northline brand-kit proposal: Jamie draft by Thursday.
- April sprint invoice: Maya sending line items.
- Intro to the operations lead: name still needed.

Next meeting
- Thursday 2:00 proposed. Waiting on Maya to confirm.

Not confirmed
- $4,800 figure. Shared-folder tool. Operations-lead name.

To: Maya Chen, Sample Studio
Subject: Recap and next steps from Tuesday
Status: Draft — not sent

Hi Maya,

Here is a short recap from Tuesday, for you to review before I send anything onward.

I will have a Northline brand-kit proposal draft to you by Thursday. Once you send the April sprint invoice line items, I will mark that question in the next note. I still need the name of your operations lead before I write that intro.

Two items I will not put in a client-facing note until you confirm them: the $4,800 figure, and which tool you want for the shared folder.

If Thursday at 2:00 still works, reply yes and I will hold it.

Jamie

This is a labeled illustration, not a live demo. Nothing here was sent or saved. A real workflow would wait for Jamie to review the recap, email, and flags before any message left the machine.

How I decide

I start with three questions. Are the notes already written down? Can a person review a recap in one glance? Will that person actually send the email, or edit it, or discard it? If any answer is no, I shrink the job or I leave it alone.

A useful recap is narrow. Decisions. Open items. Next meeting. Missing facts flagged, not filled in. The agent should not invent a name, a price, or a meeting time that was not confirmed. That is why the Sample Studio fixture leaves $4,800, the operations-lead name, the shared-folder tool, and Thursday 2:00 as flags.

I also look at the tools you already pay for. Notes plus email is enough. A new CRM is not the first move. If you later want the same facts written into a tracker, that is a second step — after the recap path is boring. That order is in the sample Audit.

When this applies

It applies when you already take notes and still rewrite them three ways. Recap. Email. List. It applies when the next email is already obvious and still does not go out because you are copying the same sentences. Someone named will look at the draft before it leaves.

It also applies when the cost of a dropped ball is a late recap, not a legal or money event. If you want the first workflow on an Audit, this is a common pick because review is fast and the rule already exists. Read what to automate first.

When it does not

It does not apply if there is no named reviewer. “Whoever has a minute” is not a reviewer. I will not build an unsupervised send to cover for a missing owner.

It does not apply if the follow-up is really a negotiation, a pricing exception, or an apology. Those stay with a person. The agent can fetch the last note. It should not make the exception. It also does not apply if you want a fully autonomous no-review agent that sends on its own.

Human control, evidence, ownership

You review the output before anything is sent or saved. A named person approves client-facing or sensitive actions. You keep the prompts, the permission plan, the runbook, and the workflow map.

The evidence on this page is the fixture: input notes beside the draft recap, email, action list, and missing-info flags. The evidence on a paid Audit is a written map, scored opportunities, and a refund if I cannot find one worthwhile workflow.

Cost and risk

Company path: start with the $1,250 Audit. A later Business build is quoted and typically $3,750–$7,500. Remaining after the Audit credit is $2,500–$6,250. 50% to start is half of that remaining balance. One person buying for their own notes: the $1,495 Personal setup can cover drafts you approve. Unsure: the $199 Fit review or tell me the task.

The real risk is not “the draft sounds slightly off.” The real risk is an unsupervised send, a price that was never confirmed, or a name the notes never contained. I keep send and save behind a named person. Custom AI engagements commonly fall well beyond this range. Effortless Agents is intentionally scoped around one practical workflow at a time.

FAQ

Next step

If this is the work you want off your plate, tell me the task or start with the Audit. If it is just you and your own notes, Personal setup may be enough. More paths live on the examples hub.