This user's problem is exactly the kind of friction that makes people feel like their spreadsheet has become a bottleneck rather than a tool. They have a clean data set, start dates, end dates, and a perfectly reasonable question: how many travel days fell in each calendar year? Yet the moment a trip spans December and January, the simple subtraction they'd normally use breaks down. ChatGPT gave them nothing useful. So they're stuck, manually splitting trips in their head or building clumsy helper columns.
That frustration is familiar to anyone who has tried to make traditional spreadsheets handle time-spanning logic. The formulas exist, `SUMPRODUCT` with `DATE` and `MAX`/`MIN` intersections, or an array formula that clips each trip to the year boundary, but they are not intuitive. They require the user to think like a programmer, not like a traveler. And when the data set grows to dozens of trips across a decade, even a correct formula becomes brittle. One misplaced cell reference and the annual totals stop adding up.
What this user needs is not a cleverer formula. They need a tool that treats time as a first-class concept, not as a pair of cells to be subtracted. An AI-native spreadsheet should let you ask: "For each year, sum the days that overlap with that year's date range." That's a plain-English query, not a nested function. The system should understand that a trip from 17 December 2024 to 20 January 2025 contributes 15 days to 2024 and 20 days to 2025, automatically, without the user writing a single `IF` statement.
This is where the gap between legacy tools and modern data platforms becomes most visible. The problem is not that the user lacks skill, it's that the tool demands skill in the wrong place. The spreadsheet should adapt to the user's logic, not the other way around. Our opinion is straightforward: if you find yourself building workarounds for a problem as common as splitting travel days across years, the tool is holding you back. Explore a solution where the formula understands your question.