How to Explain New Software to Your Committee

You've done the hard part. You've identified that your club's admin is unsustainable. You've researched the options. You've probably signed up for a trial, clicked around, and thought "yes, this would actually fix half our problems."

Now comes the part nobody warns you about: getting six volunteers who didn't ask for change to agree that change is a good idea.

This is where most software adoption fails in clubs. Not because the technology doesn't work. Not because the price is wrong. Because the person who found the tool couldn't get the committee past "we've always done it this way." The software gets trialled by one person, never adopted by the group, and the club is back to spreadsheets by the next AGM.

This guide is about preventing that. It's about understanding why committees resist, how to present new software in a way that actually lands, and how to move from "let's discuss it at the next meeting" to "this is now how we do things."

The advice here applies to any club management software. We'll reference TidyHQ because that's who we are, but the principles work whether you're pitching TidyHQ, a competitor, or even a free tool like Google Workspace.

Why software adoption fails in volunteer organisations

Enterprise companies spend millions on change management when they roll out new systems. They hire consultants, run training programmes, and still fail about 70% of the time according to McKinsey research. Volunteer-run clubs attempt the same kind of change with zero budget, zero authority, and a committee that meets once a month for ninety minutes.

The odds aren't great. But they improve dramatically once you understand what you're actually up against.

It's not about the software

The resistance you'll encounter isn't really about the specific tool you've chosen. It's about three deeper things.

Loss of control. The treasurer has spent three years building a spreadsheet that tracks everything exactly the way they want it. That spreadsheet is their system. Asking them to move to new software feels like asking them to hand over something they built - because it is. This isn't irrational. It's human.

Fear of incompetence. Committee members who aren't tech-confident are afraid they'll look foolish trying to learn something new. They won't say this out loud. They'll say "our current system works fine" or "I don't have time for this." But underneath those objections is a person who doesn't want to struggle with a computer in front of their peers.

Workload anxiety. Every volunteer on your committee is already doing more than they signed up for. Anything that sounds like more work - even if it will eventually reduce work - triggers resistance. "I don't have time to learn this" is the most honest objection you'll hear, and it deserves to be taken seriously.

McKinsey's research on digital transformation found something that matters here: transformation efforts where employees helped generate the ideas were 1.4 times more likely to succeed than those where solutions were handed down from above. In a volunteer context, this multiplier is probably even larger. Nobody on your committee wants to be told what to do. They're unpaid. They can walk away. The moment it feels like a mandate rather than a conversation, you've lost.

Before the meeting: lay the groundwork

The worst way to introduce new software is to surprise your committee with it at a meeting. The second worst way is to email them a link and say "have a look at this before Tuesday."

Instead, do the preparation that makes the meeting a formality rather than a debate.

Name the problem first, not the product

Weeks before you mention any software, start naming the problem in conversation. At the next meeting, during general business, raise the specific pain point: "We spent twelve hours this month chasing renewals by text. Is there a better way to handle this?" At the social event, mention it casually to the president: "I was adding up how long we spend on admin - it's pretty significant."

You're not proposing a solution yet. You're getting the committee to collectively acknowledge that a problem exists. This is John Kotter's first stage of change - establishing urgency - and it's the step most people skip because they're excited about the solution they've found.

Involve someone influential early

Every committee has one or two people whose opinion carries weight. It might be the president. It might be the longest-serving member. It might be the person who everyone trusts with money. Before the formal pitch, show that person the software privately. Walk them through it. Ask for their honest reaction. If they're positive, you've got an ally in the room. If they're sceptical, you've learned what objections to prepare for.

Do a quiet trial

Most club management platforms offer a free tier or trial period. TidyHQ, for example, has a free plan that lets you set up your club and test core features without committing any money. Use this. Set up your club in the system. Import a sample of your membership data. Configure one process - say, membership renewals - and run it for a couple of weeks. When you walk into the committee meeting, you're not pitching an idea. You're demonstrating a result.

The 5-minute committee pitch

You've got a committee meeting. You've got an agenda item. You probably have five minutes before someone changes the subject or asks to "table it for next time." Here's how to use those five minutes.

Minute one: name the pain

Start with something specific and numerical. Not "our admin is inefficient" but "I tracked our admin hours last month. Between renewals, communications, and event sign-ups, we spent 22 hours on things that could be automated. That's the equivalent of a part-time job."

Numbers are difficult to argue with. Feelings are easy to dismiss.

Minute two: show, don't tell

Open the software on a laptop or screen. Don't talk about features. Instead, walk through one specific scenario: "Here's what happens when a member's renewal comes due. The system sends them an automatic email. They click a link, pay online, and their membership updates instantly. Nobody has to chase them. Nobody has to update a spreadsheet. Let me show you what that looks like."

This is the most important minute. A live demonstration of a real problem being solved is worth more than any slide deck or feature comparison.

Minute three: address cost

Get ahead of the money question because someone will ask. Be specific: "The plan we'd need costs [amount] per year. That's [amount] per month. We currently spend approximately [hours] volunteer hours per month on the tasks this would automate. If we value volunteer time at even $20 an hour, we're spending $[amount] in volunteer time to avoid paying $[amount] in software."

