Transactional email usage
Email costs should follow actual sending, not hidden plan gates.
Sapling uses email for receipts, event communication, stewardship, donor notices, and operational workflows. Sending volume has real infrastructure and deliverability cost, so it belongs in a visible usage line.
What counts as sending?
The goal is simple: a small organization should not pay like a large sender, and a large sender should be able to understand what its communication volume costs.
Gift receipts and tax acknowledgment emails
Refund, correction, and transaction notices
Event confirmations, reminders, and follow-ups
Stewardship updates and segmented donor communication
Operational notifications tied to CRM workflows
Why separate email from base CRM?
It keeps base pricing fair. Teams that send a few receipts and updates should not subsidize high-volume senders, and teams with larger programs should be able to plan sending volume without surprise feature gates.