What problem are you solving?
Before you compare products, write down what fails today. Typical problems: reports built by hand each quarter, no single view of grants, budgets and results in different files, approvals lost in email, or sites using different formats. The problem you name decides the criteria that matter.
Without this step, you may buy a good tool for the wrong job.
Write the problems as a short list, ranked by how much time or risk they cost. Ask staff in each team for their top two. A finance officer may name late approvals; a MEAL officer may name data in many files; a program manager may name report assembly. The overlap shows where one system can help most.
What should the software understand about NGO work?
Grant-funded projects have features that general business tools often lack. Check whether the software handles:
- Donors and agreements: who funds what, dates, conditions.
- Results frameworks: goals, outcomes, outputs, indicators and targets.
- Budgets by grant and line: and ties from work to money.
- Reporting dates: a calendar of what is due and when.
- Approvals: with a record of who approved what.
- Roles by project: who can see or change what.
If the tool lacks these, ask how you would handle them and who would keep that work up to date.
How do you test it?
Do not rely on a demo with sample data alone. Use a short test.
- Pick one real project, with a real budget and indicators.
- Enter it and run one reporting cycle with a small group.
- Include a field user with a poor connection or a basic phone.
- Ask a finance user and a MEAL user to do their normal tasks.
- Note what took longer than expected, and what staff avoided.
Our article on choosing operations software gives a wider checklist across all functions.
What practical points matter most?
| Area | Questions to ask |
|---|---|
| Roles and permissions | Can you limit who sees sensitive records? Can a role work in only one project? |
| Field use | What works online and offline? Say exactly what needs a connection. |
| Languages | Which interface languages, and how complete are they on each screen? |
| Data | Can you export all your data in a usable format? Who owns it? |
| Security | Where is data hosted? How is it protected? Ask for written answers. |
| Cost | What is included in each plan? What is added later? |
| Support | Who answers questions, in what time zone, in which language? |
| Exit | What happens to your data if you stop using it? |
Ask for answers in writing, and compare them with what you see in a test.
Pay attention to what is not on this table: staff time. Moving to any system takes time for setup, training and data entry. Ask the vendor what a typical setup needs from your side, and plan it into the work of real staff. A tool that needs a full-time administrator may not fit a small team.
Also ask about how changes are made to the system over time: who decides, how often, and how you will be told. You will live with those changes.
What should you avoid?
- Buying on a feature list. Staff use the few things that fit their day.
- Skipping the field. A tool that works in the head office but not in the field creates two systems.
- Moving everything at once. Start with one project or one function, learn, then widen.
- No owner. Assign a person who maintains the setup and trains new staff.
- Ignoring data you already hold. Plan how you will bring in past records, or decide to leave them.
Our article on moving from spreadsheets to operations software covers the shift in more detail.
Avoid also choosing the cheapest option without checking what is missing. A low price with weak support, or with a cap on users that you may reach quickly, can cost more over two years. Work out the cost for your likely size, including extra users, storage and training, and check it in writing.
Plan a review after six months. Ask users what they use, what they avoid and what is missing, and compare this with the problems you wrote down at the start. If the tool has not helped, find out whether the cause is the tool, the setup or the training, before you decide to change again.
Where EMPOBase fits
EMPOBase is operations software for NGOs and CSOs. Programs holds project planning records such as the Project Charter and RACI, MEAL holds indicators and results, and Finance holds budgets by project and grant. Field reporting works online only; offline capture is not promised. Nine interface languages are available, though coverage varies by screen, and some content appears in English. Paid checkout is not open yet, so see pricing and ask us for a walk-through with sample data on the contact page.