If you're recommending a free tier, say so plainly: "We can start on the free plan. It covers what we need right now. If we outgrow it, the paid plan is [amount], but we don't need to decide that today."

Minute four: propose a trial, not a commitment

Don't ask the committee to commit to anything permanent. Ask for permission to run a trial: "I'd like to run our membership renewals through this system for the next six weeks. If it saves us time and works for everyone, we discuss making it permanent. If it doesn't, we go back to what we have. No cost, no risk."

A trial removes the stakes from the decision. Nobody has to commit. Nobody has to admit the old way was wrong. They just have to agree to try.

Minute five: answer questions

Keep answers short. If you don't know the answer, say "I'll find out and report back" rather than guessing. The most common questions are addressed in the next section.

Addressing the six common objections

"It costs money and we're a volunteer club"

This is the most frequent objection and often the easiest to address. Calculate the volunteer hours your club currently spends on tasks the software automates. Membership renewals, payment reconciliation, event communications, manual data entry. Multiply those hours by a modest hourly rate - even $20 an hour. For most clubs with over 100 members, the annual software cost is less than a month's worth of volunteer admin time.

If budget genuinely is the constraint, start with a free tier. TidyHQ and several other platforms offer free plans that cover basic membership management. You can prove value before spending a cent.

"Our spreadsheet works fine"

It works fine for the person who built it. Ask these questions: Can anyone else on the committee update it? Is it backed up? Can it send automatic renewal reminders? Can members update their own contact details? Can it take online payments? Can you generate a financial members report for your AGM in thirty seconds?

The spreadsheet isn't the problem. The problem is that it's a single point of failure maintained by one person, and it can't do things that members increasingly expect - like paying online.

"I don't have time to learn something new"

This objection is legitimate and should be respected. The answer isn't "it's easy" - because what feels easy to you might not feel easy to someone else. The answer is: "You won't need to learn everything. You'll need to learn the two or three things relevant to your role, and I'll sit with you for twenty minutes to walk through them. There's also a support article called 'How do I explain TidyHQ to the rest of my committee?' that covers exactly this."

Then actually follow through. One-on-one walkthroughs, not group training. Patience, not enthusiasm.

"What about our data? Is it safe?"

A reasonable concern. Any reputable club management platform stores data in secure, encrypted cloud infrastructure - which is objectively safer than a spreadsheet on someone's personal laptop that isn't backed up. Address this by explaining that the platform handles data security professionally, that you can export your data at any time if you want to leave, and that your member information is almost certainly safer in a purpose-built system than in a file emailed between committee members.

"We tried something like this before and it didn't work"

If your club has a failed technology attempt in its history, acknowledge it directly. "You're right, the last time we tried to change systems it didn't stick. I think that's because we tried to move everything across at once and nobody had time to learn it properly. This time I'm proposing we start with one thing - just renewals - and only expand if it works."

Naming the past failure shows self-awareness and signals that this attempt will be different.

"Can't we just wait until next year?"

This one is harder because it sounds reasonable. The answer is: what changes next year? The admin burden will be the same or worse. Volunteer turnover means the people who know the current system might not be here. Membership expectations for online services are only increasing. There's no magical future moment when the change becomes painless. But starting with a small trial now means that by next year, the hard part is behind you.

The phased rollout: start small, prove value, expand

The single biggest mistake clubs make with new software is trying to implement everything at once. Membership, events, communications, finances, documents - all in one overwhelming migration. This is how you burn out your most engaged volunteers and create a backlash that kills the project.

Instead, follow a phased approach.

Phase 1 (weeks 1–6): one module, one win

Choose the process that causes the most visible pain. For most clubs, this is membership renewals or member communications. Set it up in the new system. Run it for six weeks. Track the results - time saved, payments received, member response rate. Report back to the committee with specifics: "We processed 43 renewals in the last six weeks. 38 were paid online without any chasing. Last year, the same period required 26 individual follow-up messages."

Phase 2 (weeks 7–12): add the next module

With credibility from phase one, introduce the next most valuable feature. If you started with renewals, add event management or communications. Train the relevant committee member. Run it alongside the now-proven first module.

Phase 3 (months 4–6): consolidation

By now, two or three core processes are running through the new system. This is when you start retiring the old tools - archiving the master spreadsheet, redirecting email communications through the platform, pointing members to the online portal. This phase is about making the new system the default, not the alternative.

Training volunteers who aren't tech-confident

Group training sessions don't work for people who are anxious about technology. They're too fast, too public, and too generic. Here's what actually works.

One-on-one walkthroughs. Sit with each committee member individually. Show them only the tasks relevant to their role. The treasurer needs to see financial reports and payment tracking. The secretary needs member communications and contact management. Nobody needs to learn the entire system.

Screen recordings. Record a 2–3 minute video of each common task - "how to send a renewal reminder," "how to add a new member," "how to pull a financial members list." Share these in your committee group chat so people can rewatch them at their own pace. A phone recording of your screen is perfectly fine. It doesn't need to be polished.

The buddy system. Pair each less-confident committee member with a more confident one. When they get stuck, they message their buddy rather than struggling alone or giving up.

