IT support for Dallas nonprofits and churches

Who does IT for nonprofits and churches in Dallas?

I do, and it is work I take on gladly. I am Anthony Omini and I run Cross River Tech, a small, owner-led managed IT company in Dallas. Nonprofits and churches get the same service my business clients get: computers, network, Microsoft 365 or Google Workspace, backups, security and someone to call when something breaks. What changes is the shape of the problem, not the standard of the work.

Three things make nonprofit IT different in practice. Budgets are genuinely tight and every dollar has to be defended to a board. Staffing is a mix of a few paid employees and a rotating group of volunteers, so the people using the systems change constantly. And the equipment is often whatever has been donated over the years, which means five different laptop models, three ages of hardware and at least one machine nobody will admit to owning.

None of that is a reason to accept worse IT. It is a reason to prioritize ruthlessly. For an organization with a small budget, the sensible order is: protect the donor and financial data first, get the software licensing onto nonprofit pricing second, standardize the hardware slowly third, and make the Sunday or event-day experience reliable fourth. Everything else can wait for a grant.

Support can be ongoing through managed IT services, quoted per user or per device after a short conversation and billed month-to-month with no lock-in, or hourly with no agreement at all through hourly IT support and break/fix. Many small nonprofits start hourly and move to a plan once they see how much they actually call.

What do you do about donated computers?

Accept them selectively. A donated computer is only a gift if it costs less to run than it saves, and a lot of donated machines fail that test. A ten-year-old desktop that takes four minutes to boot, cannot run current Windows and needs a new drive costs more in volunteer frustration and support time than a modest new machine would.

The policy I recommend, which you can hand to a donor without offending anyone:

• Set a minimum specification. Something like: it must run a currently supported version of Windows, have a solid state drive, and have at least 8 GB of memory. Anything below that is declined politely or accepted for parts.
• Insist on a clean handover. The donor's data must be gone and the machine must not still be joined to their company's domain or management system. A donated laptop that is still enrolled in a business's device management can be remotely wiped by that business later.
• Ask for batches, not singles. Ten identical machines from one company refresh are worth far more than ten different machines from ten households, because one image and one driver set covers them all.
• Standardise what you buy. When you do spend money, buy business-line machines from one manufacturer. I work with Dell and Lenovo business lines because parts, drivers and warranty support are predictable.
• Track everything. A simple list of every machine, who has it, its age and its warranty status. Nonprofits lose track of equipment faster than businesses do because people come and go.

There is a real cost hiding in mixed hardware that boards rarely see: support time. Every different model is a different driver problem, a different failure pattern and a different replacement part. Standardising is not a luxury purchase, it is the cheapest thing you can do to reduce ongoing support hours.

How do you handle volunteers with administrator access?

Carefully, and this is the issue I find most often. In a typical small nonprofit or church, the pattern goes like this: a volunteer who was good with computers set things up years ago, gave themselves and two others full administrator rights, and then moved away. Nobody removed the access. Nobody knows the passwords they used. The accounts are still active, and one of them is the only global administrator on the Microsoft 365 tenant.

What to put in place instead:

1. Separate the roles. A volunteer who runs the sound desk needs access to the sound computer, not to the donor database. Give access by role, not by trust level.
2. Everyone gets their own account. Shared logins used by "whoever is on duty" make it impossible to know who did what, and impossible to close one departing volunteer's access.
3. Administrator rights are for administrators. Day-to-day accounts should be standard users. It stops most accidental software installs and a lot of malware.
4. The organization owns the credentials. Domain registrar, Microsoft 365 or Google Workspace, website, donor platform, bank portal. These belong in a password manager controlled by the executive director or a board officer, not in a volunteer's personal notes.
5. Review access quarterly. A fifteen-minute pass through the list of accounts, asking who still needs each one. This is the single highest-value habit a small nonprofit can adopt.
6. Offboard the same day. When a volunteer or staff member finishes, close their access that day, the same way you would collect a key.
7. Multi-factor authentication on everything. Especially the accounts that touch money, the donor system and email.

