This is a clever idea that hits a wall built by the tool itself. The user has built a functional, multi-step search system inside Excel, vertical lists of unique specialties, a scoring column, filtered results, only to have it fail when the data grows beyond what the spreadsheet can handle. That `#CALC!` error isn't a mistake in the logic. It is a hard limit imposed by a decades-old architecture that was never designed for this kind of work.
What this reveals is a fundamental tension. Spreadsheets are brilliant for small, static datasets where you control every cell. But the moment you ask one to behave like a database, to dynamically list, deduplicate, and score hundreds of entries, the cracks appear. The user's approach was sound. The constraint was the tool. Many professionals hit this same ceiling: they build something that works, then watch it break under its own weight. The frustration is real, and it is not their fault.
The practical takeaway here is that the problem is not the search logic. The problem is the container. When a list of professionals and their specialties needs to be searched, filtered, and ranked, the right tool should handle that natively. It should not require a workaround that collapses under normal use. A smarter system would treat each specialty as a first-class data point, not as text that needs to be split and scored by hand. It would let you search, combine filters, and see results instantly, without building a fragile scaffold of formulas.
If this kind of task is part of your regular workflow, it is worth asking whether the spreadsheet is holding you back. The user's experiment shows they have the right instincts. They just need a platform that matches them.