The Ramble Is the Brief: A Working Method for Client Voice Notes

There is a particular kind of message that lands on a Tuesday morning. It is three minutes and forty seconds long, recorded in a car somewhere near the A303, and it begins with “Right, so, quick one.” By the time it ends, the client has mentioned a launch date, changed their mind about the colour, remembered a meeting they had last week, and asked whether we can “maybe just make it feel a bit more premium.”

Voice notes are not the enemy. They are often the most honest form of brief a client will ever give you, because they have not yet tidied their thoughts into an email. The problem is that honesty is messy. Your job is not to scold them for rambling. Your job is to turn the ramble into something both of you can point at later.

Listen once without writing anything down

The temptation is to start transcribing immediately. Resist it for the first pass. Listen to the whole thing with your hands off the keyboard. You are not hunting for detail yet; you are listening for shape. Where does the energy go up? Which sentence sounds like a decision and which sounds like thinking out loud? Clients often announce the real brief halfway through, almost apologetically, after a run of context.

On the second listen, use a transcription tool if you like. In 2026 the automatic transcripts are good enough that there is no excuse for guessing at names or dates. But the tool will not tell you which sentence was a firm instruction and which was a stray thought about a competitor. That part is still yours.

Timestamp the decisions, not the whole recording

A full transcript is useful as an archive. It is not useful as a working document. What you need is a short list of timestamps tied to the things that actually change the job.

I use four labels: DECISION, DEADLINE, QUESTION and MAYBE. A decision is something the client has clearly settled — “we’re going with the shorter version.” A deadline is any date, even a vague one — “sometime before half-term.” A question is anything directed at you that needs an answer. A maybe is the dangerous category: “I wonder if we should also…” Those are not instructions yet. They are invitations to scope creep.

So the note might look like this:

• 0:18 — DEADLINE: launch on 4 December, assets needed a week before.
• 0:47 — DECISION: keep the existing logo, new typeface only.
• 1:22 — QUESTION: do we need a separate version for LinkedIn?
• 2:05 — MAYBE: “a bit more premium” — needs translation before it becomes work.
• 3:10 — DECISION: final sign-off with their marketing lead, not the founder.

That is a five-line document. It is also the skeleton of your scope.

Reflect it back in plain English

The next step is the one most freelancers skip: write the scope back to the client before you start. Not a formal contract, necessarily, but a clear mirror of what you heard. Start by thanking them for the voice note, because it genuinely is useful. Then give them the summary in their own language, with timestamps attached.

Something like: “Thanks for the voice note — really helpful. Here’s what I’ve taken from it: launch on 4 December (0:18), existing logo kept with a new typeface (0:47), and sign-off through your marketing lead (3:10). I’ve noted the LinkedIn question as something we can quote separately. On ‘more premium’ (2:05), I’ve interpreted that as tighter spacing, fewer colours and a more restrained image treatment — flag it if that’s off.”

The timestamps matter. They make the client feel heard, and they give you a shared reference point if memories differ later. They also save you from the dreaded “I never said that” conversation. You are not being pedantic; you are being organised.

Turn the maybe into a choice

A voice note often contains one or two maybes that the client has not yet decided how to pay for. Do not quietly absorb them into the job. Give them a clear fork: “I can include the LinkedIn adaptation in the current scope, which adds about a day, or we can keep it as a follow-on quote. Which would you prefer?”

That sentence does two things. It protects your time, and it lets the client stay enthusiastic without accidentally commissioning extra work. Most people are relieved to be asked. The ones who are not relieved were probably going to be difficult about the invoice anyway.

Keep the warmth, lose the ambiguity

There is a way to do this that feels bureaucratic, and a way that feels like good customer service. The difference is usually in the opening and the closing. Open with the thing you liked about their message — the clarity of the launch date, the useful context about the competitor, the fact that they bothered to record it while walking the dog. Close with a single clear next step and a date.

“If I don’t hear otherwise by Thursday, I’ll proceed on the summary above” is a perfectly reasonable sentence. It is not aggressive if you have just reflected their own words back to them. It is simply a door closing gently so the work can begin.

File the audio like you file the brief

One last habit: keep the original voice note and your timestamped summary in the project folder. Not because you will need to prove anything, but because six weeks from now, when someone asks why the typeface changed, you will not have to rely on memory. You will have a three-minute recording and a five-line document that says exactly what was agreed.

The voice note is not a lesser brief. It is just a brief that arrived in a less convenient format. Treat it with the same care you would give a written email, and you will find that the client’s enthusiasm survives contact with your process. That is the whole trick: keep the warmth, lose the ambiguity, and put the whole thing in writing.