Price the work your organization actually needs.
Start with a shared list of requirements before comparing starting prices. A volunteer-run club collecting annual dues, a community center enrolling families in classes and a membership nonprofit running events may need different configurations. Give each provider the same description of your people, activities and busiest day.
Ask what the provider counts when pricing the plan. Members, households, contacts, staff users, locations and transactions can describe different things. Record the applicable definition and any limit or charge that affects your proposed setup.
Separate the subscription from the other cost lines.
Ask for a written scope that identifies included capabilities, optional services and charges paid to other providers. A lower subscription does not settle the comparison if a required workflow needs an additional service. Equally, an optional website project should not be treated as a mandatory platform charge.
| Cost line | What to confirm | When to budget for it |
|---|---|---|
| Platform subscription | The agreed configuration, billing cadence, included usage and the terms for changes. | The comparison period, then each renewal period. |
| Payment processing | Available methods, percentage and fixed charges, settlement and exception costs that apply. | As applicable to your payment volume and methods. |
| Setup and migration services | What the provider will configure or import, what you must prepare and any separately quoted work. | The initial move, plus later projects only if needed. |
| Website and email | Whether you will retain existing services or choose a separately scoped design, hosting or email service. | A project cost, recurring service cost or both. |
| Equipment and integrations | Required devices, compatibility, subscriptions and responsibility for ongoing support. | Initial purchases and any recurring third-party charges. |
| Support and additional work | Included help, support channels and how work outside the agreed scope is priced. | Included in the plan or separately quoted when applicable. |
Assign each charge to one cost line and one provider. Mark an included item as included rather than adding its value to the total again.
Compare payment costs using the same assumptions.
Use your own expected payment totals and transaction counts. Separate the methods your members use, then apply the written terms for each supported method. Confirm whether a quoted charge belongs to the platform, payment processor or another service, and whether it is already included elsewhere.
For a quote with both percentage and per-transaction components, calculate those components separately: the relevant processed amount multiplied by the quoted percentage, plus the relevant transaction count multiplied by the quoted fixed amount. Add other applicable charges only when the quote identifies them. Use the same assumptions for each option.
Ask how refunds, disputed payments, failed payments and recorded offline payments affect the cost and reconciliation process. The member’s payment experience and the treasurer’s ability to explain the result belong in the demonstration alongside the fee discussion.
Build a first-year and recurring cost worksheet.
Print a copy for each option and fill it in from the written scope. Use a consistent twelve-month period. If you are comparing monthly billing with annual billing, calculate the monthly option across that period rather than adding a monthly and annual price together.
Keep an unknown amount visible as an open question. A blank line is not evidence that the cost is zero. Record optional projects separately so the board can see the required operating cost and decide whether it also wants the additional work.
| Budget line | How to record it | Amount from your quote |
|---|---|---|
| Subscription for the comparison period | The agreed billing amount multiplied by the number of billing periods. | ________ |
| One-time provider services | Required setup, agreed migration and other initial project work. | ________ |
| Required ongoing services | Services and integrations you will pay for during the period, excluding items already counted. | ________ |
| Required equipment | New purchases for the proposed setup, excluding equipment you will retain. | ________ |
| Estimated payment costs | The method-specific calculation using your recorded volume assumptions. | ________ |
| Other applicable charges | Only separately identified charges or taxes that apply to the quote. | ________ |
| First-year external cost | Add the applicable lines above once each. | ________ |
| Ongoing annual external cost | Use recurring lines for a later year. Remove one-time work and purchases, then account for any stated renewal changes. | ________ |
Keep the first-year total and ongoing total separate. They answer different questions about affordability and the commitment after launch.
Give preparation and team time their own place.
Moving a platform also takes work inside your organization. Someone needs to clean up household records, review membership categories, reconcile balances, prepare member communication and help staff rehearse. Record those responsibilities even when volunteers do the work and no new invoice is involved.
Estimate hours from your own tasks and available people. Keep those hours alongside the external cost worksheet. If you budget for paid implementation time, explain the rate and whether it represents additional spending or time already covered by an existing salary. Count the same work once.
A provider’s import service and your team’s data review can be separate responsibilities. Confirm which records can move, which require preparation and how the first and final imports will be checked. Do not assume that documents, stored payment credentials, historical transactions or every relationship will transfer simply because a member list can be exported.
Compare the complete decision, not only the total.
Put the demonstrated workflow fit beside the first-year cost, ongoing cost and preparation plan. A quote is easier to assess when the board can see what the team will receive, which systems remain and who owns the handoff. Keep requirements that were not demonstrated visible until they are resolved.
Review current plan details and the written terms before making a decision. If you expect savings, use your own measured task volumes and actual costs, state the assumptions and keep projected savings separate from the price you will pay.
A useful budget explains the scope, timing and responsibility behind the amount. That is what lets the next board member understand the decision too.
