Why does the exit criterion have to be a fact?
Because a stage defined by a mood — “interested,” “in progress,” “hot” — gets read differently by every rep, and from there the pipeline stops describing anything.
A verifiable criterion is something that happened or did not: “proposal delivered in writing,” “diagnostic meeting held.” If you cannot write it that way, the stage is not defined yet — and configuring it in the CRM only moves the ambiguity into the system.
How do you fill it in without inventing the process?
Not by asking “what are our stages?”, which produces the diagram from the corporate deck. By asking about concrete cases: “walk me through the last five deals you closed, one by one, from first contact”.
The real stages come out of those accounts, and they almost never match the official ones. The template gets filled in after those conversations, not during a theoretical definition meeting.
What is the loss-reason column for?
It is the one that pays off most and the one most often left out. Knowing at which stage deals are lost and why turns the pipeline into a diagnostic instrument instead of a record.
It also decides what to automate: if most deals are lost for lack of follow-up at one particular stage, that is where an automated sequence pays for itself.
What does the second sheet do?
It inventories the fields with one question that decides everything: is anyone going to filter or report on this field in the next three months? If the answer is no, it should not be required.
It is the rule that avoids the most common failure in a new configuration: required fields the team fills with “n/a” and “pending,” which poison the data for everyone.
What comes after the mapping?
The configuration, which with this document becomes mechanical work instead of a series of improvised decisions. It is exactly what a HubSpot Discovery delivers, and we treat it as a separate service so it is useful to you even if you implement with someone else.