Near the end of a recent demo, a consultant who advises nonprofit organizations across South Africa asked me the question I hear, in some form, almost every week. It usually arrives politely, sometimes almost apologetically, and it is always the most important question in the room: can an organization with no technical person on staff actually run this, day to day, without hiring an IT specialist it cannot afford? I love this question. It is the question our platform was built to answer, and I want to answer it here, in public.
The question behind the question
Here is what that question is really asking. In our readiness dataset, founders and executive directors are seven in ten of the people who respond, and the organizations behind them are very often teams of two and three. There is no IT department because there is barely an administration department. Whoever answers the funder emails also fixes the printer. So when a leader asks whether they will need a specialist, they are asking something deeper: was this built for an organization like mine, or for an organization I am supposed to become first?
The answer the sector usually gets
Most software gives the second answer without saying it out loud. Enterprise tools carry hidden assumptions: an administrator to configure them, a training week to learn them, a consultant for something called implementation, and a support contract for everything after. Those assumptions are reasonable in a company of two hundred. In a team of two they are a quiet exclusion. Most software assumes there is someone to call. Our users are the someone.
The Team of Two Test
So we build against a single bar, and inside the company we treat it as law. We call it the Team of Two Test: nothing ships until a team of two can use it the same day, without training, without a specialist, and without anyone to call. Not a simplified version of it. The thing itself.
In practice the test changes how everything is engineered. The compliance calendar arrives already knowing your country's regulatory deadlines and reminds you by email on its own, because remembering is the machine's job now. Your registration certificates, bylaws, and financial records live in one vault, and the platform reads them, so a proposal begins from what the system already knows about you instead of from a blank page. Funding opportunities arrive matched to your sector, your country, and your capacity, with thresholds you set once in plain language. And where your accountant already lives in Xero or QuickBooks, we connect to those tools rather than demanding you abandon them, because the test protects your existing world, not just our screens.
What the test is not
People sometimes ask if this means building for the layman, and I push back on the word every time. The leaders I demo to are experts in the hardest domains there are: early childhood development, community health, gender justice, food systems. They are not lay anything. They are simply not software people, because their job is the mission. Simplicity built for them is not condescension. It is respect, engineered. The software is the junior partner in that room, and it should behave like one.
The demo room is our design lab
There is one more part of this I rarely say out loud. I am not only the person giving the demos. I am in the platform's development, and my specific mandate is that it stays usable for people who are not technical. Every hesitation I watch in a demo, every moment a cursor hovers because a screen was not obvious enough, travels back to our engineering table as an instruction. The consultant in that demo asked whether organizations without technical staff can run this day to day. She was, without knowing it, describing our quality process. They can, because people exactly like them are the standard everything is measured against.
If you lead a small organization and software has always felt like a thing built for someone else, the test was built for you, and it is passable today. Start where hundreds of organizations have started, with the free NGO Readiness Assessment at readiness.alleviate.org, which takes one sitting and no technical skill at all. And if you advise organizations, as she does, write to me at lisa@alleviate.org. The best question in any demo is the one she asked, and I would be glad to answer it for your network in person.
Lisa Attoh is Regional Director, Africa at Alleviate Technologies. She works with NPO leaders, and with the accountants and advisors who serve them, across Southern Africa.
