You Don't Need More Software. You Need Better Systems.

Let's say your organization is in the middle of the highest donor season of the year.

For many people, that would be Christmas because people are feeling a little more generous and want to do some good in the world. You know there will be an increase in donations, but because of a lack of people on your staff, donor engagement goes down because the time it takes to respond to each person is too much.

Retaining those donations is more important than getting them once a year. If donors do not feel engaged, they are less likely to donate again.

Someone on your team proposes adding software that can do it automatically. What a great idea.

The only problem is that this becomes another software platform to search for, purchase, install, and then make sure it actually does its job. That is all assuming your current workflow is not broken already.

If you do not have a good system or workflow around responding promptly to new donations, then a new software platform or AI tool is not going to perform a miracle for your organization. Instead of getting new software first, your organization should be implementing better systems.

I think this happens to organizations more often than we realize. There is a problem, someone notices it, and almost immediately the conversation becomes, "What software can fix this?"

It makes sense. If your staff is overwhelmed, you want to help them. If something is taking too long, you want to make it faster. If people are forgetting things, you want something that will remind them. And if you hear that a new AI tool can automate half of someone's job, it is pretty tempting to see if it can do the same thing for your organization.

But there is a question that often gets skipped in that conversation:

What Is Actually Causing the Problem?

Imagine you are the executive director of a nonprofit. It is Monday morning, and you already have more things on your list than you have time to get through.

A donor needs a response. A volunteer is waiting for an answer. There is an event coming up that still needs attention. An employee needs an approval. Your board needs a report later in the week.

You sit down at your computer and start working through everything, but pretty quickly you realize that the information you need is scattered everywhere. The donor information is in your CRM, the event details are in a Google Sheet, the volunteer information is in someone's email, and the latest version of a report is sitting in a folder that you are not even sure is the right folder.

None of the software is necessarily broken. Your CRM works. Google Workspace works. Your email works. Your spreadsheet works.

The problem is that all of those things are working independently instead of working together as part of a system.

That is the difference between software and a system. Software is a tool. A system is everything that makes the work actually happen. It includes the people responsible for something, the process they follow, where the information lives, what happens when something goes wrong, who is accountable for the outcome, and how everyone knows whether the work was actually completed.

Take something as simple as following up with a first-time visitor at a church.

A family comes through the doors on Sunday morning and fills out a connection card or scans a QR code. Their information gets entered into the church's database and an email notification is sent to someone on staff. So far, everything is working exactly as it should.

But then someone says, "Hey, can somebody reach out to that family?"

Who is somebody? Is it the person who received the notification? Is it the pastor? Is it the volunteer coordinator? Is it whoever happens to notice the email first? How quickly should they reach out? What should they say? Where should they record the conversation? What happens if they do not get an answer? Who checks to make sure the follow-up actually happened?

Those are not really software questions. They are system questions.

The software can help make the process easier, but it cannot decide what your organization believes the process should be. Research from McKinsey has made a similar point when looking at technology transformations, finding that organizations tend to get more value from technology when they improve their people, processes, and technology together rather than treating technology as an isolated solution.

Why Organizations Keep Buying More Tools

I do not think organizations buy too much software because they are careless. Most of the time, someone is trying to solve a real problem.

A staff member is overwhelmed, so they find a tool. A ministry leader wants a better way to communicate with volunteers, so they find an app. An executive director hears about an AI platform that can automate administrative work and thinks it might finally take something off their team's plate.

Those are all reasonable decisions.

The problem starts when every new problem gets its own software solution without anyone stepping back and asking whether the underlying process makes sense.

Let's go back to that nonprofit with the donor follow-up problem. Maybe some donors receive a response within a day, while others do not hear anything for a week. Maybe nobody is really sure who is supposed to respond in the first place.

Someone says, "We need a CRM."

Maybe they do. But a CRM does not answer the most important questions. Who owns donor follow-up? How quickly should a donor receive a response? What should that communication look like? Where should it be recorded? What happens when the person responsible is out of the office? Who knows when the follow-up is actually complete?

