Built by a Doctor Who Got Tired of the Same Problems You Have

Dr. Alexander Bonakdar is a practicing optometrist in Southern California. After 14 months of building automation for his own OfficeMate server, he realized every independent OD practice struggles with the same operational pain points — and none of the existing tools solve them.

The Problem We Saw

Every independent OD practice running OfficeMate/ExamWriter faces the same reality: hours lost to manual ERA posting, insurance verification bottlenecks, patient recall systems that don't actually recall anyone, and staff turnover that resets institutional knowledge to zero. The core practice management software was architected in 2005 and hasn't fundamentally changed since.

Eyefinity's answer to this is Encompass — a cloud migration that strips away the on-prem control practices depend on and still can't process non-VSP ERAs properly. Meanwhile, practices limp along with the same manual workflows they've had for two decades, hiring more staff to compensate for software that should be doing the work.

The vendors who sell into this space treat optometry practices as if they're identical to dental or dermatology. They aren't. Vision plan billing, frame inventory, contact lens ordering, and the relationship between medical and vision claims create a unique operational complexity that generic healthcare automation platforms don't understand.

What refract.ing Actually Does

refract.ing installs on your existing OfficeMate server — or one you control. It reads your EMR data through OfficeMate's built-in SDK, using the same stored procedures Eyefinity uses internally. From there, 53 autonomous AI skills handle ERA posting, insurance verification, recall campaigns, collections, patient communications, and real-time practice analytics.

There is no cloud migration. No patient data leaves your network. No ripping out systems that already work. The platform operates alongside your existing workflows, automating the repetitive tasks that consume your staff's time while leaving clinical decision-making exactly where it belongs — with you.

The technical architecture matters because it determines what's possible. By connecting directly to OfficeMate's SQL Server database, refract.ing has access to the same depth of data your PM system uses internally. That means it can post ERAs with the correct fee slip line-item matching, verify insurance eligibility against real benefit structures, and generate recall lists based on actual clinical history — not just a "last visit date" field in a CRM.

Why This Is Different

Most health-tech startups are built by engineers who've never worked in a practice. They build what they think a practice needs based on market research and product manager hypotheses. refract.ing was built by a doctor who runs a practice, who got frustrated enough with the operational overhead to spend 14 months building the solution himself.

Every feature in the platform exists because it solved a real problem in a real office. ERA auto-posting wasn't built because a competitive analysis said we needed it — it was built because manually posting 40 ERAs a day was costing three hours of staff time that could be spent on patients. Insurance verification automation wasn't on a roadmap — it was born out of the reality that verifying benefits for a full day's schedule takes 90 minutes every morning.

The platform was in production for 14 months before we ever talked to another practice. That's not a beta test. That's a system that has processed real claims, real payments, real patient data, and real edge cases for over a year. The bugs have been found. The failure modes have been handled. The automation has been tuned against actual practice operations, not simulated ones.

The Founding Cohort

We're inviting 10 OD practices to join the founding cohort at 50% off published pricing, locked for 12 months. Founding members get direct access to the founder, priority feature requests, and a published case study documenting their results.

This isn't a beta test — the platform is production-proven. It's an opportunity to shape the roadmap while getting in at the lowest price we'll ever offer. Founding cohort members have a direct line to the person who built the system and the ability to influence which features get built next.

We're limiting this to 10 practices deliberately. Each founding installation gets hands-on onboarding, direct support, and the kind of attention that isn't possible at scale. We'd rather do 10 installations well than 50 installations poorly.

Our Commitment

HIPAA compliance isn't a checkbox for us — it's architectural. Patient data never leaves your server. There is no cloud database holding your patients' PHI. The AI processing happens on your network, against your data, with results stored in your database. We sign a BAA before any installation begins.

Our platform was designed for the regulatory reality of healthcare from day one, not retrofitted after a compliance audit flagged problems. Every data flow, every API call, every automation was built with the assumption that PHI is involved — because in an optometry practice, it always is.

And if you don't see measurable results in 30 days, you get a full refund. No questions, no haggling, no "let us try one more thing." Either the platform delivers value that your staff can feel in their daily workflow, or you shouldn't be paying for it.