A practical MSP RFP checklist for small and midsize businesses

Describe the business decision

Start the request with the outcome you want, the person who owns the decision, and the proposed start date. Describe the current problems in observable terms: recurring onboarding delays, unresolved tickets, missing recovery tests, or unclear responsibility. State which systems and internal roles will remain in place. Providers need enough context to propose the same job, not an invitation to replace everything.

Give every provider the same environment summary

Include employee and device counts, office locations, working hours, remote locations, operating systems, identity platform, productivity suite, networks, servers, critical applications, and existing vendors. Share sanitized inventories during the first round. Detailed configurations and sensitive records belong in an approved secure exchange after you have assessed the recipient.

• Business owner and internal IT contact.
• Locations and the hands-on work required at each.
• Applications with limited downtime tolerance and their support vendors.
• Known equipment age, support gaps, and planned changes.

Require a response against the service schedule

Use a table with a row for each responsibility and columns for included work, exclusions, service hours, accountable role, and extra charges. Ask who performs the work when a subcontractor is involved. Request examples of a monthly report, escalation process, onboarding plan, and completed recovery exercise. A software list does not demonstrate that someone operates the service.

Make pricing and assumptions comparable

Ask for recurring service costs, licenses, onboarding, remediation, project rates, travel, after-hours work, minimum quantities, and termination assistance. Require a first-year total based on your stated quantities. Have providers identify assumptions they could not validate. Ask them to separate mandatory remediation from optional improvements and show when each cost will be incurred.

Set a manageable evaluation process

Give all finalists the same deadline and answer substantive questions in a shared clarification document. Shortlist on mandatory requirements first, then invite qualified teams to demonstrate how they handle your scenarios. Tell bidders how you will assess evidence, references, and total cost. Avoid collecting increasingly detailed proposals without a clear decision owner or timetable.

Carry the winning proposal into the contract

Resolve exceptions before signing. The final service schedule should preserve the promises that mattered in evaluation, including support hours, coverage, reporting, security ownership, and handover deliverables. Keep a list of acceptance criteria for onboarding so the transition team can verify what was purchased.