Product roadmap
Published so you can hold us to it
This page is generated from the same scope map the product team works against, so it cannot drift into marketing language without the roadmap changing first.
Design-partner program · Core donor operations in active build
Beneora is being built with a small group of US and Canadian nonprofits. Product surfaces you see on this site exist in the application; the status label on each one tells you whether it runs on real data yet.
Roadmap band
Now — Release 1
The contribution lifecycle has to hold end to end before anything else earns attention. These items are the definition of done for our first release.
Tenant isolation, authentication, roles, permissions, audit
Foundation for every other item
Organization onboarding and verification
First-run path into the product
Branded donation forms and checkout
Where money enters
Cards, wallets, ACH; one-time and recurring
Requires a real processor boundary
Donors, households, organizations, relationships, duplicates
The donor record of truth
Legal donor, payer, recognition, soft-credit model
Correctness buyers audit us on
Pledges, installments, failed payments, amendments
Committed revenue lifecycle
Receipts, year-end statements, refunds and disputes
Compliance-critical
Campaigns, funds, designations and restrictions
Where each dollar is allowed to go
Processor transaction → fee → payout → bank deposit reconciliation
The core finance differentiator
Donor self-service for giving, recurring, pledges, receipts
Removes staff hours directly
Search, filters, governed reports, import/export/migration
Switching cost in both directions
QuickBooks integration boundary
Boundary and exceptions, not a ledger
Pennifi-derived contextual processes and global components
Interaction system consistency
Responsive, accessible, secure, privacy-respecting UX
Non-negotiable quality floor
Transparent pricing, support and operational health
Commercial trust
Roadmap band
Next — Release 2
Real demand, deliberately queued behind Release 1 quality gates. We will not start these while a lifecycle step is still unreliable.
Peer-to-peer fundraising
Prototype exists; hold depth
Events and ticketing
Prototype exists; hold depth
Email and SMS engagement
Provider boundary not built
DAF and stock workflows
Manual-entry depth only
Advanced recurring recovery
Basic recovery is Release 1
Basic impact updates
One donor-visible update path only
Company matching
Queue exists; no clearing
Custom domains
White-label prototype exists
Advanced reporting
Governed reports are Release 1
Governed AI proposals
Proposal-only, never autonomous
Key CRM and accounting integrations
Beyond the QuickBooks boundary
Roadmap band
Later — architecture-ready, not production priority
Some of these exist in the product as clearly labelled prototypes. They are not receiving production-depth work and must not be read as shipped.
Global donor marketplace
Discovery and checkout demo
Personal crowdfunding
Not started
Fundraising workforce marketplace
Briefs/talent/proposals demo
WhatsApp and social inbox
Omnichannel demo on seeded connections
Advanced impact ledger
Evidence and methodology demo
Grantmaker portfolio
Company-side demo
International tax treatment
US/CA only for Release 1
Multi-region payments
Single-region for Release 1
Advanced geo operations
Coverage/disaster/delivery demo
Agent marketplace
Agent centre demo only
Roadmap band
Not planned
Saying no in public is part of the product. These are not on the path unless something fundamental changes about who we serve.
Every social-network connector
Capability-honest subset only
Global freelancer liquidity and escrow
Out of the money path
Tax and legal logic for many countries
Compliance surface too wide
Delivery and logistics platform
Not donor operations
Full grant-management replacement
Adjacent product
Native general ledger or accounting suite
We integrate, we do not post
Autonomous high-impact AI actions
Human approval is a control
Beneficiary case management
Different buyer and privacy regime
Broad ESG attribution
Not the nonprofit buyer's problem
Unrelated CMS, project management, HR or ERP features
Scope dilution
Capability status
Where each capability actually stands
Roadmap bands describe intent. This table describes build reality, and it is the same source the rest of the site reads from.
| Capability | Status | Note |
|---|---|---|
| Accounts, roles and tenant isolation | Active build | Accounts, profiles, roles and organization records persist. Scoping rules are being hardened. |
| Branded donation forms and checkout | Prototype | Form builder and donor checkout are interactive with illustrative data. |
| Cards, wallets and ACH processing | Designed | Processor boundary is specified. No live money movement yet. |
| Donors, households, recognition and soft credits | Prototype | The full data model is implemented in the product against seeded records. |
| Pledges, installments and recurring recovery | Prototype | Lifecycles, amendments and failure paths are modelled and navigable. |
| Receipts and year-end statements | Prototype | Versioning and audit behaviour modelled. Not a tax-compliance guarantee. |
| Transaction → fee → payout → deposit reconciliation | Prototype | The matching workspace and exception queue are the deepest prototype in the product. |
| Funds, designations and restrictions | Prototype | Restriction tracking and allocation are modelled end to end. |
| Fulfillment and impact evidence | Prototype | Evidence chain links gifts to recorded outcomes with an immutable trail. |
| Donor self-service portal | Prototype | Giving history, recurring management, pledges and receipts are navigable. |
| QuickBooks integration boundary | Designed | Mapping model is specified. The connector is not built. |
| Governed AI proposals | Prototype | Every proposal carries sources, confidence and human approval. No autonomous action. |
| Email, SMS and social channels | Prototype | Release 2. Channel capabilities are declared per provider; unsupported replies are blocked. |
| CRM and data exchange | Designed | Import, export and mapped migration are specified for donors, gifts, pledges and funds. No vendor-specific sync connector is built. |
| Geo intelligence and fraud signals | Prototype | Provider-agnostic adapters exist behind a demo provider. No paid provider is connected. |
| Donor marketplace and services marketplace | Paused | Later-tier prototypes. Contained in the product and not marketed as shipped. |
Shipped changes are recorded on the changelog.
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.