None of this is a judgment on volunteers, who are usually the reason anything works at all. It is about making sure the organization, not an individual, holds the keys. The same principle applies to whoever provides your IT, which is why documentation and credential ownership are worth asking about. Who owns your passwords, domain and equipment covers that in detail.

How should a nonprofit protect donor data?

Treat it like client records at a law firm, because in the ways that matter it is the same thing: names, addresses, giving history, sometimes payment details, held by an organization people trusted. Most small nonprofits are not subject to the specific regulations that bind a medical or financial business, but the reputational damage from a donor data breach is severe and the practical protections are the same either way.

What I put in place:

• Access limited to the people who need it. The donor database is not a shared drive folder everyone can browse. If your giving records live in a spreadsheet on a shared drive, that is the first thing to fix.
• Multi-factor authentication on the donor platform and on email. Most donor systems are cloud services now, so the account is the perimeter.
• Backups you control. Your donor platform vendor keeps the service running; that is not the same as a copy you can restore from after a mistaken bulk delete. The same applies to email and files, as explained in Microsoft 365 security for a small business.
• Payment data kept out of your systems entirely. Card details should live with your payment processor, never in your spreadsheets, your email or your files. If a donor emails you a card number, delete it and call them.
• A rule about email requests for money. Any change of bank details, any urgent wire request, any gift-card errand supposedly from the executive director or the pastor gets confirmed by phone on a number you already had. Nonprofits are targeted for this specifically, and the FTC and CISA both publish plain-language guidance on business email fraud that is worth circulating to staff.
• Encryption on laptops. A laptop with donor records that is stolen from a car in a Dallas parking lot is a much smaller problem if the drive is encrypted.

Security work of this kind sits under cybersecurity, backup and disaster recovery, and for a small organization most of it is configuration rather than new purchases.

What does nonprofit software pricing from Microsoft and Google change?

A great deal, and it is the fastest way to free up budget. Both Microsoft and Google run programs for eligible nonprofit organizations that grant or heavily discount their business plans. Eligibility is verified through an outside validation partner, and the exact terms, seat counts and included plans change over time, so treat what any article tells you as a starting point and check the current terms directly before you plan a budget.

The important part for planning: nonprofit pricing usually puts a proper business plan within reach of an organization that assumed it could only afford free consumer accounts. That matters because the security features that protect donor data live in the business plans, not the free ones. Multi-factor authentication, conditional access rules, device management, better phishing filtering and administrative control over accounts are exactly what a small nonprofit needs and exactly what nonprofit pricing makes affordable.

What I do when an organization comes to me still running on personal Gmail accounts or a mix of free mailboxes:

1. Confirm eligibility and get the validation process started, since it takes time and paperwork rather than technical work.
2. Register or take control of a proper domain name, so email addresses belong to the organization instead of to individuals.
3. Set up the tenant properly: one account per person, admin accounts separate from daily accounts, multi-factor authentication for everyone.
4. Migrate the existing mail and files, which is usually the fiddliest part when history is scattered across personal accounts.
5. Turn on the security settings the plan includes but does not enable by default.
6. Write down who administers what, and store the credentials where the board can reach them.

Other vendors run nonprofit programs too, including hardware manufacturers and some backup and security vendors, and there are technology grant marketplaces that resell donated software to qualifying organizations. It is worth asking every vendor you already pay whether they have nonprofit pricing. Many do and almost none advertise it to existing customers. Setup and migration work of this kind is covered under Microsoft 365 and Google Workspace support.

How do you make weekend and event days work?

This is where church IT diverges from business IT completely. A business network is busiest on a Tuesday morning with twenty known devices. A church network is quiet all week and then, on Sunday morning or during an evening event, has two hundred phones asking for guest Wi-Fi, a streaming setup pushing video out, a card reader taking donations and a volunteer trying to open a presentation from a laptop nobody has seen before, with no technical staff in the building.

What actually holds up under that:

