A campaign proposal can pause for a sensible reason: the client is waiting for stock, changing a launch date or reviewing a budget. Several weeks later, a different account manager opens the record and finds only “follow up”. The team still has the proposal, but has lost the reason for the next conversation.
The useful note is usually short. Record what the client actually said, when the exchange happened, what the agency agreed to do and when it is appropriate to check again. If the client asked for contact after a planning meeting, keep that context alongside the review date.
That date is a prompt to review the relationship, not an instruction to send an automatic sales message. Circumstances may have changed, the client may have already replied elsewhere, or another colleague may own the next step.
Keep two different kinds of progress
A client relationship and a delivery project do not always move together. An existing client can have a completed campaign and a new proposal under discussion. Marking the whole client “complete” hides the conversation; marking an old project “active” just to retain the reminder distorts the delivery board.
For a small agency using Notion, the guide to keeping client follow-ups separate from project status describes a lightweight arrangement built around client records, projects and explicit next actions. It also distinguishes the last meaningful contact from the last edit to a database row. Updating a note today does not mean the client was contacted today.
NotionSolutions publishes this and other practical guides for people organising client work in Notion. A manual setup can suit a small list, although teams needing automatic email capture or a full sales history may be better served by a dedicated CRM.
Before the next account handover, try one record as a test. Could a colleague write an informed, considerate message using the note alone? If the answer is no, clarify the context before adding more fields to the system.