You’ve found the tool. You’ve watched the demo. You know it would save the board 10 hours a month and eliminate the spreadsheet that’s been causing fights since 2022. You’re ready to sign up.
Then someone says: “We should discuss this at the next board meeting.”
The board meeting is three weeks away. At the meeting, the discussion goes sideways. Someone asks about the price. Someone else asks “can’t we just keep using Google Sheets?” The founding member says “we’ve always done it this way.” Nobody kills the idea. Nobody approves it either. It gets tabled for “more research.”
You leave the meeting feeling deflated. Not because the software was wrong. Because you didn’t make the case.
Here’s how to make the case.
Why “It’ll Be Easier” Isn’t Enough
Board members aren’t against new tools. They’re against spending money on things they don’t understand. And “it’ll make things easier” doesn’t help them understand. Easier for whom? Easier how? How much easier? What’s wrong with the current system?
Your board approves spending on venue rental because they can see the room. They approve the picnic budget because they can taste the food. Software is invisible. It does its work behind the scenes. The benefit is time saved, errors avoided, problems that don’t happen. Those are hard to point at.
A business case makes the invisible visible. It puts numbers on the problem and numbers on the answer. Not complex numbers. Simple ones.
Step 1: Count the Hours
Most business cases should start here, and many could end here too. Count how many volunteer hours your organization currently spends on tasks that software would handle.
Sit down with your treasurer, secretary, and membership chair. Ask each one: “How many hours a month do you spend on these tasks?”
- Updating the member list
- Tracking who’s paid and who hasn’t
- Sending payment reminders
- Answering “when’s the next event?” questions
- Reconciling bank statements against records
- Sending newsletters or announcements
- Managing RSVPs
- Generating reports for the board
Write down the numbers. Be honest. Don’t round down to seem reasonable. If the treasurer spends four hours a month chasing payments, write four hours.
Most community organizations find the total is between 15 and 30 hours per month across all volunteers. That’s 180 to 360 hours per year. Independent Sector’s 2025 report values volunteer time at $34.79 per hour. At the low end, that’s $6,262 worth of volunteer labor per year spent on administrative tasks.
Your proposed software costs what? $20 a month? $30? You’re spending $6,000 in invisible labor to avoid a $360 annual subscription. That’s the number that changes the conversation.
Step 2: List What’s Broken
Hours are abstract. Broken things are concrete. Your board members have experienced these problems personally. Naming them creates recognition.
Build a short list. Five items, maximum. Choose the ones your board will nod at.
“In the past 12 months, here’s what happened because of our current system.”
- The membership spreadsheet had three conflicting versions in March. The new treasurer spent a weekend reconciling them.
- We don’t know whether 14 members have paid their 2025 dues because the records are scattered across Venmo, Zelle, and checks.
- Two members were accidentally left off the annual meeting invite because they weren’t in the ‘current’ spreadsheet. One of them was offended.
- The outgoing events chair’s contact list was on her personal laptop. When she stepped down, we lost it.
- It took three weeks to send dues reminders because nobody was sure who’d already been reminded.
These aren’t hypothetical. Pull them from your actual experience. Every organization in the messy middle between spreadsheets and enterprise software has a list like this.
Step 3: Show the Cost of Doing Nothing
This is the part most people skip, and it’s the most persuasive part. The question isn’t “should we spend $300 a year on software?” The question is “can we afford to keep losing volunteer time and member trust?”
Frame it this way:
“If we keep our current system, here’s what we can expect in the next 12 months.”
- The treasurer will spend approximately 48 hours on manual tracking (4 hours/month x 12)
- We’ll have at least one more data conflict when multiple people edit the spreadsheet
- We’ll continue to have no clear record of who’s paid, leading to awkward conversations
- The next board transition will require rebuilding records from scratch, again
“If we adopt [tool name] at [$X/month], here’s what changes.”
- Payment tracking becomes automatic. Treasurer time drops from 4 hours/month to 30 minutes.
- One member list. Always current. No conflicting versions.
- Members can check their own payment status. No more “did I pay?” emails.
- Board transitions keep all data intact. Nothing lives on anyone’s personal laptop.
The cost of doing nothing isn’t $0. It’s the volunteer who doesn’t run for reelection because they’re exhausted. It’s the member who leaves because nobody tracked their payment. It’s the new board that starts from scratch because the old board’s records disappeared.
Step 4: Address the Objections Before They Come Up
Every board has the same three objections. Prepare answers for all of them.
“We can’t afford it”
Your organization’s annual budget is probably $5,000 to $15,000. A $20-30/month tool is 2-7% of that budget. Frame it against the venue rental: “We pay $150/month for the meeting room. We’re asking for $20/month for a tool that saves the treasurer an entire weekend every month.”
If the budget genuinely can’t absorb it, propose a trial period: “Let’s try it for three months. If it doesn’t save us time, we cancel.” Most evaluation frameworks for non-technical users include a trial period as standard advice.
“Can’t we just keep using what we have?”
Yes. But the question is whether “what we’ve got” is working. If the spreadsheet requires three people’s personal laptops, the payment tracking depends on one person’s memory, and the membership list has errors nobody catches, then what you have is a system held together by individual heroism. Heroism doesn’t scale and it doesn’t survive leadership changes.
“It’s too complicated to switch”
This is the objection that kills the most software proposals. And it’s worth taking seriously. Migration is real work. But frame the timeline: “Setup takes one afternoon. We import our member list from the spreadsheet, configure dues, and we’re collecting payments by next week. We run both systems in parallel for one month, then retire the spreadsheet.”
One afternoon of setup versus 360 hours of annual manual work. The math isn’t close.
Step 5: Present It in Under 10 Minutes
Your board meeting has a packed agenda. You won’t get 30 minutes to make this case. You’ll get 10, maybe 15. Here’s the structure.
Minutes 1-3: The problem. “Here’s what’s happening right now.” Use your list from Step 2. Name specific incidents. Keep it to three examples that the room will recognize.
Minutes 3-6: The cost. “Here’s what this is costing us.” Use your hours calculation from Step 1. Show the total annual volunteer time and what it’s worth. Then show the annual cost of the software. Let the gap speak for itself.
Minutes 6-8: The fix. “Here’s what changes.” Walk through the before/after from Step 3. Keep it concrete. “The treasurer goes from 4 hours/month to 30 minutes. Members pay online. The list updates automatically.”
Minutes 8-10: The ask. “I’m proposing we try [tool] for three months at [$X/month]. I’ll handle the setup. If it’s not working after three months, we cancel with no commitment.”
The three-month trial offer is critical. It removes the feeling of permanence from the decision. The board isn’t committing to software forever. They’re saying yes to a test. That’s a much easier yes.
The One-Page Summary
After your presentation, leave behind a one-page document. Not a slide deck. Not a proposal. One page.
Current situation: 3-4 sentences describing the problem. Specific examples.
Cost: Annual volunteer hours spent on manual admin. Dollar equivalent using Independent Sector’s valuation.
Proposed tool: Tool name, monthly cost, what it replaces.
What changes: Three bullet points on specific improvements.
Ask: Three-month trial at $X/month. You handle setup.
This page is what board members refer to when they discuss it after you leave the room. Make it clear enough that someone who wasn’t at the meeting can understand it.
After the Vote
If they say yes: set up the tool within a week. Don’t let momentum die. Import the member list, configure dues, and send the first automated reminder within the first week. Early wins build confidence. At the next board meeting, report: “We’ve collected $X in dues through the new system. The treasurer spent 30 minutes on admin this month instead of 4 hours.”
If they say no: ask why. If it’s budget, propose a cheaper option or a fundraiser to cover the cost. If it’s fear of change, offer to run a personal demo for the board members who are skeptical. If it’s “we need more time,” set a specific date to revisit: “Can we add this to the September agenda?”
If they table it: don’t let it die. Email the board chair the following week: “I’d like to put the software discussion back on the agenda for next month. Happy to do additional research if anyone had specific questions.”
Persistence isn’t pushiness. It’s caring enough about the organization to follow through. Your volunteers’ time is worth protecting. You just need to show the board the math.
Making the case is easier when you can show the results. Somiti offers a simple setup that lets your board see automated dues collection and member tracking in action, so the business case makes itself.