How to Prep for a Client Meeting in Two Minutes (Without a Cloud CRM)

There’s a specific two minutes that most people who take client calls will recognise. The calendar notification fires, you’ve got a link to click, and you spend the gap doing frantic archaeology: who is this person again, which company are they at, what did we agree last time, and — the uncomfortable one — did I promise them something I haven’t done?

You can usually assemble the answer. It’s in there somewhere: a thread in your inbox, a note from three weeks ago, a task you wrote down. The problem is that it’s spread across four places and you have ninety seconds. So you join the call under-prepared, and either bluff it or open with “remind me where we left off” — which is fine occasionally and corrosive if it’s every time.

This post is about closing that gap, and specifically about doing it without moving your client relationships into somebody else’s cloud.

Why the scramble happens

The information you need before a call is almost never missing. It’s unjoined.

Your calendar knows who you’re meeting. Your notes know what you discussed. Your task list knows what you committed to. Your contacts know who they work for. Four systems, each holding one quarter of the answer, none of them able to answer the question you actually have — which is “brief me on this meeting.”

Nothing joins them because they weren’t designed to be joined. A calendar app has no concept of a deal. A task manager doesn’t know that “Dana” and “Dana Whitfield at Northwind” are the same person. So the join happens in your head, every time, on a deadline.

The manual version, and why it’s worth doing once

Before reaching for software, it’s worth knowing what “prepared” actually means, because the tooling only helps if you know what you’re asking it for. A useful pre-call brief answers five questions:

1. Who’s on this call, and what do they do? Names, roles, and which side they’re on.
2. What’s the commercial context? Is there an open deal, a renewal, a proposal outstanding? What’s it worth and what stage is it at?
3. What did we decide last time? Not the whole transcript — the decisions.
4. What’s outstanding on my side? The single highest-value question, because walking in owing something you’ve forgotten is how trust erodes.
5. What’s outstanding on theirs? So you can ask without it sounding like an accusation.

Doing that by hand takes ten to fifteen minutes per meeting. For two or three client calls a week it’s survivable. For a day of back-to-backs it doesn’t happen, which is exactly when you most need it.

What the meeting-tool market does about it

This is a genuinely contested space now, and it’s worth being accurate about who does what, because the answer depends on your situation.

Granola generates pre-meeting briefs from your earlier notes — it surfaces open threads from previous conversations before you join. If your context genuinely lives in your meeting notes, this is a good fit.

Otter’s Sales Agent briefs you before a call by reading Salesforce or HubSpot: latest exchanges, deal value, decision-makers, suggested talking points. It’s on Otter’s sales tiers, and it assumes you already run a cloud CRM.

Fireflies surfaces past meetings with the same attendees and your open action items, with deal status pulled from a connected CRM, on its paid plans.

Fathom is strong at interrogating meetings after the fact — you can query your history conversationally — but it doesn’t brief you beforehand.

Daylite, if you’re on Mac, has all the raw material: its activity pane shows a contact’s full history including email. You review it manually rather than getting an assembled brief, but the data is there and it’s mature.

So the honest summary is: if you already run Salesforce or HubSpot and don’t mind cloud transcription, several of these will prep you competently. Pick one.

The catch, if you’d rather not run that stack

Two things are true of nearly every option above.

The first is that the briefing is generated on someone else’s servers, from data held on someone else’s servers. For a lot of people that’s a non-issue. For anyone doing client work under confidentiality terms — legal, health, finance, or just a client who’d be unhappy to learn their commercial situation is being summarised by a third-party AI service — it’s a conversation you may not want to have.

The second is cost stacking. The good pre-call briefings read a CRM, which means you’re paying for the meeting tool and the CRM. A solo consultant can easily end up at $60–100 a month across a notetaker and a CRM seat, to answer a question about their own client list.

There’s also a subtler limitation. These tools brief you from meetings. They’re excellent at “what did we say”, weaker at “what did I commit to across every project this account touches” — because a commitment often isn’t made in a meeting at all.

The local-first version

The alternative is to keep the four systems in one place to begin with, on your own machine, so the join is a database query rather than an integration.

That’s the approach Life Manager Pro takes: contacts, companies, a deal pipeline, projects, tasks, notes, and calendar sync all live in a single SQLite file on your Mac. Because they’re one store, a pre-meeting briefing is something the app can simply assemble — no connectors, no sync, no second subscription.

Practically, it works like this. Right-click a calendar event and a floating panel opens with:

• The attendees, matched to your contacts by email, showing company and role — and a one-click add for anyone new.
• The company context: deals open against that account with stage and value, plus live projects.
• Decisions from previous meetings with those same people, pulled forward automatically.
• Open commitments on both sides, ranked by how closely they relate to this meeting and how soon they’re due, each tagged with why it surfaced.
• Your own talking points, saved against that event so a recurring meeting keeps its thread.

The action items are real tasks, so you can close them during the call rather than reading about them afterwards. And because it’s all local, it works with the network off, and nothing about your client list is transmitted anywhere.

It isn’t strictly better than the alternatives. If your team runs on HubSpot and you need shared prep across five reps, a cloud tool is the right answer and this isn’t. If you’re one person who’d rather not rent a CRM to be told about your own clients, the trade goes the other way.

Whichever route you take

The habit matters more than the tool. Answer those five questions before a client call and you’ll be better prepared than most of the people you’re meeting — whether you get there through Granola, a HubSpot integration, a Daylite activity pane, or a local dossier.

What shouldn’t happen is the two-minute scramble, three times a day, forever. The information is already yours. It’s just filed badly.