Design-partner program · Core donor operations in active build

See the roadmap
Skip to content
Beneora

About

We are building the layer nobody owns

Every part of nonprofit fundraising has software. The joins between those parts — the place where a gift becomes a donor record, a deposit, a restriction and a demonstrated result — belong to a person with a spreadsheet. That is the thing we are building.

Beneora is pre-production. We are working with a small group of design partners and we publish the honest status of every module rather than a launch date we cannot keep.

Last updated March 1, 2026

Design partners

We would rather be corrected early

If your reconciliation, receipting or recurring programme does not fit what we have described, that is the conversation we want.

Where does the work hurt today?

No mailbox integration yet — submission shows a local confirmation and tells you what to do next.

Why this, and why now

Online giving made taking money easy and made reconciling it harder. A single gift now touches a form, a processor, a CRM, a bank and an accounting package, and none of them is responsible for the whole. The cost of that gap lands on the smallest teams: two or three people doing donor operations, finance and reporting between them.

The organizations we build for are past a donation widget and unwilling to accept an enterprise implementation. They do not need more features. They need the joins to hold.

How we decide what to build

We keep a written product constitution with a north star, a defined ideal customer, a four-tier roadmap and a ten-question decision gate that every proposed feature must pass. Anything that does not strengthen the contribution lifecycle, reduce workload or improve financial truth is filed as Later.

That document is not marketing. It governs the application: capabilities outside Release 1 are contained in navigation and labelled as prototypes in the product itself.

How we talk about status

  • Available means persisted, permissioned, error-handled and verified end to end.
  • Prototype means interactive with illustrative data. It is not production software.
  • Designed means specified and drawn, with no implementation.
  • Paused means deliberately not being worked on while Release 1 quality gates are open.

What we will not build

  • A general ledger or accounting suite.
  • A grant-management replacement.
  • Beneficiary case management or any store of beneficiary personal data.
  • Autonomous AI that takes financial or donor-facing action.
  • A data business built on donor records.

Something here unclear, or a claim you think we cannot support? Tell us — correcting this page is cheaper than defending it.