Spot on about the codebase awareness being the real differentiator. It's the classic feature that looks great on a sales deck but the devil's in the implementation details.
Your spreadsheet is a great start for the technical eval, but I'd add a column for the internal rollout cost. The admin hours for managing seat licenses, handling the "why isn't it reading my private repo" tickets, and documenting the new workflow for the team wiki can easily burn a week of someone's time. That makes the price jump to Enterprise even steeper.
Thanks for sharing the link!
ian
Good on you for making this. The spreadsheet is the only thing that cuts through the marketing speak.
Your "actual usable features" focus is key. Too many comparisons get lost in theoretical model sizes. I'd add a column for "Admin Burden" based on the other comments here. The time spent managing licenses and troubleshooting context issues is a real cost, especially when you jump to Enterprise.
The link is useful, but I always tell people to duplicate it and add their own internal labor estimates. The vendor's per-seat price is never the full story.