Twenty hours into an Excel project, and you're stuck staring at 119 query tables, each named after a team and its content. You've tried XLOOKUP, gotten #VALUE!, and now you're considering INDIRECT, INDEX, MATCH, SCAN, anything that might finally pull the visiting team's roster into place. This is not a failure of effort. It is a failure of the tool. Traditional spreadsheets were never designed to handle this kind of relational complexity gracefully, and the workarounds you're hunting for are proof.
Our take is plain: you are wrestling with a problem that AI-native spreadsheets solve in seconds. The core issue isn't your formula syntax or your French-language Excel version. It's that you're asking a static grid to behave like a dynamic database. You have 17 teams, each with profiles and stats split across two sheets, and you need to assemble a visiting roster on demand based on a team name in cell A49. That's a lookup across 119 named tables, with different column layouts for goalies, forwards, defense, and staff. In a traditional spreadsheet, you'd need a nested maze of INDIRECT and XLOOKUP calls, fragile, hard to debug, and impossible for a colleague to maintain. An AI-native spreadsheet would let you describe what you need in plain language: "Show me the visiting team's goalie profile and stats, then the forwards, then defense, then staff, using the team name in A49." The AI handles the table matching, the column mapping, and the row alignment automatically.
What this means for you in practical terms is that your 20-hour struggle is not a personal limitation. It is a signal that the tool has reached its limit. You've already done the hard part: you structured the data, named the tables, and defined the roster layout. The missing piece is a system that understands relationships, that can say, "Team1_goalie_profile and Team1_goalie_stats belong together, and I know how to merge them for any team name." That's exactly what AI-native spreadsheets are built to do. They treat your data as a connected whole, not as 119 isolated islands. They let you ask questions like "What's the visiting team's full roster?" instead of forcing you to write a formula that chains together seven lookups per team.
The concrete point is this: stop looking for the right formula. Instead, look for a tool that makes formulas optional. You don't need to master INDIRECT or SCAN. You need a spreadsheet that understands your intent and executes it. Your 20 hours are a sunk cost. The smarter investment is in a platform that treats your data the way you already think about it, as a connected, queryable system, so next time, the answer is one sentence, not one hundred twenty-seven lines of nested lookups.