Essay · Fundraising · Systems

Your giving platform is a stewardship decision.

The right tool should care for the person making the gift—and the people doing the work after it.

By

A giving platform looks like a technology decision. Compare the fees. Watch the demo. Check whether it connects to the software you already use. Pick one.

But that decision reaches further than the giving form. It shapes how someone participates in your mission, how your team cares for that person, and how faithfully you account for the resources entrusted to you.

At AUSTEROM, I put together a practical guide on how to choose a giving platform, including the platforms I would shortlist for churches and nonprofits. Here, I want to spend more time on the leadership question underneath that comparison: what are we actually asking this tool to carry?

What should a church look for in a giving platform?

Look for a platform that your congregation can give through easily and your team can manage reliably. Start with your current problems, then evaluate mobile giving, recurring gifts, donor records, financial reporting, total cost, and the work involved in switching. Test the whole journey—from a gift to the bank deposit—not just the checkout screen.

The same principle applies to nonprofits. The best choice is not necessarily the platform with the longest feature list. It is the one that fits the relationships you are building and the people responsible for sustaining them.

Start with a problem, not a product.

Before you book a demo, ask your team where the current process breaks down. Are people struggling to give on their phones? Is updating a recurring gift confusing? Does someone spend every Monday repairing records or matching deposits?

Those are different problems. A better checkout might help with the first. It will not automatically solve the last. Write down the three problems that matter most, and use them to guide every vendor conversation.

Then ask a harder question: is this a limitation of the platform, or a decision our organization has not made? If no one owns donor follow-up, a new tool will not appoint that person. If fund names mean different things to development and finance, an integration will not resolve that disagreement for you.

Sometimes the next step is new software. Sometimes it is getting the right people in a room and making the decisions you have been asking software to make.

The giving experience is part of hospitality.

Imagine someone giving to your church for the first time. They are not evaluating your technology stack. They are deciding whether they can confidently participate in something they care about.

Can they find the giving page? Is it clear where their gift will go? Do they know whether they selected a one-time or recurring gift? Can they find a receipt, update a payment method, or get help without having to start over?

In my essay on hospitality and systems, I wrote that people do not experience your intentions. They experience your systems. A giving form is one of those systems. So is the message after the gift, and the response when something goes wrong.

Test the experience with someone who did not configure it. Let them use their own phone. Watch where they hesitate. Their questions may tell you more than another presentation.

Follow the gift all the way to the books.

A gift appearing in your donor database does not mean your accounting process is complete. Your donor record needs to tell the story of a person's support. Your books need to explain the movement of money. Those are connected responsibilities, but they are not interchangeable.

Bring the person who reconciles deposits into the evaluation. Ask the vendor to walk through a sample gift, its processing fee, the payout containing it, and the report your team will use to match that payout to the bank.

  • Can you connect an individual gift to its transaction and payout?
  • Are fees, designated funds, refunds, and exceptions understandable?
  • What happens when records fail to sync, and who notices?
  • Can your team complete the process without a spreadsheet only one person understands?

This is where a polished demo has to become a workable process. The person closing the books should not discover the limitations after the contract is signed.

Recurring giving is a relationship, not a setting.

Recurring support deserves particular care. Someone has chosen to make giving an ongoing part of their life. How easy is it to change the amount, update a card, or understand why a payment failed? Who follows up, and what does that communication feel like?

If you are switching platforms, do not assume recurring gifts will move with you. Ask for written confirmation of what can transfer, what requires a donor's authorization, and what your team must communicate. Plan for that work before announcing a launch date.

A migration plan is also a care plan. It should protect continuity and make the next step clear for the people whose generosity supports your work.

Choose for the team you actually have.

A volunteer treasurer and a staffed finance department do not have the same capacity, even if their churches have similar attendance. A tool that fits one team may create unnecessary work for another.

Compare more than processing rates. Include subscriptions, integrations, implementation, support, and staff time. Ask who will own the platform after launch, who can cover for that person, and how much training they will need.

Apply the same discipline to AI features. Ask for a demonstration of a real task. Can the team verify the answer against the underlying records? Do permissions still apply? What happens to donor information? A compelling answer is not a substitute for an accountable process.

Build a shortlist. Then prove the fit.

In the AUSTEROM guide, Fundraise Up is a frequent starting recommendation for nonprofits. For churches, Overflow and Tithely often belong on the shortlist, with Planning Center Giving worth evaluating when Planning Center already anchors your operations. Those are starting points, not a universal ranking.

Read the full AUSTEROM giving-platform guide for the platform-specific considerations, integration questions, and reconciliation checks. Then ask your shortlisted providers to demonstrate your priorities—not only their favorite features.

Before you sign, make sure your team can explain five things: how someone gives, how you care for them afterward, how the money reaches the books, who owns the process, and what switching will require.

Choose the system that helps you care for what has been entrusted to you.

A giving platform cannot create a culture of generosity for you. But choosing and running one thoughtfully is part of making your organization worthy of the generosity it receives.

A useful next step

Get clear on the work behind the gift.

If the challenge goes beyond choosing software, let's talk about the donor relationships, decisions, and systems underneath it.

Start a conversation →