You are reading Part 1 of our 12-part Non-Profit Authority Series.
A non-profit planning its annual IT budget should account for managed support, cybersecurity, user protection, technology infrastructure, lifecycle replacement, and optional risk-management services. For planning purposes, a properly secured managed IT environment can reasonably fall around $125-$175 per endpoint per month, although that is not a universal quote. A 15-30 employee organization should also budget separately for major projects, equipment replacement, BCDR, penetration testing, compliance tools, and other services that may fall outside its monthly agreement.
The 6-Part Non-Profit IT Budget Framework
Instead of treating IT as one line item called “computer support,” leadership should divide the technology budget into six categories:
- Managed services
- Security
- Technology infrastructure
- Lifecycle replacement
- Optional risk-management services
- Projects and exceptional work
This makes the budget easier for an executive director, finance committee, or board to understand and reduces surprises during the year.
1. Budget for the Managed Services Foundation
WTITC structures managed client engagements around three layers:
| Layer | Purpose |
| Security Package | Protect devices, users, identities, and cloud systems according to the selected package |
| Managed Services Fee | Monitoring, patching, documentation, Help Desk, alerting, remediation, and coordinated support |
| Tiered Technology Fee | Supports the operational infrastructure required to manage the environment |
The Managed Services Fee is $40 per managed endpoint per month and applies to managed workstations and servers.
It includes Datto RMM monitoring and patching, proactive alerting and remediation, IT Glue documentation, secure password management, unlimited Help Desk support, and coordinated remote and onsite support when warranted.
The Tiered Technology Fee is based on environment size. For example, the monthly fee is $1,650 for 10-19 managed devices, $2,750 for 20-29 devices, and $3,850 for 30-39 devices.
That fee helps fund 24/7 monitoring infrastructure, security operations, alert triage, monthly service audits, Technology Alignment Manager oversight, tooling, automation, escalation, dispatch, and quality control.
For a non-profit, this structure is useful because adding or removing a few endpoints does not necessarily require renegotiating the entire agreement.
2. Budget for Both Device Security and User Security
A common budgeting mistake is protecting the computer but overlooking the person using it.
WTITC’s Essentials Security Package is designed around device protection and includes antivirus, Endpoint Detection and Response, unified device backup, and Datto SaaS Protection where applicable.
The Complete Security Package adds protections around users and the broader environment, including:
- Inky email security
- BullPhish ID security awareness training
- Dark Web ID monitoring
- SaaS Alerts
- Microsoft 365 management and maintenance
Complete is WTITC’s standard recommendation for most organizations.
That distinction matters for non-profits because employees may work with donor information, financial records, credentials, cloud applications, and other sensitive information. Regulatory, contractual, insurance, or funding-related expectations can also affect the controls an organization needs.
An annual budget should therefore ask two different questions:
Are we adequately protecting the endpoint?
Are we adequately protecting the user, identity, email, and cloud environment?
Those are related problems, but they are not the same problem.
3. Create a Technology Replacement Reserve
An organization can have predictable managed services costs and still get surprised by technology expenses if it never budgets for aging equipment.
Workstations, servers, firewalls, switches, wireless equipment, battery backups, and other infrastructure eventually require replacement.
Rather than waiting for something to fail, leadership should maintain an inventory showing:
- Equipment age
- Warranty status
- Operating system support
- Business criticality
- Expected replacement year
- Estimated replacement cost
This turns replacement from an emergency into a planned capital decision.
A documented technology lifecycle helps non-profits replace aging systems before unsupported or unreliable equipment becomes an operational problem.
That principle is particularly valuable for organizations with limited administrative staff. A failed workstation is inconvenient. A failed server, firewall, or critical network component can affect many employees at once.
4. Separate Recurring Services from Projects and Optional Risk Controls
Not everything should be assumed to be part of the monthly managed services agreement.
WTITC uses $150 per hour as its professional services benchmark for work such as server projects, network upgrades, security upgrades, cameras, new locations, migrations, exceptional work, and other out-of-scope activities.
Some onsite hours may be included based on agreement size, but onsite support should not be treated as unlimited labor. Major projects or additional onsite requirements may be scoped separately.
WTITC also offers several services on an a la carte basis, including:
- Business Continuity and Disaster Recovery
- Third-party penetration testing through Vonahi
- Compliance Manager
Organizations that decline an appropriate optional service should understand and acknowledge the related operational, security, or compliance risk.
Knowing what work sits outside a managed services agreement helps leadership build a realistic budget instead of assuming every future technology expense is covered by the monthly fee.
This distinction is especially important when a non-profit is planning a relocation, adding a location, replacing infrastructure, migrating systems, or addressing new regulatory or contractual requirements.
5. Connect the IT Budget to Risk and Compliance Readiness
A technology budget should not be evaluated only by asking, “How much does IT cost?” A better question is, “What risk are we accepting at this spending level?”
For example, leadership should understand whether the budget supports:
- Current endpoint protection
- Email and identity security
- Employee security awareness
- Backup validation
- Microsoft 365 management
- Appropriate access controls
- Monitoring and alert response
- Documentation
- Recovery planning
- Evidence needed for audits or reviews
Technology does not automatically make an organization compliant with every regulation, contract, grant requirement, or insurance policy. However, documented controls and active technology management can support regulatory compliance readiness, improve audit readiness, and help demonstrate that security controls are being managed.
The organization’s legal, regulatory, insurance, and funding requirements should still be evaluated with the appropriate professional advisors.
6. Build a Multi-Year Budget Instead of Starting Over Every January
The strongest IT budgets look beyond the next 12 months.
A five-year view allows leadership to identify years in which several expensive items might otherwise collide. For example, a server replacement, firewall refresh, Microsoft project, office expansion, and workstation refresh should not all become surprises in the same budget year.
Technology alignment makes this process more useful because the goal is not simply to replace equipment based on age. The goal is to understand whether technology continues to support the organization’s work reliably.
When systems, connectivity, security, and equipment are properly aligned, employees experience less technology friction and fewer recurring issues. That can reduce downtime and help staff spend more time on the organization’s mission.
A five-year IT strategy connects today’s managed services investment with future infrastructure, security, growth, and replacement decisions.
Example: Building a Budget for a 22-Employee Non-Profit
Consider a hypothetical non-profit in Midland with 22 employees and 25 managed endpoints.
The organization should not simply multiply 25 devices by a single number and assume every technology expense is covered.
A more realistic budgeting process would identify:
- The appropriate security package.
- The $40-per-endpoint Managed Services Fee.
- The applicable 20-29 device Technology Fee tier.
- Planned workstation or infrastructure replacements.
- Any upcoming migrations or technology projects.
- Whether BCDR, penetration testing, or Compliance Manager is appropriate.
- Any additional user-security requirements.
Using the published structure, 25 devices fall within the 20-29 device tier, which carries a $2,750 monthly Technology Fee, before adding the Managed Services Fee and applicable security package.
The purpose of the example is not to create a quote. It shows why endpoint count, security requirements, environment size, optional services, and projects all matter when developing an annual technology budget.
Non-Profit IT Budget Checklist
Before approving the annual technology budget, leadership should be able to answer:
- How many managed endpoints do we have?
- Which security package are we using?
- Are user and email security adequately addressed?
- What equipment will need replacement during the next 12-36 months?
- Which major projects are anticipated?
- Do we have an appropriate recovery strategy?
- Are there regulatory, insurance, grant, or contractual requirements affecting technology?
- Which services are outside the managed agreement?
- What risks are we consciously accepting?
- Does the budget support growth or only today’s environment?
When evaluating providers, pricing should also be considered alongside scope, security, proactive management, and long-term planning. A strong IT-provider comparison examines what is actually included and how the provider manages risk, not simply which monthly proposal has the lowest number.
What Should a Non-Profit Actually Budget?
For initial planning, $125-$175 per endpoint per month is a realistic range for a properly secured managed environment, but the final investment depends on the organization.
The important budgeting principle is predictability without pretending every technology expense can be bundled into one number.
A good budget identifies recurring managed services, security, lifecycle replacement, projects, optional risk controls, and future requirements separately. That gives executive leadership and the board a much clearer picture of both cost and risk.
Review a managed services approach built around predictable costs, proactive operations, and measurable business outcomes.
