Spotlight: Alec Stephens @ Syntegrity
![]()
A spotlight is a short-form interview with a leader in health tech. In this spotlight, you'll hear from Alec Stephens, founder of Syntegrity.
What does Syntegrity do?
We build software that helps independent eye care and dental practices chase what insurers owe them, with far less work. Our main product is ClaimStride, which reads a practice's aging report, asks each insurer where every unpaid claim stands through Stedi, and gives the billing specialist one list with the next step on each claim. Alongside it we build agents that work the practice's own EHR the way a person would, for the systems that offer no API. Everything runs in the practice's own HIPAA-compliant AWS account under a BAA.
How did you end up working in health tech?
My first healthcare client was actually my dad's optometry clinic. We started off knocking out some admin work for his staff, including a new payroll system, a knowledge base for the front desk, then automating invoices into QuickBooks. Each project moved closer to the money, and when we got to insurance claims I saw how much of a practice's time goes into chasing insurers and getting claims paid. I knew instantly that it was the problem I wanted to spend my time on.
How does your role intersect with revenue cycle management (RCM)?
It's really the center of what we do. ClaimStride takes the aging report the practice already runs, sends a 276 status request for each unpaid claim, and turns the 277 responses into a worked list. Coverage lookups run on 270/271, and the 835 payment files load in as they arrive, so the list reflects what has been paid. At our first eye care clinic it read a 1,140-claim report with every total adding up, and the first live run came back in about 2 minutes. Where the practice's EHR has no API, our agents collect those payment files from the screen, the way a staff member would.
What do you think RCM will look like two years from now?
I think status requests and payment posting will run in the background, and a billing specialist's day will start with a short list of claims that need a human to handle them (like an appeal or a phone call), and the agents will handle the rest. The clearinghouse side is no longer the hard part, because it's finally simple to build on. The real bottleneck is the practice software, which in a lot of small practices still has no API and makes the claim data extremely difficult to find. I think agents that work those screens the way staff do will bridge that gap for the next few years, and the practices that adopt them will get access to results that only mid-size and enterprise businesses have today. At Syntegrity, we're here to help small practices close that gap.