Local / Desktop reference architectureDonor operations
A Local / Desktop reference architecture for donor operations in Nonprofit. Triggered by new donation or donor interaction, Padiso orchestrates 3 specialist agents on Claude Code + Ollama, on your machines, reaching donor crm (salesforce nonprofit success pack) and your tools through the Model Context Protocol, with budgets, approvals and an audit trail throughout.
Local / DesktopRuntime: Claude Code + Ollama, on your machinesTrigger
New donation or donor interaction
Nonprofit
Orchestration
Padiso Orchestrator
goals · tasks · heartbeat
Governance
budgets · approvals · audit
Runtime & agents
Agent runtime
Claude Code + Ollama, on your machines
Donor ops agent
agent
Grants agent
agent
Comms agent
agent
Integrations · MCP
MCP gateway
Your systems
Donor CRM (Salesforce Nonprofit Success Pack)
Payments
How the data flows
Trigger: New donation or donor interaction
- 1
Donor-ops agent records the gift, issues the receipt and updates the donor record
- 2
It schedules and drafts personalized follow-ups
- 3
Flags major gifts for the development lead
- 4
Acknowledgement sends after a quick human check
Agent team
- Donor ops agent
- Grants agent
- Comms agent
Integrations
Reached through the Model Context Protocol, scoped and governed.
Runtime & data
Claude Code + Ollama, on your machines
Donor CRM (Salesforce Nonprofit Success Pack)
Payments
Security & operational considerations
- Donor PII handled per policy
- Approvals on major-gift outreach
- Receipts retained for compliance
Local / Desktop deployment
Self-hosted: agents and models run on your machines, so regulated data and credentials never leave your network. Best when data residency is non-negotiable.
Run this blueprint anywhere
More Nonprofit blueprints
Run your business on agents.
Start free, or talk to us about putting an agent workforce to work across your operations.