Independent consultants often live between two unhelpful extremes. At one end, follow-up depends on an inbox, memory and scattered calendar reminders. At the other, a full CRM asks for fields, stages and administration that make sense for a sales team but not for one person managing a modest number of valuable relationships.
There is a smaller system between them. It does not try to model every opportunity. It answers four practical questions: who is this, why does the relationship matter, what happens next and what happened last time?
Why the business card stack becomes a follow-up backlog
The problem is rarely a lack of good intentions. It is the number of small jobs created after the conversation: scan the card, create a contact, find the right note, add a reminder and perhaps copy everything into a CRM. Each handoff is an invitation to postpone the work.
That friction matters. In two pre-registered experiments, researchers found that people set fewer external reminders when reminder-setting required more physical effort. The study did not examine consultants or business cards, but it supports a useful design principle: make the future action easy to record at the moment the intention is formed. Read the open-access reminder-setting study.
Start with the job, not the software category
A CRM is designed to manage a broad commercial process. Your immediate job may be much narrower: remember the context behind a person and keep the next promise from disappearing.
If your work is mainly referral-led, project-led or built on a small number of trusted relationships, you may not need a pipeline for every conversation. You do need a dependable way to return to the right person at the right time with the right context.
The four records in a lightweight follow-up system
1. The person
Keep the contact methods you will actually use. Add company and role when they help distinguish the person. Avoid turning capture into a research project.
2. The context
Write a short note about the situation, need or shared interest. This should make sense months later without rereading an email thread.
3. One open next action
Use a verb, a concrete object and a date: “Send the process map on Tuesday.” One open action forces a useful decision and keeps your view small.
4. The outcome history
When you complete or attempt the action, record what happened. “Sent outline, asked for Thursday review” is more useful than a silent tick. The outcome gives the next action its context.
The loop: person → context → one next action → outcome → next action.
Why one next action works
A long task list attached to a person creates the same problem as a long sales pipeline: maintenance competes with the work. One next action shows the current commitment. When it is complete, you decide whether another is needed.
This is especially useful for consultants because the relationship can move between prospect, client, delivery partner, referrer and past client. A rigid stage often describes only one part of that history. A next action describes what you need to do now.
Use a daily view, not a relationship dashboard
Your working view should be boring and obvious:
- Overdue actions that need a decision.
- Actions due today.
- A short view of what is coming next.
For each item, choose one of three outcomes: do it, move it or close it. Do not let overdue actions become permanent wallpaper. If the relationship no longer needs attention, close the action and keep the history.
Connect to your existing system only when useful
Your calendar may be the best place for a timed meeting. Your accounting or project system may own active client work. A company CRM may need the qualified opportunity. The lightweight system does not need to replace any of them.
Use a deliberate handoff at the moment the other system becomes relevant. Export the record, add the calendar event or send structured data into an automation you control. Avoid automatic synchronisation until you know which data should move and which system is authoritative.
A weekly maintenance habit that takes less effort
Once a week, review three small groups:
- Overdue: complete, reschedule or close every item.
- No next action: check only recent or commercially important relationships.
- External handoff: move records that have genuinely reached another workflow.
Do not review every contact. A lightweight system stays lightweight by showing the decisions that are live now.
When you really do need a CRM
Move to a full CRM when you need shared ownership, permissions, pipeline governance, forecasts, repeatable campaigns, reporting or a common system of record across a team. Those are real needs. They are simply different from personal post-meeting follow-up.
You can also use both. Keep the immediate capture habit close to the meeting, then hand qualified records to the CRM when the shared process begins.
The smallest system you will keep using wins
Reliability rarely comes from capturing more fields. It comes from making the next decision easy and returning to it at the right time. Start with the person, context, one action and outcome. Add complexity only when a repeated, valuable workflow proves it belongs.
If the hardest part is the message itself, use the guide to following up after a networking event without sounding generic.
Turn the card into an action before it becomes admin.
Followup is a local-first post-meeting companion, not another CRM. Free trial at launch, then a paid subscription.