Choosing a managed service provider (MSP) is a multi-year decision. The provider will hold admin rights to your systems, answer your users’ calls, and stand between you and your next security incident. A well-written request for proposal (RFP) is how you turn that decision from a gut call into an apples-to-apples comparison.
The problem is that most IT RFPs produce proposals that all look the same. Every bidder promises “24/7 support,” “proactive monitoring,” and “best-in-class security.” This guide shows you how to write an RFP for IT services that gets specific, comparable answers, and how to run a process that’s fair to every bidder, including the ones you don’t pick.
Want to skip the blank page? Get the RFP Template and follow along section by section.
Do you need an RFP? RFP vs. RFI for IT services
A formal RFP takes real effort from you and from every bidder. It’s worth it when:
- The contract is large or long. Multi-year agreements, or spend significant enough to need board or finance approval.
- You’re replacing an incumbent. A structured process helps you document why you’re switching and what must improve.
- Compliance requires it. Public-sector, healthcare, financial services, and some private-equity-backed organizations must show a competitive process.
- The scope is complex. Multiple locations, hybrid cloud, regulated data, or co-managed arrangements with an internal IT team.
A lighter approach is often enough in other situations:
| Approach | Best for | What you send | Typical effort |
|---|---|---|---|
| RFI (request for information) | Early research, unclear scope, or a long list of unknown providers | A short questionnaire on capabilities, size, industries served, and service model | Days, not weeks |
| Direct evaluation | Smaller environments, a short list you already trust, or a single well-defined service | A scoping call and a quote | 1–3 weeks |
| RFP | Complex scope, formal approval, or a required competitive process | Full environment detail, requirements, pricing format, and scoring criteria | 6–10 weeks end to end |
Many organizations combine them: an RFI to narrow a long list to four or five qualified providers, then an RFP to that short list. That saves bidders from writing full proposals they have little chance of winning, and saves you from reading them.
Decided an RFP is the right fit?
What to include in a managed IT services RFP
A strong managed IT services RFP gives bidders enough context to price accurately and asks questions specific enough that answers can be compared. Below is each section of our template, in order: what goes in it, why bidders need it, and how a weak requirement compares with a strong one. Most organizations can complete the template in 4 to 8 hours. Start with the environment section, because it takes the longest.
About this RFP and submission instructions
Include: Deadlines, a single point of contact, the required file format, communication rules, and how long proposals must stay valid.
Why bidders need it: Clear rules keep the process fair. Bidders who know not to contact your staff or current provider, and who all submit in the same format, compete on the same footing.
- Weak: “Send proposals to the IT team by the end of the month.”
- Strong: “Submit three files by 5:00 p.m. CT on [date]: a PDF answering Sections 3 to 7 in our numbering, the completed pricing workbook, and the signed acknowledgment. Direct all questions in writing to the RFP contact.”
1. Company Overview
Include: Your industry, headcount, locations, expected growth, regulatory environment, internal IT team, decision makers, and two fields that matter most: why you’re issuing the RFP now, and what success looks like in year one.
Why bidders need it: The “why now” tells bidders what problem they’re really being hired to solve. A firm whose insurer now requires 24/7 monitoring needs a different proposal than one whose main issue is slow tickets.
- Weak: “We are seeking a reliable IT partner.”
- Strong: “Our contract expires in June, response times have slipped, and our cyber insurer now requires 24/7 monitoring. In year one, success means 95% of tickets resolved within SLA, MFA and EDR on every device, and an approved 3-year IT roadmap.”
2. Current Environment
Include: Users and devices, servers, network gear, sites, core applications, current security tools, existing contracts with notice periods, and your top 3 to 5 pain points.
Why bidders need it: Most per-user and per-device quotes are built directly from these numbers. Vague counts are the top reason bids can’t be compared. Round to the nearest five if you need to, and say so.
- Weak: “Approximately 300 users with a mix of cloud and on-prem systems.”
- Strong: “287 named users (40 part-time), 310 Windows laptops, 42 Macs, 14 VMs on 2 Hyper-V hosts, Microsoft 365 with Entra ID, and Fortinet firewalls at 4 sites. Current MSP contract ends 6/30 with 60 days’ notice.”
Tip: The template's environment section breaks this into seven tables: users and devices, servers and network, locations, applications, security tools, contracts, and pain points. Fill in the counts once and they carry into the pricing workbook. Get the RFP Template
3. Scope of Services
Include: Your service model (fully managed, co-managed, or security-only) and each service marked Required, Optional (price separately), or Not needed, across end-user support, network and cloud, and security.
Why bidders need it: Scope gaps are where disputes start. Marking services Optional lets you see what add-ons cost without committing to them. If you’re keeping internal IT staff, describe the split of responsibilities.
- Weak: “Full IT management.”
- Strong: “Co-managed. Provider owns the help desk (including after hours), endpoint and server patching, and backup testing. Our IT manager keeps ERP administration. On-site support at our two largest sites is Optional, priced separately.”
4. Security and Compliance Requirements
Include: The frameworks that apply to you (HIPAA, PCI DSS, SOC 2, CMMC, cyber insurance controls), minimum controls the provider must deliver, and evidence of the provider’s own security.
Why bidders need it: Your MSP holds admin access to everything, so its security is your security. Bidders need to know which standards they’ll be held to and what proof you’ll ask for.
- Weak: “Provider must follow security best practices.”
- Strong: “EDR on 100% of endpoints and servers, monitored 24/7. Incidents triaged by a human analyst within 15 minutes. Provide a current SOC 2 Type II report and describe MFA and least-privilege access on your RMM and ticketing tools.”
5. Service Level Expectations
Include: Priority definitions with response and resolution targets, coverage hours, support channels, monthly reporting, business reviews, and remedies when targets are missed.
Why bidders need it: SLAs are where proposals look most alike and differ most in practice. Response-only SLAs look good on paper but don’t tell you when work actually gets done.
- Weak: “24/7 support.”
- Strong: “P1 response within 15 minutes, 24/7/365, with a 4-hour resolution or workaround target and monthly reporting on SLA attainment by priority. Service credits apply when attainment falls below the agreed threshold.”
6. Transition Requirements
Include: Your target go-live date, any overlap with your current provider, blackout dates, what the onboarding plan must contain, and exit terms.
Why bidders need it: Transitions fail on documentation and credentials, not technology. Asking for exit terms now, while you have leverage, protects you later.
- Weak: “Smooth transition required.”
- Strong: “Provide a phased plan with a named owner and acceptance criteria per phase, full asset and credential documentation within 30 days, and a 30/60/90-day review. On exit, return all documentation and data within 30 days at no charge.”
7. Vendor Questionnaire
Include: Numbered questions with word limits, grouped by company stability, service delivery, security operations, strategy, transition, and commercial terms.
Why bidders need it: Word limits force focused answers and make side-by-side scoring faster. The best questions ask for proof, not promises.
- Weak: “Describe your approach to customer service.”
- Strong: “Provide your actual first-response time, resolution time, and customer satisfaction across all clients over the last 12 months. (150 words max)”
8. Pricing
Include: A required pricing workbook, pre-filled with your counts from Section 2, broken into one-time onboarding, monthly recurring services, tooling and licensing, after-hours labor, project rates, and contract terms.
Why bidders need it: Bundled “one price covers everything” quotes are the main reason MSP bids can’t be compared. When everyone prices the same quantities on the same sheet, you can calculate three-year total cost on the same basis.
- Weak: “Provide pricing.”
- Strong: “Complete the Bid Pricing tab without adding, removing, or merging lines. If a service is included elsewhere, enter $0 and explain. List every pass-through tool and license, plus your annual price escalator.”
The pricing workbook is included. Every bidder prices the same quantities in the same six categories, so you can compare year-one and three-year cost on the same basis. Get the RFP Template and workbook
9. Evaluation Criteria and Timeline
Include: Your weighted scorecard, the scoring scale, how many finalists you’ll invite, and dates for every milestone.
Why bidders need it: Published criteria tell bidders what matters. A published timeline lets good providers plan the time to respond well.
The template closes with a bidder acknowledgment (Appendix A), where each bidder confirms its pricing is valid and lists any exceptions to your terms.
How to run the MSP RFP process
A good document is only half the job. How you run the process determines whether bidders can give you their best answer, and whether your final decision holds up to scrutiny.
Set a Realistic Timeline
A typical managed IT services RFP runs 6–10 weeks from release to signed contract:
- Week 0: Release the RFP to your short list.
- Weeks 1–2: Discovery window and written questions.
- Week 2: Publish answers to all bidders.
- Weeks 3–4: Proposals due.
- Weeks 5–6: Scoring and finalist selection.
- Weeks 6–7: Finalist presentations and reference checks.
- Weeks 8–10: Negotiation, contract review, and award.
Build in a buffer for legal review. Contract redlines often take longer than the evaluation itself.
Building your short list?
Open a Discovery Window
Give bidders a defined period to learn your environment: a walkthrough call, read-only access to documentation, or a short session with your IT lead. Offer the same access to every bidder. The better they understand your environment, the fewer assumptions and contingencies end up in their pricing.
Run Written Q&A and Share Answers With Everyone
Require questions in writing by a set date, then publish every question and answer to all bidders (with the asker’s name removed). This keeps the field level. If one bidder learns something material on a side call, the others are pricing a different project.
Score Against Published Criteria
Agree on weights before proposals arrive, and have each evaluator score independently on a 1 to 5 scale before you compare notes. Changing weights after you’ve seen the bids invites bias. The template’s starting weights:
Not all managed service providers are equal. Use these seven weighted criteria to evaluate MSP proposals and choose the right IT partner for your business.
Price sits deliberately below security and service delivery: the cheapest bid is rarely the lowest three-year cost once out-of-scope work is added. Adjust the weights to your priorities, but keep the total at 100%.
Use Scenario-based Finalist Presentations
Skip the generic capabilities deck. Give each finalist the same two or three scenarios in advance and ask them to walk through their response live, for example:
- “A user reports a ransomware note on their screen at 9:40 p.m. on a Saturday. Walk us through the first two hours.”
- “We acquire a 60-person company with its own Google Workspace tenant. How do you bring them onboard?”
- “Our help desk SLA was missed three months in a row. What do you do, and what do we see?”
Ask to meet the people who would actually support you, not only the sales team.
Check References With Purpose
Ask for references of similar size, industry, and complexity, including at least one client who has been through a transition in the past year. Ask what went wrong and how the provider handled it. That tells you more than what went right.
Negotiate the Whole Agreement, Not Only The Price
Once you’ve chosen a preferred provider, negotiate SLA credits, annual increase caps, termination and exit assistance terms, data ownership, and documentation handover. Tell the providers you didn’t select promptly, and offer a debrief. It’s a courtesy that keeps your options open for the future.
Common IT RFP Mistakes (and how to avoid them)
These are the IT RFP best practices most often missed. Each one makes proposals harder to compare or hides the information you need.
Generic boilerplate. RFPs copied from a template without tailoring get boilerplate answers back. If a question could apply to any company, expect an answer that could apply to any provider. Tie every requirement to your environment and goals.
Line-item-only pricing. Asking for a price per service without asking what’s excluded invites low base fees and high add-ons. Request total cost over the contract term at your current size and projected growth, plus a clear list of exclusions and project rates.
No security scenarios. Every provider will say security is a priority. Asking them to walk through a specific incident shows you who has a tested process and who has a slide.
Too little environment detail. Vague environment data is the most common reason proposals come back with wide price ranges and long assumption lists. If you can’t share specifics in the RFP, share them during the discovery window under NDA.
Writing requirements around one provider. It’s tempting to describe your favorite bidder’s exact offering. It narrows the field, weakens your negotiating position, and other bidders can usually tell. Describe the outcome you need and let providers show how they’d get there.
Unrealistic response windows. Two weeks for a complex, multi-site environment produces rushed proposals full of assumptions. Allow at least three weeks so bidders can do discovery properly.
Avoid these from the start.
Frequently Asked Questions
How long should an IT RFP response period be?
Allow at least three weeks between issuing the RFP and the proposal deadline, and four for complex or multi-site environments. That gives bidders time for discovery, written questions, and accurate pricing. Good providers often decline rushed RFPs, which shrinks your field.
How many vendors should receive an RFP?
Three to five qualified providers is usually right. Fewer limits your comparison. More creates a heavy evaluation load and discourages strong bidders who see low odds of winning. If you’re starting with a longer list, use an RFI to narrow it first.
What's the difference between an RFP and an RFI for IT services?
An RFI gathers general information about providers’ capabilities so you can build a short list. An RFP asks short-listed providers for a specific solution and price based on your environment and requirements. Many organizations use an RFI first, then an RFP.
Should we tell bidders our budget?
You don’t have to, but sharing a range can help. It keeps bidders from proposing solutions far outside what you can approve, and focuses proposals on the best value within your limits.
How long does the whole MSP RFP process take?
Plan for 6 to 10 weeks from release to signed contract. Add time if you need board approval or extensive legal review, or if your current provider’s notice period sets the timeline.
Run a Fair Process and Get Better Proposals
A well-written RFP benefits everyone. You get proposals you can compare. Bidders get the information they need to put forward their best solution. And the provider you choose starts the relationship with clear, shared expectations.
Our RFP template includes every section covered above, with guidance notes, sample SLA targets, a 20-question vendor questionnaire, and a pricing and scoring workbook that comes with it. Use it as-is or adapt it to your organization.