The pinnacle of digital transformation remains Business Process Automation (BPA): Business Process Management (BPM) engines, expressed by the notation you see above. Tools that shepherd business processes from end to end, spanning multiple software systems, departments, divisions, and even organizations.
These systems are often massive in terms of effort and expense. Only the wealthiest institutions can afford the commitment required to succeed.
They were and are used for things like employee onboarding, insurance claims processing, loan origination, and telecom provisioning. When well done, they achieve heights of adaptiveness and flexibility. When they failed... we all know what it can be like to deal with banks and phone and insurance companies.
The rest of the world was stuck with a hodgepodge of systems — ERP, CRM, payroll, HR — with people as the glue connecting the dots.
Today, each of those dots has been supercharged by bolting on an LLM. The chatbots every software vendor now ships.
"Little master, would you like me to design the perfect landing page for you? How about five variations? How about an outbound email sequence?"
Too often, chatbots just multiply the artifacts you can create within isolated applications. People are still the glue holding the system together — and in my experience, that's where the cracks are starting to show in the world of work.
What if, instead of just providing the design and content for three variations of a landing page, your system designed and built the actual HTML pages, integrated them into your site architecture, ran the test suite, deployed them, and verified the deployment? Then it could add those pages to outbound sequences, monitor conversion performance, keep the winner, and retire the rest.
Truth be told, the biggest line item in those BPM systems was often the automation connecting all those boxes.
You needed a software developer, sometimes several, to interpret the output of one system and map it to the input requirements of the next, all while keeping the overall business goals in mind. And since they were usually consultants, those goals were never really theirs.
It was time and labor intensive even when each system had a robust API. Without an API, you had to use robotic automation (though nowadays it's mainly browser automation), which was exponentially more work and brittle to boot; whenever an application's UI changed, it would break the automation.
It's no accident that LLMs write code better than almost anything else. They've been trained on petabytes of open source code. Integration coding, where there are demonstrable criteria for success, is a task they are especially well-suited for. A mechanical integration can often be completed in minutes, even when you have to resort to browser automation.
But the mechanical integration is only the first step. Time and again this year, I've set out to use an LLM to automate something I'd been doing through an application UI, and the results have been better than what I did by hand—by a lot.
You and your team know your business better than anyone. Automating an end-to-end business process can be an opportunity to improve it. Think project initiation and termination, customer onboarding, and cold outreach as in the example above. Look for complex recurring tasks, especially ones where you touch multiple systems, or multiple parts of a software application.
As you go, I bet you'll discover that some of the software you pay for is no longer necessary. It might even be an opportunity to rethink some of your practices from the ground up. When I work with clients, it amazes me how often we discover that processes exist simply because things have always been done that way.
As I write this in the summer of 2026, I think collaborating with a talented developer is still the fastest route to genuinely transformative results. If your organization is fortunate enough to have a strong dev team, you are probably already reaping the rewards of their work (and aren't reading this).
You can get remarkably far even without access to formal development resources. Platforms like n8n, Make, and Zapier put these tools within reach of motivated business users. I wouldn't have recommended this option to most people a year ago, but today I recommend it enthusiastically, at least as an experiment.
One of the other things you paid for with those BPM systems was the task list or cockpit that allowed users to interact with the BPM engine. What we now call "human in the loop." They made it easy for a developer to build forms, but the user ergonomics were rudimentary at best.
Today agents can be wired directly into the workspace your team already uses, like MS Teams, Slack, Discord, etc. You interact with them as you would with any collaborator. Current models are excellent at reading intent from an ambiguous conversation and converting it into function calls with the right arguments.
You have an opportunity to reimagine and reengineer the way work gets done. Your organization will reap the rewards for years to come — even if the models never get one bit better.
***
Yes, this is exactly the sort of automation that makes people and jobs redundant. Early in my career, I justified that by telling myself they weren't good jobs anyway.
That was an ethical and political lapse. For twenty-five years I've worked only where software acts as a multiplier: improving workers' daily lives, enabling mission-driven organizations to do more with scarce resources, and helping founders bring something genuinely new into the world.