This user isn't too dumb for Excel. They've just hit the wall that everyone hits when a general-purpose tool asks them to think like a programmer instead of like a person solving a real problem.
What they're describing is a common workflow. A field worker opens an input sheet, checks boxes for services a customer needs, and expects two things to happen automatically: the estimate page should show only selected line items, and the summary page should hide everything unselected. That's not an exotic request. It's a straightforward sequence of conditional logic. Yet in traditional spreadsheets, making it work across sheets with mobile compatibility requires nested IF statements, VBA scripts, or third-party add-ins. Each of those is a barrier. Scripts break on mobile. Formulas become brittle when rows shift. The result is that a person with a perfectly clear vision of what they need spends their time apologizing instead of building.
The real problem isn't the user's skill. It's that the tool expects you to micromanage the mechanics instead of stating the outcome. Checkbox clicked on Sheet1 should equal filtered rows on Sheet2. That's a single intent. But Excel makes you translate that intent into cell references, range names, and hidden toggle columns. The abstraction leaks. The field worker wants to click a checkbox and move on. The spreadsheet asks them to become a part-time developer.
This is exactly where AI-native spreadsheets change the equation. When the tool understands intent, you don't write a formula to hide rows. You say "hide rows where the checkbox wasn't selected" and the tool handles the rest. The logic lives in the layer between data and display, not in fragile cell-by-cell instructions. For someone like this user, that means their field team gets the mobile experience they deserve. Open the sheet. Click the boxes. See the estimate. Walk away.
The vision here is practical and human. It's about reducing friction for people who are already doing the hard work of serving customers in the field. Spreadsheets should be a silent partner in that work, not a hurdle that makes someone feel dumb. What this user needs isn't more VBA tutorials. It's a tool that understands that a checkbox is a decision, not a calculation. That shift is available now. The only question is whether we're ready to stop fighting our tools and start using them.