Every CRM has tasks. We deliberately do not, and the reason is not branding.
The word you use for something shapes what people put in it. Call a list “tasks” and it fills with everything: reminders, admin, notes to self, an item about updating the pricing sheet, a follow-up from a conversation three weeks ago that has since become irrelevant. Within a month it is long enough that nobody reads it properly, and the one thing on it that would have advanced a deal is sitting fourteen rows down between a expenses reminder and a note about a webinar.
That is not a failure of the person maintaining the list. It is what happens when a container has no entry criteria.
A Move has a definition
In PragmaCRM, a Move is a real-world action that advances a specific lead or deal. A call, an email, a meeting, a follow-up. It has a type, a due date, an owner and a record it belongs to.
What it is not is equally important. It is not an internal admin item. It is not a reminder to update something. It is not a note. Those things are real work, but they belong somewhere else, because mixing them into the same list is exactly what destroys the list’s usefulness.
The entry criterion is simple: does doing this thing move the deal forward from the buyer’s side? If yes, it is a Move. If no, it is something else.
What the constraint buys you
Three things follow from having a list that only contains one kind of item.
A deal with no next Move is visibly stalled. This is the single most useful signal in pipeline management and almost no team has it, because in a general task list the absence of an item means nothing. It could mean the deal is stuck or it could mean the rep keeps their follow-ups in their head. When the list has one purpose, an empty slot means something specific.
The daily list is short enough to actually work. A rep opening a queue of eleven actions, each attached to a named deal, will work through it. The same rep opening a list of forty mixed items will triage, then defer, then eventually stop opening it.
Activity data becomes meaningful. If you count completed tasks you are counting a mixture of sales work and admin, and the number tells you nothing. If you count completed Moves you are counting attempts to advance deals, which is a number a sales manager can actually coach against.
Why it has to be attached to a record
A Move always belongs to a lead or a deal. It cannot float free.
This matters because it is what connects effort to outcome. When every action is attached to a record, the history of a deal becomes an honest account of what was done to win it, and you can see at the end of the quarter that the deals you lost had four Moves against them while the deals you won had eleven. That is a finding you can act on. It is invisible if your activity lives in a calendar and your deals live in a CRM.
It also means nobody has to write the history. Completing a Move writes it automatically. The record maintains itself as a by-product of the work rather than through anyone’s diligence.
The uncomfortable part of the design
There is a cost to this, and it is worth being upfront about it.
Because a Move must attach to a lead or a deal, you cannot use it as a general to-do list. If you want to remember to renew your own software subscription, PragmaCRM is not where that goes.
Some people find that restrictive. We think it is the point. Every tool that tries to hold both your sales pipeline and your general work ends up doing neither cleanly, and the sales pipeline is always the one that suffers, because admin items are more numerous and more urgent-feeling than the call that will not pay off for a month.
What to take from this if you use a different CRM
You do not need our product to get the benefit. What you need is the discipline the naming enforces, which you can apply anywhere.
Pick one list and declare that it only holds actions that advance a specific deal. Move everything else out of it, into whatever you use for general work. Then adopt one rule: no deal in the pipeline without a next action and a date.
Run that for a month and two things will happen. The list will get shorter, and you will find deals in your pipeline that nobody can think of a next action for. Those deals were already dead. You just could not see it.
The name is the mechanism
Naming things well is not decoration. A name sets an expectation about what belongs, and that expectation does more to keep a list clean than any amount of process documentation.
“Task” invites everything. “Move” invites one thing. That is the whole argument, and after watching sales teams fill and abandon task lists for years, it is one we are confident about.
Moves sit at the centre of how PragmaCRM works. Every lead and deal carries its next action, overdue ones surface automatically, and completing one writes the history for you. See how Moves work.