Definition
What this research area means for a product, in plain language.
RPA research
RPA research tests whether a stable UI path can be automated safely. We'll build anything for anyone to help solve problems and save them money.
What this pass is
RPA research tests whether a stable UI path can be automated safely. A first experiment is scoped on your problem and samples—not a generic tutorial. You leave with reliability notes and a sunset-to-API recommendation when relevant.
Questions this area can take
- Definition: What this research area means for a product, in plain language.
- First experiment: Automate one painful path with logging and failure alerts.
- Constraints: Data, privacy, and device limits written before work starts.
- Handoff: Notes and whether to productize—productization is a new quote.
What the first experiment includes
First experiment
Automate one painful path with logging and failure alerts.
Constraints
Data, privacy, and device limits written before work starts.
Handoff
Notes and whether to productize—productization is a new quote.
How we implement a pass
A research pass is a small program on your samples, not a tutorial. We keep the question, the input, and the result you can rerun. If it becomes a product, that is a new quote: screens in React and TypeScript, an API, and Postgres when the record has to stay.
A person still judges the output. We do not hide a miss. We do not print a timeline we have not agreed.
Questions
Is research the same as a production feature?
No. Research answers a question; production hardening is quoted separately.
How long does a first experiment take?
Duration is in the quote after scope. We do not publish a default two-week promise.
Notes
This is a learning note, not a case study. We will not claim a client, a savings percent, or a certification. Productizing the experiment is a separate request.
More notes live on Notes.
