The Sales Rep Knows the Real Path. The System, Not Always.

TL;DR

• The formal quoting and order process is rarely the flow a sales rep actually follows in practice: the gap between the two is where business pain begins.
• Pricing rules and commercial terms frequently live in places the rep accesses outside the official system, via spreadsheet, memory, or a call to the back office.
• Configuring a platform on top of the formal process, while ignoring the real flow, guarantees low adoption and rework.
• The right discovery maps where the pain is greatest in practice before any decision about a solution is made.

Why your documented sales process is not the process that actually happens

Every B2B commercial operation has two versions of the same flow. The first is the official version: the funnel drawn in PowerPoint, the proposal playbook approved by leadership, the pricing policy saved somewhere in a shared drive folder. The second is the version the sales rep executes at six in the evening when the customer needs an answer before the month closes.

These two versions rarely match.

A rep managing distribution accounts in the industrial supply sector, for example, does not consult the official price list for every quote. He has built his own logic over months: he knows that particular customer has a negotiated rate that never made it into the ERP, remembers that the maximum discount for product line X was adjusted in a meeting nobody formalized, and resolves the impasse by calling someone in finance who "knows how it actually works." The order goes out. The deal closes. And the system records a transaction whose decision criteria were never captured anywhere.

That gap, between the formal process and the effective flow, is the correct starting point for any serious commercial diagnostic. And it is exactly what most platform projects ignore.

Where the rules actually live

The question that exposes the problem is simple: where do pricing rules and commercial terms live today, and how does the sales rep access them?

In most B2B operations with any depth of customer history, the honest answer is fragmented. Some of the rules are in the ERP, but out of date. Another portion lives in spreadsheets maintained by one or two people on the sales or pricing team. A third part exists in the head of the senior rep who built those conditions through years of customer relationships. And a fourth part, the most dangerous, exists only as informal practice that everyone follows without anyone having deliberately decided on it.

When a platform is configured on top of the formal process, without first mapping this real territory, the predictable result is low adoption. The rep opens the system, does not find the condition he knows exists, closes the system, and handles it over text or email. The technical project was delivered. The operation stayed the same.

The cost of mapping late

The risk is not only operational. It is financial and strategic.

Every time the real flow diverges from the system, the transaction happens outside established controls. This means that prices negotiated outside the platform are not traceable, special terms granted by relationship are not auditable, and the true cost of each sale, including implicit discounts and accumulated exceptions, remains invisible to the people making margin decisions.

What looks like a tool adoption problem is, in practice, a commercial governance problem. And weak commercial governance carries a cost that surfaces late: in margin compression with no clear explanation, in a customer who received terms that should never have been offered, in the loss of the senior rep who carried in memory the rules nobody documented.

In the context of operations seeking to scale with automation, this cost becomes even more visible. The principle repeats across different sectors and has been observed directly in projects conducted by CWS Platform: AI agents and automation amplify the existing structure. When the decision logic, the rules, the criteria, the processes, is well designed before implementation, automation scales efficiency. When that logic is fragmented or implicit, automation scales chaos. This is why CWS Platform's discovery methodology always begins with mapping the real flow, not the documented process: configuring on top of the wrong flow is faster and more expensive than not configuring anything at all.

The Cost of Inaction

Maintaining the gap between formal process and real flow carries cumulative consequences that rarely appear on a single P&L line:

• Pricing rules and commercial terms that exist in practice but not in the system create auditable exposure and risk of inconsistency across customers.
• The rework cost of a rep accessing parallel sources to complete a quote is invisible in productivity metrics, but real in cycle time.
• Dependence on specific individuals to interpret undocumented rules is a continuity risk that only surfaces when those people leave.
• Platform projects configured on the formal process, without discovery of the real flow, have a documented history of low adoption and the need for costly reconfiguration.

Principles for a discovery that serves the operation

• Map the real flow before documenting the ideal process: follow the rep, not the manual.
• Ask where pricing rules and commercial terms live today, not where they should live.
• Identify the workarounds, the moments when the rep leaves the system to get something resolved, as symptoms of where the pain is greatest.
• Treat the divergence between formal process and effective flow as configuration input, not as a behavior failure of the team.
• Only propose a solution after mapping the real territory: a platform configured on the real flow has a lower adoption cost and faster results.

Frequently asked questions

Shouldn't the formal process be the real process? It should, and that is exactly what the platform is for. But sequence matters: first understand why the real flow diverged, then configure the system to accommodate what is legitimate and govern what is not. Imposing the formal process without understanding the real flow generates resistance and workarounds.

How do you identify where the undocumented rules are? Interview the reps who close the most and the ones who open the most exceptions. Map the orders that required manual approval. Look at the spreadsheets the sales team maintains outside the ERP. These are the symptoms of the real flow.

Does this mapping need to happen before choosing the platform? Not necessarily before choosing, but absolutely before configuring. A platform configured without this input will need to be reconfigured later, at cost and with a loss of internal credibility.

Who already lives this

In the automotive sector, where customer accounts carry negotiated terms, credit conditions, and customer-specific pricing, this kind of complexity is routine. A verified reviewer on Software Advice, from the Automotive sector at a company with 5,001 to 10,000 employees, described what she found working with CWS Platform:

"The support and project team, responsive, technically engaged, and willing to work through complex commercial rules (negotiated pricing, credit, customer-specific conditions)."

(Software Advice, verified review, available at: https://www.softwareadvice.com/product/546664-CWS-Platform/)

What the review describes, willingness to work through complex commercial rules, is exactly what the right discovery needs to capture before any configuration begins. Negotiated pricing rules, credit terms, and customer-specific conditions are not exceptions: they are the commercial DNA of the operation.

A case that illustrates

CWS Platform's discovery methodology starts from a recurring observation in projects conducted with complex B2B commercial operations: when the implementation team arrives at a new operation and asks where pricing rules and commercial terms are documented, the answer is almost never "in the system." The real answer is a combination of spreadsheets, old email threads, the memory of specific individuals, and informal practices that everyone follows without anyone having deliberately decided on them.

The work that must precede any platform configuration is therefore to make that logic explicit. Not to replace it, but so it can be governed. Rules that exist only in the head of a senior rep are not scalable, not auditable, and do not survive turnover. When those rules are mapped, formalized, and configured as decision criteria inside the platform, what was a continuity risk becomes a structural operational asset.

This is the principle that guides CWS Platform's discovery: the negotiation DNA of the operation, built over years of customer relationships, is the most valuable asset the platform needs to capture, not ignore.

About this publication

**The