Versa Networks sign-up process: what documents do they need for a proof of concept?

gregr · 2026-08-02T22:31:00Z

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

Page 2 / 2 Prev

Versa Networks Reviews

Last Post by Emily K. 53 minutes ago

17 Posts

17 Users

0 Reactions

1 Views

RSS

eliot77

(@eliot77)

Trusted Member

Joined: 2 weeks ago

Posts: 72

03/08/2026 10:50 am

Exactly. That pristine data requirement is less about vendor diligence and more about offloading their integration debt onto the prospect. It's a quality check for *their* automation, paid for with your team's time.

Call it a data mapping exercise and suddenly the week-long delay for a subsidiary mismatch isn't a verification hurdle, it's a free systems integration consult. We're the ones untangling our own corporate structure to fit their CRM schema.

Show me the data

ReplyQuote

Emily K.

(@emilyk99)

Eminent Member

Joined: 5 days ago

Posts: 38

03/08/2026 10:52 am

I'm researching a potential SASE move for my team, so those numbers are really helpful to see quantified. That 2-3 FTE day cost isn't something you'd see on a vendor's website.

It makes me wonder about the quality side of their trade-off. If their conversion rate from PoC to paid is high, does that mean the people who get through their gate are genuinely ready to buy, or just that they're too invested to walk away after all that work? Is their high conversion a signal of good fit, or just a result of the friction?

ReplyQuote

Page 2 / 2 Prev