Take a dose of SD-WAN and the doctor will call you in the morning 

Why writing an RFQ for SD-WAN is like visiting the doctor. 

When we visit our doctor, we have a problem we need help fixing. Maybe we know exactly what the issue is and just need a quick prescription filling out. Or perhaps we’re not sure what’s going on, but we know it isn’t right. Either way, we know that a doctor will assess, investigate, prescribe or refer us until we get the right treatment to solve our problem. 

Imagine you visited a doctor with pain in your foot after playing sports. Instead of sending you for an x-ray or scan, they just gave you some painkillers and sent you home. That’s not fixing the problem. It might make things a bit better for a while, but at the end of the day there’s still something wrong and you need to fix it – properly. 

If you’re considering upgrading your current network infrastructure to SD-WAN, you might well find yourself coming up against this kind of scenario when writing your RFQ. Rather than asking for all the detail so a supplier can fully assess how an SD-WAN system could be suitable for you, many RFQ templates ask for the bare minimum detail and make assumptions about security, privacy and network performance requirements. 

Like the doctor who only prescribes a painkiller, these kinds of RFQs would be able to give you some kind of resolution, but not the one you really want. 

Writing an RFQ for the SD-WAN system you deserve

When you visit the doctor, you don’t just roll up without an appointment or any idea of what you want to discuss with them. You take the time to think about what you need to discuss, any recent events that might have caused illness or injury, or any medication you’re taking. Writing an RFQ for SD-WAN requires the same level of forethought and planning.  

Exactly like how health is different between every person, each business will have different needs from their network system; there is no one-size-fits-all approach. 

It’s important to remember that SD-WAN is no magic pill for fixing struggling, outdated or inflexible network infrastructures. If you’re genuinely looking to switch to SD-WAN, you need to consider that your network design and structure will likely need to change to suit more modern methods. 

Make sure your IT departments and enterprise network teams can support you in writing this critical document. Both your company and the potential supplier need to be transparent with each other to get the best results! You’d tell the doctor if you dropped a brick on your foot – so tell your team to be honest with the current issues they face in the network and what they want to get out of an SD-WAN system.

Considerations to include in an RFQ for SD-WAN:

  • Understand your wider architecture – what reason do you have for choosing SD-WAN? What benefits do you want it to bring to your architecture? Have you got an idea of what your architecture could look like or do you need assistance developing this?
  • Consider whether you need managed, co-managed or un-managed support. Do you need or want equipment on your premises? 
  • Do you need or want zero-touch deployment? What would work better for your teams and staff? 
  • Do you have existing solutions such as UCC that need to be integrated, or is this an additional requirement?
  • Do you want application performance monitoring? This can be useful if you are looking to shape and develop your enterprise network. 
  • Is the highest level of cybersecurity and data protection included or offered at extra cost?
  • Is there a proof-of-concept or demo/trial available of the SD-WAN system? 
  • What features does your company need an SD-WAN system to deliver on? What is a priority? 
  • Network traffic flow – do you need it to branch or web? If you use Office 365, bear in mind that already has an optimized web connection.
  • What kind of PoP coverage do they offer? This is important to consider for networks working globally in particular. 

Once your initial RFQ document is complete and you’ve entered into discussion with a potential SD-WAN supplier, this is the time to get into the granular detail and really lay out every bit of detail. Your RFQ should be thorough and clear in your needs and requirements, but for ultra-specific insight, wait until you’re past the pitch stage. 

Remember to approach your RFQ like a doctor appointment. Think about what the problem is, how you want to solve it, and what kind of plan, care and support you think is best going forwards. Then let the experts fill in the blanks before you collaborate on a best practice plan.