Recording a sales opportunity can involve considerably more work than entering a customer’s name. Someone has to check the account, capture the request, assign responsibility, schedule the next action and keep the information current as the deal develops. Each step deserves scrutiny when a business evaluates the productivity of its sales team.
The CRM automation benchmarks published by Bitrix24 in 2026 give that administrative workload a useful reference point. Around 35% of sales teams in the study spend more than half their working week on administrative tasks and manual data entry. About 30% of surveyed companies have automated less than 10% of their CRM workflows. The research covers 1,001 companies using the vendor’s CRM across 12 markets.
These findings describe the participating businesses, rather than the entire CRM market. For organizations reviewing their own operations, however, they suggest a practical starting point: examine the work required to move an inquiry forward, including the activity employees perform outside the CRM.

Where a customer record becomes repeated work
A customer record serves several legitimate purposes. It helps a salesperson prepare for a conversation, gives colleagues access to account history and provides information for forecasting. Maintaining that record takes time, so the value of each requirement needs to be clear.
Consider a salesperson receiving a quotation request by email. The request may need to become a contact, an opportunity and a task for a technical colleague. If the customer already exists, the representative may first need to find the correct account. The commercial details may then be entered into another system to prepare the quotation.
This illustrative workflow contains several distinct activities: identifying the customer, interpreting the request, transferring information and coordinating people. They require different treatments. Interpreting a technical requirement may need an experienced employee. Copying an existing address into another record is a candidate for integration or automation.
A process review can separate these activities by following actual opportunities through their next commercial milestone. For each step, record who performs it, which information they need and whether another employee has already entered that information. Repeated entry, unclear ownership and unnecessary approvals then become specific issues to resolve.
Automation coverage needs an operational definition
The share of workflows automated offers only a partial view of a sales operation. A business also needs to understand how often each workflow runs, how much effort it removes and what happens when it encounters an exception.
An automated task used for every incoming inquiry may affect daily workload more than several rules used occasionally. Equally, a process that creates records quickly may leave substantial checking and correction to employees. Counting the configured rules will not capture that surrounding work.
Implementation teams can assess a workflow against three concrete outcomes:
- Work removed: Which manual actions employees no longer need to perform.
- Work remaining: Which checks, decisions and approvals still require attention.
- Exceptions created: Which cases need correction, reassignment or investigation.
Those measures help determine whether a configuration has reduced the burden or moved it to another person. They also make the next investment decision more specific. The appropriate response might be a routing change, a shared data field, a simpler approval requirement or an integration between existing systems.
Lead response times reveal a handoff worth examining
The benchmark reports that 68% of companies in its English-speaking group answer new leads within an hour, compared with 36% in Germany. The English-speaking group combines the United States, United Kingdom, Canada and Australia.
| Market | Respondents | Respond within one hour |
|---|---|---|
| English-speaking group | 186 | 68% |
| Brazil | 306 | 66% |
| Spain | 310 | 63% |
| Poland | 108 | 44% |
| Germany | 28 | 36% |
Germany’s small sample makes the comparison indicative. These percentages describe companies’ reported practices, rather than the share of individual inquiries answered within an hour.
For an individual business, response time can be broken into stages that its managers can influence. An inquiry arrives, enters a queue, receives an owner and reaches someone able to act. Measuring the interval between those events makes it easier to locate a delay.
The next step is to review the conditions around that delay. Requests arriving outside working hours, inquiries requiring specialist knowledge and messages from existing customers may need different routes. A team can test whether its assignment process handles those situations and provides a fallback when the usual owner is unavailable.
A useful answer needs its own measure
An automated acknowledgment confirms that a request arrived. It can set expectations and provide a reference number, but it may leave the buyer’s underlying question unanswered. A sales dashboard benefits from distinguishing that event from a substantive response.
For example, a buyer asking whether a product meets a technical requirement needs an answer, a relevant clarification or access to someone qualified to help. A generic message may be appropriate while that work begins. Measuring both events keeps the acknowledgment from obscuring the time required to provide useful assistance.
A business can define separate timestamps for receipt, assignment, first substantive response and the next agreed action. The definitions should fit its channels and selling model. A routine price inquiry and a complex project request do not necessarily require the same response standard.
Reviewing inquiries that missed those standards can reveal the intervention needed. A staffing gap, missing product information and a failed assignment rule call for different changes, even when each produces a similar delay on the dashboard.
Sales cycles depend on more than the first reply
The benchmark also reports that 28% of respondents experienced longer sales cycles and 27% reported declining funnel conversion. The survey does not establish the causes of those changes.
Broader buying research adds context. In its January 2026 State of Business Buying findings, Forrester reported that a typical buying decision involves 13 internal stakeholders and nine external influencers. It also identified procurement professionals as decision-makers in 53% of business buying cycles.
Those findings concern a different research population and should not be combined with the CRM benchmark as though they form one dataset. They do illustrate why a sales team needs visibility into the decisions and participants involved after initial contact.
An opportunity may be waiting for technical validation, an approved budget, contract terms or agreement among the buyer’s stakeholders. Internal sales activity may be complete while the customer’s evaluation continues. A pipeline review should capture that distinction before assigning a reason for slow progress.
Within the seller’s organization, stage-level review can identify avoidable waiting. Each opportunity should have an understandable next action, an owner and the information needed to proceed. Where an internal approval is holding up a proposal, the team can examine that approval directly.
Data quality belongs in the workflow design
An automated process needs rules for recognizing customers, handling incomplete requests and keeping records consistent. Without clear rules, the team may spend time repairing the output or deciding which record to trust.
Take an existing customer submitting a new website inquiry. The workflow needs to determine whether to attach the request to the existing account, create another contact or send the case for review. An incorrect match can be as disruptive as a duplicate, so ambiguous cases need a defined route to a person.
Form design also affects the work that follows. Every required field should have a clear purpose at the point it is requested. Information needed for initial assignment may differ from information required later to prepare a contract. Collecting it at the appropriate stage can make both the customer’s task and the employee’s task easier to understand.
For organizations connecting CRM with ERP, finance or order management, the review should specify which system owns shared information. Customer terms, approved prices and delivery details need clear update and exception processes. The proposed integration can then be evaluated against the manual checks and transfers it is intended to replace.
Saved time needs a commercial purpose
Research on sales AI highlights another part of the productivity question. In findings published in May 2026, Gartner reported average time savings of 4.8 hours per seller per week from AI tools. It also reported that 72% of sales organizations showed low reinvestment of those savings into higher-value sales activities. The release described a survey of 210 chief sales officers and senior sales leaders conducted in January and February 2026.
AI assistance and rules-based CRM automation are different interventions, so their results should be assessed separately. The management issue raised by the Gartner findings is relevant to both: a team needs a plan for using any capacity released.
That plan can identify specific activities, such as preparation for priority accounts, follow-up with qualified prospects or deeper discovery conversations. Managers can then review whether employees gained time for those activities and whether the change helped advance comparable opportunities.
Financial assessment should distinguish additional capacity from reduced expenditure. Releasing time for customer work may create value while leaving payroll unchanged. The business case should describe the intended benefit and the evidence needed to assess it.
Measure the change against actual work
A manageable review can begin with one recurring process, such as assigning demonstration requests or preparing a standard quotation. Establish a baseline for the time taken, manual actions required, corrections made and cases needing escalation.
After changing the workflow, repeat the measurement under comparable conditions. Include the effort spent maintaining the rules and handling exceptions. A process that appears efficient in its ordinary path may still demand substantial attention when information is missing or an employee is unavailable.
Measures worth considering include:
- Inquiries awaiting assignment and the time they remain unassigned.
- Time to a substantive response, separated by channel and request type.
- Manual minutes spent preparing and updating an opportunity.
- Records requiring correction or reconciliation.
- Opportunities with overdue or missing next actions.
- Time spent in internal approval stages.
Commercial outcomes can be reviewed alongside those operating measures. Changes in lead source, customer mix or deal complexity should be considered when interpreting conversion and time-to-close results. This makes it easier to judge how much of an improvement can reasonably be associated with the workflow change.
Use external benchmarks within their limits
The Bitrix24 CRM survey was conducted July 21 to July 28, 2026. It uses self-reported answers from Bitrix24 customers; Spain and Brazil account for 62% of responses. It is not a representative sample of the wider business population and cannot establish that automation causes particular sales outcomes.
Its practical value lies in directing attention to work a company can examine for itself. Comparisons become more useful when matched with the organization’s own channels, opportunity types, staffing arrangements and operating data.
At the next process review, select a group of inquiries that took longer than intended or required repeated correction. Trace what happened, involve the employees responsible and agree on one change with a measurable result. Retain, adjust or remove the workflow based on what that review shows.
Sources

ERP News Editorial Team
We cover ERP and enterprise technology for the people who select, implement, and run these systems.
Pitch a guest article or work with our editorial team on a news story, customer case study, or executive interview.
Editorial Calendar · Pitch a Guest Article · Commission a Story
Advertising Options · ERP News Magazine · ERPNews.com
Editorial Inquiries · [email protected]
Copyright & Usage · Our original editorial content is produced by the ERP News Editorial Team, with expertise in ERP and enterprise technology.
© ERP News. All rights reserved. Except as permitted by law, reproduction, republication, and redistribution require prior written permission or a licence from ERP News, along with clear attribution to ERP News as the source.
ERP News Content Licensing · License full-text ERP News articles for your internal research tools, delivered through a private JSON feed. [email protected]