You can buy the best CRM in the world and still have no answer to any of those questions.

That is why buying software is often easier than redesigning how work actually happens.

Redesigning a process means sitting down with people and asking what is actually happening. It means figuring out why something keeps getting missed. It can mean changing responsibilities or admitting that the way something has always been done no longer makes sense.

Buying software feels more concrete. You can put it on a credit card, schedule an implementation, and have a training meeting. But none of those things guarantee that the underlying problem has been solved.

Software Sprawl Creates Its Own Problems

There is another problem that comes with constantly adding technology: eventually, people stop knowing where things belong.

Maybe donor information is in the CRM, but the most recent notes are in someone's spreadsheet. The event information is technically in the church management system, but the volunteer schedule is in Google Sheets. Someone has an important document sitting in their email because they could not remember where it was supposed to be stored.

Then a new employee joins the organization and you have to explain how everything works.

"Donor information is here, except for these donors. Those are in this spreadsheet. Events are technically here, but we usually use this other document. If you need the latest version of this report, ask Sarah because she keeps the most recent copy."

At that point, the problem is no longer just technology. It is the system around the technology.

IBM describes this problem as SaaS sprawl, which refers to the unchecked growth of software applications within an organization. Their research points to inefficient workflows, data silos, unnecessary costs, and security concerns as some of the problems that can come with it.

I think this becomes even more important as AI continues to make it easier for people to add new tools. Someone on your team can find an AI application in five minutes and start using it before anyone else even knows it exists.

Maybe it saves them an hour every week, which is great. But six months later, you might have six different people using six different tools for six different pieces of work, with no shared understanding of how those tools fit into the organization's overall process.

The technology may be helping each individual person, but is it helping the organization?

That is the question I think we need to ask more often.

When Everything Works, But the Process Still Fails

One of the easiest ways to see this is through something as simple as visitor follow-up.

Someone attends your church for the first time and fills out a digital connection form. The form works. The information goes into the database. The database works. An administrator receives an email. The email works. The administrator tells a ministry leader that the family visited. The ministry leader's phone works.

Everything works.

Three days later, someone asks, "Did anybody ever follow up with them?"

Nobody knows.

That is one of the most frustrating types of problems because nothing appears to be broken. The form worked. The database worked. The email worked. The phone worked.

The problem was that nobody clearly owned the process, there was no deadline, there was no defined workflow, and there was no easy way to see what happened.

The same thing can happen with volunteer onboarding, donor communication, event planning, staff requests, purchase approvals, employee onboarding, and reporting.

You can have good people and good software and still have a broken system. In fact, every individual piece of technology can work exactly as designed while the overall process completely fails.

Technology is supposed to remove friction, not create more of it.

I do not think most pastors or nonprofit leaders want another piece of software just because it is new. They want fewer things falling through the cracks. They want their staff to know what is happening. They want information to be easy to find. They want volunteers to know what they are supposed to do. They want donors and the people they serve to receive the attention they deserve.

Most importantly, they want their people spending more time doing the work the organization exists to do and less time trying to figure out which spreadsheet is the right one.

CDW's 2026 research into what it calls the "Frictionless Enterprise" surveyed more than 950 IT decision-makers, and 54% said introducing new tools felt slower or more difficult than it should. Their research looked at technology alongside processes and teams rather than treating technology as the only factor.

For a large corporation, that might mean another project for the IT department. For a church with five employees, it might mean the children's director is suddenly responsible for learning another platform. For a nonprofit with a small staff, it might mean the executive director is now managing another subscription, another login, another integration, and another process.

A smaller organization might actually have fewer software platforms than a large company, but it also has fewer people available to manage those platforms. That means complexity can become painful very quickly.

The cost is not always the monthly subscription. Sometimes the real cost is the time your people spend trying to keep everything connected.

AI Still Needs a System

This is especially important now that AI is becoming part of everyday work.

AI can write, summarize, organize, analyze, search, communicate, and automate in ways that would have sounded unrealistic a few years ago. There is real value there.

