Nonprofit IT Support: How to Choose the Right Help Without an IT Department

Six ways small nonprofits get IT help, what each one covers, and the questions that keep your systems in your own hands.

A Mission Critical guide Updated November 17, 2026

Most nonprofits don't need an IT department. They need a handful of things done reliably: someone to fix a laptop that won't boot before Monday's board meeting, someone to make sure a departing staff member's email is locked down, someone to know whether the backups would actually restore. When nobody owns that work, it lands on the operations manager, the executive director or whoever is "good with computers".

This guide is for that person. It lays out the ways nonprofits get IT support, what each model is good and bad at, how providers charge, and the questions to ask so that whoever you hire leaves you stronger, not more dependent.

What IT support actually covers at a nonprofit

"IT support" is several jobs under one name. Before comparing providers, check which of these you need covered, and which already are:

  • Help desk and devices: fixing laptops, printers, phones and the everyday "I can't log in" problems; setting up a new starter's machine.
  • Accounts and access: running your Microsoft 365 or Google Workspace admin console, turning on multi-factor authentication, and adding and removing people as they join and leave.
  • Security: keeping operating systems and software patched, endpoint protection, spotting phishing, and a plan for when an account is compromised.
  • Backups and recovery: knowing what is backed up, where, and having tested that it restores.
  • Network and office: Wi-Fi, firewalls, internet service and phones, if you have a physical office.
  • Software and vendors: licenses, renewals, nonprofit discount applications, and being the person your CRM or accounting vendor talks to.
  • Planning: a technology budget, a replacement cycle for hardware, and policies people actually follow.

A fully remote team on a cloud productivity suite needs very little of the network row and a lot of the accounts row. An organization with a shared office, client records and a dozen donated laptops needs most of the list. The right support model follows from that, not from what a provider happens to sell.

The six ways nonprofits get IT support

Nonprofit IT support models compared
ModelWhat you getWorks best whenWatch for
A staff member who "does IT"Someone in-house who knows your people and systemsYou are small, cloud-based and the work is a few hours a monthIt is rarely in their job description, and everything they know leaves with them
Volunteers and pro bono helpSkilled time at no fee, from board members, supporters or skills-based volunteering platformsThe work is a defined project with an end date: a migration, a security review, a policyDay-to-day support depends on someone's goodwill and availability
Break-fix contractorA technician you call, and pay, when something breaksProblems are rare and you can tolerate waiting for a fixNobody is paid to prevent problems, so prevention doesn't happen
Managed service provider (MSP)Help desk, monitoring, patching and backups for a recurring feeYou have enough people and devices that problems are weekly, not yearlyWhat the fee includes, who holds the admin accounts, and how you leave
Fractional IT director or vCIOPart-time senior judgement: planning, budgets, vendor selection, policiesYou have decisions to make (a CRM, a migration, a security baseline) more than tickets to closeThey plan and oversee; someone else still does the hands-on work
Vendor and community supportYour software vendors' help desks, TechSoup, NTEN and local capacity-building organizationsA question is specific to one product, or you need peers who have solved it beforeEach vendor supports only its own product; nobody looks at the whole picture

Most organizations end up with a mix: an MSP or contractor for the hands-on work, a named staff member who owns the relationship and the documentation, and occasional pro bono or fractional help for the big decisions.

Volunteers deserve a special word of caution. A supporter who set up your file server or built your database as a favour is generous, and also a single point of failure. If you rely on volunteer technical help, set it up the way Managing Volunteer Developers in Nonprofit Technology Projects describes: written scope, accounts in the organization's name, and a handoff before they move on.

How to tell which model fits

Answer four questions honestly before you talk to anyone selling support:

  1. How often does something break? If the answer is "every week", you are already paying for IT support in staff time; a recurring provider is likely cheaper than the hours lost. If it is "a few times a year", a contractor or a well-supported staff member may be enough.
  2. What would hurt most if it failed? Lost donor or client data, a locked-out finance system and a compromised email account are different risks. Rank them; the provider you choose should be strongest where your risk is highest.
  3. Do you hold sensitive data? Health, case-management or children's records change what "good enough" security means. See HIPAA Compliance for Nonprofits Running Health or Social Service Programs if that applies to you.
  4. Is the problem support, or decisions? If you keep debating which CRM to use, whether to migrate or what to budget, you need planning help (fractional or pro bono) before you need a help desk.

How IT support is priced, and where to check what it costs

