Whitepaper
The Microsoft Support RFP Rewrite Kit: A Vendor-Neutral Evaluation Guide
If your renewal RFP still uses Microsoft's own tier names and role titles, you've already written the competition out.
Download the Whitepaper (PDF, opens in a new tab)What You’ll Learn
A competitive Unified Support renewal starts with an RFP that measures outcomes instead of vendor packaging. This guide gives IT, Procurement, and Finance leaders a path to rewrite renewal scope around outcomes, score bidders on a shared rubric, and ask every vendor the same set of questions.
THE PROBLEM
Most renewal RFPs inherit language from the last cycle.
Each new RFP is often built from the last one instead of written from scratch. Requirements copied forward this way describe how one vendor packages its own service. A provider with a different staffing or pricing model can fail those requirements and still deliver the same result.
THE BLIND SPOT
Missed SLA targets often carry no consequence.
Many RFPs never ask whether a vendor's SLA includes financially backed remedies. Without that question, a missed response time carries no consequence beyond the vendor's own goodwill.
THE RISK
An unintentionally sole-sourced RFP can trigger a protest.
Federal and state competition rules require full and open procurement unless a documented exception applies. GAO has sustained protests against agencies that narrowed a solicitation to one brand. South Carolina's procurement office has flagged this same pattern in Microsoft support renewals.
THE NEXT STEP
Publish criteria before proposals arrive.
Replace brand-specific language with outcome-based criteria. Weight your evaluation rubric and document the reasoning behind each requirement before the RFP goes out.
Who Should Read This Whitepaper?
- IT Directors who need renewal scope language that measures response times and technical depth instead of one vendor's internal role names.
- Procurement Leaders who want evaluation criteria documented, weighted, and published before proposals are due.
- Contract Managers who need pricing structures mapped to actual support usage rather than a fixed percentage of annual software spend.
- Executive Sponsors who are accountable for a defensible procurement record and need market research documented behind any requirement that could narrow the field.
- Compliance Officers responsible for confirming the RFP meets full and open competition requirements before it goes out to bid.
- IT Operations Leaders who will manage the winning vendor's escalation path and SLA remedies long after the contract is signed.