But AI does not remove the need for a good system.

If nobody knows who owns a request, AI cannot create accountability. If five different systems contain conflicting information, AI cannot automatically know which one your organization trusts. If nobody knows what "finished" actually means, AI can send reminders all day and still not solve the problem.

You can automate a bad process. You just end up doing the wrong thing faster.

McKinsey's research on automation has similarly emphasized improving and standardizing processes rather than simply automating isolated problems.

That is why I think the order matters.

First, understand the process. Then figure out how technology can support it. Then look for opportunities to automate.

Technology can absolutely help you build a better process, but you should understand what you are trying to accomplish before asking a tool to accomplish it for you.

Diagnose Before You Prescribe

Before your organization buys another piece of software, sit down with the people who actually do the work and ask some simple questions.

What starts the process? What happens next? Who owns the result? Where does the information live? How do we know it happened? If a visitor submits a form, what happens next? If a donor gives, who follows up? If an employee submits a request, who sees it? If someone is out sick, does the process stop? If the person who normally handles something leaves the organization tomorrow, could someone else figure out what to do?

Those questions might seem obvious, but they can reveal problems that another software subscription never will.

A good system should make work feel simpler. People should know what they are responsible for. Information should have a clear home. Important tasks should not depend entirely on someone's memory. Leadership should not have to chase five people just to find out whether something was completed. A new employee should not need to spend six months learning all of the unwritten rules of how things work.

Technology should be able to sit quietly in the background and help people do their jobs instead of constantly demanding their attention.

Good systems are often almost invisible. You notice them because fewer things fall through the cracks.

And I think that matters even more for churches and nonprofits because the mission is the reason you exist in the first place.

A church is not trying to become more efficient because efficiency itself is the goal. A nonprofit is not trying to streamline its operations because streamlined operations are the mission.

The point is what that efficiency makes possible.

If your staff spends less time searching for information, they have more time to serve people. If a pastor does not have to spend an afternoon tracking down information from three different people, they have more time for ministry. If an executive director can see what is happening without sending ten emails, they have more time to lead.

Efficiency is not the mission. Efficiency creates additional capacity for the mission.

Sometimes You Really Do Need Better Software

I also do not want to take this argument too far. Sometimes your organization really does need better software.

Maybe your current CRM does not work for you anymore. Maybe your church management system is outdated. Maybe your nonprofit needs a centralized database. Maybe your website needs to be rebuilt. Maybe your systems need better integrations. Maybe AI really can eliminate hours of repetitive work.

There is nothing wrong with any of those things.

The problem is buying them before understanding what you are actually trying to fix.

Before replacing software, look at the process. What is supposed to happen? What actually happens? Where does it break? Who is responsible? Where is the information? What happens when something goes wrong?

Once you understand that, the answer becomes much easier to see.

Sometimes you need new software. Sometimes you need to connect the software you already have. Sometimes you need to remove software. Sometimes you need to change the process. Sometimes you simply need to make sure everyone understands what they are responsible for.

That is why I like the phrase, "Diagnose before you prescribe."

A doctor does not prescribe medication simply because you walked into the office and said you do not feel well. They ask questions first. They try to understand what is actually wrong.

Organizations should approach technology the same way.

If I were sitting down with your staff tomorrow, I probably would not start by asking what software you use. I would ask where things are getting stuck. I would ask what your staff spends too much time doing. I would ask what people constantly have to remind each other about. I would ask what information is difficult to find. I would ask which processes depend on one person knowing exactly what to do.

And then I would ask one question that I think every church and nonprofit should consider:

If one key member of your organization unexpectedly left tomorrow, which important process would suddenly become difficult for everyone else to understand?

Whatever your answer is, that process might be worth examining before you purchase another tool.

You may discover that you do not need another piece of software at all. You may just need to step back, look at how the work is actually happening, and build a better system around the people and technology you already have.

Because technology should strengthen a good system. It should not be expected to create one.

And sometimes, the best technology decision your organization can make is realizing that the problem was never the software in the first place.

It was the system.