Selecting software for your nonprofit is one of the most consequential decisions you will make. The right choice can transform operations and amplify impact; the wrong choice can waste scarce resources and frustrate staff for years. This guide walks you through a systematic selection process, from defining requirements to making the final decision.
Step 1: Gather Requirements Systematically
Before looking at vendors, clearly define what you need. Rushing to evaluate software without proper requirements leads to poor decisions.
Stakeholder Interviews
Talk to staff across all departments who will use the system. Ask:
- What are your biggest pain points with current tools?
- What tasks take the most time that technology could streamline?
- What information do you need but cannot easily access?
- What do you wish the current system could do?
- What are your must-haves vs. nice-to-haves?
Document Current Processes
Map out key workflows before evaluating alternatives. This helps you:
- Identify inefficiencies to eliminate, not replicate
- Understand integration points between functions
- Estimate data migration complexity
- Set realistic expectations for change
Requirements Documentation Template
For each requirement, document:
Step 2: Define Evaluation Criteria
Establish clear criteria before seeing demos. Otherwise, you will be swayed by slick presentations rather than substance.
Functional Fit
How well does the software meet your documented requirements?
Core Functionality
- Does it handle fund accounting natively?
- Can it manage multiple currencies?
- Does it support grant tracking and reporting?
- Is there donor/CRM functionality?
- Can it track program outcomes?
Technical Considerations
- Is it mobile-responsive?
- Does it work offline?
- What are the integration capabilities?
- Is there an API for custom integrations?
- What is the uptime guarantee?
Vendor Viability
Will this vendor be around and supporting the product in 5 years?
Total Cost of Ownership
Look beyond the subscription price to understand true costs:
Cost Components to Consider
One-Time Costs
- Implementation/setup fees
- Data migration
- Initial training
- Customization
- Integration development
- Hardware (if needed)
Ongoing Costs
- Subscription/license fees
- Additional user licenses
- Premium support
- Additional modules
- Training for new staff
- Annual price increases
Hidden Cost Warning
Implementation costs often exceed the first year of subscription fees. Vendors sometimes understate implementation complexity to win business. Get detailed quotes and talk to reference customers about actual implementation experience.
Step 3: Run a Structured Selection Process
Create a Long List
Research potential vendors through:
- Industry publications and software review sites
- Peer organizations (ask what they use)
- Nonprofit technology conferences and forums
- Consultant recommendations
Send a Request for Information (RFI)
Send your requirements to 6-10 vendors. Ask them to explain how they would address your needs and provide pricing estimates. Use their responses to narrow to 3-4 finalists for demos.
Conduct Focused Demos
Do not let vendors control the demo agenda. Instead:
Check References
Ask for references from organizations similar to yours. Questions to ask:
Reference Check Questions
Common Pitfalls to Avoid
Choosing Based on Price Alone
The cheapest option often has the highest total cost of ownership due to limited functionality, poor support, or expensive customization. Evaluate value, not just price.
Buying for Today Only
Consider where your organization will be in 3-5 years. Can the system scale? Will it support new programs or geographic expansion?
Over-Customizing
Extensive customization increases costs, complicates upgrades, and creates dependencies on specific consultants. Adapt your processes to the software where possible.
Ignoring User Experience
A system with excellent features that staff refuse to use delivers no value. Ease of use matters enormously for adoption.
Underestimating Change Management
Budget for training, communication, and the temporary productivity dip during transition. Staff need time to learn new systems.
Planning for Successful Implementation
Before signing a contract, ensure you have a clear implementation plan:
Project Team
Identify who will lead the implementation, which staff will participate, and how much time they can dedicate. Implementation is work; plan for it.
Timeline
Agree on a realistic timeline with milestones. Avoid going live during your busiest periods (fiscal year-end, major campaigns, etc.).
Data Migration
Plan what data will be migrated, who will clean it, and how it will be validated. Data migration is often the most underestimated task.
Training Plan
Who needs training? How will it be delivered? What about staff who join after go-live? Plan for initial and ongoing training needs.
Go-Live Support
What support will the vendor provide during and immediately after go-live? Plan for intensive support in the first few weeks.
Contract Considerations
Before signing, review these key contract elements:
- Service Level Agreements (SLAs): What uptime is guaranteed? What happens if they miss it?
- Data Ownership and Portability: Can you export all your data? In what format? At what cost?
- Price Escalation: Are annual price increases capped? What is the typical increase?
- Termination Terms: What happens if you need to cancel? What is the notice period? How do you retrieve your data?
- Security and Compliance: What security certifications do they hold? Will they sign a data processing agreement?
- Scope Creep Protection: Are implementation deliverables clearly defined? What is the process for change requests?
Negotiate from Strength
You have the most leverage before signing. Once you are a customer and have invested in implementation, switching costs make negotiation harder. Negotiate pricing, terms, and implementation support upfront.