When the System Builds Itself 3/3
- Claas

- Jul 9, 2025
- 3 min read
Part 3: Partners in a self-building world, what humans will still be hired for
Enterprise systems are entering a new phase, one where intent becomes implementation, and software doesn’t just support business processes but creates them. As we’ve explored in Parts 1 and 2, platforms like Salesforce, Microsoft, and SAP are moving toward systems that build themselves, guided by AI agents and natural language. This isn't an incremental shift. It's the beginning of a fundamental redefinition of what “delivery” means.
The question now is no longer what AI can automate. The question is: where do humans still matter?
The fear is real and understandable
Let’s acknowledge it upfront. Across industries, people are concerned. A recent survey found that over 40% of under-25s in Germany believe they’ve already lost a job to AI. Even among more experienced professionals, anxiety is rising. When Amazon’s CEO tells staff that AI will reduce office roles, or when BT predicts tens of thousands of jobs will disappear from customer service and diagnostics, it's no longer theoretical.
But these headlines tell only half the story.
Yes, automation will remove some tasks. And yes, some roles will decline. But history tells

us that disruption does not equal disappearance. Every major shift from the steam engine to the spreadsheet created new demand, new skills, and new careers that didn’t exist before.
AI will be no different. But adaptation is not automatic. We need to be clear-eyed about the change and proactive in shaping what comes next.
But not everything will be replaced. AI can execute logic. It can follow rules, model workflows, even interpret complex queries. But it cannot own outcomes. It cannot care. It cannot mediate between politics and context. And it cannot, at least not yet, design systems around the human reality of change. That’s where partners, consultants, and internal delivery experts remain not just relevant, but essential. As the platforms take over the “how,” humans shift to the “why,” the “when,” and the “what now.”
Five Roles That Will Grow in a Self-Building World
Business Prompt Designers
The more natural language drives configuration, the more precision in language becomes a competitive advantage. These professionals act as translators — not between business and IT, but between intent and clarity. They shape how requests are phrased, how priorities are expressed, and how systems understand what to build.
Outcome Architects
Where solution architects once defined system components, outcome architects frame success. They help clients think beyond features to impact. They guide decisions about what not to automate, what trade-offs matter, and how progress is actually measured.
Ethical Stewards
As platforms build more autonomously, the risk of unintentional bias or compliance failure grows. Ethical stewards design boundaries. They ensure that what the system builds aligns with company policy, regulatory expectations, and human values even when it’s done at machine speed.
Behavioral Coaches
Fast deployment does not guarantee fast adoption. When systems adapt constantly, people need support, not in learning buttons, but in navigating change. Behavioral coaches help teams evolve with the tools, not chase them.
Trust Builders
In a world of self-building systems, clients still need a sounding board. Trust does not come from how much you configure, it comes from how well you help others decide. These are the advisors who listen better than they pitch, who clarify more than they convince, and who stay relevant long after go-live.


Comments