This is the kind of data challenge that should be simple but somehow never is. Lundorff has two lists of IDs and amounts, and they need to know which IDs have mismatched totals between the two. In a traditional spreadsheet, this requires a mix of VLOOKUP, IF statements, and careful manual checking. It works, but it is slow, error-prone, and it pulls your focus away from the actual question: *which records need attention?*
We think the real issue here is not the comparison itself, but the friction in getting to the answer. When you have to build a formula for every basic reconciliation, you are not analyzing data. You are maintaining spreadsheet infrastructure. Lundorff's request is a perfect example of a task that feels like it should be a single step, not a multi-formula project. The underlying need is straightforward: take two lists, match by ID, flag any row where the amount changed. The difficulty comes from the tool, not the logic.
What this means for anyone doing regular data work is that the cost of these small tasks adds up. A five-minute formula build here, a ten-minute debug there, and suddenly you have spent an hour on what amounts to a simple check. The smarter approach is to use a tool that understands the relationship between the two lists natively. An AI-native spreadsheet can interpret the intent: "compare these two lists and return the IDs where the amount differs." No lookup tables, no nested IFs, no dragging formulas down a column. Just a clear result.
Our opinion is that this task should be a single command, not a project. When you can ask for the mismatched IDs directly, you free yourself to focus on *why* the amounts changed, not on how to find them. That is the shift that matters. Stop building the bridge. Start walking across it.