As organizations grow, so does the technology behind the work. More staff, more locations, remote and hybrid teams, rising expectations from board members and insurers on cybersecurity, and now AI tools showing up in everyday work. At some point, the scope outgrows what any one person or internal team can stay on top of, however capable they are.
That’s usually when leaders start looking at a managed services provider (MSP), or take a fresh look at the one they have. We help nonprofits, associations, and foundations assess their technology, and IT support comes up in nearly every engagement. Here’s what we’ve learned about choosing well.
What is a managed services provider (and what isn’t it)?
A managed services provider is an outside firm that runs and supports your day-to-day IT for a recurring fee: the helpdesk, laptops and phones, your network, patching and updates, monitoring, and backups. A good MSP adds depth and a bench of engineers behind your team, so routine IT runs reliably while your staff focus on the mission.
What an MSP generally isn’t is your technology strategist. Many MSPs offer “virtual CIO” (vCIO) services, but in our experience they’re limited on software and business-systems strategy: your CRM, finance system, association management system, and how data moves between them. That’s not a knock on MSPs; it’s just not their core business. Pair your MSP with a strategic technology leader, whether that’s an internal role, a fractional or virtual CIO, or an outside advisor.
Hiring an MSP also doesn’t eliminate internal roles. It changes them. Someone on your team still manages the vendor relationship, coordinates first-line requests, and owns your business systems. Plan for that time.
Why security and AI change the MSP decision
Cybersecurity and AI are two of the biggest reasons organizations are adding IT capacity right now. Both raise the same question: what should your MSP handle, and what should stay with you?
Cybersecurity
In our security assessments, the pattern is consistent: an MSP is a strong supplement to internal security ownership, not a replacement for it.
Tasks well suited to an MSP include log monitoring, running a security awareness training platform, internal vulnerability assessments, network management tooling, and advanced threat detection and response. MSPs also bring their own remote monitoring and management tools, which few organizations could justify buying on their own. Hardening your Microsoft 365 tenant (multi-factor authentication, conditional access, admin roles, and sharing settings) is an especially good fit for an MSP-led project.
A few practices to build in from the start:
- Require monthly operations and security/incident reporting.
- Keep a baseline security plan and update it about every six months. Your MSP can help.
- Get an independent outside security assessment about every three years, so your MSP isn’t grading its own work.
AI
This is Build’s point of view, informed by the AI policy work we do with clients.
Staff are already using AI tools, approved or not, so every organization needs an acceptable-use policy. At a minimum, it should cover: no confidential data or personal information in unapproved tools, MFA on any AI tool, IT review and pre-approval of new tools, human review of AI outputs, and an expectation that your vendors follow your AI policy too.
There’s a technical side as well. AI tools like Microsoft Copilot can surface anything a user already has access to, so file and SharePoint permissions need attention before rollout. In one engagement, a leader told us it was “scary easy” to reach data that should have been firewalled. That’s a common discovery, and it’s why we treat permissions cleanup as a prerequisite for AI.
We see the division of labor this way:
- Your MSP handles technical controls: permissions cleanup, MFA and single sign-on, app allow/block lists, logging, data loss prevention, and configuring approved AI tools.
- Your organization owns policy: which tools are approved, disclosure rules, staff training, and governance. Governance needs a named owner, not just a document.
For more, see What Nonprofit Leaders Need to Know About AI Governance and A Strategic Framework for Nonprofit AI Investment. If you’re shaping your broader approach, our AI and data strategy work starts there.
How much does an MSP cost? What drives the price
There’s no single price for managed IT services. What you’ll pay depends mostly on how many people and devices you support, how many locations you have, the hours you need covered, and how much security you want included. The pricing model matters too, because it shapes what’s in the quote and what isn’t.
How MSPs price their services
- Per user: a monthly fee for each staff member, covering their devices and support. It’s easy to budget as you grow.
- Per device: a fee for each laptop, server, or network device. This can work well when staff share equipment.
- Tiered packages: bundles, often labeled basic, standard, and premium, with more services at each level. Check what each tier actually includes.
- Block hours: a bank of support hours bought up front. This is a good fit for smaller organizations, or as a supplement to an internal team.
What drives the cost
- The number of users and devices (the biggest driver)
- The number of sites, and whether any need onsite support
- Coverage hours, including staff in other time zones
- Security scope: monitoring, threat detection and response, training, and reporting
- How many systems and platforms you run, and how complex they are
What quotes often leave out
Many quotes cover the monthly service and little else. Ask about:
- Onboarding and transition, usually a one-time cost
- Security services sold as add-ons
- Onsite visits and travel
- After-hours and weekend support
- Projects outside routine support, like migrations or setting up a new office
- Exit terms: what it costs to leave, and how they hand over documentation and admin access
How to compare quotes fairly
Give every vendor the same inventory and the same requirements, then compare the quotes side by side on what’s included, not just the bottom line. A lower monthly price can cost more over a year once security, onsite visits, and after-hours support are priced separately. Also budget for the costs around the contract: outside help with the selection if you want it, and staff time during the transition.
Signs your IT needs have outgrown your current setup
Whether you have no MSP or have worked with one for years, these signs suggest it’s time to add capacity or take a fresh look:
- Knowledge sits with one role. When everything about your systems lives with one staff member, or one technician at your MSP, the organization carries a single point of failure. That’s a structural risk, and one of the most common we find.
- Support isn’t keeping pace with growth. Response times stretch, recurring issues stay open, or support quality depends on who picks up. That usually means the provider doesn’t have the bench depth your organization now needs.
- Security practices haven’t kept up. In one assessment, we found an MSP emailing passwords in plain text. Practices like that need to change quickly.
- You’re not ready for AI. If permissions, policies, and approved tools aren’t in place, your current setup may not support the AI use already underway.
- The relationship has never been re-competed. Many organizations have worked with the same provider for years without comparing it to the market. In one assessment, our recommendation was to assess, improve, or replace, and from then on to compare the current MSP against at least two alternatives every three years.
Right-sizing the service
There’s no single right model. The most common options:
- Fully outsourced. The MSP handles everything, from password resets to network engineering. This works well when you have no internal IT staff.
- Hybrid. You keep first-line and onsite support in-house and outsource escalation and engineering. This often fits organizations with an internal IT lead who wants a deeper bench behind them.
- Pay-per-use or block hours. Smaller organizations can buy a bank of support hours rather than a full monthly contract.
- Shared services. For very small organizations, shared IT services through a parent body, federation, or network can be a lower-cost alternative to a full MSP.
The right model depends on your internal capacity, how many locations you support, and how much risk you can accept. Start from your needs, not from the vendor’s default package.
A five-step selection process
A good selection doesn’t need to take months. Here’s the process we recommend:
- Form a small selection team led by a senior leader (or your fractional CIO). Include someone who works closely with IT support day to day.
- Document your requirements and an IT inventory: users, devices, sites, systems, and security needs. MSPs price on this information, so a clear inventory gets you comparable quotes.
- Issue a streamlined RFP to two or three qualified vendors. Pre-qualify where you can. For example, look for certified partners for your core platform, like Microsoft 365.
- Ask finalists to include their onboarding and transition plan in the proposal. How they plan to take over tells you a lot about how they’ll run things.
- Check references at similar mission-driven organizations, and negotiate service levels and exit terms before you sign.
A few things help the process go smoothly: keep the RFP focused and the vendor list short, write your requirements yourselves rather than borrowing the incumbent’s, and make sure every vendor prices the same scope. This is the same discipline we bring to software selection.
Plan for the transition, too. Moving MSPs means handing over admin credentials, documentation, licensing, and vendor contacts. Request these in writing early, and let staff know what will change and when.
What to look for: selection criteria
Price matters, but it shouldn’t lead. Weigh these:
- Relationship and communication fit. Do they explain things in plain language? Are they responsive during the sales process?
- Technical depth. Look for a real engineering bench, not one star technician.
- Nonprofit and association experience. Firms that understand grant cycles, board reporting, and mission-driven budgets make better partners.
- Geography. Can they come onsite when needed, support multiple offices, and cover international staff across time zones?
- A documented security baseline and a clear security services offering.
- Platform partnerships relevant to your technology stack.
- A single helpdesk entry point and transparent ticket reporting.
Some MSPs publish their own selection guides, and they’re worth a read. Community IT’s guide to choosing nonprofit IT support makes good points about working alongside internal staff, disclosing all fees up front, and scaling as you grow. Just keep in mind that the firms writing these guides are also candidates for the job.
Checklist: questions to ask every MSP finalist
- Who will be our primary contact, and who backs them up?
- How many engineers would work on our account, and at what levels?
- Which mission-driven organizations like ours do you support today? Can we talk to two of them?
- What are your response and resolution times, and how do you report against them?
- How do staff submit tickets, and can we see ticket trends monthly?
- Can you provide onsite support at all our locations? How do you cover staff in other time zones?
- What does onboarding look like, how long does it take, and what do you need from us?
- What’s included in your quote, and what’s billed separately?
- What happens if we leave? How do you hand over documentation, credentials, and admin access?
Security and AI questions to ask
- How do you secure a Microsoft 365 tenant like ours, and what’s in your standard baseline?
- What do you monitor, and what will you report to us each month?
- Walk us through how you handle a security incident, from detection to final report.
- Can you help us control which AI tools can access our data, and how?
- How would you approach cleaning up file and SharePoint permissions before we roll out AI tools?
- Do you support independent security audits, and how do you respond to findings?
Keeping your MSP accountable
Selection is the start, not the finish. To keep the relationship healthy:
- Define service levels for response and resolution times, uptime, and reporting, and put them in the contract.
- Hold regular ticket reviews to spot trends. A recurring issue is a signal to fix the root cause.
- Use one helpdesk entry point so every request is tracked in one place.
- If performance slips, work to fix it or replace the provider, and document it against the agreed service levels.
- Re-compete every three years, paired with an independent security assessment.
The bottom line
Choose an MSP for fit, depth, and security, not just price. Let it run your day-to-day IT and technical controls, and keep strategy and governance, including AI governance, owned inside your organization.
If you’d like help assessing your current IT support or running an MSP selection, we’d love to talk. We don’t take referral fees from MSPs, so our only interest is the right fit for you. Let’s talk.
A note on vendors and our independence
We sometimes name vendors, products, and service providers in our content, including firms that offer services like ours. We do that because it’s useful to you, never because someone paid us to. Build is passionately independent: we accept no referral fees, sponsorships, webinar co-hosting, or event fees from any vendor, so our advice answers only to our clients. Learn more about our independence.
