You adopted AI but the delivery timeline didn’t change. Our paper explains why →

HealthTech / EdTech

AI MODERNIZATION

How Rolai Cut Automation Build Time from 80 Hours to One with Claude

Users at Rolai can now describe a complex workflow in plain language and Claude builds it in about an hour — a process that used to take two developers a full week.

INDUSTRY

HealthTech / EdTech

ON THIS PAGE

    The Impact

    What this delivers in production

    80h → 1h

    to build a complex automation Flow — from two developers spending a week, to one non-developer spending an hour

    ~99%

    reduction in automation build time, with no loss in the quality or complexity of the Flow

    3 models

    Claude Haiku, Sonnet, and Opus available within Flows — customers choose the model that fits their accuracy and cost requirements

    • THE CHALLENGE

    Higher education and healthcare organizations run on manual, multi-step processes,

    like admissions, financial aid, prior authorizations and revenue cycle work. These span many systems, need judgment at each step, and fall under HIPAA and FERPA. Generic AI tools couldn’t safely handle them.

    Building a complex Flow still took technical skill. Even with Rolai’s drag-and-drop designer, customers relied on developers, and a complex Flow could take two developers a week.

    • THE APPROACH

    Rolai built Flows, which automate a process end to end, with Claude.

    In Flows, Claude handles reasoning, extraction, classification or generation at every step. Flows run on events, schedules, webhooks or a chat request, and connect to tools like Canvas, Blackboard and FHIR-based healthcare systems. Where integrations stop, Rolai’s browser extension works inside the user’s signed-in session to reach any web application, such as messaging a provider or writing back to a progress note in an EHR, which FHIR doesn’t support. Flows run on SOC 2, HIPAA, FERPA and GDPR compliant, ISO 27001 certified infrastructure, and users choose their Claude model: Haiku, Sonnet or Opus.

    To open Flows up to non-technical users, Rolai built Chat to Build. Users simply describe a process in plain language inside the Rolai app, and Claude turns it into a validated, runnable Flow they can refine through conversation.

    Rolai brought in Incubyte as its engineering partner to build the platform, from the Flow engine and integrations to Chat to Build.

    • THE OUTCOME

    Flows now take manual, multi-step work off people's plates, with Claude handling the judgment inside each step.

    Through Rolai’s Microsoft Teams integration, users run automations across their external systems without switching tools, with access managed in one place. The browser extension extends Flows beyond standard integrations, bringing the full EHR within reach of automation, not just what FHIR exposes.

    Chat to Build changed who can build those automations. A Flow that took two developers a week, about 80 hours, now takes a non-developer about an hour, cutting build time by roughly 99%. With Rolai’s Chrome recording feature, non-developers capture the technical details a Flow needs without engineering help. Automation is no longer limited to specialists, so adoption scales beyond Rolai’s delivery capacity.

    • STACK

    Tech

    Claude API

    Claude Haiku, Sonnet, Opus — user-selectable per Flow

    Team

    Akshay Vadher

    Software Craftsperson – Tech Advisor

    Sanket Dhokte

    Technical Product Craftsperson

    Yogendra Jaiswal

    Software Craftsperson

    Weighing a rewrite?

    There’s a third path. Most of our work begins with a thirty-minute conversation.
    Contact Us