The user who asked this question has identified a real friction point in spreadsheet work, and they've done something smart: they've named the problem precisely. They want a single dynamic summary sheet that automatically pulls in data from every client sheet, including new ones they add later, without rewriting a formula each time. And they want to sort that consolidated data by part number, not by the order of sheets. This is exactly the kind of workflow tension that makes people feel like their tools are fighting them instead of working for them. Our view is clear: this should be straightforward, and the fact that it isn't yet is a sign of how much room there is for improvement in how we manage data across sheets.
The core challenge here is that most spreadsheet functions, including VSTACK, require explicit references. You tell it exactly which ranges to stack, and if you add a new sheet, you have to update the formula manually. That creates a maintenance burden that increases with every new client. The user is right to worry about mistakes, manual updates are where errors creep in, especially when you're managing dozens of sheets. The workaround that many people turn to involves indirect formulas or helper sheets that list all sheet names, but those approaches can become brittle and hard to audit. What this user really needs is a way to make the summary sheet self-aware: to look at the workbook, identify all sheets except itself, and pull their data automatically. That's not a feature of standard functions today, but it points to a design principle that should be standard: formulas should adapt to the structure of your workbook, not require you to adapt the formula to the workbook.
The sorting requirement adds another layer. Even if you get the dynamic stacking to work, you then need to reorder the results by part number across all clients. That's a separate operation, and in many spreadsheet tools, sorting a dynamic array means either using a helper column with SORT or accepting the default order. The user wants the summary to be both live and organized by part number, which is a reasonable expectation for a tool that claims to handle data. It's not an exotic request, it's basic data management. The fact that it requires workarounds suggests that the underlying logic of these tools hasn't fully caught up to how people actually use them.
This is where the opportunity lies. A truly AI-native spreadsheet wouldn't ask the user to manage sheet references or sort orders manually. It would understand the intent: "I want a summary of all part numbers from every client sheet, sorted by part number, and I want it to update automatically when I add a client." That's a single instruction, not a multi-step formula construction. The technology to parse that intent exists. The gap is in applying it to the everyday reality of spreadsheet users who are managing real client data, not theoretical exercises. The user's question is a blueprint for the kind of feature that would save time, reduce errors, and make the tool feel like a partner rather than a puzzle. The solution isn't a better workaround, it's a better design.