Reassurance that mistakes are reversible. The single most powerful thing you can say to someone who's nervous about new software is: "Nothing you click will break anything. Everything can be undone." Most modern club management platforms, including TidyHQ, are designed so that accidental changes are easily reversed. Say this early and often.

Getting members to drive adoption from the outside in

Here's something counterintuitive: your members might adopt the software faster than your committee. When you enable online membership payments, event registrations, and contact updates, members start using these features immediately - because they're convenient. They don't need training. They click a link in an email, pay with their card, and they're done.

Once members are using the system, it becomes very difficult for the committee to revert to the old way. You can't go back to manual payment tracking when 80% of your members have already paid online. This is adoption from the outside in, and it's one of the most effective dynamics in club software implementation.

Enable member-facing features early. Send the first renewal round through the new system. Share the event registration link. Let members update their own contact details. Every member who interacts with the platform is evidence that the system works.

The generational dynamic

Most committees include a mix of ages, and this creates a predictable tension around technology. Younger volunteers - often parents of junior members who've joined the committee - expect digital tools. They find it frustrating when the club operates on paper sign-up sheets and bank transfers. Older volunteers - often the most experienced and most committed - may prefer established processes and find constant digital change exhausting.

Neither group is wrong. The goal isn't to force everyone into the same comfort level. It's to find an approach that respects both perspectives.

In practice, this means letting digital-native committee members champion the new system while providing patient, pressure-free support to those who need more time. It means keeping a paper option available during the transition period for members who prefer it. And it means framing the change not as "we need to modernise" (which implies the current way is outdated and the people who run it are behind) but as "we need to reduce the admin burden so our volunteers can spend time on the things they actually enjoy."

Measuring success in the first 90 days

You need numbers, not feelings, to demonstrate that the new system is working. Track these from day one.

Volunteer hours saved. Compare the time spent on key tasks before and after. If renewal chasing took 8 hours per month and now takes 1, that's your strongest argument for expanding to other modules.

Online payment rate. What percentage of membership fees are now paid online versus manual bank transfer or cash? This number will climb steadily and is visible proof that members prefer the new system.

Data completeness. Are member records more complete now than they were in the spreadsheet? Can you generate a financial members list instantly? Can you pull emergency contacts for a Saturday morning game? These are the practical outcomes that matter.

Committee confidence. Informally, are committee members using the system without asking for help? Are they logging in independently? This is the adoption metric that determines long-term success.

Member feedback. Are members commenting positively on the convenience of online payments or event sign-ups? Capture these comments - they're ammunition for the next committee discussion.

Set a 90-day check-in on the committee agenda. Present the numbers. Ask what's working and what isn't. Decide together whether to expand to the next module. This structured review keeps the project accountable and gives sceptics a formal opportunity to raise concerns - which, by 90 days, are usually far fewer than they expected.

When adoption stalls

Sometimes the trial goes well but momentum fades. People revert to old habits. The spreadsheet reappears. Here's how to diagnose and fix the most common stalls.

One person is blocking adoption. Usually because they feel their role or expertise is being diminished. Talk to them privately. Acknowledge their contribution. Show them how the new system makes their role easier, not redundant. If they're the treasurer, show them the reporting features. If they're the membership coordinator, show them the automated reminders. Make them the expert in the new system, not the victim of it.

The system is set up but nobody is using it. This usually means the transition was announced but not managed. Go back to phase one: pick one process, make it the official way of doing that task, and remove the old option. You can't run two systems indefinitely - at some point, the committee has to commit to one.

Members aren't engaging with online features. Send the link again. And again. Most members need to see an online payment link three or four times before they use it. Include it in every communication. Make it the default option, with manual payment as the exception rather than the other way around.

The committee voted to "revisit it later." This usually means the trial didn't produce clear enough results, or the results weren't communicated effectively. Go back to measuring. Collect specific numbers - time saved, payments processed, manual tasks eliminated - and present them at the next meeting. If the numbers genuinely don't support the change, that's useful information too.

The long view

Adopting new software isn't a project with a finish line. It's a shift in how your club operates. The first 90 days are the hardest. After six months, the new system will feel normal. After a year, nobody will remember what it was like before - or rather, they'll remember, and they won't want to go back.

The volunteers who were most resistant often become the strongest advocates once they see the results. The treasurer who didn't want to give up the spreadsheet discovers that automated payment reconciliation gives them their weekends back. The secretary who was nervous about technology finds that sending a newsletter takes five minutes instead of an hour.

Your job isn't to convince everyone on day one. It's to create the conditions where the software can prove itself. A low-risk trial. One visible win. Patient training. Clear numbers. That's the formula.

And if you're looking for a place to start, TidyHQ's free plan lets you set up your club, import your members, and test the core features without spending anything or committing to anything. It's specifically designed for the situation you're in right now - you've found the tool, you just need to bring your committee along.

The support team has even written an article called "How do I explain TidyHQ to the rest of my committee?" which covers the practical side of that conversation. It's worth reading before your next meeting.

Your committee doesn't need to love the software. They need to agree that the current situation costs more than the effort of changing. That's a much easier argument to win.