Managed IT · October 6, 2026 · intSignal Team

Nonprofit IT: Getting Enterprise Capability on a Nonprofit Budget

Share this article

Nonprofits run on constrained budgets with the same obligations as any other organisation: donor data to protect, financial controls to maintain, and staff who need to work.

They also qualify for a substantial amount of donated and discounted technology — and a surprising number never claim it, because nobody has the time to find out what exists.

What is actually available

Verify current terms directly with each provider; programmes change. As a map of what to look for:

Microsoft offers nonprofit grants that include a number of donated Microsoft 365 Business Premium licences for eligible organisations, with discounted pricing above that. Business Premium is significant — it includes device management, advanced threat protection and information protection, which are the controls a small nonprofit would otherwise never afford.

Google offers Google Workspace for Nonprofits at no cost for eligible organisations, with discounts on higher tiers.

Cloud credits are available from the major providers for eligible nonprofits, which can cover hosting for websites, databases and applications.

Discounted software across a wide range of categories is available through nonprofit technology marketplaces — security products, backup, collaboration, design, accounting.

Hardware at reduced cost through refurbishment programmes, which for many roles is entirely adequate.

The common requirements are registered charitable status, a mission that meets the provider's eligibility criteria, and validation through a third-party verification service. Allow a few weeks for verification the first time; it is reusable afterwards.

The catches, honestly

Eligibility excludes some organisations. Programmes commonly exclude political, and sometimes religious, organisations — and criteria differ between providers. Check rather than assume.

Donated licence counts are capped. Grants cover a number of users; above that you pay discounted rates. Plan for the discounted tier as you grow.

Not every product is included. The grant covers specific SKUs. The add-on you want may not be in it.

Support may differ. Donated licences sometimes come with different support entitlements. Know before you depend on it.

Migration costs are yours. A free licence does not move your email, train your staff, or reconfigure your systems. Budget for the work even when the software is free.

Where to spend what you save

Free licences do not make an organisation secure. The gaps that matter in nonprofits:

Multi-factor authentication, everywhere. Free with every platform above, and the single highest- value control. Nonprofits are targeted specifically because they handle donations and often have weak controls — the dominant attack is business email compromise redirecting a payment.

Backup, with a tested restore. Cloud platforms replicate; they do not protect you from deletion, ransomware or a mistake. Third-party backup for Microsoft 365 or Google Workspace is inexpensive and frequently missing.

Someone accountable. The most common nonprofit IT risk is that technology belongs to whoever is most comfortable with computers, as an addition to their actual job. That person leaves and takes undocumented knowledge with them. Either assign it formally with time allocated, or engage a provider.

Donor data protection. Donor databases contain names, addresses, giving history and sometimes payment details. That data has the same obligations as any customer data, and a breach damages the trust the organisation runs on.

Financial controls in the systems. Separation of duties, approval workflows, and the verbal verification step for payment changes. Small finance teams make dual control hard, which makes the technical controls more important.

The practical starting sequence

  1. Apply for the grants. Microsoft and Google first. It takes an afternoon and recurs annually in value.
  2. Consolidate onto one platform. Mixed environments cost more in support and confusion than the licence savings justify.
  3. Enable MFA for everyone. Before anything else technical.
  4. Set up backup for your platform, and test a restore.
  5. Document who has access to what, especially banking, donor systems and the website.
  6. Write down the offboarding process. Volunteer and staff turnover is high; access tends to accumulate.
  7. Put the payment verification procedure in writing and train everyone who could receive an invoice.

Volunteers and board members

Two specific issues that nonprofits have and businesses mostly do not:

Volunteers need access without becoming a permanent liability. Time-limited accounts, access scoped to what the role needs, and an actual end date. A volunteer account from three years ago with access to the donor database is a common finding.

Board members use personal devices and personal email. Board papers containing financial and personnel information circulating through personal Gmail is normal and risky. Give board members accounts on your platform, or use a board portal. It is a small cost and it keeps governance material in a place the organisation controls.

The honest framing

Nonprofit IT is not a smaller version of corporate IT. The constraint is rarely money alone — it is attention. Nobody has spare capacity to research programmes, compare products or maintain documentation.

Which means the highest-value decision is usually not a product but an arrangement: someone whose job includes this, with enough time to do it. The donated licences are worth claiming and they are not a substitute for that.

Share this article