Customer Effort Score
Customer Effort Score (CES) measures how much effort a customer had to expend to accomplish something with your product or company. It is typically captured through a post-interaction survey that asks "How easy was it to [complete this task / resolve your issue]?" on a scale of 1 to 7, where 1 is "very difficult" and 7 is "very easy." The simplicity of the question is the point: it captures the customer's subjective experience of friction at the moment that matters most.
CES was introduced by the Corporate Executive Board (now Gartner) in a landmark Harvard Business Review article that argued companies should stop trying to delight customers and instead focus on reducing effort. Their research found that effort, not satisfaction, was the strongest predictor of future loyalty. A customer who has an easy experience will stick around. A customer who has to fight to get something done will leave, even if the outcome was eventually positive.
The insight behind CES is counterintuitive but well-supported by data: exceeding customer expectations has almost no impact on loyalty, but falling below them has a massive negative impact. Customers do not reward you for making things wonderful. They punish you for making things hard. CES operationalizes this asymmetry by focusing measurement on the dimension that matters most.
Why it matters for SaaS
In SaaS, effort is everywhere. Every login screen, every configuration wizard, every support interaction, every workflow that requires more steps than it should. Each moment of unnecessary effort is a small withdrawal from the customer's patience account. Enough withdrawals and the account goes to zero, usually in the form of a cancellation.
The data from Gartner's research is striking: 96% of customers who have a high-effort experience become more disloyal, compared to only 9% who have a low-effort experience. Among customers who had a low-effort interaction, 94% said they would repurchase. Among high-effort customers, only 4% said the same. For subscription businesses where repurchase is renewal, these numbers translate directly into retention rates and revenue.
For PLG companies, CES is especially diagnostic because the product is the primary interface with the customer. There is no account manager absorbing friction or customer success team smoothing over rough edges for the majority of users. If the product is hard to use, the effort shows up immediately in CES scores, and subsequently in churn. PLG companies with consistently low CES scores across key workflows have a structural retention advantage that is difficult for competitors to replicate.
How it works in practice
CES is measured at specific interaction points, not as a general sentiment survey. The most common triggers are: after a support ticket is resolved, after a user completes a key workflow for the first time, after onboarding, and after a product update changes a familiar interface. The survey appears in context, usually as a single question with an optional follow-up for qualitative feedback.
A project management SaaS might deploy CES surveys at three points: after initial project setup, after the first team invitation, and after the first report generation. They discover that project setup scores 6.1 out of 7, team invitation scores 5.8, but report generation scores only 3.4. The aggregate CES looks decent, but one workflow is creating real friction. Without workflow-level measurement, this pain point would be invisible in overall satisfaction data.
Acting on CES data requires connecting the score to the specific friction sources. A low CES on report generation might stem from confusing filter options, slow load times, an unintuitive export process, or all three. Teams that pair CES surveys with session recordings and user behavior analytics can pinpoint exactly where effort spikes and design targeted interventions. The goal is not a higher survey score. It is the removal of the friction that created the low score.
Customer Effort Score vs Net Promoter Score
NPS asks "Would you recommend this product to a colleague?" CES asks "How easy was this specific interaction?" They measure different things and predict different outcomes. NPS captures overall brand sentiment and word-of-mouth potential. CES captures the friction of a specific moment and predicts whether the customer will continue using the product.
The difference matters in practice. A user might give your product an NPS of 9, indicating strong overall satisfaction and willingness to recommend, while also reporting a CES of 3 on a specific workflow that is frustratingly complex. The NPS suggests everything is fine. The CES reveals a problem that, if it recurs enough times, will eventually erode that NPS score and the customer relationship.
NPS is better for benchmarking against competitors and tracking long-term relationship trends. CES is better for identifying and eliminating specific friction points in your product. The most effective SaaS teams track both: NPS to monitor the relationship, CES to continuously reduce effort. When NPS starts declining, CES data often reveals why.
How Floe approaches this
Floe directly reduces customer effort by replacing complex, multi-step workflows with guided, conversational experiences powered by the browser SDK. Instead of forcing users to navigate menus, read documentation, and figure things out through trial and error, Floe's AI agent walks them through the process step by step. The effort shifts from the user to the agent.
This is particularly impactful for the workflows that generate the worst CES scores: first-time setup, complex configurations, and tasks that span multiple product areas. These are exactly the situations where users historically had to either struggle through on their own or contact support and wait for help. Floe provides immediate, in-context guidance that compresses what might have been a 30-minute struggle into a two-minute conversation, directly improving the effort scores on your most challenging workflows. Floe's support agent resolves issues by doing, not just explaining.
FAQ
How do you calculate Customer Effort Score? Sum all survey responses and divide by the number of responses to get the average. On a 1-7 scale, scores above 5 are generally considered good, indicating low effort. Some companies simplify to a 1-5 scale or use a binary "easy/not easy" format. The specific scale matters less than consistency: pick a scale, deploy it at key interaction points, and track trends over time.
When should you measure CES instead of NPS or CSAT? Measure CES immediately after specific transactions or interactions where effort is the relevant variable: completing a workflow, resolving a support issue, finishing onboarding. Measure NPS periodically to track overall relationship health. Measure CSAT after interactions where the quality of the outcome matters more than the ease of achieving it. Most SaaS companies benefit from running all three at different touchpoints.
What is a good Customer Effort Score? On the standard 1-7 scale, an average CES of 5.5 or above indicates that most customers find interactions easy. Scores between 4 and 5.5 suggest room for improvement. Scores below 4 indicate notable friction that is likely contributing to churn. Industry benchmarks vary, but the more important comparison is your own score over time and the variance across different workflows. A high average with one low-scoring workflow may be worse than a moderate average with consistent scores.