We build custom operations software for healthcare.
Opexia is a healthcare software development agency for care-management organizations and healthcare SaaS founders. Our engineering is led by founder Sheharyar Amin, who designs the architecture and leads every build.
A CCM/PCM platform, Excel to 8,000+ patients
We designed and built the platform that took a US CCM/PCM (care-coordination) organization from Excel to 8,000+ patients. Monthly reports and invoices are generated automatically from CPT paycode counts, and it became multi-tenant so other care-management organizations run on it independently.
Read the case studyMealCircle, our founder's own product
MealCircle is a retention-first nutrition-coaching SaaS that founder Sheharyar Amin built and runs: a patient mobile app and a coach web app, multi-tenant with row-level security. The patterns we use on client platforms run there in production.
Read the MealCircle case studyHow we work
We document requirements before any code is written, build in short sprints so you see working software regularly, and give you a realistic start date after the first call. You own the source code on final payment.
See how an engagement runsOur Founder and Lead Engineer
Sheharyar Amin, Opexia's founder and lead engineer, designed and built the custom multi-tenant platform (PostgreSQL, FastAPI, Flutter web) that took a US CCM/PCM (care-coordination) organization from Excel as it scaled from ~3,200 to 8,000+ patients, with monthly reports and invoices generated automatically. The platform is built to HIPAA requirements (encryption, audit logging, role-based access), with schema-per-tenant PostgreSQL and row-level security separating tenants.
He also built and runs MealCircle, a retention-first nutrition-coaching SaaS on Google Cloud with Firebase Authentication and Stripe billing. It is his own product, not a client project, so the way we build for clients comes from shipping and operating healthcare software, not only advising on it.
Stack Shipped in Production
Questions we get asked
Where do you work from and how is PHI access controlled?
Opexia works from Pakistan with US business-hours overlap. Access to patient data is controlled by role-based access and audit logging, and production PHI access is limited to what an engagement requires, with de-identified or synthetic data used during builds wherever possible.
Do you sign a BAA?
Yes. We sign a Business Associate Agreement (BAA) before any PHI access: no one on our team sees protected health information until it is executed. Our HIPAA BAA page (opexia.io/hipaa-baa) explains when one applies and what it covers.
Who does the work?
Opexia's engineering is led by founder Sheharyar Amin, who designs the architecture and leads every build.
What happens after launch?
Either a retainer, where we keep maintaining and extending the system, or a handover to your team. Either way, you own the source code on final payment.