Asking how to get unique customer counts alongside total sales in Power Query might seem like a simple technical question, but it reveals something deeper about where spreadsheets are falling short. The user who posted this query knows the data they need, understands the logic required, and even has a clear vision of the final table. Yet they are stuck navigating a tool that demands manual workarounds for what should be an intuitive process. This is not a reflection of their skill, it is a reflection of the limitations baked into traditional spreadsheet workflows.
The core problem here is elegantly simple: you need to count each customer only once while still summing all of their purchases. In Excel, this requires careful filtering, a distinct count function, and often a pivot table or Power Query steps that feel anything but natural. The user explicitly asks to avoid writing M code, which is a polite way of saying they want the tool to meet them halfway. Compare this to similar challenges we have explored, like how to Simplify Your Spreadsheet with Targeted XLOOKUP Searches or how to Pull text-based data across sheets with smarter cross-sheet referencing. In each case, users are forced to learn a specific syntax or interface trick to accomplish what should be a standard analytical request. The tool becomes the obstacle.
What this story underscores is the gap between what users need and what legacy tools can deliver without friction. A human-centered approach to data management would recognize that this query, group by branch and product, count distinct customers, sum sales, is one of the most common patterns in business analysis. It should be a single command, not a multi-step puzzle involving Group By dialogs and Count Distinct Rows options hidden inside Power Query's interface. The fact that it is not speaks to how spreadsheet software evolved: feature by feature, rather than task by task.
Our take is clear: the era of expecting users to contort their logic to fit the tool is ending. AI-native spreadsheets can interpret a request like "show me total sales and unique customer count by branch and product" and handle the deduplication logic without the user ever touching M code or even a dropdown menu. This is not about replacing Excel, it is about removing the friction that makes honest questions like this one feel like a burden. The user deserves a tool that understands the difference between counting a customer and counting a transaction, because that distinction is the entire point of their analysis.
The practical takeaway for anyone reading this is simple: if you find yourself searching forums for how to avoid writing code in Power Query, ask whether the tool is making you work harder than necessary. The answer should guide where you invest your time next.