Prices vary by region, by the size of your team and by what is included, so any single figure would mislead you. What you can compare is how providers charge:

  • Per user per month: common for MSPs serving cloud-based teams. Check whether volunteers and part-time staff with accounts count as users.
  • Per device per month: common where laptops, desktops and servers drive the work.
  • Hourly or block hours: typical of break-fix contractors and fractional IT directors. Ask whether unused hours roll over.
  • Project fees: for migrations, office moves or security reviews, quoted separately.
  • Onboarding fees: many providers charge to document and take over your environment at the start.

To find what support costs for you, write down your staff count, devices, systems and the problems you have had in the last six months, then ask at least three providers to quote against that same list. Ask peers at similar organizations what they pay, and ask each provider whether it offers nonprofit pricing; some do, and the terms are theirs to set.

Licenses are usually billed separately from support. Microsoft and Google both run nonprofit programs for their productivity suites, and TechSoup brokers discounts across many vendors. Eligibility and current terms change, so check them on Microsoft's nonprofit pages, Google for Nonprofits and TechSoup, or start with Negotiating Software Discounts With TechSoup and NTEN. If you plan to pay for support from a grant, read Grant-Restricted Technology Budgets and Allowable Expenses and confirm with your program officer first.

What to have ready before you bring anyone in

The cheapest hour of IT support is the one a provider doesn't spend discovering what you have. Pull together, in one shared document:

  • Every system you use (email, file storage, CRM, accounting, website, phones) and who the account owner and admins are for each.
  • Where your domain name is registered and who can log in to change it.
  • A list of devices, who uses each, and roughly how old they are.
  • What is backed up, where, and when someone last tested a restore.
  • The recurring problems that made you look for help.

Technology Documentation Standards for Nonprofits Without IT Staff shows how to keep that document current, and Password and Credential Management Policies for Nonprofits covers how to store the logins it points to. If you are handing over systems that someone built for you, Infrastructure Readiness Signals Nonprofits Must Verify Before Handing Systems to an Outside Engineering Firm is the longer checklist.

Questions to ask an IT support provider

  1. Which nonprofits of our size do you support, and can we speak to one?
  2. What exactly does the recurring fee include, and what is billed on top (projects, on-site visits, after-hours work, hardware)?
  3. What response times do you commit to in writing, and for which kinds of problem?
  4. Will every admin account and the domain stay registered to our organization, with our own emergency admin login we hold ourselves?
  5. What security baseline do you put in place (multi-factor authentication, patching, backups), and how do you prove backups restore?
  6. Who is our named contact, and who covers when they are away?
  7. What documentation will you keep about our systems, and do we get a copy?
  8. If we leave, what do you hand over, how much notice is required, and is there an exit fee?
  9. Will you help us apply for the nonprofit licensing programs we are eligible for, or do you resell licenses?

Red flags

  • Admin accounts, the domain or the backup service registered in the provider's name rather than yours.
  • No written scope: "we'll take care of everything" without a list of what everything is.
  • Long contracts that renew automatically and charge to leave.
  • Reselling licenses at full price when you qualify for donated or discounted ones, without saying so.
  • No documentation you can see. If the provider disappeared tomorrow, could someone else pick up your systems?

The same risk exists inside your organization. When the person who holds the admin keys leaves, staff or provider, follow Offboarding Staff Who Own Critical System Access.

When the problem isn't IT support

IT support keeps standard tools running. It is the wrong kind of help for a custom database, a volunteer-built app or an integration that holds your programs together: those need someone who can read and change the code. If that is where your problems come from, start with Rebuilding a System After a Volunteer-Built Tool Breaks in Production and Why Nonprofits Need a Ranked Debt Assessment Before Any Engineering Studio Touches Their Stack.

Frequently asked questions

Can a nonprofit get IT support for free?

Sometimes, for defined pieces of work. Skills-based volunteers, board members and pro bono programs can take on a project such as a migration or a security review. Ongoing day-to-day support is rarely free; nonprofit licensing programs reduce what you pay for software, not for someone's time.

What is the difference between an MSP and a fractional IT director?

A managed service provider does the hands-on work: help desk, patching, monitoring and backups. A fractional IT director (sometimes called a vCIO) provides part-time planning and oversight: budgets, vendor choices and policies. Many organizations use one to keep the other accountable.

Does our IT support need to be local?

Most work on cloud systems is done remotely. Local help matters when you have an office network, phones, printers or hardware that needs hands on it. Ask a remote provider how on-site visits are arranged and billed.

Can we pay for IT support from a grant?

It depends on the grant's terms. Some funders allow technology costs tied to program delivery; others treat them as overhead. Check the award language and ask your program officer before you commit.