Before you buy another platform, look at the computer nobody has switched on for six months.
It might be useful.
Not magical. Useful.
A modest machine can be a place to learn, test an application, and discover what your organization actually needs. Whether 6–8 GB of RAM is enough depends on the operating system, the application, and everything else competing for memory.
That is a starting question. It is not a production guarantee.
A lab is not your donor system
The safest first project does not contain real donor records.
It contains a few invented contacts, a sample campaign, and a checklist you can repeat.
There is no award for discovering your backup problem with the only copy of your fundraising history.
Start with one job
Do not begin with “replace everything.”
Begin with a job someone can describe:
- Record a sample contact.
- Record a sample interaction.
- Find that contact again.
- Export the sample records.
- Back up the application data.
- Restore it into a disposable test setup.
If the tool cannot do the actual job, a dashboard full of features will not rescue it.
CiviCRM is one example of nonprofit-oriented software released under the AGPLv3 license.1 That gives the project a concrete licensing basis to examine. It does not mean every extension, hosting arrangement, or support service is free.
Read the license. Read the requirements. Test the workflow.
A mail platform is not free email delivery
Running a mailing application and delivering messages are separate tasks.
Your setup may still need a delivery service, DNS configuration, consent records, unsubscribe handling, and an administrator who can investigate failures.
Likewise, a CRM can organize donor prospects without granting access to a proprietary wealth-screening database. A database you control is not a license to somebody else’s data.
The honest course explains those boundaries before asking you to connect a real account.
Volunteers need a handoff, not a heroic rescue
A volunteer who wants development experience can help build the lab.
Give them a defined project, sample data, a named reviewer, and a place to document decisions. Do not make a personal account the organization’s only administrator. Do not make enthusiasm the backup plan.
The project should remain understandable when the volunteer gets a new job, graduates, or simply needs a break.
That is not distrust. That is continuity.
Learn before the funding decision
You do not need a grant to compare workflows or learn what a container does.
You do need to separate practice from production.
Before handling real records, decide who owns updates, access, backups, incident response, and recovery. Budget for the parts that cost money. Keep a supported operating system underneath the application.
For Keeps exists to make that learning approachable.
We want you to leave with more than a screen that says “running.” We want you to understand what is running, where the data lives, and how to bring it back.
Start with the computer you have, if it fits the lesson.
Finish with a skill you can take somewhere else.