When tasked with selecting a Course Management System (CMS), the first step many responsible colleges, universities and consortia take is to name a selection committee of faculty, administration, students and possibly IT staff. They do some Web searching and talk to colleagues, friends and counterparts at other institutions. This same committee also defines goals, objectives and selection criteria. They then assemble a long list of vendors and send out requests for proposals (RFPs)--inevitably a long list of features and functions that the institution requires in a CMS. This plan of attack is better than flying blind. However, the biggest mistake a college, university or consortia can make is treating the RFP as the Magna Carta and selecting a software product on features and functions alone. This article features ten considerations beyond features and functions for making a great CMS decision.