What Is Sales Friction?

1. Sales friction is not the same as sales difficulty

A difficult sale may require engineering judgment, careful discovery, multiple stakeholders, commercial negotiation, regulatory review, or a long delivery cycle. Those demands can create value or control legitimate risk. They are not automatically friction.

Friction is the avoidable part: entering the same information twice, searching for the current quote, asking who owns an approval, rebuilding customer context, translating one system into another, correcting preventable errors, or waiting because the next action is invisible.

This distinction matters because indiscriminate simplification can remove necessary controls. The goal is not the fewest steps. It is a process in which each step advances a decision, protects quality, coordinates responsibility, or creates evidence the next participant can use.

2. Four forms of friction

Sales friction usually appears in four related forms. Administrative friction is duplicate entry, formatting, searching, reconciliation, and status reporting. Cognitive friction is the mental cost of switching tools and reconstructing the Job. Workflow friction is waiting, unclear ownership, approval queues, and broken triggers. Knowledge friction is the loss of requirements, rationale, commitments, and risk across a boundary.

Salesforce’s 2026 State of Sales survey reported that respondents spent 60% of an average workweek on nonselling activity, used eight tools on average, and included a substantial group who felt overwhelmed by tool volume. This is vendor-sponsored survey research, and nonselling time is broader than avoidable friction, but it demonstrates why administrative and system burden deserve direct measurement.¹

Controlled psychology experiments have also found measurable switching-time costs when people alternate tasks, with costs increasing as task rules become more complex. Laboratory task switching is not a direct estimate of sales productivity, but it supports a cautious conclusion: repeated movement between incompatible workflows is not cognitively free.²

• Administrative: re-enter, search, format, reconcile
• Cognitive: switch, remember, reconstruct, reorient
• Workflow: wait, chase, escalate, clarify ownership
• Knowledge: lose rationale, requirements, commitments, or risk

3. Why friction hides between systems and stages

Most applications measure what happens inside their boundary. CRM can show an Opportunity stage. CPQ can show quote status. Email can show an approval message. ERP can show an order. A project tool can show delivery tasks. None necessarily measures the human translation required between them.

A two-minute copy-and-paste looks insignificant. So does one Slack message asking for approval context or one meeting spent re-explaining the accepted scope. Across many Jobs and transitions, the distributed burden can become substantial while remaining absent from every dashboard.

NIST’s construction interoperability research documented the cost of searching for, validating, recreating, and transferring facility information among fragmented participants and systems. Its dollar estimates are historical and industry-specific, so they should not be applied as a current sales benchmark. The enduring insight is structural: information can exist and still be costly when the next participant cannot use it reliably.³

4. Friction before Awarded: from Qualify through Close

Pre-award friction begins when qualification evidence, discovery findings, stakeholder roles, solution assumptions, pricing logic, approvals, and quote revisions become separate stories. The Opportunity advances, but the reasoning behind the stage change lives in inboxes, documents, recordings, or memory.

Common symptoms include stale next steps, repeated discovery, untraceable quote revisions, spreadsheet pricing that disagrees with the proposal, approvals without version control, and managers who must interview the seller before every review.

Research involving 240 salespeople found perceived usefulness to be the strongest influence on CRM acceptance, followed by accurate expectations, innovativeness, ease of use, and supervisor support. The implication is not that every field should disappear; it is that capture should help the seller or the next decision rather than function only as retrospective administration.⁴

Current Capterra reviews of Salesforce Sales Cloud show the balance clearly: users value centralized tracking, reporting, automation, and breadth, while some describe complexity, learning curve, cost, or customization burden. These are product-specific qualitative experiences—not evidence that CRM inherently creates friction—but they show how a capable platform can still impose operating costs when configuration and workflow do not fit the team.⁵

5. Awarded is the critical conversion boundary

Awarded is where commercial intent must become executable work. In the SMP model, it closes Opportunity and creates Project under the same parent Job. Friction appears when the system transfers only a status, contract value, or customer name while leaving the accepted quote, scope, commitments, documents, risks, and unresolved conditions behind.

The result is reconstruction: project teams chase documents, customers repeat requirements, order entry retypes commercial data, and disagreements emerge over what was promised. A handoff meeting may help, but a meeting cannot compensate for an operating record that has no continuity.

