Built because I needed it to exist, not because I spotted a market.

I run a school. 600 to 1,000 pupils, in Uganda. The problems SchoolPro is built around aren't hypothetical — they're mine first: fee money moving between the bursar's office and the bank with no visibility, term-end reconciliation done by hand or in scattered spreadsheets, and the quiet fear of losing years of student and financial records to one crashed laptop with no backup.

So I built the thing I needed. Then I kept building until it covered the whole school — students, fees, payroll, exams, attendance, library, inventory, health, dormitory — because a school doesn't run in one department at a time, and the software shouldn't pretend it does either.

That's SchoolPro's real edge. Not a feature on a comparison chart — authorship. Every workflow matches how a Ugandan school actually operates, because it was built by someone doing that operating every day, not a vendor guessing at the market from the outside.