Also, beware of ANY vendor who will give you a list of supported AP-to-client distance charts with their gear, because it shows they have a severe lack of understanding of RF in the client space. As a vendor, we can speak to our AP-to-AP link distances based on testing we do with our own controllers, software, APs, and antennas. But there is too much variability with client performance, client environment, and drivers to make that possible.
A more practical approach, and what is best relayed to your customers (one we do often withing DoD) is to build a standard AP/Antenna deployment, mast it, and walk the environment with the client type being used at the site, to get an understanding of the performance characteristics of that customer's environment, end-devices, etc. This allows us to properly model and set a design to support the customer's needs. Sometimes the clients used are spectacular and perform great, others have severe issues (either with power, driver, roaming, etc) that require drastic design accommodations. This provides the customer with both the best possible outcome with little time investment, as well as a revenue and PS stream for the partners/integrators that allow the partner/integrator become the 'expert' for the customer. The side benefit is, the partner/integrators also gets to warehouse that data for comparative analysis in case future projects pop up with similar client/environment characteristics.