US HEALTH TECH
AI MODERNIZATION
AI inside software you can't change. No rewrite.
It rides in through the browser, inside the session people are already signed into. No new app to learn, and the software’s maker builds nothing.
INDUSTRY
Line-of-business software / US health tech
SERVICE
AI Modernization
ENGAGEMENT
2+ years, ongoing
TEAM
Entire tech org, ~21 people
ON THIS PAGE
OUTCOMES
What we measured
230,000+
FLOW RUNS IN
ONE MONTH
~18 sec
EVENT TO NOTIFICATION,
END TO END
0
VENDOR APIS OR
CHANGES REQUIRED
From the client
I'm delighted with where it's going. This is crazy what it'll end up doing.
[Pending client sign-off],
Founder, Rolai
- THE CHALLENGE
Users live inside legacy software AI can't reach.
A clinician in the EHR. A biller in the payer portal. A rep in the CRM. They know their software cold and will not leave it. Not even for AI.
That software gives AI nothing to connect to. No API, no vendor building one.
So the value stays parked: copied data, switched tabs, manual work an automation could run, if it could reach the screen.
If it's on the screen, it can be acted on.
The principle
- THE APPROACH
A browser extension: if it's on the screen, we act on it.
Most modernization starts with a rewrite. We started with the browser: an extension that carries Rolai’s AI into the screen the user is already on, inside the session they are logged into.
The founder’s bet: “Once you get the authentication, you’ll be able to manipulate the DOM because you will run in that session. That’s the key.”
01
Page context
Reads the page and surfaces the flows that matter for it. In production.
02
In-page actions
AI buttons injected onto the existing screen, where the work happens. Releasing soon.
03
User Continuity
Operates no-API software on the user’s behalf. A payer portal, filled from EHR data. Roadmap.
04
Event-driven flows
A change in a connected system fires a flow and notifies the right people. In production.
Schematic, inside the legacy screen: the legacy screen (EHR / payer portal / CRM) with the Rolai extension panel alongside it, listing Flows for this page, Run, and Notify. Injected into the page. No API. No vendor change.
INSIDE THE LEGACY SCREEN
*[Pending client sign-off]
- THE OUTCOME
Live with real users, and still shipping.
Shipped: the page-context extension, live with real users. Roughly 230,000 flow runs in one month. Event to notification in about 18 seconds.
Shipping: AI buttons on the legacy screens themselves, so the action appears where the work happens.
Next: payer portals operated on the user’s behalf, a prior authorization filled from EHR data, about 6 hours saved per run (an estimate). A check-in flow collapsing 8 screens into one. For anyone weighing a rewrite, the third path is real: leave the legacy system where it is, and put the AI inside it.
METRIC
Throughput
Event response
Vendor asks
BEFORE
Manual, tab by tab
Manual follow-up
An API per workflow
AFTER
At scale, unattended
~18 seconds
None
- ENGAGEMENT TIMELINE
1
Day one,
5 developers
2
Entire tech org,
PM through design
3
~21 people,
first enterprise customers
4
Enterprise EHR partner,
next release
- HOW THE POD WORKS
01
Composition
Product management, infrastructure, DevOps, development, QA, design. One team, end to end.
02
Ownership
The team that builds it runs it. Nothing handed over, nobody rotates off.
03
Governance
Runtime credentials, isolated surfaces, SOC 2 and HIPAA on the platform.
04
Growth
Five developers at the start, about twenty-one today, as the product scaled.
- STACK AND TEAM
Tech
Browser extension
DOM automation
Event-driven flows
Runtime credentials
HIPAA
Spec-driven development
SOC 2
Team
[Pending sign-off]
Tech Lead
[Pending sign-off]
Software Craftsperson
[Pending sign-off]
Software Craftsperson
- ABOUT THIS ENGAGEMENT
Rolai is an enterprise AI platform: an AI Workbench, Agents, and Automation on top of the software and data an organization already runs on. Incubyte is Rolai’s entire embedded engineering organization, two years and counting.
The problem is the one most enterprise AI never gets past. The people who would benefit most, a clinician inside an EHR, a biller inside a payer portal, a rep inside a CRM, know their software cold and will not leave it for a separate AI app. Most of that software has no API, and no vendor is building one for every workflow.
We built a browser extension that brings the AI to them instead. It runs inside the user’s already-authenticated session, reads the page, and surfaces the flows and applications relevant to that screen. Because it operates inside the session, it can act on software that exposes no API at all, with nothing requested from the software vendor. In the founder’s words: “Sometimes you want to write to that one field and there’s no API available, but you’re on that web page.”
Event-driven automation closes the loop. When something changes in a connected system, a flow fires and the right people are notified automatically, about 18 seconds end to end. In one month, the customer’s own analytics dashboard recorded roughly 230,000 flow runs on the platform.
The cadence continues because the team does. AI actions injected directly onto legacy screens are releasing soon. Portal operation, filling a patient’s prior authorization form from EHR data, is on the roadmap, projected to save about six hours of manual work per run. A customer-requested check-in flow would collapse about eight screens into one. Roadmap items are labeled as roadmap; the 230,000 runs are not.
The pattern proved out in US health tech and generalizes to any web-based legacy software: payer portals, CRMs, other line-of-business apps. For teams weighing modernization against a rebuild, this is the third path: leave the legacy software where it is, and put the AI inside it.
- FAQ
Frequently asked questions.
How do you add AI to legacy software that has no API?
Through the browser. Rolai’s extension runs inside the user’s already-authenticated session, reads the page, and acts on it, so it can reach and operate software that exposes no API, with nothing requested from the vendor. In the founder’s words: “Sometimes you want to write to that one field and there’s no API available, but you’re on that web page.”
What results has this produced in production?
Through the browser. Rolai’s extension runs inside the user’s already-authenticated session, reads the page, and acts on it, so it can reach and operate software that exposes no API, with nothing requested from the vendor. In the founder’s words: “Sometimes you want to write to that one field and there’s no API available, but you’re on that web page.”
Do users have to learn a new app?
Through the browser. Rolai’s extension runs inside the user’s already-authenticated session, reads the page, and acts on it, so it can reach and operate software that exposes no API, with nothing requested from the vendor. In the founder’s words: “Sometimes you want to write to that one field and there’s no API available, but you’re on that web page.”
Is operating software through the user's session secure?
Through the browser. Rolai’s extension runs inside the user’s already-authenticated session, reads the page, and acts on it, so it can reach and operate software that exposes no API, with nothing requested from the vendor. In the founder’s words: “Sometimes you want to write to that one field and there’s no API available, but you’re on that web page.”
Does the software vendor need to change anything?
Through the browser. Rolai’s extension runs inside the user’s already-authenticated session, reads the page, and acts on it, so it can reach and operate software that exposes no API, with nothing requested from the vendor. In the founder’s words: “Sometimes you want to write to that one field and there’s no API available, but you’re on that web page.”
What is shipping next?
Through the browser. Rolai’s extension runs inside the user’s already-authenticated session, reads the page, and acts on it, so it can reach and operate software that exposes no API, with nothing requested from the vendor. In the founder’s words: “Sometimes you want to write to that one field and there’s no API available, but you’re on that web page.”
Does this only work in health tech?
Through the browser. Rolai’s extension runs inside the user’s already-authenticated session, reads the page, and acts on it, so it can reach and operate software that exposes no API, with nothing requested from the vendor. In the founder’s words: “Sometimes you want to write to that one field and there’s no API available, but you’re on that web page.”
Weighing a rewrite?
There’s a third path. Most of our work begins with a thirty-minute conversation.
- GLOSSARY
-
Browser extension.
Software that runs inside the user's browser and can read and act on the pages they visit.
-
Authenticated session.
The logged-in context a user already has open. The extension operates inside it rather than logging in separately.
-
DOM.
The live structure of a web page. Acting on it lets the extension read and operate any on-screen element.
-
Event-driven automation.
A flow that fires automatically when something changes in a connected system.
-
Flow run.
One execution of an automation flow on the Rolai platform.
-
Prior authorization.
The insurance approval a provider must obtain before certain care. Filling the form is manual, multi-system work today.
-
Payer portal.
The insurer's website where providers submit and track authorizations and claims.
- READ NEXT
More work in us health tech
- US Health Tech
- AI Product
FHIR ran out. The roadmap didn’t.
Rolai, 0 new vendor APIs to reach the full record.
- US Health Tech
- AI Product
Built by people who don’t code.
Rolai, 1 weekend from prompt to a shipped interface.