Case study
The starting point
Sophro began with a close friend who runs a school. His own children study there, and between school and family they use five or six applications, each doing something different. It is the same pattern seen in golf: many tools, none of them connected.
What it replaces
The mix of spreadsheets, WhatsApp and paper that manages the life of a school today. Sophro covers the full cycle in one system, built for several schools and in two languages from the start.
How it was designed
The backend is the single source of truth and the phone is the first screen, with a mobile-first design system of its own.
Money is handled in whole units and every payment operation is idempotent, so a double click never duplicates a payment. Health data is encrypted, and permissions keep what belongs to the platform separate from what belongs to the school.
Where it stands
A pilot runs with a real school in Panama, and the full cycle is already running in production there. The platform is open to other schools and markets.
What it covers
Everything the school does, in one system.
What it demonstrates
Unify instead of add
Five or six disconnected applications become one system that shares data and users.
Proof that a message arrived
Every announcement shows how many people opened it and how many confirmed, instead of hoping the right people saw it.
Money handled with care
Whole-unit amounts and idempotent operations protect payments from duplicates and rounding errors.
Data that answers questions
Reports on attendance, money, enrollment, communication and learning, each with its table, exportable to Excel or PDF.
Does your operation run on too many applications?
If your organization has the same pattern, we can start with a conversation about how it works today.
Start a conversation