Workflow assessment
We map the process with your operators, measure the current workload, and agree the result checks. You get a defined scope before committing to a build.
Start with the workflowTHE COMPANY BEHIND OPENADAPT
OpenAdapt is an AI automation company that builds and maintains workflows across existing systems for operations teams.
We combine hands-on implementation with software your team can inspect and reuse. Start with one workflow, agree what a good result looks like, and build from there.
Discuss your workflowPEOPLE & ORIGINS
FOUNDER
Richard is an AI architect and the founder of OpenAdapt. He helps businesses put AI automation into production and develops the software behind OpenAdapt. He holds a Master of Applied Science from the University of Toronto.
MLDSAI Inc. builds OpenAdapt in Toronto, Canada. The project’s public code dates to 2023. Richard leads the work, with open-source contributors improving the software through public issues and pull requests.
Meet the project through its workCUSTOMER WORKFLOW
Dr. Victor Abrich’s monthly RVU audit requires evidence from clinical records and report spreadsheets. OpenAdapt collects the evidence from Cerner PowerChart and reconciles the findings into a workbook for his review.
The physician checks the findings before the billing follow-up. That division of work guides our implementation process: automate the repeated steps and give the operator a result they can check.
Read the workflow and evidenceThe case study’s financial figures remain preliminary, pending customer confirmation.
WHAT OPENADAPT DOES
We map the process with your operators, measure the current workload, and agree the result checks. You get a defined scope before committing to a build.
Start with the workflowWe use APIs, conventional code, document processing, and AI where each fits. OpenAdapt’s computer-use software handles steps that require the application interface.
See the delivery processWe test normal cases and exceptions with your team, then train the people who operate the workflow. Continued support covers the monitoring, changes, and exceptions agreed in your scope.
Plan ongoing supportOpenAdapt compiles demonstrated GUI workflows into deterministic, locally executable programs. The platform connects recording, execution, and result evidence for teams that build and operate their own workflows.
Explore the platformWHAT MAKES OPENADAPT DIFFERENT
We agree the baseline, acceptance criteria, and operator responsibilities for one workflow. Those checks determine whether the implementation is ready for daily use.
The Flow runtime can check the intended effect against an independent result source. When the configured checks can’t establish the result, the workflow stops for review.
The compiler, runtime, and local launcher are MIT-licensed. Your engineers can inspect the code and run it locally; Cloud and implementation services are commercial offerings.
We agree the execution environment and data boundary with your technical owner. Sensitive observations stay inside that boundary, with review before approved material leaves it.
WHO WE BUILD FOR
Start with a workflow that has a named owner, enough volume to justify automation, and a result you can verify.
HOW WE WORK WITH YOU
The first step is a 30-minute workflow discussion. Tell us which systems you use, how often the task runs, and how you check the result today.
Before a paid build, we agree the scope, price, acceptance criteria, delivery schedule, and people responsible. Your proposal sets the communication channel and response expectations. We plan operator training before handover and scope ongoing maintenance separately.
For software issues, use GitHub. Community discussion takes place on Discord.
COMPANY REFERENCE
BEFORE WE TALK
You can use the open-source engine yourself or work with us on a paid deployment. The Services page explains delivery; the Platform page explains the software.
An API can be the best integration path when one is available. For steps that require a browser or desktop interface, we assess OpenAdapt’s computer-use capabilities against your workflow.
We agree the data boundary and execution environment before deployment. Native and remote desktop work runs in the customer-controlled environment specified for that workflow.
We quote after reviewing the workflow, its systems, and its acceptance criteria. The build and ongoing maintenance have agreed scopes; software plans are listed on the pricing page.
A description of one repeated task, the systems involved, and an estimate of the time it takes. Explain what can go wrong and how someone checks that the work is complete.
START WITH THE WORK