Pricing and Packaging
Start with HeartBeat. Expand only where donor work needs capacity.
DonorOps pricing is organized around the operating architecture: HeartBeat for governed donor context, Pulse Packs for modular capabilities, and Pulse Companion for governed AI work under your rules.
HeartBeat holds the context
Pulse Packs add the capability
Pulse Companion moves the work
The commercial path should mirror the migration path: connect what you have, consolidate the work, and replace what no longer needs to stay in the donor stack.
Packaging Model
Three parts. One governed donor operating system.
This page is intentionally a packaging overview, not a fixed-price calculator. It gives buyers a clear way to understand what they are buying before a scope review.
HeartBeat
The secure donor operating core where donor context, relationship memory, permissions, workflow state, and AI action history become durable.
Donor and household context
Source lineage and migration mapping
Permission-aware operating memory
Foundation for every Pack and Pulse Companion
Pulse Packs
Modular donor-operation capabilities that replace disconnected reports, trackers, workflows, and manual prep one function at a time.
Board-ready reporting
Stewardship workflows
Grant and opportunity tracking
Relationship intelligence and prioritization
Pulse Companion
Governed AI workers that prepare, analyze, draft, and recommend using approved HeartBeat context and approved tools.
Donor brief preparation
Follow-up and stewardship drafts
Portfolio review support
Human review and action boundaries
Migration scope
Which systems need to connect, which sources need cleanup, and which workflows need a replacement path.
Capability scope
Which Pulse Packs create the first measurable displacement event instead of adding another tool.
Governance scope
Which Pulse Companion permissions, approvals, and audit evidence are required before AI moves donor work.
Pricing FAQ
Does DonorOps publish exact pricing?
This overview explains the packaging model. Exact pricing depends on migration scope, systems connected, Pulse Packs activated, and Pulse Companion governance needs.
Can DonorOps replace tools we already pay for?
Yes, that is the intended destination where it makes operational sense. The migration path starts by connecting current systems, then consolidates donor work, then replaces tools that no longer need to stay in the stack.
What is the first package most nonprofits start with?
Most teams start with HeartBeat because durable donor context, permissions, and relationship memory are the foundation for every Pack and Pulse Companion.