Stages are defined by seller activity
Visits, proposals, and demos count as progress while customer approval, review, and resource commitments lack evidence.
Sales Process and Commercial Operations
Why does the CRM look optimistic when the customer has not taken corresponding action?
Define stages by customer behavior, support forecasts with evidence, and connect process, tools, data, and operating cadence.
The work starts with real business symptoms
The symptoms are entry points for investigation, not ready-made diagnoses. We test whether they share one root cause or several different constraints.
One process has many interpretations
Stage names are shared, but entry, exit, evidence, and next-action criteria differ by person.
Forecasts break at month end
Management relies on subjective probability and verbal confidence instead of customer behavior, aging, and historical bias.
Tools multiply, but management behavior does not change
CRM, templates, and dashboards exist separately; duplicate entry, missing fields, and unused data remove their value.
Assess before designing
The diagnostic starts with a 40-question, multi-role assessment, then verifies the starting situation through interviews, policies, CRM samples, operating data, and live opportunities. Scores guide investigation rather than replace judgment.
Priority assessment dimensions
Sales strategy and account managementSales organization and collaborationSales process and operationsSales capability and performance
Evidence requested during research
- 1Sales process, stage definitions, entry and exit criteria, and current tool templates
- 2CRM fields and samples covering stage aging, regression, closure, and missing data
- 3Forecast accuracy, funnel conversion, win-loss, cycle time, and exception records
- 4Live samples from weekly reviews, monthly operating meetings, deal reviews, and manager coaching
The score is not the conclusion
We compare role differences, evidence gaps, business impact, and root causes before deciding what should change.
Are stage gates defined by observable customer behavior and evidence?
Do CRM fields support decisions or merely satisfy reporting?
Does forecasting account for individual bias, stage aging, and historical conversion?
Do review meetings change the next customer action and resource decision?
What the solution can include
The final scope follows the diagnosis. The workstreams below show the typical design space and expected outputs, not a pre-sold standard package.
Customer-behavior sales process
Rebuild the process around customer decisions, resource commitments, and validation actions instead of seller activity.
EXPECTED OUTPUT
End-to-end process and critical scenario branches
Stage evidence and tool standards
Define entry, exit, customer evidence, essential tools, and exception handling for each stage.
EXPECTED OUTPUT
Stage-evidence standard, toolkit, and exception rules
Minimum CRM data contract
Retain fields that support decisions, forecasting, and collaboration, with definitions, ownership, and data-quality rules.
EXPECTED OUTPUT
Field dictionary, data ownership, and governance rules
Forecasting and operating cadence
Connect weekly reviews, deal reviews, monthly operations, and exception escalation into a decision-producing cadence.
EXPECTED OUTPUT
Forecast rules, review scripts, and operating calendar
How progress becomes visible
The project records the starting situation, observes a bounded pilot, and performs a T2 reassessment. External business outcomes are tracked, but never guaranteed.
Stage-evidence completeness and critical CRM data quality improve
Forecast bias, aged opportunities, and stagnant deals become visible and actionable
Review meetings produce clear decisions, owners, and customer actions
Process adoption and stage conversion are measured with real business evidence
Anonymized company caseModule 3/4
A sales-system consulting case, unpacked
A global logistics company
Global logistics company: replacing nine vague stages with five usable stages
A global logistics COO needed reliable worldwide pipeline visibility. Twenty percent of opportunities had no stage and one-third were entered only halfway through the deal. The company reduced nine stages to five and changed weekly operating routines.
Company names are anonymized. The public page keeps the four-part structure, three core judgments in each part, and selected examples. Full operating detail remains in the internal manual.
01
CASE PAGE 1/3
STARTING SITUATION
KEY POINTThe CRM contained opportunities but could not show customer progress or forecastable revenue
The problem was not simply reluctance to use CRM. Nine unclear stages, inconsistent definitions, and operating meetings detached from the system created competing versions of business reality.
- Management objective
- The COO wanted consistent global pipeline reporting so forecasting, resource decisions, and financial planning used the same opportunity facts.
- Measured problems
- Twenty percent of opportunities had no stage and one-third were entered halfway through the deal, preventing reliable qualification and cycle analysis.
- Process causes
- Nine stages did not match field work, definitions varied by region, and weekly management still accepted oral updates outside CRM.
02
CASE PAGE 2/3
SOLUTION AND IMPLEMENTATION
KEY POINTStart with customer progress and management decisions, then define CRM stages, fields, and meeting rules
The company did not add more dashboards. It simplified stages, standardized definitions, required every opportunity to start at stage one, and used the CRM dashboard as the weekly meeting record.
- 1
Reconstruct the actual sales process
Analyze stage gaps, late entry, and stage duration, then interview sellers and managers to compare system stages with actual customer decisions.
Data used: 阶段完整度80%；及时录入约67%；各阶段停留天数
Decision: 先确认问题来自阶段设计、录入规则还是经理不使用，不能只责怪销售。
Participants: Sales operations and regional managers
- 2
Reduce nine stages to five
Recombine stages around observable customer actions, remove duplicate or seller-only stages, and define entry, customer evidence, required fields, and exit conditions.
Data used: 最近赢单与输单、客户承诺、阶段转化、停留时间
Decision: 九个阶段减为五个；同一案例由不同经理判断时应得到相同结果。
Participants: Sales operations, sales leaders, and field representatives
- 3
Require entry from stage one
Require every opportunity to start at stage one, retain only fields needed for qualification and forecasting, and assign field ownership.
Data used: 必填率、字段使用率、重复字段、后补次数
Decision: 全部商机从阶段1进入；没有下一客户动作和日期的商机不得列入承诺。
Participants: Sellers, managers, and the CRM administrator
- 4
Run weekly reviews from system facts
Use the CRM dashboard in weekly reviews; opportunities outside the dashboard are not discussed. Managers decide from customer evidence, next actions, and risk, then update the record.
Data used: 本周新增／前移／后退／失单、超龄、预测差额
Decision: 不在看板中的商机不讨论；会后责任人当日更新决定与日期。
Participants: Regional sales managers and sales operations
03
CASE PAGE 3/3
RESULTS AND CONTINUED OPERATION
KEY POINTFive stages, shared definitions, and one meeting rule made CRM an operating tool again
The company reduced nine stages to five, standardized definitions, required stage-one entry, and ran weekly reviews from the CRM dashboard. Visibility and critical-data tracking improved.
Five-stage sales process
Customer progress, Entry criteria, Exit criteria, Ownership
Owner: Sales leadership and operations
Minimum CRM record
All opportunities start at stage 1, Qualification, Next customer action, Expected date
Owner: Sellers and managers
Weekly pipeline review
CRM dashboard as meeting list, Customer evidence, Risk decision, Owner and date
Owner: Regional sales manager
Global forecasting basis
Stage consistency, Opportunity completeness, Cycle visibility, Critical-data tracking
Owner: COO and sales operations
80%到98%
Stage completeness before change
67%到94%
Timely entry before change
7步
Number of sales stages
每周
CRM pipeline review
Field-case guidance
The ten field cases at the end illustrate live-deal decisions and actions; the main case explains how a sales system is built and run.
CASE_004 · 医药制药
某创新药厂质量数据平台选型：审计倒计时下的跨部门立项
Helps explain stage evidence, data accountability, and joint approval mechanisms in a highly regulated setting.
View caseCASE_006 · 电力与电网
某区域电网智能巡检项目：关键联系人调离后的真实进展重建
Helps explain how customer behavior calibrates deal stages and how safety review and acceptance evidence replace subjective probability.
View caseStart with the business question that matters most
Bring the current symptoms, available evidence, and management concerns. The first conversation clarifies whether a formal assessment is warranted.