Mobile · Consumer
A dating app engineered for real conversations
Swipe-based matching, realtime chat and trust & safety — built to turn matches into conversations rather than dead ends.
- React Native
- Node.js
- PostgreSQL
Web + Mobile · Platform
One modular ERP serving both schools and hospitals
A shared operational core — identity, roles, scheduling, billing, reporting — with vertical modules for academics and for clinical care, plus a mobile app for everyone outside the office.
- Client
- Education and healthcare group
- Industry
- Education & healthcare
- Timeline
- 9 months, phased rollout
- Platforms
- Web · iOS · Android
Overview
A group running both schools and hospitals was paying for two disconnected sets of software and reconciling them by hand. We built one platform: a shared core for the operational concerns both verticals genuinely have in common, and separate modules where they genuinely differ.
The challenge
The naive version of this project builds one generic system and forces both verticals to compromise. The hard part was deciding precisely where a school and a hospital are the same operation — and where pretending they are would break both.
- Admissions, staff records, scheduling, billing and reporting duplicated across two tool sets
- Attendance, fees and pharmacy stock still moving on paper and spreadsheets
- Parents, staff and patients had no self-service access to anything
- Wards and campuses had unreliable connectivity, so an online-only app was not viable
Our approach
How we built it
-
01
Find the true shared core
Identity, role-based permissions, org hierarchy, scheduling, invoicing, notifications and reporting are genuinely common. We built those once, properly, as the platform foundation.
-
02
Keep the verticals separate
Academics — enrolment, timetables, attendance, grade books, fee cycles — and clinical — OPD and IPD flow, appointments, prescriptions, pharmacy stock, discharge — are distinct modules on that core, not configuration of one generic entity.
-
03
Model permissions seriously
A teacher, a nurse, a registrar, a parent and a patient see sharply different slices. Role-based access is enforced server-side per record, not hidden in the UI.
-
04
Offline-first on mobile
The companion app queues attendance marking, rounds notes and stock counts locally and reconciles on reconnect, so patchy ward and campus Wi-Fi never blocks work.
-
05
Roll out in phases
One campus and one department first, with parallel running against the old process until the numbers matched, then progressive rollout.
What we shipped
In the delivered product
Shared core: identity, RBAC, scheduling, billing, notifications, reporting
Academics: admissions, timetables, attendance, grade books, fee cycles
Clinical: OPD/IPD flow, appointments, prescriptions, pharmacy stock, discharge
Mobile app for staff, parents and patients with offline queueing
Consolidated dashboards across both verticals
Audit logging and data export for compliance
The outcome
Results
2 → 1
Systems to run and reconcile
~11 hrs
Admin time saved per staff member weekly
9 months
To full phased rollout
Offline
Attendance and rounds keep working
More work
View all projects
Other projects
AI · Public sector
Natural-language reporting across a government data warehouse
Analysts ask a question in plain language; the system writes verified, read-only SQL against a governed warehouse and returns the answer with its workings.
- Python
- FastAPI
- Self-hosted LLM
AI · Customer support
A website assistant that answers only from your own content
A retrieval-grounded support assistant that cites its sources, knows when to escalate, and never invents an answer.
- Node.js
- LLM API
- pgvector
Ready to build something people trust?
Book a free consultation. We'll map the highest-impact opportunity for your business — no obligation.