Key takeaways
- A useful note covers what happened, what you learned, the next step and date, and why you reached out.
- Write for a teammate who has never seen the account, because in three months that teammate is you.
- Logged outcomes are what make tomorrow's account list smarter, so record them every time.
Good CRM notes are short, structured records that let anyone who opens the account later understand what happened and what to do next. To write them, record the same four things in the same order every time: what happened, what you learned, the next step with a date, and the signal behind the outreach.
Most notes do not do that. They are written fast, in shorthand, for the person who wrote them, on the day they wrote them. Three months later, even that person cannot remember what “LVM, follow up Q3” was about.
Why CRM notes fail
Notes usually fail for a few predictable reasons:
- They record activity, not meaning. “Called, no answer” tells you the rep was busy. It does not tell you anything about the account.
- They use private shorthand. Abbreviations and nicknames make sense in the moment and nowhere else.
- They have no next step. Without a dated next action, the account drifts until someone stumbles on it.
- They lose the “why.” The reason the rep reached out in the first place, such as a new leader or a hiring push, is not written down. The next rep has to rediscover it.
- They are buried. Important details sit inside a long, unstructured paragraph that nobody reads.
The fix is not writing more. It is writing the same few things, in the same order, every time.
A simple note structure
Use four short parts. Each one should be a sentence or two.
- What happened. The action and the result. Who did you talk to, through which channel, and how did it go?
- What we learned. Anything new about the account, the person, or the problem. This is the part future you needs most.
- Next step and date. The specific next action, who owns it, and when it is due.
- Source of signal. Why you contacted this account now: the change you saw, where you saw it, and when.
If you can only write one part, write the next step with a date. If you can write two, add what you learned.
Why the source of signal matters
Signals are evidence that something changed at an account, not proof that it wants to buy. Recording the source lets the next rep check whether the reason still holds. A leadership change from last week is a timely reason to call. The same change from eight months ago may not be. The guide on B2B buying signals explains how to judge signal strength.
Before and after examples
These examples use a fictional 400-person freight software company.
A call with a real conversation
Before:
Spoke w/ JM. Interested-ish. Send info. F/u later.
After:
What happened: 12-minute call with the new VP of Sales (started last month). Open to a follow-up conversation.
What we learned: They are splitting one territory into three regions next quarter and have not decided how accounts will be assigned. Current process is a spreadsheet owned by sales ops.
Next step: I send a short summary of how other teams handle territory splits by Thursday. Ask for a 20-minute call with sales ops the week after.
Signal: Leadership change, from the company’s announcement on their news page, seen three weeks ago.
The second note lets anyone on the team continue the conversation without asking the original rep a single question.
A call with no answer
Before:
No answer. LVM.
After:
What happened: Called the director of operations, no answer, left a 20-second voicemail referencing the new regional office.
What we learned: Nothing new. Direct line confirmed as correct.
Next step: Email on Tuesday with the same angle, then one more call attempt on Friday.
Signal: Expansion into a second region, from a press release dated this month.
Even an unanswered call produces something useful: a confirmed phone number, a planned sequence, and a reason that the next attempt can build on.
A clear no
Before:
Not interested.
After:
What happened: Replied to my email and said they renewed a competing tool last month.
What we learned: Contract renewal cycle appears to be annual, in the autumn.
Next step: No outreach now. Revisit in the summer before their next renewal. Marked do-not-contact until then.
Signal: Hiring for three sales development roles, from their careers page, seen two weeks ago.
A “no” with a reason and a date is one of the most valuable notes you can write. It stops teammates from calling too soon and tells someone when to try again.
Log outcomes that improve tomorrow’s plan
Notes are not just for people. If your team ranks accounts using fit and recent signals, the outcomes you log should feed back into that ranking.
Make a habit of recording the outcome as a field, not just in free text, whenever your CRM allows it:
- Connected, positive. The account may deserve a higher place tomorrow.
- Connected, not now. Lower its priority and set a revisit date.
- No answer. Keep it in the sequence; the signal may still be valid.
- Wrong person. Note who the right person is, if you learned it.
- Opted out. Stop all outreach and make sure the opt-out is recorded everywhere.
When outcomes are logged consistently, tomorrow’s list can skip accounts that just said no, move up accounts that showed interest, and prompt follow-ups before they go stale. The guide on CRM data versus a daily execution plan explains how this record turns into a ranked daily list.
A few habits that make notes stick
- Write the note within minutes of the conversation, before the next call.
- Use full names and titles, not initials.
- Put dates on everything: the call, the signal, the next step.
- Keep each part short enough to read on a phone.
- Never record sensitive personal details. Keep notes about the business, not the person’s private life.
The rule to remember
Write every note for a teammate who has never seen the account: what happened, what you learned, the next step with a date, and the signal that started it. In a few months, that teammate will be you.
To see how logged outcomes shape the next day’s priorities, explore the daily attack plan.
Common questions
How long should a CRM note be?
Long enough to cover four things and short enough to read in under a minute: what happened, what you learned, the next step with a date, and the signal behind the outreach. For most calls and emails that is a few short sentences. A meeting with real discovery may need more detail in the learning section.
What should you never put in CRM notes?
Leave out sensitive personal details, such as health, family matters or anything about someone's private life, and avoid opinions about a person's character. Keep notes about the business, the problem and the next step. Write every note as if the prospect or a colleague could read it, because records are shared and kept for a long time.
Should SDRs and AEs use the same CRM note format?
Using the same basic structure helps, because anyone can pick up an account and find what they need in the same place. An AE's meeting notes may add deal details such as decision process or timeline, but the core parts stay useful: what happened, what was learned, the next step and the reason for the outreach.
