How to prepare for a client meeting in thirty seconds
It's 9:52. You have a call at 10:00 with a client you haven't spoken to since March.
You open your inbox and search their name. You scroll back through a twelve-message thread looking for what was agreed. You open the shared drive to check which version of the proposal is current. You look for your meeting notes, unsure whether you took any. By 9:58 you've reassembled maybe 60% of the context, and you start the call with the uncomfortable sense that something's missing.
That quarter of an hour wasn't preparation. It was archaeology.
Preparation and reconstruction are not the same job
Preparing for a meeting means deciding what you're going to do in it: what you want to walk away with, what you need to tell them, the one question you can't leave without asking.
Reconstruction means recovering a state of knowledge you already had. You produce nothing. You buy back, at a premium, information you owned for free three months earlier.
Almost all the time spent "preparing for a meeting" is time spent buying back lost context.
And it's expensive for a specific reason: the information didn't disappear, it scattered. One fragment in an email thread, another in a shared document, a third in a phone call that left no trace at all. Reconstructing means joining those by hand, under time pressure, eight minutes before the call.
Why the usual answers don't fix it
The company CRM. It's built to track a sales pipeline: what stage, what value, what probability. Those are the questions a manager asks when reviewing a forecast, not the ones you have at 9:52. No field in it answers "what did we actually agree last time?"
Notes in your inbox. Email preserves what was written and nothing of what was said. But the meetings that matter happen out loud, and that's where the real decisions get made. The thread keeps a record of the logistics, not the substance.
Your memory. It's excellent at impressions and poor at dated facts. Six months on, you're certain "it went well." You no longer know who was chasing whom, or why the budget slipped to the next quarter.
What all three share: they're consulted at the moment of need, long after the only good opportunity to do this properly has passed.
The work belongs at the exit, not the entrance
The reversal fits in one sentence: your next meeting gets prepared at the end of the previous one.
Three minutes after hanging up, you hold for free what will cost you twenty minutes in three months. The context is still intact, you need no act of recall, and you know exactly what matters — because you just lived it.
That's a complete inversion of the cost. Three minutes while warm, once, against twenty minutes cold, every single time.
The four lines that do the job
This isn't about writing minutes. Minutes are a document for other people. What you need is a note addressed to yourself, six months from now.
Four lines, straight after the meeting:
- What was decided. Not the discussion, the conclusion. "Delivery pushed to October, they're briefing their director."
- Who owes what, and by when. Each commitment with its date. This is the line you'll re-read most often.
- What was left unresolved. Open questions are precisely where the next conversation starts. They're also the first thing you forget, because no decision pins them down.
- One human detail. They're relocating in September, a colleague is taking over the account, they hate Monday morning calls. This line is useless today and decisive six months from now.
Two rules make it hold. Always date it — "they've just hired someone" means nothing if you don't know when it was written. And attach the note to the person, not the project. Projects end, relationships continue, and the name is what you'll be searching at 9:52.
What preparation becomes
With that timeline available, twenty minutes turns into a re-read.
You open the client's record. You see the last four exchanges in order, with their dates, their decisions and their open questions. You read bottom to top. Thirty seconds later, you know where you stand.
Which leaves time for the real preparation — deciding what you want out of this call. That's the work with actual value, and it's exactly the work that last-minute archaeology eliminates first.
It also produces the most visible effect on the other side of the call. You open with: "Last time you were waiting on your director's answer about the October slip — where did that land?" Nobody thinks they have a good system. They think: this person is genuinely on top of my account.
In Keepsake, that's what a contact record is: every note, task and interaction accumulating into one dated timeline, so the pre-call re-read happens on a single screen.
The arithmetic nobody runs
Take the number of recurring meetings in your week and multiply by fifteen minutes of reconstruction. You get a number that appears on no timesheet, because it's distributed in ten-minute slices immediately before each call.
You're not losing that time because you're disorganised. You're losing it because you write at the wrong moment.
Three minutes after, instead of twenty minutes before. It's the same work, moved — and moved, it costs seven times less.