Customer story
Falcon Academy
Multi-campus US private K-12 · Virginia · Live since
The challenge
A different vendor for every operational surface.
Falcon Academy operated like most independent K-12 schools: a different vendor for each operational surface. Admissions software talked to nothing. Tuition billing sat in its own portal. Daily operations — front desk visitor logs, lunch ordering, transportation routing, enrichment program rosters, library circulation, incident reports — each lived in a separate system, with parents holding a separate login for each. The cost showed up in three places: family friction (5+ portals per family), staff overhead (parallel records across admissions, finance, front desk), and the vendor transaction tax (2-4% on tuition compounding into five-figure annual leakage).
The decision
One Operating System. One family record. One parent login.
Falcon selected Edumagined as its single operational platform, replacing the fragmented vendor stack with one administrative interface, one parent portal, and one unified record per student and family. The decision criteria that mattered: zero platform transaction fees on tuition / applications / enrollment / donations, one family record across every native app, one parent login for everything, auxiliary programs included natively (not extra), and Hijri-native calendar engine for the school's faith-community calendar.
Deployment
Multi-campus, in production.
Falcon went into production with multi-campus support (Chantilly and Ashburn), per-school branding, and Falcon's own Stripe Connect account routing tuition payments directly family→school bank. Families across both campuses transact daily across admissions, tuition, auxiliary programs, and library fines on a single platform with one login per family.
The result
What changed.
Replaced a fragmented vendor stack with one Operating System. Zero platform transaction fees on tuition. Parent portals reduced from 5+ to 1. Vendor invoices reduced from 7+ to 1. Duplicate-data reconciliation eliminated structurally. Hijri calendar handling moved from bolt-on display to first-class data-model concept.
| Outcome | Before | After Edumagined |
|---|---|---|
| Parent portals per family | 5+ | 1 |
| Vendor invoices/month | 7+ | 1 |
| Tuition transaction fees | 2–4% (~$135K/yr) | 0% |
| Duplicate-data reconciliation | Weekly staff hours | Eliminated structurally |
| Hijri calendar handling | Bolt-on display | Native; Ramadan/Eid/Jummah first-class |