Design-partner program · Core donor operations in active build

See the roadmap
Skip to content
Beneora

Changelog

Dated, attributed to a surface, status attached

We publish changes to prototypes as well as to core workflows, because hiding prototype work is how a roadmap starts lying.

  1. Scope governance

    Product Constitution applied across the product

    Active build

    Every route in the application is now classified against the constitution, and later-stage prototypes are contained in navigation rather than presented alongside core workflows.

    • Added an internal Product Direction area: north star, roadmap bands, quality gates, decision gate and scope audit.
    • Prototype and duplicate surfaces now carry an honesty strip describing their real status.
    • Marketplace, workforce, social, advanced geographic and grantmaker areas are hidden from primary navigation by default.
    • Added a core-journey verification board tracking Built, Persisted, Integrated, Permissioned, Error-handled, Responsive and Verified per step.

  2. Engagement

    Provider-agnostic channel layer

    Prototype

    Channel capability is now declared per connection, so the composer refuses to promise a reply or a publish action a channel cannot actually perform.

    • Unified inbox across website, email, SMS and social conversations.
    • Capability gate resolves reply ability from the connection rather than the channel type.
    • Community and moderation queues built on the shared resource surface.

  3. Platform foundation

    Identity spine on real persistence

    Active build

    Sign-in, sign-up, onboarding and invitations now write to and read from the database rather than in-memory demo state.

    • Profiles, roles, tenants and organisations persisted with row-level authorisation.
    • Google sign-in alongside email and password.
    • Invitation tokens validated against real records instead of demo fixtures.
    • Route-level audit harness scoring every application route against twelve platform dimensions.

  4. Experience architecture

    Universal resource surface

    Active build

    Collections across the product share one contract: list and grid parity, a quick panel for triage, a full detail route, and create and edit through panels rather than dialogs.

    • Shared search, filter, row and card components with identical data in both densities.
    • Level-one quick panels for triage and level-two panels for nested work.
    • Dialogs reduced to destructive confirmation only.

  5. Finance and intelligence

    Reconciliation workspace and governed proposals

    Prototype

    Deposit matching, exception handling and fee breakdowns landed as a workspace, with AI restricted to proposals carrying sources and confidence.

    • Payout to bank-deposit matching with gross, fee and net breakdown.
    • Exception queue for partial and unmatched deposits.
    • Agent proposals require evidence, an approval threshold and an undo path.

What is coming, and what we have declined, is on the product roadmap.

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 programSee the roadmap