TL;DR:
After a meeting, update four things on the deal: stage, amount, next step and contacts.
Change a field only if the meeting gave you evidence for the change.
Keep the free-text note short and put facts in fields, where they can be filtered.
Your notes from a meeting are for you: fragments, arrows, half words. The CRM is for everyone else, including future you, and for the reports your team reads on Monday. The job is translating one into the other, and doing it the same day so the details are still fresh.
What an update should change
Not everything in your notes belongs in a field. Ask what a colleague would need to see at a glance: where the deal is, how big it is, what happens next and who is involved. Everything else can live in a short note.
Before you begin
Open the deal record and your notes side by side.
Know your team's stage definitions. If a stage means "proposal sent", you move into it only after sending one.
Have the date of the meeting and any dates people agreed to.
Check whether your CRM keeps a history of changes, so that a mistaken edit can be undone.
Step by step
Underline the facts in your notes: Mark anything that is a decision, a number, a date or a name. Leave opinions and small talk.
Decide on the stage: Compare what happened with your stage criteria. If the criteria are not met, leave the stage alone.
Update the amount only if it was discussed: Change it when the scope or price actually changed, and mention why in the note.
Write the next step with an owner and a date: One action. If there are several, put the most urgent in the field and the rest in the note.
Add or correct contacts: Add any new person who joined, with their role in the decision. Fix any role that you learned was wrong.
Write a three-line note: What happened, what was agreed, what is uncertain.
Worked example: updating a deal after a call
The deal is a reminder service for a clinic group. Before the call it sits at Discovery with an estimated amount of 3,000. The names and figures are invented for this example. Your messy notes from the call read:
dana + new person Marcus (finance)
likes demo, wants 2 locations first not 4
then maybe rest in spring
budget ok if under 2k for pilot?
I send quote fri 14
marcus signs offNow go through the fields one at a time.
Field | Before | After | Why |
|---|---|---|---|
Stage | Discovery | Discovery | The quote has not been sent yet, so the proposal stage is not reached. |
Amount | 3,000 | 2,000 | Scope shrank to a two-location pilot, and the budget they named is under 2k. Use the pilot figure, not the guess. |
Next step | none | Sam sends quote, Fri 14 Nov | Stated by you on the call, with a date. |
Contacts | Dana (operations) | Dana (operations), Marcus (finance, signs off) | Marcus joined and has approval. |
Check each decision against the notes. The amount did not move to 2,000 because you hoped for it; the notes say pilot budget under 2k with two of four locations. If a number is unclear, write the uncertainty in the note and keep the amount as a labelled estimate. The note could read:
Call 12 Nov. Demo went well. Scope is now a pilot at two locations; the other two may follow in spring. Marcus (finance) approves the budget, which they indicated is below 2,000. Open question: exact pilot price to be set in the quote.Notice the difference between what was agreed and what is uncertain. The next reader can see at once that the 2,000 is not a signed figure.
Mistakes to avoid
Moving the stage because the meeting felt positive.
Leaving the old amount in place after the scope changed.
Entering a next step that is a wish, such as "touch base soon".
Burying a new decision-maker in the note instead of adding them as a contact.
Overwriting history. Add the update; do not erase what the record said before unless it was wrong.
A quick test before you save
Read the finished record as if you were a colleague taking over the deal tomorrow. Can you tell where the deal stands, what it is worth, what happens next and who to talk to? If you must open the old email thread to answer any of those, the update is not finished.
A second test is to look at each field you changed and point to the line in your notes that justified it. If you cannot point to one, change it back. This habit keeps your pipeline honest, because every number and stage traces to something that was said.
Last, check dates. A next step without a date is a hope, and a date in the past is a reminder that has already failed. If a date was agreed in the meeting, copy it exactly as spoken and confirm it in your follow-up email so both sides hold the same one.
Doing it faster
Take notes during the meeting in the order of the fields. Then the update is a copy and tidy job. Do it in the five minutes after the call, while you still remember. If you like having a second check, DuckyHelper can read your notes and the CRM form on screen and ask you out loud why you are changing a field.
Frequently asked questions
What if my CRM has no field for something important?
Put it at the start of the note in a consistent format, for example "Decision-maker: Marcus". Then you can search for it.
Do I need to update after every email?
No. Update when something changes in the stage, amount, next step or contacts, or when a call or meeting happened.
