NETIFY PROCUREMENTPrivate drafting. Anonymous publication. Buyer-controlled engagement.
Procurement service
Private draft

SD-WAN & SASE procurement

Get proposals for your SD-WAN or SASE project.

Bring an existing or AI-generated RFP, or build your requirement here. Publish anonymously and choose which supplier requests to approve.

Paste or import your brief below. Supplier participation and proposals are not guaranteed.

Start privately. No company name or email needed yet.

Already have a brief or RFP? Paste it above.
Free to publish. No commitment to buy.Suppliers pay Netify when an introduction leads to business.

From your RFP to supplier discussions

Bring your RFP. Publish your requirement. Choose who can respond.

Netify is a procurement service for SD-WAN and SASE projects. Bring an existing RFP, including one drafted with an AI assistant, or build a simple RFI or detailed RFP here. Review what will be shared, verify your work email and publish an anonymous opportunity.

  1. Bring or build your requirement. Paste your existing brief or import its text, then check the scope and supplier questions.
  2. Approve anonymous publication. Your public listing excludes your name and contact details. Remove identifying details from the fuller requirement you authorise approved, signed-in suppliers to review.
  3. Review requests to bid. Approved suppliers can review that requirement and ask to engage. Publication does not automatically invite every provider in Netify's research directory.
  4. Choose your supplier discussions. Approve the requests you want to pursue. Approval opens a private conversation where you and that supplier can discuss its approach and proposals.

Free to publish, with no commitment to buy. Supplier participation, proposals and response times are not guaranteed. An RFI can ask for capabilities and indicative information; a detailed RFP can request a proposal against your selected questions.

See an illustrative supplier response journey

Demonstration only. The requirement, supplier and messages below are fictional. This is not a live project, an actual supplier response or evidence that suppliers will participate.

Example requirement
A business needs managed SASE for its offices and remote users, with a phased move from its existing VPN.
Fictional supplier request
We would like to discuss your migration and support requirements before preparing a proposal.
Example buyer decision
The buyer approves this request to open a private conversation. Other requests can remain unapproved.
Fictional supplier reply
We suggest a discovery stage and a pilot. Please confirm your locations, user numbers and identity platform so we can explain our proposed scope, assumptions and pricing.

No supplier names, prices, response counts or success rates in this demonstration describe real marketplace activity.

Start with your requirement.

SASE and SD-WAN RFP guidance, examples and methodology
SD-WAN RFP
An SD-WAN RFP is a request for proposal that sets out an organisation's sites, underlay circuits, application performance targets, failover, security integration and managed service needs so that SD-WAN vendors and service providers can respond with comparable, priced bids.
SASE RFP
A SASE RFP is a request for proposal for converged networking and security delivered from the cloud: SD-WAN plus ZTNA, SWG, CASB, FWaaS and DLP, with identity, data residency, logging and operating model requirements stated so that SASE vendors can be evaluated on the same criteria.

What an SD-WAN or SASE RFP covers

The eight areas below are the sections Netify builds and validates. Each row shows the SD-WAN emphasis, the SASE emphasis and the evidence Netify recommends requesting from suppliers; adapt them to your own procurement rules. Reviewed .

SD-WAN and SASE RFP sections compared: what each area covers and the supplier evidence Netify recommends requesting. Source: Netify governed question bank; content reviewed 2026-11-08.
RFP areaSD-WAN RFPSASE RFPSupplier evidence
Organisation and scaleSites, regions, users per site, growth plans and the procurement route.Remote and hybrid users, devices, identity provider and data residency by region.Site list, user counts and regions stated in the RFP; supplier confirms coverage per region.
Network architectureUnderlay circuits, WAN topology, hub and cloud on-ramps, application performance targets, QoS and routing.PoP footprint, cloud on-ramps, traffic steering between SD-WAN and the security edge, private application access.Reference architecture, PoP list with locations, latency and throughput figures per region.
SASE securityFirewall integration, segmentation and how security is applied at the branch.ZTNA, SWG, CASB, FWaaS, DLP, threat prevention, identity and device posture, logging and SIEM integration.Capability statement per function, single-vendor or partner delivered, certifications and independent test results.
ResilienceAccess diversity, failover behaviour, availability targets per site tier and disaster recovery.PoP redundancy, fail-open or fail-closed policy, control plane availability and regional fallback.Published SLA, availability history and a description of the last significant incident.
Managed serviceService ownership, service desk, change management, monitoring, reporting and co-managed options.Policy administration, incident response, SOC integration and who owns the security policy day to day.RACI, escalation path, sample monthly service report and named service management roles.
ImplementationDiscovery, pilot sites, migration waves, cutover and rollback, dependencies and training.Identity integration, agent rollout, legacy VPN and proxy retirement, phased policy migration.Implementation plan with milestones, pilot acceptance criteria and named delivery team.
Pricing and contract termsPricing model per site and per circuit, hardware, licences, contract term, indexation and exit.Pricing per user and per function, bundles, licence tiers, overage, term and exit provisions.Itemised pricing schedule, total cost over the proposed contract term (Netify recommends a three-year basis for comparison) and the assumptions behind it.
Supplier evidenceCustomer references in comparable sectors, accreditations and financial standing.Analyst coverage, security certifications, data handling and sub-processor disclosure.Customer references (Netify recommends at least two, in comparable sectors), certification copies, insurance and the evidence request answered in full.

