Compare WLAN vendors by the service your people need and the evidence a pilot produces. Begin with the rooms, client devices, applications, support responsibilities and expected lifetime of the network. Then ask each supplier to meet the same requirements and explain the full cost of keeping them working.
This method suits a small business or campus team evaluating managed wireless LAN equipment. Involve the administrator who owns switching, identity and internet access: an access point's feature list describes only part of the deployment.
Write requirements before requesting prices
List the busiest locations, simultaneous users and representative client models. State the task that must work in each space, such as an ordinary voice call, a browser application or a handheld inventory transaction. Record guest and staff separation needs and any managed authentication requirements.
Ask suppliers to identify the complete bill of materials: access points, mounts, power requirements, switching capacity, uplinks, gateway, management host and licenses. Check the exact hardware variants and supported software versions. Use Wi-Fi certification records to verify the scope of relevant certified features.
Separate mandatory acceptance gates from preferences. A solution that fails a required security or compatibility test needs remediation before weighted scores become meaningful.
Compare the complete lifecycle
On a narrow screen, scroll the table sideways. Keyboard: focus the table and use the arrow keys.
| Criterion | Evidence to request | Pilot or review result |
|---|---|---|
| Client experience | Exact supported features and design assumptions | Intended tasks succeed on representative devices in required locations |
| Power and backhaul | PoE requirements, port capacity and full topology | Installed infrastructure supports the proposed equipment under load |
| Administration | Roles, MFA, backups, exports and local/cloud dependencies | Assigned staff can perform and recover an authorized change |
| Licensing | Included functions, renewal terms and expiry behavior | Written model-specific explanation of management and traffic behavior |
| Support lifetime | Hardware and software lifecycle policy, replacement terms | Required operating period is covered or a replacement plan is costed |
| Exit and migration | Account ownership, configuration export and device release process | Your organization retains the access and records needed to move |
Cisco Meraki's co-termination licensing FAQ describes the consequences of license expiry under that licensing model. Ubiquiti's control-plane guide describes different management arrangements, including local consoles. These examples show why “cloud managed” alone tells you little about cost or failure behavior. Verify the exact arrangement being quoted.
Run the same pilot for each candidate
Use a representative area and repeatable device mix. Record placement, channel configuration, firmware, upstream service and the workload. Test busy-period conditions as closely as practical, and document any difference from production.
Include joining, the actual application task, movement through required coverage areas, sleep/wake and supported recovery after a planned service interruption. Test guest separation using authorized endpoints and the guest-management acceptance method. Have suppliers explain failures with evidence, then repeat corrected tests under the same conditions.
Give staff a practical administration task as well: grant a limited role, locate a client incident by timestamp, export a configuration record or follow a supported restore procedure in the pilot. A feature that exists but cannot be operated by the responsible team adds ongoing effort.
Use scores transparently
The WLAN pilot scorecard combines mandatory gates, observations and optional weighted preferences. It is an editable planning aid, not a vendor ranking.
Fictional scoring example: after all mandatory gates pass, assign weights of 40 to client experience, 25 to operations, 20 to lifecycle cost and 15 to exit readiness. On a 0–5 scale, scores of 4, 3, 5 and 2 produce (40×4 + 25×3 + 20×5 + 15×2) ÷ 5 = 73 out of 100. Preserve the observations behind each score; an untested item remains pending rather than receiving a guessed score.
The weights express your priorities. Change them before comparing candidates, and examine whether a modest change reverses the decision. That reveals a close tradeoff that deserves discussion.
Make the purchase reviewable
Compare the same ownership period and currency. Add hardware, installation, support, subscriptions, required internet services, training and planned replacement. Record quote dates, taxes and exclusions. Separate fixed charges from assumptions about future growth.
Retain the accepted topology, exact SKUs, pilot results, documented exceptions, account owner and renewal dates. Agree on the acceptance process for the real installation. A successful pilot is evidence for its tested conditions; the full site still needs verification after deployment.