People & relationships
Individuals, households, organizations and sponsor representatives, with reviewed duplicate matching and merge history.
One supporter record.
A much fuller story.
A donor CRM being built around the way nonprofits work: people, gifts, volunteers and events, with the context to connect them.
Remember more than the last gift.
Giving history belongs alongside the hours someone volunteered, the fundraiser they attended and the conversation your team wants to remember.
Keep households, organizations and individual legal donors clear while building one useful view of the relationship.
Givesmith · Product prototype
Actual prototype screen · Fictional demonstration data
The everyday work of looking after generosity.
These are the donor-management capabilities we’re building toward. The demo currently illustrates selected workflows using sample data.
Gifts, pledges & recurring giving
Cash and check entry, received installments, open commitments, split allocations and processor reconciliation.
Tributes & memorials
Keep the donor, honoree and notification recipient distinct. Preserve the personal meaning behind a gift.
Funds, campaigns & appeals
Track what the gift supports, the fundraising initiative and the solicitation that prompted it.
Acknowledgments & statements
A thank-you queue, reviewed benefit values, versioned receipts and accurate year-end giving statements.
Reports that answer real questions
Giving totals, donor retention, lapsed supporters, campaign progress and useful exports for your team.
Connected by the person.
Clear about the details.
Your nonprofit’s supporter record will connect enabled products within your organization. Gifts, volunteer activity and event transactions keep their own source and meaning.
WhoCanBeThere
Planned shared supporter identityA shift signed up for, an event attended and approved hours served. See the difference between someone planning to help and actually giving their time.
AnyRegistration
Planned shared supporter identityTicket purchases, sponsor packages, included guests and event attendance. Keep the purchaser, guest and legal donor connected without confusing them.
VolunteerReminder
Planned shared supporter identityUseful reminder activity and communication preferences, with the controls to avoid turning every delivery event into clutter.
A gift recorded with care.
Fast entry for received gifts, with a live acknowledgment preview and a separate fair market value for benefits provided.
The prototype lets you explore tribute gifts and in-kind descriptions. It records browser-local sample entries without charging cards or sending messages.
Try gift entryGivesmith · Product prototype
Actual prototype screen · Fictional demonstration data
Open to your team.
And your AI assistant.
We’re planning a scoped API and MCP server so staff can look up a supporter, find lapsed donors and prepare thoughtful follow-up from connected records.
Permissions, source links, audit history and review of write actions belong in the application. An assistant does not get a shortcut around them.
Planned workflow · Not connected in the demo
Help me prepare a thank-you for Eleanor’s latest gift.
Find the gift. Check its purpose and benefit information. Prepare a draft with links to the underlying records.
Let a staff member review before anything is sent.
Assistant compatibility will be verified during implementation.Let a staff member review before anything is sent.
Moving from DonorPerfect or GiveSmart?
That is the replacement we’re building toward. Migration means checking the history, balances and workflows—not simply moving a list of names.
Prove the history before the switch.
Map gifts, funds, pledges, acknowledgments and event balances. Reconcile totals and review difficult records with your staff before a cutover.
Keep the next fundraiser running.
Validate the event tools your team actually uses, including auctions and checkout. Retire the old systems only after those required workflows pass acceptance.
Get to know the people behind the giving.
Take a look around the Givesmith prototype.