Read the SD-WAN and SASE question bank that the builder draws from, or see a finished document: the SASE sample RFP (identity, ZTNA, SWG, CASB, FWaaS and SSE) and the SD-WAN sample RFP (routing, underlay, application performance, failover and managed operations).

SD-WAN and SASE RFP questions answered

Can I use an AI-generated or existing RFP to get supplier proposals?

Yes. Bring an RFP drafted with an AI assistant or elsewhere, paste or import its text, and review the requirement before publishing an anonymous opportunity. Approved, signed-in suppliers can review the requirement you authorise for them and request to bid. You choose which requests to approve, opening private conversations for supplier discussions and proposals. Supplier participation, proposals and response times are not guaranteed.

Who can see my requirement and respond?

Your public listing excludes your name, contact details, documents and exact estate counts. Approved, signed-in suppliers can review the fuller requirement you approve for sharing, so remove identifying details from it. They can request to bid; approving a request opens a private conversation with that supplier. Publication does not automatically send your RFP to every provider in Netify's research directory.

What should an SD-WAN RFP include?

An SD-WAN RFP should state the site list and regions, the underlay circuits and WAN topology, application performance and QoS targets, failover and availability requirements, security integration, the managed or co-managed operating model, the implementation and migration plan, the pricing model and contract terms, and the evidence suppliers must attach. Netify's question bank covers each of these areas with supplier questions you can select.

What should a SASE RFP include?

A SASE RFP should cover the user and device estate, identity provider and device posture, the required security functions (ZTNA, SWG, CASB, FWaaS and DLP), SD-WAN or branch connectivity, PoP coverage and data residency, logging and SIEM integration, resilience and fail-open policy, the operating model, implementation phasing, per-user pricing and contract terms, and the certifications and references suppliers must provide.

What is the difference between an RFI and an RFP?

An RFI (request for information) asks suppliers to describe their capabilities so a buyer can learn the market and build a shortlist; it usually explores capabilities before detailed proposals; buyers may also request indicative pricing. An RFP (request for proposal) sets out defined requirements, evaluation criteria and a pricing structure so suppliers return comparable, priced proposals. Netify can produce either from the same project, depending on how far the requirement has been developed.

How should SD-WAN and SASE vendors be evaluated?

Score each supplier against the same weighted criteria: capability fit against the stated requirements, security efficacy, performance and PoP coverage in your regions, resilience and SLA, operating model fit, implementation approach, total cost over the contract term and the quality of evidence provided. Netify's provider research helps you assess capabilities. In this service, you approve supplier requests to open private conversations and review the proposals received against your own requirements.

Is the Netify RFP Builder free?

Yes. Drafting and anonymous publication are free for buyers, with no commitment to buy. Suppliers pay Netify when an introduction leads to business. Suppliers request to bid and you choose which requests to approve; publication does not guarantee supplier participation, proposals or response times.

Evidence and method

From requirements to comparable supplier responses.

Open the validation method, factual capabilities and worked example. Last reviewed 2026-09-06.

What the checker actually does

  • Checks technical, security, resilience, commercial, implementation, support and response-format coverage.
  • Tests whether mandatory requirements, evidence currency, pricing structure and evaluation rules are clear enough for comparable bids.
  • Applies healthcare, financial-services, retail and manufacturing considerations when that sector is stated.
  • Flags named-provider wording that lacks an outcome-based or “or equivalent” alternative.
  • Maps gaps to canonical Netify question IDs; recommendations are never added without buyer approval.
386governed questions
8procurement areas
30evaluated provider records, not a participating supplier count
Question bank v2026.1The reference bank includes the condensed core and sector packs. A separate extended SASE collection adds 43 questions. The builder currently offers the condensed 27-question core for selection. The wider governed reference bank and the extended SASE material are separate from Harry Yelland’s public 120-question, 20-pillar framework. Private draft downloads need no publication. Personalised provider matching unlocks after anonymous publication.

Example AI-generated input

“Create an SD-WAN RFP for 20 sites. Suppliers should describe their solution and provide pricing.”

Example Netify output

Information to confirm: Organisation and scale: add sector or operating context, regions or countries. Solution scope: add required security components, business outcomes or use cases. The checker identifies topics to review; it does not certify that an RFP is ready to issue.

Agentic and MCP capability

Supported MCP clients can use public provider comparisons and evidence, and turn supplied text into requirements with provenance. Private project tools require the credentials stated by each tool. Publication requires verified buyer approval. Approved suppliers can request to bid; buyer approval opens a private conversation. The connector guide describes the available supplier tools and access requirements.

See a SASE brief, actual gap check, and Short and Detailed RFP examples.

See a fictional manufacturing workflow.

Compare named providers or review MCP capabilities and access requirements.

Methodology and limitations: this is a deterministic coverage assessment, not legal advice or a guarantee of supplier performance. It does not invent unstated requirements. Read the public question bank, machine-readable bank, methodology data and validator data.