Calendar as a BD Instrument: Capture, Follow-Up Cadence, and Meeting Memory

A partner's calendar is the most honest artefact in the firm. Time-sheets describe what was billable. Emails describe what was said. The calendar describes where attention actually went — which clients, which prospects, which conferences, which internal meetings, which lunches that got moved three times and finally happened. For business development purposes, that record is gold, and most firms ignore it.

The reason is mechanical. Calendars sit in Outlook or Google, the CRM sits somewhere else, and nobody has the time to manually log a coffee with a long-standing client as a "business development activity." So the coffee happens, the relationship deepens, and the firm's system of record knows nothing about it. Multiply that across forty partners and you have an enormous blind spot.

Capture is the first problem

The fix is not asking partners to log things. That has been tried for thirty years and it does not work. The fix is reading the calendar directly and inferring the BD-relevant events from it.

A meeting with an external attendee whose domain matches a client of the firm is, almost certainly, a client touchpoint. A meeting with an attendee whose domain matches a prospect on a target list is, almost certainly, a BD meeting. A recurring internal meeting with the same five people every Tuesday is not BD and should be ignored. The rules are not complicated; they just need to be applied consistently, which is a job for software rather than humans.

Lexi handles this in LeadLex by reading the partner's calendar with her consent, classifying the events, and writing the relevant ones to the relationship record. The partner sees a draft, approves or corrects, and moves on. The cost in attention is seconds per week.

Follow-up cadence is the second problem

A meeting that does not produce a follow-up within a week is, statistically, a meeting that produced nothing. Every BD professional knows this and most partners know it too. The gap is not understanding — it is execution under the pressure of a busy practice.

A useful cadence rule for IP work looks something like this. A first meeting with a prospect gets a follow-up within forty-eight hours, with a specific reference to something discussed. A client touchpoint that surfaced a new matter gets a written confirmation the same day. A conference contact gets a connection request and a short note within a week, while the context is still warm. A dormant relationship that has been touched for the first time in a year gets a structured re-engagement sequence, not a one-off note.

None of this is novel. What is novel is having a system that watches the calendar, knows which cadence applies to which type of meeting, and drafts the follow-up so the partner is editing rather than composing from scratch. The draft is wrong sometimes and the partner fixes it. The point is that the alternative — the partner remembering on the train home and then forgetting by Tuesday — is worse.

Meeting memory is the third problem

The relationship that matters most to an IP firm is usually the one that has been running for fifteen years. That relationship has hundreds of meetings in its history and nobody remembers what was discussed at any particular one. When the partner is preparing for the next meeting, she relies on memory and on whatever she can reconstruct from her inbox in the ten minutes before the client arrives.

A calendar-aware BD layer can do better. It can pull the last three meetings with the same person or company, surface the matters that were live at the time, note any commitments the partner made that have not been delivered on, and present the lot as a one-page brief. Lexi does this in LeadLex and the meeting brief becomes a standard artefact rather than a luxury.

What this is not

This is not surveillance. The partner controls what is read and what is logged. It is not a substitute for relationship work — Lexi cannot have the coffee, only prepare for it. And it is not legal-substance work. The calendar tells you the meeting happened; the substance of the matter sits with the partner and the file.

What it is, is the smallest possible intervention that converts an honest record the firm already keeps into BD output the firm currently does not produce.

Related: The Monday Morning BD Review. Document Management and the BD Picture. What a Relationship Strength Score Actually Measures.