FIELD NOTE / 2026.09.212 MIN READ / 5 SOURCES

The Minds Behind Robotic Process Automation – 7 People Redefining Software

Seven founders and evangelists helped turn screen interaction, workflow rules, and software bots into robotic process automation for repetitive digital office work.

TL;DR

Seven founders and evangelists helped turn screen interaction, workflow rules, and software bots into robotic process automation for repetitive digital office work. [1][2]

Why you should read it anyway

Many business processes were trapped between modern applications and legacy systems that lacked clean APIs. RPA offered a pragmatic bridge: software could operate existing user interfaces the way a human worker did.

Imagine where Robotic Process Automation would be without them

Without RPA, enterprises would rely more heavily on manual clerical work, bespoke integrations, screen scraping, and major system-replacement programs to automate legacy processes.

Time Estimate of how many years we would be hindered without them for human progress

Editorial counterfactual estimate: 3–6 years. This is not a measured historical fact. It is an editorial estimate of how much slower the field might have matured without this cluster of people, institutions, products, and ideas.

The 7 people behind Robotic Process Automation

1. Alastair Bathgate

Why they matter: co-founded Blue Prism in 2001 and helped pioneer enterprise software robots for automating repetitive back-office work.[1]

2. David Moss

Why they matter: co-founded Blue Prism and helped build its early automation platform for rule-based business processes.[2]

3. Pat Geary

Why they matter: as Blue Prism’s chief evangelist, coined the term robotic process automation in 2012, giving the emerging category its enduring industry name.[3]

4. Daniel Dines

Why they matter: co-founded UiPath and led its evolution from an automation engineering company into one of the world’s largest RPA platforms.[4]

5. Marius Tîrcă

Why they matter: co-founded UiPath and served as a central technical architect of its automation platform.[5]

6. Mihir Shukla

Why they matter: co-founded the company that became Automation Anywhere and helped build one of the major enterprise RPA platforms.[1]

7. Neeti Mehta Shukla

Why they matter: co-founded Automation Anywhere and helped shape its enterprise automation strategy, product direction, and category growth.[2]

How they each differ from one another

Bathgate and Moss built Blue Prism’s early enterprise automation; Geary named the category; Dines and Tîrcă scaled UiPath; Mihir and Neeti Mehta Shukla built Automation Anywhere into another global RPA platform.

Final Take

RPA became important because it automated around software that was never designed to integrate. Its strength—and limitation—is that it can make legacy interfaces programmable without changing the systems underneath.

RESEARCH / PROVENANCE

Works Cited

5 SOURCES
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05

CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.

Contribute / Corrections

Improve the record.

Use this moderated submission form to suggest a correction, provide a source, challenge a priority claim or identify a missing contributor. Submissions are treated as research leads, not automatically published comments.

Submit a research lead

Please do not submit confidential material or claims you cannot support.