Why will you not publish a price?

Because we are pre-revenue and would be guessing. Publishing a number we then change twice would cost more trust than saying this plainly. Our first organisations set pricing with us, and we publish it after that.

Do you take a percentage of donations?

No. Card, wallet and ACH processing fees are charged by the payment processor and shown on every gift and payout. Beneora revenue comes from the subscription, not from your donors.

What happens to donor-covered fees?

If a donor elects to cover fees, the gift records the donor's intent, the fee actually charged and the resulting net separately. Your receipt reflects the deductible amount and your reconciliation reflects the deposit.

Is there a free tier?

No. A free tier for a system that holds receipting and reconciliation obligations would set the wrong expectation about support and durability.

What does the contract length look like?

Annual or monthly, and month-to-month for design partners. We would rather you be able to leave than be locked in while we are still earning the work.

Pricing

We charge for the system, not for your donors

Every fee your organisation pays should be legible on the page where the money is. That principle sets our pricing as much as it sets our reconciliation design.

Pricing principle
Processing fees are the processor's, and we show them
Beneora does not take a cut of your donations. Processor fees appear on every gift, in the payout that batches it, and in the net that reaches your bank — so your gross, fee and net always tie out.
Pricing principle
Seats are not the tax
Finance and programme staff who only need to look something up should not cost the same as a fundraiser running campaigns all day. Plans price on what an organisation operates, not on how many people glance at it.
Pricing principle
No implementation fee to be quoted separately
Migration and setup support is part of the plan for our early organisations. We are not funding a services business on the back of onboarding pain.
Pricing principle
You can leave with your data
Full export of donors, gifts, pledges, receipts and reconciliation history is a product feature, not a support request or an offboarding negotiation.

Plans

Priced on what you operate

Plan boundaries follow operational reality: a single entity running two streams has different obligations from a finance lead closing a month across five.

Design partner

Active build

Our first organisations, working with us while Release 1 quality gates are still being met.

Pricing being validated

Design partners help us set the number. In exchange: migration support, direct access to the product team, and month-to-month terms.

Everything in Core
Migration and setup support included
Direct product-team access
Month-to-month, no lock-in
Production SLA commitments

Core

Active build

One entity, one or two giving streams, 2–6 staff who touch giving.

Pricing being validated

Published once it is set with our first organisations, rather than guessed now.

Donation forms and checkout
Donors, households and recognition
Receipts and year-end statements
Recurring giving and pledges
Payout and deposit reconciliation
Funds and restrictions
Donor portal
Multi-entity consolidation
Custom domain white-label

Growth

Active build

Several giving streams, a finance lead who owns close, 6–30 staff.

Pricing being validated

Same principle: we publish the number when we can stand behind it under load.

Everything in Core
Close batches and accounting mappings
QuickBooks export boundary
Governed reports and metric traceability
Exception matching workspace
Approval workflow for acknowledgements
Audit trail across financial state
Multi-entity consolidation

Enterprise

Designed

Chapters, affiliates or a parent organisation consolidating several entities.

Not yet sold

The tenancy model exists and is exercised in the product, but we will not sell consolidation until Release 1 quality gates pass on a single entity.

Everything in Growth
Entity hierarchy and scoped roles
Consolidated and per-entity reporting
White-label custom domains

Not sure which side of a boundary you are on? The finance and operations walkthrough describes the close in enough detail to tell.

What we will not do

We would rather say the number is unset than set one we change twice

Beneora does not take a cut of your donations. Processor fees are the processor's, and every gift shows gross, fee and net.

Pricing principleDesign-partner pricing is being validated with our first organisations.

Pricing questions

Answered without hedging

Why will you not publish a price?: Because we are pre-revenue and would be guessing. Publishing a number we then change twice would cost more trust than saying this plainly. Our first organisations set pricing with us, and we publish it after that.
Do you take a percentage of donations?: No. Card, wallet and ACH processing fees are charged by the payment processor and shown on every gift and payout. Beneora revenue comes from the subscription, not from your donors.
What happens to donor-covered fees?: If a donor elects to cover fees, the gift records the donor's intent, the fee actually charged and the resulting net separately. Your receipt reflects the deductible amount and your reconciliation reflects the deposit.
Is there a free tier?: No. A free tier for a system that holds receipting and reconciliation obligations would set the wrong expectation about support and durability.
What does the contract length look like?: Annual or monthly, and month-to-month for design partners. We would rather you be able to leave than be locked in while we are still earning the work.

Design-partner program

Build the donor-operations layer with us

We are working with a small number of US and Canadian nonprofits who feel the reconciliation and donor-data pain most acutely. Partners shape the sequence, see the honest status of every module, and are never charged for a capability that is still a prototype.

Join the design-partner program Compare the category