CRM KitsNonprofits
Every pledge. Accounted for.
Start with the campaign. Cause puts a wide progress bar of recorded pledges against a recorded goal across the top of a white page, the donors inside each campaign underneath it, and the recorded volunteer shifts beside them. Black text, thin gray rules, gold bars, tabular figures.
Open with the number you read out loud.
Every recorded campaign is a full-width card: a progress bar of recorded pledges against the recorded goal reference, the recorded pledge count, the recorded end date, and a donor journey strip counting the people involved by their recorded stage.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Campaign progress board with derived progress bars and donor journey strips
- Selected-campaign panel pairing the donor list with recorded volunteer shifts
- Donor relationships, campaign register, recorded pledges and volunteers views
- Recorded shifts grouped by week with needed and filled counts
- Insights drawn only from recorded workspace data
- White and gold Cause application frame with full CRM tools
four pipelines
- Donor cultivation · 8 stages
- Campaign pledges · 7 stages
- Volunteer onboarding · 7 stages
- Grants and partnerships · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- First gift thank-you task
- Pledge reminder task
- Lapsed donor outreach
- Major donor meeting prep note
- Campaign kickoff note
- Campaign close follow-up
- Volunteer welcome task
- Shift reminder task
- Grant report due task
Inactive until you review and publish them. None send customer messages.
Sample workspace
Explore fourteen fictional donor records across five recorded journey stages, thirteen recorded pledges, three campaigns with recorded progress and eight recorded volunteer shifts in the separate sample view. Example edits stay in the current page’s memory and reset on navigation or reload; sample records are never inserted into your CRM.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set organization name, descriptor, and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original Cause helper is required for connected creation, editing, campaign references and starter setup. It preserves native account permissions and unrelated custom fields, and checks the current record state and a server-owned revision before saving. Deploy it from your authoritative backend source before connected edits. Pipeline presets and workflow drafts remain optional.
A donor relationship is a native contact-linked opportunity with namespaced details: recorded journey stage, household or organization label, up to eight giving interest labels, steward label, last gift date and reference amount, next touch date and note, pledges as child records, and volunteer shifts as child records. Campaigns are separate account-level reference rows with their own recorded goal, currency and end date. Other custom fields are preserved.
Every amount is a recorded reference. The kit processes no payment, hosts no donation form, issues no tax receipt or acknowledgement, posts to no ledger and tracks no restricted fund. Campaign progress is recorded pledges divided by the recorded goal, counting only pledges whose donor record shares the campaign currency; pledges in another currency are counted separately rather than converted, and a pledge label that matches no recorded campaign is listed under its own heading rather than dropped. Shift rows are recorded counts, not a roster: nothing is scheduled, assigned, reminded or tracked for credit, and a shift recorded on several donor records is grouped into one. The recorded donor journey stage is a staff label, separate from the native pipeline stage, and the kit adds no stage automation. The grants pipeline records status only.
Four optional pipeline templates and nine inactive workflow drafts. Fourteen fictional in-memory donor records, thirteen pledges and eight shifts.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Get the Nonprofit Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 270 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
How do I receive the kit?
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?
Cause keeps its nonprofit navigation across the original views and native CRM modules. Full CRM tools remain available within the same signed-in account and application theme. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
More hospitality, events & creative kits
Browse all 220 kits
