Contact WiFi Hotshots — Fixed-Fee SOW From a 30-Minute Scoping Call
Send floor plans to sales@wifihotshots.com or call (844) 946-8746. Ekahau ECSE certified engineers scope, quote, and document every engagement as a fixed-fee SOW — no hourly billing, no scope ambiguity.
WiFi Hotshots is a vendor-agnostic enterprise network engineering firm serving enterprise customers, enterprise architects, infrastructure buyers, and network engineering teams across Southern California and the broader US market. Send us your scope; we’ll return a fixed-fee SOW within three business days.
Ekahau ECSE — Certified Survey Engineer on every engagement
Multi-CCIE engineering bench
Fixed-fee SOW — no T&M surprises
25 years of enterprise networking leadership
Valencia HQ — Southern California dispatch base
23890 Copper Hill Drive, #148
Valencia, CA 91354
(844) 946-8746 · sales@wifihotshots.com
Same-day dispatch radius
- 15 min → Burbank, Glendale, Santa Clarita core
- 30 min → Downtown Los Angeles, Woodland Hills, Simi Valley
- 60 min → Inland Empire (Ontario), Orange County (Irvine), Antelope Valley (Palmdale), Long Beach
- 90 min → San Diego, Palm Desert, Bakersfield
Outside Southern California, we dispatch by air for critical cutovers and coordinate regional install partners for routine work — all managed from Valencia.
When you contact us at WiFi Hotshots, you reach an engineer-led, vendor-agnostic wireless and network services firm headquartered in Valencia, California. Every inbound begins the same way: share the site, describe the scope, and we return a fixed-fee SOW within three business days of the scoping call. Learn more about the engineering credentials and 25-year leadership bench, review the enterprise wireless services overview, or see our vendor partnerships across Cisco, Meraki, HPE Aruba, Juniper Mist, RUCKUS, and Extreme. For detailed technical questions before a scope call, the engineering FAQ documents methodology, deliverables, and timeline expectations across the full service portfolio.
Contact Us Directly — Customer Success + Engineering Bench
Three direct paths to contact us, monitored by our Customer Success Manager (CSM) team and routed directly to engineering — not a sales funnel. Inbound from IT directors, network engineers, VPs of infrastructure, and procurement leads is triaged the same day it arrives.
Email — sales@wifihotshots.com
Email: sales@wifihotshots.com — acknowledged within 4 business hours during our posted hours; same-day for most inbound received before 2pm Pacific. Attach floor plans (CAD, PDF, or photographed as-built drawings), a rough device-count estimate, and one or two sentences describing the environment (building type, vendor in place, timeline). That is the minimum packet we need to begin predictive modeling in Ekahau AI Pro and return a written SOW.
Phone — (844) 946-8746
Phone: (844) 946-8746 — Monday through Friday, 7am to 6pm Pacific Time. After-hours voicemail is monitored by the engineering on-call rotation for active-incident inbound (controller failure, outage support, pre-scheduled cutover coordination). The on-call engineer returns the call inside 60 minutes for declared emergencies; non-emergency voicemail is returned the next business morning.
Headquarters — Valencia, California
Headquarters: 23890 Copper Hill Drive #148, Valencia CA 91354. The Valencia dispatch base sits inside the Santa Clarita Valley, 45 minutes by vehicle from downtown Los Angeles outside rush traffic, 15 minutes from Burbank, and 90 minutes from Bakersfield. On-site engagements inside Southern California are dispatched from this HQ; national multi-site rollouts mobilize a regional tech via vetted partners on the same fixed-fee SOW structure. LinkedIn: linkedin.com/company/wifi-hotshots.
Send floor plans directly to sales@wifihotshots.com — most Southern California engagements are scoped and quoted on a fixed-fee SOW within three business days of a 30–60 minute scoping call, not hourly billing.
What Happens After You Contact Us
The intake-to-engagement cadence is documented so you know what to expect and when. We do not use an open-ended estimate or a retainer to absorb scope creep; every step ties to a named deliverable and a written quote.
Day 1 — Acknowledgement and Scope Clarification
A WiFi Hotshots Customer Success Manager (CSM) — not an account coordinator or call-center bot — acknowledges the inbound within 4 business hours and triages the request to the right engineering discipline. If the submitted packet is complete (floor plans at scale, device count, vendor context, construction type, timeline target), the CSM routes it to the engineering bench and predictive modeling begins the same day in Ekahau AI Pro or in the appropriate design platform for non-wireless work (Cisco Catalyst Center for campus LAN, Juniper Mist Wired Assurance for switched LAN, vendor-native design tools for SD-WAN fabrics). If scope is ambiguous, the CSM schedules a 30-minute scope call with the engineer who will own the design rather than guessing. Scope calls happen on Zoom, Webex, or Teams — whichever platform your organization operates on.
Day 2 — Written SOW Quote
Within three business days of the scoping call, we return a written SOW containing: scope-of-work narrative, methodology (predictive design, AP-on-a-Stick validation, post-install validation, or combined passes), deliverable list, timeline, and fixed-fee price. The SOW is signed before any on-site work begins. If scope changes during engagement, a change order is issued in writing and signed before the additional work is performed. The client is never invoiced above the SOW total without a signed change order. That is the operational definition of a fixed-fee engagement.
Kick-Off — Pre-Survey Coordination
Before mobilization, a pre-survey coordination document is issued: site-access contacts, escort requirements, HIPAA or PCI badge protocols where applicable, building-access credentials, infection-control constraints for clinical floors, production-schedule access windows for soundstage and retail-operating environments, and the survey phase-by-phase plan. The document identifies which test phases, if any, require an off-hours window. For multi-site rollouts, the coordination document is templated per site so regional teams have the same standard operating procedure.
Engagement — On-Site or Remote Delivery
On-site engagements dispatch from the Valencia HQ or from a regional tech for national rollouts. Remote-capable engagements — controller configuration review, SD-WAN policy design, security architecture review, voice/UC platform migration planning — run over Zoom/Webex/Teams and vendor management consoles without site dispatch. Every engagement closes with a formal deliverable handoff: survey reports, configuration documentation, as-built drawings, or runbooks. The documentation belongs to the client and is formatted for a 10-year shelf life.
Floor plans and device counts are all we need to scope the work — most engagements are quoted on a fixed-fee SOW within three business days of a 30–60 minute scoping call.
Contact Us From Any Southern California Metro — Service Area and Dispatch Times
Dispatch times below are measured from the Valencia HQ at 23890 Copper Hill Drive #148 under typical traffic. Site-specific access credentialing (HIPAA escort, PCI-zone access, airport access with Part 161 coordination, school-district LiveScan badging) is factored into on-site scheduling, not mobilization time.
- Santa Clarita Valley (home): Valencia, Newhall, Saugus, Canyon Country, Stevenson Ranch — inside the same zip-code corridor as HQ. Same-day mobilization routine. See Santa Clarita site survey coverage.
- San Fernando Valley: Burbank, Van Nuys, Northridge, Encino, Studio City — 15-minute dispatch via the 5 and 405 corridors. See San Fernando Valley site survey coverage.
- Los Angeles metro: Downtown LA, Hollywood, Century City, LAX, West LA, South Bay — 30- to 45-minute dispatch. See Los Angeles site survey coverage.
- Antelope Valley: Palmdale, Lancaster, Mojave, Rosamond — 60-minute dispatch via the 14 corridor. See Antelope Valley site survey coverage.
- Inland Empire: Ontario, Riverside, San Bernardino, Corona, Rancho Cucamonga — 60-minute dispatch to Ontario, 90 minutes to Riverside. See Inland Empire site survey coverage.
- Orange County: Irvine, Anaheim, Santa Ana, Costa Mesa, Newport Beach — 60- to 75-minute dispatch via the 5 and 405 corridors. See Orange County site survey coverage.
- San Diego: Downtown San Diego, Carlsbad, La Jolla, Chula Vista — 2-hour dispatch via the 5 corridor; overnight stay routine for multi-day surveys. See San Diego site survey coverage.
- Coachella Valley: Palm Desert, Palm Springs, Indian Wells, La Quinta, Rancho Mirage — 2-hour dispatch via the 10 corridor. See Palm Desert site survey coverage.
- Kern County: Bakersfield, Taft, Delano, Shafter — 90-minute dispatch via the 5 and 99 corridors. See Bakersfield site survey coverage.
National Multi-Site Rollouts
National rollout capability extends beyond Southern California through a vetted regional-technician partner network operating under the same fixed-fee SOW structure. We have scoped and delivered 1,000-plus store rollouts across a national discount retail chain, distribution center and store rollouts across a national pet retail chain, and multi-campus concurrent validation within a 72-hour window for a top-tier academic medical center.
Engagement structure is identical regardless of geography: a WFHS engineer owns the design, survey methodology, and deliverable quality; regional partners execute on-site work under our standard operating procedure, with remote oversight from the Valencia HQ. Client-facing reporting remains centralized. Confidentiality and NDA structures are standard — we do not name clients publicly.
What to Send With Your Floor Plans
The packet below is the minimum information required to produce a written SOW within three business days of the scoping call. Missing items do not block the response; we schedule a 30-minute scope call to capture what is missing. Submitting the full packet up-front reduces the scope-call round trip and accelerates the quote.
- Floor plans at measured scale: CAD-exported PDF, native DWG/DXF, or a photographed as-built drawing with a known reference distance so it can be re-scaled in Ekahau AI Pro. Per-floor plans for multi-story buildings, not a single stacked view.
- Rough device count per zone: number of wireless clients expected per floor or per area (employees, guests, BYOD, IoT, scanners, handsets, medical devices, POS terminals). An approximate figure is sufficient — we refine during scope.
- Current vendor and platform if this is a refresh: Cisco Catalyst 9800, Meraki dashboard, HPE Aruba ArubaOS 8/10 or Central, Juniper Mist, RUCKUS SmartZone, Extreme ExtremeCloud IQ, or legacy on-prem controller. Model numbers where known.
- Construction type: drywall-and-stud office, CMU block, tilt-up concrete, poured concrete with rebar, plaster-over-metal-lath, sheet-metal hangar, steel-truss soundstage, high-bay warehouse rack, historic brick. If unknown, flag it and we confirm during survey.
- Timeline target: survey completion date, go-live date, any hard constraints (school summer recess, retail holiday blackout, clinical census pattern, sports or concert event calendar, audit or compliance deadline).
- Regulatory constraints: HIPAA segmentation requirements, PCI-DSS scope, E-rate FY2026–2030 Category 2 procurement rules, CJIS for law enforcement, ERRCS applicability (LA County 50,000 sq ft / three-story threshold or equivalent), California Title 24 Part 6 energy-code constraints on AP-type selection.
- Access and credentialing: escort requirements, infection-control policies, PCI-zone access, airport Part 161 coordination, school-district LiveScan, badge lead time, visitor-registration platforms (iVisitor, Envoy, Proxyclick) in use.
Large attachments: send via email if under 25 MB; for larger packets, request a secure upload link in your initial email and we issue a time-bound link (Sharepoint, Google Drive, or client-preferred platform). NDA and MSA execution happens before any floor-plan material crosses our boundary when the client requests it — send the NDA template with your initial email and we countersign inside one business day.
Scope a Site Survey.
Email sales@wifihotshots.com or call (844) 946-8746 to start a scope call — written SOW returned within three business days of the scoping call.
Contact WiFi Hotshots FAQs
How fast can you respond to a scope request?
Inbound to sales@wifihotshots.com is acknowledged by a Customer Success Manager within 4 business hours during our posted hours of Monday through Friday, 7am to 6pm Pacific. Submissions received before 2pm Pacific on a business day are typically acknowledged the same day.
A complete packet — floor plans at scale, device count estimate, vendor context, construction type, timeline target — returns a written SOW within three business days of the scoping call.
If the packet is incomplete, we schedule a 30-minute scope call within one business day and produce the SOW within three business days of the scope call.
After-hours voicemail to (844) 946-8746 is monitored by the engineering on-call rotation; declared emergencies are returned inside 60 minutes, non-emergency voicemail the next business morning.
We do not use a sales-funnel autoresponder as the first-touch reply — the acknowledgement comes from a Customer Success Manager who triages scope with the engineering bench.
Do you quote remotely or require a site visit before pricing?
Most engagements are quoted remotely. Floor plans at measured scale plus a rough device count per zone is sufficient for Ekahau AI Pro predictive modeling and a fixed-fee SOW within three business days of the scoping call.
A site visit before quote is only required when the construction materials cannot be confirmed from drawings (historic brick, unknown shear-wall reinforcement, opaque above-ceiling conditions in infection-controlled clinical environments, sheet-metal aerospace hangar shells) or when access credentialing is a scoping factor in itself (airport Part 161, data-center colo, CJIS-controlled law-enforcement space).
A pre-quote walk-through inside Southern California is included at no charge when we judge it necessary.
Outside SoCal, pre-quote walk-throughs are quoted as a separate line item when required — most national rollouts do not need one because drawings and construction type are documented at the procurement level.
Can we share an NDA before sending floor plans?
Yes. Send your NDA template with the initial email and we countersign within one business day. We operate under both one-way and mutual NDA structures routinely, including NDAs that require data-handling protocols (SharePoint-only upload, no local copies, document-watermarking, per-engineer named access).
If your organization does not have a template, we issue a mutual NDA template drafted for engineering-services engagement scope — covers site drawings, network topology, device inventory, IP addressing, and configuration material.
NDA execution happens before floor-plan material crosses our boundary when the client requests it.
MSA execution (master services agreement) is similarly fast — most MSA reviews clear legal inside three business days of a scoping call when the MSA is not heavily customized.
SOW-only engagements without a parent MSA are also routine.
Do you work weekends or evenings for surveys that cannot happen during business hours?
Yes. Off-hours surveys are routine: retail stores surveyed overnight between close and restock, clinical environments surveyed during low-census windows, K-12 districts surveyed during summer recess and winter break, soundstages surveyed during production dark days, data centers surveyed during scheduled maintenance windows, trading floors surveyed before market open or after market close, warehouses surveyed during shift-change or overnight.
Off-hours and weekend work is quoted on the same fixed-fee SOW; the surcharge (if any) reflects actual incremental cost, not a premium multiplier.
Pre-survey coordination documents identify which test phases require a specific window and schedule around your operational reality.
We do not surprise a retail manager with a noon survey during lunch rush.
How do you handle after-hours emergency support for active incidents?
After-hours voicemail to (844) 946-8746 is monitored by the engineering on-call rotation. For declared emergencies — controller failure, site-wide WLAN outage, post-cutover rollback, active production incident — the on-call engineer returns the call inside 60 minutes. Emergency response is quoted separately from standard fixed-fee SOW engagements and is structured as an emergency statement of work issued in writing before billable work begins.
Clients on active managed-services retainers have an established incident-response SLA documented in the retainer; non-retained inbound is supported on a time-and-materials basis under a signed emergency SOW.
Emergency and temporary connectivity deployments for disaster recovery or live-event backup are a discrete service line; see emergency connectivity for scope.
Do you serve sites beyond Southern California?
Yes. National rollout capability runs through a vetted regional-technician partner network, operating under the same fixed-fee SOW structure and WFHS standard operating procedure. We have scoped and delivered a 1,000-plus store rollout for a national discount retail chain, a distribution-center and store rollout for a national pet retail chain, and multi-campus concurrent validation within a 72-hour window for a top-tier academic medical center.
Structure: a WFHS engineer owns design, methodology, and deliverable quality; regional partners execute on-site work under remote oversight from Valencia; client-facing reporting stays centralized.
International engagements are considered case-by-case.
Client names are not disclosed publicly; industry/vertical references are provided in the SOW and SOW reference calls arrangeable for enterprise procurement diligence.
What is your minimum project size?
No fixed minimum. We scope single-floor predictive surveys, single-site AP-on-a-Stick validations, and controller-configuration reviews on the same fixed-fee SOW structure used for multi-building campus work. The deliverable quality does not change with project size — a single-floor Ventura Boulevard tenant-improvement survey gets the same Ekahau .esx project file, heatmap exports, vendor-agnostic AP BOM, and installation runbook that a multi-building healthcare campus gets.
What changes with scale is the timeline and the survey methodology mix (predictive-only vs. predictive-plus-AP-on-a-Stick vs. predictive-plus-validation).
Small engagements are genuinely welcome; the engineering team is not optimized for a minimum project size.
If you are unsure whether your scope fits, email a two-sentence description and we answer the same business day.
Do you offer ongoing managed services after a project closes?
Yes. Ongoing managed services are available as a separate retainer engagement, structured as a fixed monthly fee with a defined scope: controller platform health monitoring, firmware patch management, incident response with documented SLA, quarterly RF health reports, and pre-scheduled change-window support.
Managed-services retainers are not automatic; they are a deliberate client decision made post-project, typically when the client organization does not carry in-house enterprise WLAN engineering expertise.
Clients with mature internal networking teams often use WFHS for project work only and handle day-two operations internally — that is a valid and common model.
We do not require a managed-services retainer as a condition of project delivery. For clients on retainers, incident inbound has priority over new-project scope queue.
Contact Us at WiFi Hotshots — a minority-owned, engineer-led wireless and network services firm with 25 years of enterprise networking leadership. Our practice runs on Ekahau Connect with Ekahau ECSE certified survey engineers and a multi-CCIE bench — every engagement a fixed-fee SOW, vendor-agnostic, and documented to a standard your operations team can reference for the life of the infrastructure. Email sales@wifihotshots.com, call (844) 946-8746, or visit the Valencia HQ at 23890 Copper Hill Drive #148, Valencia CA 91354. For detailed service-line context before contact, review the full service portfolio, the engineering team and credentials, or the engineering FAQ.
Contact Us — Further Reading
Adjacent service lines that intersect with the engagement most readers land on /contact-us/ to start. Each link below describes how the destination service line behaves once you have decided to engage — what gets scoped, what gets surveyed, what gets quoted, what gets delivered, and what the post-engagement deliverable looks like — not the destination service line in the abstract.
- Enterprise wireless engineering — the most common inbound: a fixed-fee site survey scoped from floor plans within three business days. Predictive modeling in Ekahau AI Pro with Ekahau Sidekick 2 hardware, AP-on-a-Stick validation under ECSE-certified methodology, and post-install validation against −67 dBm RSSI and 25 dB SNR design targets per CWNP CWDP design discipline; deliverable is the .esx project file, heatmap exports, vendor-agnostic AP BOM, and installation runbook in your hands — not a vendor portal screenshot.
- Campus LAN refresh — what gets scoped on a wired-access engagement: per-MDF and per-IDF Cat 6A drop counts, multigig (2.5/5/10GBASE-T) per IEEE 802.3bz, IEEE 802.3bt Type 4 (90 W) PoE budget per IEEE 802.3bt-2018 at every access port, MACsec link encryption per IEEE 802.1AE-2018 on switch-to-switch trunks, and the StackWise Virtual / VSF / VC stacking control-plane decision — quoted as a fixed-fee SOW from existing drawings without a pre-quote site visit in most cases.
- Data center fabric design — what an EVPN-VXLAN spine-leaf engagement actually delivers: rack elevations, MPO fiber-trunk count per row, polarity Method A/B/C decision documented before procurement per ANSI/TIA-568.3-E, EVPN Type 2 / Type 5 route-exchange topology per IETF RFC 8365, anycast-gateway scale planning, and the DCI handoff that carries north-south traffic to the campus core — closed out with a written acceptance pass against vendor admin-guide configuration baselines.
- SD-WAN fabric design and migration — what a branch-edge engagement scopes from your existing drawings: dual-carrier diverse entrance pathway, IPsec / IKEv2 underlay tunnels per IETF RFC 7296, per-VRF service-VPN policy that tags voice / video / clinical / OT / guest at the LAN-side trunk handoff, application-aware path selection on SIP signaling vs media, and AppQoE / FEC during transient brownouts — mobilized as a remote design engagement first, on-site only when the demarc panel or carrier handoff requires physical inspection.
- Network security architecture — what gets reviewed on a security-architecture engagement: 802.1X EAP-TLS supplicant certificate handling per IETF RFC 5216, NAC policy (Cisco ISE 3.4, HPE Aruba ClearPass 6.12, Juniper Mist Access Assurance, Forescout 4D), east-west microsegmentation enforcement on the EVPN-VXLAN overlay, ZTNA / SASE PoP placement for remote-access edge, and zero-trust verification mapped to NIST SP 800-207 rather than to a vendor self-attested telemetry dashboard.
- Unified communications migrations — what a Webex Calling, Microsoft Teams Phone Direct Routing, Zoom Phone, or RingCentral migration delivers: SBC perimeter design, SIP-TLS signaling per IETF RFC 5630 and SRTP media per IETF RFC 3711, STIR/SHAKEN inbound-attestation per IETF RFC 8224 and RFC 8226, E911 dispatchable-location validation, and post-cutover MOS / R-factor measurement per ITU-T G.107 — quoted as a fixed-fee migration SOW from a 30-minute scoping call.
- Structured cabling — what a cable-plant design package contains when WFHS is the engineer of record: AutoCAD plans, CSI Division 27 00 00 specification, BOM, commissioning plan, and post-install Fluke DSX-8000 channel and permanent-link certification to ANSI/TIA-568.2-E Cat 6A limits with full per-pair measurement, OTDR Tier 2 fiber characterization, bonding-and-grounding verification per ANSI/TIA-607-E, and the LinkWare PC archive turnover so the cable-plant warranty travels with the closeout package.
- AI-ready infrastructure — what gets scoped on a GPU-cluster network engagement: GPU count and collective-communication profile (NCCL ring vs tree, all-reduce dominant vs all-to-all), spine-leaf vs rail-optimized topology decision, RoCEv2 lossless transport per IBTA RoCEv2 Annex A17 with PFC / ECN policy at the leaf, 800GBASE-FR4 OS2 single-mode trunks per ANSI/TIA-568.3-E, and a fabric design that names the Spectrum-X, Etherlink, Silicon One G200, or Quantum-X800 platform on the spec rather than handing you a generic reference architecture.
Contact Us Engineering References
Technical claims on this page are cited against primary sources where applicable. RF design coverage targets referenced elsewhere on the site (‑67 dBm RSSI minimum, 25 dB SNR) derive from Cisco Meraki Site Survey Guidance and the CWNP RF Design Methodologies. Ekahau Sidekick 2 hardware and Ekahau AI Pro software specifications per Ekahau Sidekick 2 product page and Ekahau AI Pro product page.
Wi-Fi 6/6E and Wi-Fi 7 certification program definitions per Wi-Fi Alliance CERTIFIED 6 Resources and Wi-Fi Alliance CERTIFIED 7 Resources. 6 GHz device class rules (LPI, Standard Power, VLP) per FCC Part 15 Subpart E. CWNP CWDP design certification per CWNP CWDP page. NetAlly AirCheck G3 Pro for independent post-install validation across 2.4, 5, and 6 GHz. Ekahau ECSE certification per Ekahau ECSE certification program.