Having recently navigated the process of initiating a proof of concept with Versa Networks for a potential SASE architecture implementation, I found the documentation requirements to be more comprehensive than those of some other vendors in the networking and security space. My interest was piqued by their integrated approach, promising a unified stack for SD-WAN, security, and analytics, which led me down the path of requesting a PoC. For fellow tinkerers and architects considering a similar evaluation, here is a detailed breakdown of the documents and information they typically require to commence a formal proof of concept engagement.
Based on my experience and corroborated by discussions with their sales engineering team, the following items were necessary to move beyond the initial demo stage. It's worth noting that the exact list can vary slightly depending on the scale and declared intent of your PoC, but this forms the core.
* **Corporate Documentation:** This establishes the legitimacy of your organization. They required a copy of our business license or certificate of incorporation. This is fairly standard when dealing with enterprise software vendors, especially those providing security-focused solutions.
* **Technical Environment Overview:** A detailed, non-public network diagram was essential. This needed to illustrate current WAN topology, primary and branch office locations, internet breakouts, and existing security appliances (firewalls, proxies). They were particularly interested in understanding traffic flows and potential insertion points for their Controllers and Gateways.
* **PoC Scope & Success Criteria Definition:** We had to collaboratively draft a document outlining the specific features to be tested. This went beyond "test SD-WAN." We itemized use-cases like:
* Application-aware path selection policies for SaaS traffic.
* IPSec tunnel establishment between a cloud gateway and a simulated branch CPE.
* Integration of their cloud-delivered firewall with a subset of our internal services.
* Basic reporting and monitoring capabilities during the trial period.
* **Contact Information Roster:** A clear list of technical and business contacts from our side, including roles (network architect, security lead, project manager) and their responsibilities within the PoC. This ensures efficient escalation and support.
* **IP Addressing Scheme:** They requested our planned internal and external IP address ranges for the PoC infrastructure to avoid conflicts and assist in configuration templating. This included public IPs for their CPE devices and private subnets for simulated user networks.
* **Signed PoC Agreement:** A formal document provided by Versa outlining the terms of the evaluation, including duration (typically 30-60 days), support levels, data handling policies, and the process for returning or decommissioning equipment after the trial.
The process felt more structured than, for instance, setting up a pure cloud-service PoC with a vendor like Cloudflare or Zscaler, where the initial barrier is often just a credit card. The requirement for the network diagram and success criteria, however, was immensely beneficial. It forced a disciplined evaluation framework and allowed their engineers to pre-configure elements of their Versa Director and Versa Controller platforms, which significantly accelerated the *actual* hands-on tinkering phase once the virtual appliances or hardware were provisioned.
For those preparing to engage, I would strongly recommend having these documents prepared in advance. The most time-consuming part for us was sanitizing and detailing the network diagram to a sufficient level. Compared to initiating a PoC with a more component-oriented vendor like a standalone SD-WAN provider, Versa's process reflects the complexity of their integrated stack—they need a clearer picture of the entire system to ensure a valuable evaluation. The payoff is that once provisioned, the environment is quite rich for comparative testing against a fragmented toolset.
testing all the things
throughput first
That's a very accurate starting point. Their focus on corporate documentation upfront, while standard, really sets the tone for the kind of engagement Versa is looking for. I've seen them use this not just for legitimacy, but as a filter for readiness. If an organization can't quickly provide those basic artifacts, it often signals they aren't far enough along in their internal procurement or planning process to justify the resource investment a true PoC requires from their SE team.
It's a subtle but effective way to separate tire-kickers from genuine evaluators. Compared to some other vendors who'll hand out trial licenses with just an email, this initial hurdle ensures everyone's time is spent on qualified opportunities. The variation you mentioned based on PoC scale is key - for a single-site lab, they might move faster, but for a multi-branch rollout simulation, expect the documentation phase to be even more rigorous, possibly extending to network topology diagrams and security policy overviews before any hardware even ships.
Exactly. That filter's effective but it's also a cost driver for their sales cycle.
Ran some numbers for a blog post comparing onboarding friction across vendors. Versa's pre-PoC admin overhead is high, roughly 2-3 FTE days for a medium enterprise to gather and sanitize those docs. That's a real internal cost before you even see the product.
The vendors that hand out trials on an email? Their conversion rate to paid is lower, but their total addressable market for PoCs is huge. It's a volume vs. quality trade-off. Versa's betting on the latter.
Benchmarks don't lie.
That's a really helpful and specific start. The corporate documentation piece is exactly where many evaluators either stumble or realize they need to align internal stakeholders first. I've found that while it's a common requirement, the way Versa verifies it is quite thorough; they often cross-reference the details on that business license with the domain in your email address and the stated company size.
This can actually be a positive checkpoint for you internally. If gathering that single document reveals friction or confusion within your own organization, it might be a sign to pause and solidify your project's sponsorship before proceeding further with any vendor. It saves everyone time in the long run.
Looking forward to seeing the rest of your breakdown, especially on the technical scope documents.
Stay curious.