I'm not exactly clear what you're asking. Where do you draw the line between "workflow automation" and "doing work"? To me it just seems like a spectrum with rapidly moving goal posts.
A decade ago, enterprises had quite a lot of roles involving essentially moving data from one ERP screen to another. From what I'm seeing, these roles seem to be quickly disappearing, with a combination of proper API-based automation, GUI automation and most recently LLM "agents" in crucial steps.
And on a very different note, I as a developer could ask an AI tool such as Aider or Windsurf to perform a big refactoring or other code change, working autonomously across code changes and shell commands until it passes all tests - this is agentic behavior that I didn't have even a year ago.
A decade ago, enterprises had quite a lot of roles involving essentially moving data from one ERP screen to another. From what I'm seeing, these roles seem to be quickly disappearing, with a combination of proper API-based automation, GUI automation and most recently LLM "agents" in crucial steps.
And on a very different note, I as a developer could ask an AI tool such as Aider or Windsurf to perform a big refactoring or other code change, working autonomously across code changes and shell commands until it passes all tests - this is agentic behavior that I didn't have even a year ago.