30 days. No fee. Three deliverables yours regardless of what you decide at day 30.
The pilot is structured so the Director can evaluate without budget commitment and walk away with usable artifacts even if the decision is no. The terms below are the standard pilot; minor adjustments are negotiable on request, but the shape stays the same. The pilot is not a sales tactic; it's the actual way the platform proves itself in your environment.
30 calendar days. Three signed artifacts. Yours regardless of what you decide at day 30.
The terms.
Duration: 30 days
Starts on the day the ESE is fully deployed and connected to the in-scope switches. Pilot can be extended by 15 days at customer request if the calendar slips; no fee for the extension. Most pilots complete on time.
Cost: no fee
No license fee for the 30-day pilot. No setup fee. No professional-services charge for the deployment or the kickoff. You cover the small on-prem server the ESE runs on (Linux or Windows; lightweight; no specific hardware spec) and the network access credentials for the in-scope switches. That's the full customer-side cost.
Scope: customer-selected, segment-bounded
You pick the segment: one VLAN, one building, one network zone, one set of conference rooms. Typical pilot scopes 50 to 500 devices and 5 to 50 switches; larger scopes are possible but extend the deployment window. The framework you map evidence against is your choice (PCI 4.0, SOC 2, HIPAA, NIST CSF 2.0, CMMC L2, NDAA 889, or just an inventory baseline without a framework cover-sheet).
Three deliverables, yours at day 30 regardless of decision
(1) The continuous inventory export for the piloted scope. Signed, PDF + JSON. (2) The 30-day drift report covering every change observed during the pilot window, cross-referenced against your change-management system where you integrate it. Signed, PDF + JSON. (3) The evidence pack mapped to the framework you selected, with control-by-control mapping. Signed, PDF + JSON. You keep all three even if you decide not to proceed.
What we ask of you
Kickoff call attendance (60 minutes, network engineer plus optional security or audit lead). Read-only switch credentials provisioned before day 1 (typical pre-work: 1 to 3 hours of your network team's time). Network connectivity from the ESE to the in-scope switches. A point of contact for change-management integration if you want auto-suppression on approved changes (optional). Standard MNDA signed on our form or yours.
What we don't ask of you
No hardware purchase. No SPAN or mirror-port provisioning. No agents on the devices being inventoried. No write-access to your switches. No commitment to proceed at day 30. No restriction on running competing pilots in parallel. No reference-call obligation if you do proceed (we'll ask, but it's voluntary).
What happens at day 30.
Three outcomes are possible. Decision to proceed: we move to a paid agreement scoped to your full environment. Standard contract length is 12 months, with the pricing depending on environment shape and product (RoomIQ per-room SKU or SpacesIQ deployment-scale). Decision to wait: we decommission the cloud instance within 5 business days, you keep the three deliverables, and we close out cleanly. The on-prem ESE is your software to decommission on your own schedule. We don't re-engage automatically; if you want to revisit later, you call us. Decision to extend: if you need more data or you're aligning to a calendar (audit, renewal, board meeting), we extend the pilot by up to 15 days at no fee. Beyond that, we'd convert to a short-term paid engagement.
The pilot terms are designed to remove procurement friction. No PO required for the pilot itself (MNDA is the only paper). No data exits your environment that you haven't reviewed. No code on devices outside the ESE you control. If procurement wants a stronger commitment from us about the boundary, the MNDA covers most of the standard ask; if they need more, the demo closes with the additional terms you'd want in writing before kickoff.
Ready to scope the pilot?
A live demo of the platform and a conversation about whether CybrIQ fits your environment. If we agree a pilot makes sense, we scope it after the demo.
Book a demo