For nonprofits and ministries
Nonprofits run on programmes rather than projects, and the money attached to them is restricted: given for a stated purpose and acquitted against it. That single fact shapes everything — a grant is not revenue, a volunteer is not staff, and the same quarter has to be reported twice, to a funder and to a board, who are asking genuinely different questions.
The unit of work is the programme
Everything else follows from that. The lifecycle it moves through:
- 1Grant or appeal secured, with conditions
- 2Programme designed against those conditions
- 3Volunteers and staff assigned
- 4Delivery, with evidence collected as you go
- 5Acquittal to the funder
- 6A different report to the board
Where it actually leaks
Evidence collected at acquittal rather than during delivery
A funder wants attendance, outcomes and photographs against the conditions of the grant. If that was not captured while the programme ran, someone reconstructs it near the deadline from memory and a shared drive — which is both slower and less true.
Two audiences, two reports, one quarter
The funder asks whether the money did what it was given for. The board asks whether the organisation is sustainable. Both answers come from the same activity and almost never from the same system, so both are assembled by hand.
Volunteers are not staff, and the tools assume they are
Volunteers turn over, work irregular hours, and need access to some things and not others. Most software prices and models them as employees, so organisations either overpay for seats or share a login, and the second is the more common answer.
The tools built for this, honestly
- Bloomerang — donor management and retention, which is the fundraising engine rather than the programme.
- Salesforce Nonprofit Cloud — the enterprise answer, with genuine depth and the implementation cost that comes with it.
- Little Green Light — small-organisation donor management without the enterprise overhead.
What WaymakerOS covers
Commander (the productivity suite) runs the company around the work: business email on your own domain, documents, contacts, tasks, goals, forms and the org chart. Host (the build layer) is where the one process that is genuinely yours runs, with access to the same data rather than a copy of it. One (the AI intelligence layer) reads across both.
From $19 per user per month, with every tier including all 20 Commander tools.
What we do not do
- —Donor management and fundraising. We do not do donation processing, pledge tracking, campaign attribution or donor retention scoring — buy the dedicated tool.
- —Fund accounting. Restricted-fund ledgers are a regulated accounting discipline and belong in accounting software built for it.
- —Grant discovery and application management as a product. We hold the programme once a grant is won, not the search for one.
The realistic setup for most operators is both: the vertical tool for the work it was built for, and a business platform for the company around it — with a deliberate decision about which system owns each piece of information.
Frequently asked questions
- What software do nonprofits need?
- Usually three things that are often confused: donor management for fundraising, fund accounting for restricted money, and something to run the organisation and its programmes. The third is where most nonprofits have nothing but a shared drive, because the first two get budgeted for and it does not.
- Does WaymakerOS offer nonprofit pricing?
- Yes. Verified nonprofits and ministries receive a discount on standard tiers: 40% off Platform, 50% off Business and 60% off Enterprise, applied to the existing plans rather than a separate product. Verification is required.
- What makes nonprofit software different?
- Restricted funding. Money given for a stated purpose has to be acquitted against that purpose, which means evidence collected during delivery rather than assembled at the deadline. Commercial software assumes revenue is fungible and does not model that at all.
- How do you manage volunteers without paying for full seats?
- Decide first what volunteers actually need to see, because it is usually far less than staff. Sharing a login is the common workaround and the one that causes problems later — the honest options are limited access or accepting the seat cost for people who genuinely need the system.