• A separate guest network. Guests get internet and nothing else: no access to the office computers, the donor database or the streaming equipment. This is one setting on business-grade equipment and it is the most important one.
• Enough access points, placed properly. One consumer router in the office will not cover a sanctuary or a fellowship hall. Coverage needs access points mounted where the people are, on cable, which is a data cabling job rather than a shopping trip.
• Wired connections for anything that matters. The streaming computer, the card reader and the sound system should be on cable, not competing with two hundred phones for the same airspace.
• Bandwidth that matches what you push out. Streaming a service uses upload capacity, which is the number most internet plans skimp on. Check the upload speed, not the download headline.
• A one-page runbook for volunteers. Which cable goes where, what to do if the stream drops, which power strip to check, and the number to call. Written for someone who is not technical and is already stressed.
• A test before the event, not during it. Fifteen minutes on the Thursday saves an hour of panic on the Sunday.

Because remote support is available around the clock including holidays, an event-day problem does not have to wait for Monday, though after-hours rates apply for weekend work. Much of what goes wrong on an event day is fixable remotely if someone in the building can be my hands for two minutes. What can and cannot be fixed remotely sets out where that line falls.

What should a small nonprofit actually spend on IT?

Less than you might fear, if you sequence it correctly. Here is how I would order the spending for a small Dallas nonprofit or church with, say, five to fifteen staff and a group of volunteers, from highest value per dollar down.

Items one and two cost almost nothing but time and remove most of the real risk. That is the honest advice: if your budget only stretches to a few hours of paid help this year, spend it there rather than on new equipment.

For hourly work, rates are $100 per hour remote and $150 per hour onsite during business hours, Monday to Friday, 8 AM to 5 PM Central, and $150 remote and $225 onsite after hours, weekends and holidays, with a one-hour minimum. A cleanup of accounts and licensing for a small organization is usually a handful of hours, not a project. Ongoing plans are quoted per user or per device, month-to-month, so a nonprofit is never locked into something a lean year cannot support.

How do you keep IT running when nobody on staff is technical?

By writing things down and removing single points of failure. The failure mode I see in nonprofits is not a dramatic breach. It is that the person who understood the systems has left, and now nobody can add an email address, nobody knows who the domain is registered with, and the donor database backup has been failing quietly for months.

What to have in place, whoever supports you:

• A written inventory. Every account, service and piece of equipment, what it does, what it costs and who to call about it. One document, kept current.
• Credentials in a shared password manager owned by the organization, with at least two officers holding access.
• Monitoring on the things that fail silently: backups, disk space, antivirus, and the internet connection.
• A named person to call, with the number posted where volunteers can find it.
• An annual review with the board: what broke this year, what is aging out, what the next twelve months should include. This turns IT from an emergency line item into a planned one, which boards approve far more willingly.

A small, owner-led provider suits this well, because you deal with me every time and nobody has to re-explain the building or the history, while my team keeps the routine monitoring and updates running behind me. It also has an honest limit worth naming: onsite visits are by appointment, and event-day coverage depends on documentation and a volunteer who can be my hands rather than on a night shift. A small IT company vs a big MSP lays that out fully, and national IT chain or local Dallas provider covers the same trade-off from the other direction.

If you run a nonprofit or a church in Dallas and you are not sure where you stand, get in touch. Tell me roughly how many staff and volunteers you have, what you use for email and donations, and what has been breaking. I will tell you what I would fix first, what it would cost, and what you can genuinely do yourselves without paying anyone.

Questions people ask

Written and reviewed by

Anthony Omini, founder of Cross River Tech

Over 15 years in IT across many industries, now running Cross River Tech, a small owner-led managed IT company in Dallas. Every article is written from his own client work and checked by him before it is published.

Running a Dallas nonprofit or church on donated equipment and goodwill? Tell me how many staff and volunteers you have and what keeps breaking. I will tell you what to fix first, what nonprofit pricing could save you, and what you can do yourselves for nothing.

Ask Anthony(214) 612-7080About Anthony