Research on R&D–sales knowledge transfer found that email was widely used but did not satisfy the need for findable knowledge, visibility, accountability, and a centralized shared workflow. The study concerns R&D–sales cooperation rather than sales-to-project conversion, but the cross-functional knowledge problem is closely analogous.⁶

A recent Sales Operations discussion described complex deals spread across CRM, Slack, shared drives, and approval spreadsheets, leaving one owner to piece together cross-functional context. The discussion includes vendor-affiliated replies and is anecdotal; it is included only as a field example of how fragmentation feels in practice.⁷

6. Friction after Awarded: Intake through Handover

Post-award friction is not limited to delivery delay. It includes validating a quote that operations cannot execute, discovering missing selections after procurement begins, losing review comments, tracking orders separately from the Project, releasing equipment before dependencies are ready, and handing over documents that the recipient cannot use.

USACE submittal procedures connect evaluation and approval to procurement, delivery, schedules, action dates, follow-up, and quality control. The regulation governs a specific construction environment rather than all B2B sales, but it illustrates why approval evidence and procurement timing must remain coordinated rather than scattered across disconnected queues.⁸

NIST’s General Buildings Information Handover Guide similarly focuses on transferring accurate, usable information to operations. Its historical estimates are not a present-day benchmark, but the underlying failure mode is relevant: delivery is incomplete when the receiving party must verify, reformat, or recreate what should have crossed the boundary.⁹

7. Universal layers should lead to action and collaboration

Capturing more activity is not the same as reducing friction. A chronological feed can become another archive that people must interpret. Universal Activities and Notes create value when they preserve context on the correct record and make ownership, decisions, evidence, and next actions easier to understand.

Connected Communication reduces another boundary by keeping Email, SMS, Group Chat, and future channels inside the relevant module. It creates value when conversations can become Activities, decisions can be preserved in Notes, and participants can see the complete thread without searching separate inboxes.

A useful Activity answers who will do what by when. A useful Note explains what changed, why a decision was made, what risk remains, or where the source evidence lives. Together they should help a new participant act without interviewing everyone who touched the Job before them.

A recent practitioner discussion in Sales Operations made this distinction directly: teams may collect calls, emails, meetings, and notes yet still reconstruct the Opportunity story because facts are fragmented. The thread is not representative research and contains promotional comments; its value is the practical test it surfaces—whether a new participant can understand why the Job matters, what changed, and what decision comes next.¹⁰

8. How to measure sales friction without invented benchmarks

There is no defensible universal friction score that applies equally to every sales model. A configured product sale, a professional-services engagement, and an engineered equipment Job have different necessary work. Measure improvement against your own baseline and segment by Job type, complexity, team, and stage.

Start with ten to twenty representative Jobs. For each stage and transition, record elapsed time, active work time when available, number of systems touched, manual entries, quote or document revisions, approval cycles, clarification requests, handoff defects, reopened work, missing required items, and time spent reconstructing context.

Then separate necessary effort from avoidable effort. Engineering review may be necessary; finding the approved drawing is friction. Credit approval may be necessary; asking three people who owns it is friction. Customer training may be necessary; rebuilding the training list at Handover is friction.

• Elapsed time versus active work time
• Wait time by stage and owner
• Manual entries and systems touched
• Revisions caused by missing or inconsistent information
• Approval cycles and aging
• Clarification requests at Awarded and Intake
• Reopened tasks, order exceptions, and handover defects
• Context-reconstruction time for a new participant

9. Reduce friction at the operating-model level

Begin with the largest repeated source of rework or delay, not the broadest technology purchase. Clarify the parent record, define stage evidence, assign decision ownership, standardize the Awarded conversion, and eliminate duplicate sources of truth. Automate only after the intended decision and exception path are clear.

The solution may be better CRM configuration, fewer required fields, a CPQ or order integration, clearer process, a shared handoff standard, improved training, or a broader Sales Management Platform. Modern CRM suites can support extensive workflows; an SMP should not be recommended merely because several tools exist.

The decisive test is continuity: can the team follow one Job from Qualify through Handover, understand what has happened, trust the current commercial and operational record, and see what must happen next? When the answer improves, sales friction is being reduced rather than merely relocated.

Frequently asked questions