A definition you can quote, a backwards mapping method, an illustrative worked example with real dates, and why a close date without a mapped path is a guess.
Free Forever • No Credit Card Required
Quick answer
The decision process is the sequence of steps, people, and approvals a buying organisation will go through between evaluating options and being able to proceed.
It answers who, in what order, and by when. Decision criteria answer what will be judged. A seller can win entirely on criteria and still lose the deal to a process they never mapped, usually by running out of time or by meeting an approval nobody had mentioned.
Ask when they need this working, and why that date. Then work backwards. A date derived from the seller's quarter is an aspiration; a date derived from the buyer's operational need has a reason behind it.
What has to be true immediately before that date? And before that? Continue until you reach today. Each answer names a step, and each step has an owner and a duration.
For every step, ask how long it took the last time they bought something comparable. People estimate the past accurately and the future optimistically, and this single substitution improves forecast quality more than any other question in a sales conversation.
Which steps depend on a scheduled meeting? A monthly approval forum with papers due a fortnight in advance turns a ten-minute decision into six weeks of elapsed time, and it does so entirely predictably.
A map the buyer has not seen is a private theory. Sharing it, ideally as a mutual action plan with owners on both sides, converts it into something both parties maintain.
These dates are invented to demonstrate the method and describe no particular organisation.
The buyer wants to be live by the first of September, because a busy trading period begins in October and they want a month of settled use first.
Working backwards. Implementation and data migration take three weeks, so signature is required by around the tenth of August. Legal review took three weeks on their last comparable purchase, so the contract must be issued by roughly the twentieth of July. Procurement will not issue a purchase order without a completed security review, which took four weeks previously, so that review must start by about the twentieth of June. The internal approval forum meets monthly, with papers due a fortnight before, which places the decision meeting in early June and the paper deadline in late May.
Counting forward from today, that means the business case must be complete, the economic buyer engaged, and the security questionnaire already returned before the end of May. A seller who mapped this in March has a plan. A seller who did not has a close date of the thirtieth of June and will move it three times.
Three things. It produces a defensible close date, which is the difference between a forecast and a wish. It functions as a risk register, because every step is a place the deal can stop and the longest, least controllable steps deserve attention first. And it tells you what to do next, which on most deals is the genuinely scarce piece of information.
It also protects the buyer. Internal processes are frequently unclear to the people inside them, especially for a first purchase of a given kind, and a supplier who maps the path is reducing work the buyer would otherwise do alone under time pressure.
Most process mapping ends when the buyer says yes. The steps after that point, security review, legal, procurement, purchase order, signature authority, routinely consume as long as the evaluation did.
Two weeks is what people say. Asking how long it actually took last time produces a different and far more reliable number.
Monthly committees, financial year ends, audit periods, and holiday seasons all move dates in ways that are entirely knowable in advance.
A plan the buyer has not agreed to cannot slip visibly, because nobody on their side is watching it. Shared, it becomes an early warning system.
Questions about how things work here are welcomed. Questions about who has power, or pressure for a date, are not. Sellers frequently avoid the first because they have been told buyers dislike the second.
A well-mapped deal has a step list with owners and dates, a close date that can be traced to a specific step, historical durations rather than estimates, calendar constraints identified, and a shared plan the buyer has acknowledged. When something slips, both sides know within days.
A poorly mapped one has a close date at the end of a quarter, no knowledge of what happens after agreement, an assurance that it should be quick, and a history of dates moving with no explanation attached.
| Step | Who owns it | What makes it slow |
|---|---|---|
| Business case preparation | The champion or sponsor internally | Waiting on numbers from other departments |
| Internal approval forum | A committee on a fixed schedule | Meets monthly, with papers due in advance |
| Security or technical review | The technical buyer or IT function | Queued behind other reviews already in progress |
| Legal review and redlines | Legal, internal or external counsel | Negotiation cycles, each with a waiting period |
| Procurement and purchase order | The procurement function | Supplier onboarding and vendor record creation |
| Signature | Whoever holds authority at this value | Absence, delegation limits, and holidays |
Record the steps on the opportunity with owners, expected dates, and a status. The close date then becomes derivable rather than asserted, a manager can ask which step it depends on, and a colleague inheriting the deal receives the map instead of asking the buyer to explain everything a second time.
Continue with what a CRM is, lead management software, sales automation, CRM for small business, CRM versus spreadsheets, and product features.
Every team in this space loses revenue to the same recurring gaps. Here is what they cost you and how HelloGrowthCRM closes each one.
Close dates move every month and nobody can explain why.
Dates set from the seller's quarter rather than from the buyer's process will always slip. Map the steps backwards from the buyer's target date, using how long each step took last time in that organisation, and derive the close date from that map. A date with a documented path behind it can be defended and, more importantly, corrected.Dates derived from a mapped path
A verbal agreement in March turned into a signature in June.
The decision was made and the process was not mapped past it. Ask early what happens after you agree commercially: security review, legal, procurement, purchase order, signature authority. Those steps are knowable in advance and are the difference between an accurate forecast and a recurring surprise.Map beyond the verbal yes
The buyer said two weeks and it has been two months.
Stated intentions are optimistic almost everywhere. Ask instead how their last comparable purchase actually progressed, step by step, and how long each part took. People are considerably more accurate about the past than about the future, and the historical answer is usually the better forecast input.Historical evidence over intent
A monthly approval committee added six weeks nobody had planned for.
Ask which steps depend on scheduled meetings and when those meetings occur. A step that takes ten minutes of somebody's attention can take five weeks of calendar time if the forum meets monthly and the papers are due a fortnight in advance. These delays are entirely predictable to anyone who asks the question.Calendar-bound steps identified
AI-powered CRM with the features you need to close more deals.
Common questions about using HelloGrowthCRM in your industry.
Join small businesses that close more deals with HelloGrowthCRM.
Free Forever • No Credit Card Required
Free Forever • No Credit Card Required
Prefer email? Write to sales@hellogrowthcrm.com