The platform decision is infrastructure, not procurement: the organization choosing where its campaigns live is choosing its donor experience, its data's home, its fee structure across years, and — more than most boards realize — its fundraising ceiling, because the tools available shape what campaigns are even possible. And yet most organizations choose by inertia (whatever the last campaign used) or by a single headline number (the fee). This guide is the diligence framework — the four tests, the questions that sort any field, and the honest disclosure that we are a platform writing about choosing platforms: the framework below is exactly the one we built ChaiRaiser to win, and you should run it on us as skeptically as on anyone.
Test one: the money test
Beyond the fee anatomy — which you should run first and on real numbers — the money test asks three structural questions. Whose rails does the money ride? The pledge-versus-charge architecture decides whether funds flow through the platform's hands or your community's own arrangements — with everything that implies for control, timing, and trust. What does the donor's checkout serve? Run a test gift and watch: tip defaults, upsells, data harvesting, extra screens — the checkout is where a platform's real customer is revealed. And what happens to the pledge that isn't instant? The follow-through infrastructure — ledger, reminders, the pledge-to-paid machinery — is where communal campaigns win or leak; a platform with no answer here is pricing you for the decay.
Test two: the tools test
The fee differential between platforms is a rounding error next to the tools' effect on totals — so test the toolset against the campaigns you actually run. The participation engines: does the platform have an answer for the middle of your pyramid — the games and wheels that lift completion and average gifts, or just a form with amount buttons? The communal formats: teams and leaderboards for your natural tribes, the matching mechanics with real windows and public accounting, the phone-room tooling if your campaigns run on callers. The organizer's cockpit: the live board, the update stream, the analytics that tell you which ring is alive — campaign steering requires instruments. And the honesty architecture where games ride: sealed outcomes, single entries, the free entry path — because a platform's game layer is either built on structure or on hope, and your organization's name goes on whichever it is.
Choose the platform the way you'd choose a beis medrash building: the rent matters, but the question is whether the structure can hold what you're planning to build in it.
Test three: the community-fit test
The test most frameworks skip and frum organizations can't afford to. Does the platform speak the community's calendar? Campaigns that understand Shabbos and Yom Tov (the pledge model's whole logic), Hebrew where your donors need it, the seasonal genres — Tishrei appeals, maos chitim — as first-class shapes rather than exotic requests. Does it respect the community's dignity norms? The discretion architectures for sensitive genres, anonymity handled properly, copy rails that keep campaigns honest — the platform's defaults become your campaigns' manners. Does its game layer fit the community's register? Donation games built from the community's own culture (the dreidel, the pushke, the auction table) land differently than slot-parlor imports — and your board will feel the difference before they can name it. And who answers when the gabbai calls? Support that understands "the campaign must close before candle-lighting" is community fit in its most practical form.
Test four: the years test
Platforms are annual relationships compounding; evaluate the trajectory, not the demo. The data question: your donor history, pledge records, and campaign learnings accrue somewhere — confirm they accrue to YOU (exportable, yours) rather than becoming the platform's leverage. The pricing legibility question: can the treasurer explain the cost model at the annual meeting in one sentence, and will that sentence still be true next year? Published flat models pass; negotiated opacity fails. The roadmap question: is the platform building for organizations like yours — the features shipped last year tell you more than the sales deck's next year. And the exit question, asked without embarrassment: if you leave in three years, what leaves with you? A platform confident in its answer ("your data, your donor list, your records — we keep you by being good") is displaying exactly the incentive alignment the whole relationship rests on.
Running the decision
The practical sequence for a board doing this properly. Shortlist by the four tests on paper (an afternoon with each platform's public pages — the ones that hide fee terms or game rules have answered early). Test-drive the reality: a real trial campaign or at minimum the full donor-and-organizer walkthrough — the launch checklist's real-phone test applied to the choosing itself. Reference the peers: two calls to organizations your size on each finalist — "what surprised you in year two?" is the single highest-yield diligence question that exists. And decide with the annual calendar in view: the platform serves the whole year's portfolio — the annual campaign, the seasonal moments, the standing funds — and the right choice is the one whose toolset maps to your actual calendar, not to the one impressive demo. Then hold the winner to its own pitch: the fee on the receipts, the tools in the campaigns, the support when the gabbai calls — infrastructure earns its place annually, ours included.
Frequently asked questions
Should a small organization choose differently than a large one?
The tests are identical; the weights shift: small organizations should over-weight the built-in follow-up rails and volunteer-proof tooling (the office they don't have), while large ones over-weight data ownership and the annual-calendar fit. The fee test matters least at both ends — tools move totals more than points move costs.
Is a general-market platform with a big brand safer than a community-built one?
Safer against vendor failure, weaker against every community-fit test — the calendar, the dignity norms, the pledge culture, the game register. The honest framing: the general platform treats your community as a segment; the community platform treats it as the spec. Run the four tests and let them decide.
How many platforms should an organization actually use?
One, deliberately — the data, the donor experience, and the annual learnings compound only when they accrue in one place. The exception is a transition year run as exactly that: a decided migration with an end date, not a permanent hedge.
What's the single fastest disqualifier when evaluating?
Opacity anywhere money moves: the fee terms that require a sales call, the checkout with engineered tips, the game rules that don't exist on a page. A platform's transparency habits are set long before you arrive — and they are exactly what your donors will experience wearing your organization's name.