Many pipeline errors come from small updates that nobody made. A deal stays in the proposal stage after the buyer stops replying. A close date passes without anyone changing it.
Agree what each field means first
Habits only help when everyone records the same thing in the same way. Before you introduce them, agree a short definition for each field the pipeline report uses.
| Field | Example definition |
|---|---|
| Deal stage | The last step the buyer has completed, shown by buyer evidence that meets the stage's exit criteria |
| Amount | The value in the latest approved proposal or order, excluding tax, stated as one agreed measure |
| Close date | The date the buyer expects to sign, based on what they told you |
| Next step | The next agreed action with the buyer, with a date |
| Lost reason | One value from a fixed list, chosen when the deal closes as lost |
Choose one measure for amount, such as annual recurring revenue or total contract value. A report that mixes measures cannot be added up.
Write these definitions where people can find them, such as the help text on each field.
Set stage criteria from buyer evidence
Give each stage an entry and an exit criterion. Base each one on something the buyer did or said, so two reps put the same deal in the same stage.
| Example stage | Enter when | Exit when |
|---|---|---|
| Discovery | The buyer agrees to a meeting about a defined need | The buyer confirms the problem, a rough timeline and who else is involved |
| Demo | The buyer accepts a demo with people who will use or approve the product | The buyer asks for pricing or a proposal |
| Proposal sent | The rep sends a proposal the buyer asked for | The buyer gives feedback, asks for changes or starts approval |
| Negotiation | The buyer starts approval or contract review | The buyer signs or declines |
A rep's own activity, such as sending a proposal nobody requested, leaves the stage where it is.
Learn the ten habits
The last column shows how a manager or administrator can check each habit.
| # | Habit | Why it matters | How to check |
|---|---|---|---|
| 1 | Record a dated next step after every buyer conversation | A deal with no next step has often stalled without anyone noticing | Meetings logged this week on deals with no next step dated after the meeting |
| 2 | Move the stage only when the buyer meets its exit criteria | Stage drives forecast weighting, so early moves inflate the forecast | A sample of deals that changed stage this week, checked for the buyer evidence each stage requires |
| 3 | Change the close date when the buyer's timeline changes | Past close dates make the current month look fuller than it is | Open deals with a close date before today, plus a sample of notes that mention a new timeline |
| 4 | Keep the amount in line with the latest approved proposal or order | Old amounts carry early estimates into the forecast | The CRM amount compared with the latest approved proposal or order value |
| 5 | Log calls and meetings on the same day | Same-day notes are more accurate, and others can see the deal's history | Activities created a day or more after the activity date, where your CRM records both dates |
| 6 | Add each member of the buying group to the deal | A deal that rests on one person is exposed if that person leaves | Late-stage deals whose contacts differ from the buying group named in notes or the proposal |
| 7 | Close deals that meet the closure criteria, with a reason | Dead deals in the pipeline hide the real coverage gap | Lost deals with no reason, and stalled deals with no dated follow-up |
| 8 | Search before you create a company, contact or deal | Duplicates split activity and double-count pipeline | Records created this week that your duplicate report matches to an existing record |
| 9 | Use controlled values for categories you need to compare | Use a fixed list for categories such as lost reason or source; keep notes for context that does not fit a list | Lost reasons or sources recorded as "Other" or left blank |
| 10 | Review your own open deals before the weekly pipeline meeting | A short personal review catches gaps before the meeting | Counts for checks 1, 3 and 4 taken the day before the meeting and again that morning |
Checks 2, 3 and 6 need a short sample review, because a report cannot read the buyer evidence in notes. Five to ten deals a week is an example sample size.
In habit 7, a stalled deal has, for example, no logged buyer activity for 30 days. Set your own threshold to match your sales cycle, and use it in every report.
A buyer who goes quiet has not necessarily decided against you. Agree the follow-up steps first, such as two further contacts over two weeks. Close the deal as lost when those steps get no reply.
A single contact can be correct for a small purchase with one decision-maker. Check the contacts on the deal against the buying group the buyer described.
Give each habit a place in the week
Link each habit to a regular moment in the rep's day or week.
| When | Habits |
|---|---|
| Straight after each buyer conversation | 1, 5 and 6: next step, activity log, new contacts |
| When the buyer meets a stage's exit criteria | 2: stage |
| When a proposal or order is approved | 4: amount |
| Whenever the buyer mentions timing | 3: close date |
| Before creating any new record | 8: search first |
| Friday afternoon or before the pipeline meeting | 7, 9 and 10: follow up or close quiet deals, tidy fields, review your list |
Follow one deal through the habits
Example (illustrative): a mid-sized software deal over three weeks
An account executive meets a prospective customer's operations manager. Straight after the call, the rep logs the meeting and adds the operations manager as a contact. The rep then records a next step: a demo for the finance lead in ten days.
At the demo, the finance lead joins and asks for pricing. The rep adds the finance lead to the deal and sends a proposal two days later. The rep then moves the stage to "Proposal sent" and sets the amount to the approved proposal value.
A week later, the operations manager says the budget will not be approved until next quarter. The rep moves the close date into next quarter and notes the reason. The rep also sets a dated next step to check in after the budget meeting.
In the pipeline meeting, the manager sees the deal in next quarter with a clear next step. Without these updates, the deal would have sat in the current month and overstated the forecast.
Check the habits without a scoreboard
Build one data quality report that runs the checks from the table. Review it as a team each week, with totals for the whole pipeline, and fix gaps together.
- Create a saved report or dashboard with one view for each check that a report can run.
- Record the starting count for each check before you introduce the habits.
- When a check stays high across many reps, look at the process or the field itself.
Agree a target with the team. For example, a team might aim for most open deals to pass checks 1 and 3 within a month.
When a rep keeps missing the same habit, ask what makes it hard. The field may be in the wrong place, or the update may take too many clicks.
Introduce the habits a few at a time
Add two or three habits a week, starting with the next step and the close date. To train each role on these tasks, see role-based CRM training.
Avoid these common mistakes
- Making fields required at creation. People fill them with placeholder values. Require a field at the stage where the information exists, such as a lost reason when a deal closes as lost.
- Cleaning the data once and stopping. A clean-up without habits drifts back within a few months.
- Naming individuals in team reports. Public lists make people defensive. Share team totals and discuss individual records one to one.