Sales CRM: How to Organize Deals, Ownership, and Next Actions

A CRM doesn’t sell. It exists to answer three questions at any moment: which deals are open, who’s working them, and what’s the next thing to do on each one. If the system you have doesn’t answer these three, the problem isn’t solved by adding fields.

The difference between a CRM that gets used and one that gets abandoned isn’t the tool. It’s whether the stages are defined so that two sales reps, looking at the same deal, would place it in the same stage.

Stages are defined with conditions, not feelings

“Contacted,” “interested,” “hot,” “closing” are labels everyone interprets their own way, and they produce a list that can’t be read. A stage is useful when it has an entry condition anyone can verify.

The rule that holds everything up: you move forward on facts, not impressions. A customer who sounds enthusiastic on the phone doesn’t move anything forward; a proposal that’s been sent does. The reverse movement matters too: a deal can go back a stage, and that has to be stated explicitly, or the list fills up with stalled deals sitting in advanced stages that nobody has the nerve to move back.

Three pieces of information that hold up everything else

• The contact person, with their role. Who uses it, who pays, and who signs are often three different people: recording only the first contact means finding out at the end that you needed to talk to someone else.
• The estimated value, with the basis for the estimate. A number thrown in helps nobody; a number next to “three systems at list price, maintenance excluded” can be discussed and corrected.
• The next action, with a date and an owner. It’s the field that decides whether the CRM is alive. A deal with no next action isn’t an open deal: it’s a hope.

A deal, from inquiry to signature

An illustrative example, for a company that sells systems with installation.

1. A request comes in from the website: a company asks if you provide maintenance on systems you didn’t install. A deal is created in “inquiry to qualify,” with next action “call by tomorrow” and an owner identified by name.
2. The call clarifies that there are three systems, that the contact is the plant manager, and that ownership makes the decision. Both names are recorded, the deal moves to “need defined,” next action “site visit next week.”
3. After the site visit, the proposal is prepared. Until it goes out, the stage doesn’t change: a draft document isn’t a proposal sent, and treating it as one skews the whole list.
4. The proposal goes out. Next action: “call back in a week if there’s no response.” Without this line, the document just sits waiting until someone remembers it, which is usually too late.
5. The customer asks for shorter response times. The deal enters negotiation, and what was requested and what was granted are recorded: the same request will come up again with other customers, and it’s information that concerns the offering, not just this deal.
6. It closes, one way or the other. If it’s lost, the reason is recorded by picking from a short list. If it’s won, the handoff starts to whoever invoices and whoever will do the work.

The last step is the one most often forgotten. A deal won but not handed off to whoever has to install it produces exactly the phone call nobody wants to receive.

Loss reasons are worth as much as win reasons

A closed list of five or six reasons — price, timing, a missing feature, chose a competitor, project postponed, no response — is worth more than a free-text field, because it can be counted and compared.

“No response” deserves a line of its own. If it grows, the problem isn’t the offering: it’s the follow-up that isn’t happening. It’s the only loss reason that depends entirely on you, and the only one that gets fixed without touching price or product.

Views and metrics that mean the same thing to everyone

Views exist to work with, not to report with. The three most used are: what do I need to do today, what’s been stalled too long, what’s closing this month.

• “Stalled too long” requires a threshold decided together, and a different one for each stage: a week of silence after a proposal isn’t the same as a month with no contact during qualification.
• The total value of open deals should be read with caution: adding up estimated figures with different probabilities gives a number that doesn’t correspond to anything. If you use it, always state what it includes.
• Every metric needs a one-line written definition. If “active deal” means different things to management and to sales reps, every meeting starts with an argument about the numbers instead of about the customers.

If the company closes few deals a year, statistical metrics won’t say anything reliable, and the CRM stays useful for a different reason: keeping the history of each customer and not losing the follow-up. That’s a legitimate goal, but it changes which fields are worth asking for and which aren’t.

What this guide doesn’t cover

This guide covers organizing the deal from the moment it exists. How inquiries arrive — from the website, email, messages, phone — and how to keep them from getting lost before they even enter the system is an upstream problem, with a dedicated guide. Building quotes from price lists and discount rules is also covered separately.