How to Automate Meeting Notes into Action Items and Client Recaps for a Consulting or Accounting Firm

A consulting or accounting practice runs on meetings, and the value of a meeting is decided afterwards. What was agreed, who owes what, and by when. If nobody writes that down within a day, the next meeting opens with fifteen minutes of reconstructing the last one.

The write-up itself is not hard. It lands at the wrong moment, at the end of a call, thirty seconds before the next one, and it loses every time.

This guide turns the recording or transcript of a client meeting into three things: an internal action list, a client recap email, and tasks in whatever system your team already opens. Setup takes about two hours, and there is a manual version you can run after your next meeting with no setup at all.

What you are building

One capture habit and one automation. The meeting is recorded or transcribed, an AI assistant splits the transcript into a fixed set of outputs, and the drafts land where you approve them. The recap goes to the client the same day, in your wording, with the commitments on both sides written down.

Tools: the meeting software you already use, most of which will produce a transcript, or a phone recorder for meetings held in a room. Plus an automation tool such as Zapier, Make or n8n, an AI assistant such as ChatGPT or Claude, and your task list or practice management system.

The manual version needs none of the wiring. Paste the transcript into the assistant with the prompt below, copy the four outputs where they belong and send the recap. That is about six minutes per meeting, and it is worth running twice before you automate anything, because you will change the prompt both times.

Step 1: get consent, and get it on the record

Recording a client meeting is not a technical decision. Say at the start of the call that you record client meetings so the notes are accurate, say where the recording is kept and how long you keep it, and ask. Put the same sentence in your engagement letter so it is never a surprise on the day.

If a client says no, the workflow still runs. Dictate a three-minute summary into your phone the moment the call ends and feed that in instead. Nothing downstream cares whether the input is a transcript or a voice note.

Step 2: the splitter prompt

One prompt produces everything, because the action list and the client recap have to agree with each other. Two separate prompts drift, and the drift is always in the commitments.

The deadline instruction matters more than it looks. A recap that turns we will try to get that over to you next week into we will deliver on Tuesday creates an obligation nobody agreed to, and you find out about it when the client chases.

Step 3: make the recap sound like your firm

The recap is the only output a client reads, and the default output of a language model reads like a firm that charges by the adjective. Give it a sample and a set of rules, once.

Save the rules block. It goes at the top of the splitter prompt from then on, and the recap stops needing a second pass.

Step 4: wire it up

1. 1The transcript or recording lands in one folder, or your meeting tool sends it to your automation tool directly when a call ends.
2. 2A new file triggers the scenario. If the input is audio, transcribe it first.
3. 3Send the transcript to the assistant with the splitter prompt and the voice rules.
4. 4Split the response on the four headings.
5. 5Create one task per line in the ACTIONS section, with the owner and the deadline. Put anything marked NO DATE AGREED into a review list rather than the task list.
6. 6Save DECISIONS and OPEN QUESTIONS to the client file, and put the CLIENT RECAP in the drafts of whoever ran the meeting.
7. 7Notify that person that a recap is waiting, with the client name in the subject line.

Keep the client recap as a draft permanently rather than only for the first fortnight. It is correspondence about engagements and money, and thirty seconds of reading before sending is not a bottleneck worth removing. Everything else can go straight through.

Send the tasks into the system your team already opens every morning. A perfect action list living in a new tool nobody has a habit of checking is the most common way this build quietly dies in week three.

Run the whole thing on an internal meeting first. The output of a badly tuned splitter prompt is a confident list of commitments nobody made, and it is far better to find that out in front of your own team than in front of a client who now believes you promised something on Tuesday.

Step 5: use the open questions

The OPEN QUESTIONS section is the part most firms throw away, and it is the one that compounds. It is a list of things a client raised that nobody has answered yet, which is also a list of work they have not asked you for yet.

Keep them in one place per client. Before the next meeting, read the list. Arriving with an answer to something raised three weeks ago and never chased is the cheapest way to look like the firm that pays attention, and it costs a minute of preparation.

What changes

The recap goes out the same day, every time, instead of whenever somebody has a gap. The action list lives in the system rather than in three different sets of handwriting. And the meeting stops being a thing you have to remember and becomes a thing that is written down.

Turning what was said into what is written is the whole subject of Workflow 03: Talk, Don't Type, the AutomateFirst module that turns short voice notes and recordings into emails, briefs and task lists. This guide is one complete build from it, free. The playbook has seven workflows for one payment of $297, with a 30 day refund.