Vendor-neutral isn't a marketing line. It's a set of rules we wrote down.

Our vendor-neutrality rules

1. 01No OEM referral revenue. Ever. We don't accept finder's fees, rebates, or back-end margin from any hardware OEM, software vendor, integrator, or carrier.
2. 02No preferred-partner programs. We're not in any vendor's partner program at any tier.
3. 03No vendor-paid travel or events. We attend vendor briefings — we pay our own way.
4. 04Multi-vendor designs by default. Where a single-vendor stack is the right answer, we say so in writing with a documented rationale. Where it isn't, we design across vendors.
5. 05Client owns the data. Raw survey data, configurations, drawings, and methodology documents belong to the client at delivery. We retain only what we need for our own records.
6. 06Hand-off is portable. Our deliverables are written so any qualified integrator can build them. You're not locked to us at construction.

How we run an engagement

Most of our engagements follow the same shape, even when the technical work is different. The phases below are deliberate; we'd rather skip a phase than do it half-way.

1. 01Discovery. We walk the site, read the help-desk tickets, sit with operations, and read the last two years of incident reports. We're trying to understand the actual failure modes, not just the requested coverage map.
2. 02Baseline measurement. Calibrated equipment, documented methodology, written assumptions. The baseline is what every subsequent design decision will be compared against.
3. 03Design. Predictive modeling, on-site validation, and an engineered design package. The design is vendor-neutral by default; where it isn't, the rationale is in writing.
4. 04Procurement support. RFP authorship, bid review, vendor selection, and contract review. We're in the room with you, not behind a one-way mirror.
5. 05Construction oversight. Periodic site visits, RFI review, and integrator hand-off. We're not a project manager — but we're available when the integrator and the design diverge.
6. 06Acceptance. Witnessed testing against the criteria we agreed to in design. Pass/fail, with documentation.

What we hand you

The artifacts vary by engagement. The principles don't.

• Raw data. Survey traces, drive-test logs, controller exports — in the equipment's native formats, not summarized PDFs.
• Methodology documents. What we measured, how, with what equipment, and what we assumed. You can reproduce our work; that's the point.
• Engineered drawings. Antenna placement, cable runs, IDF assignments, power budgets, and a vendor-neutral BOM.
• Decision documents. Where we recommended one option over another, the reasoning is in writing with dissenting considerations called out.
• Acceptance test plans. Pass/fail criteria, witnessed test procedures, and the data structure for the final test report.

Where we'd disagree with a typical brief

We'd rather have the disagreement up front. A few things we've learned to push back on:

• "Just match what the vendor recommended" usually doesn't survive the on-site survey. We'd rather argue the survey results than skip the survey.
• "Coverage everywhere" is rarely the actual requirement. We work to identify the specific places coverage matters and the specific devices that are driving the requirement.
• "Add more APs" or "swap to a different vendor" are two of the three most common recommendations we see. The third is "fix the channel plan and reconfigure roaming thresholds." It's almost always cheaper.