Our website uses cookies to enhance your online experience by; measuring audience engagement, analyzing how our webpage is used, improving website functionality, and delivering relevant, personalized marketing content, and measure the performance of our digital advertising campaigns.
Your privacy is important to us. Thus, you have full control over your cookie preferences and can manage which ones to enable. You can find more information about cookies in our Cookie Policy, about the types of cookies we use on Atos Cookie Table, and information on how to withdraw your consent in our Privacy Policy.
Our website uses cookies. You have full control over what you want to activate. You can accept the cookies by clicking on the “Accept all cookies” button or customize your choices by selecting the cookies you want to activate. You can also decline all non-necessary cookies by clicking on the “Decline all cookies” button.
These are essential for the user navigation and allow to give access to certain functionalities such as secured zones accesses. Without these cookies, it won’t be possible to provide the service.
Matomo privacy policy
These cookies are used to deliver advertisements more relevant for you, limit the number of times you see an advertisement; help measure the effectiveness of the advertising campaign; and understand people’s behavior after they view an advertisement.
Adobe Experience Cloud Marketo | Google Ads
These cookies are used to measure the effectiveness of social media campaigns.
LinkedIn Policy
Our website uses cookies to enhance your online experience by; measuring audience engagement, analyzing how our webpage is used, improving website functionality, and delivering relevant, personalized marketing content. Your privacy is important to us. Thus, you have full control over your cookie preferences and can manage which ones to enable. You can find more information about cookies in our Cookie Policy, about the types of cookies we use on Atos Cookie Table, and information on how to withdraw your consent in our Privacy Policy.
Global EN | FR
Atos homepage
Digital enterprises face a paradox.
They invest heavily in processes, platforms, and AI, yet customer value remains slow, opaque, and fragile. The root cause is rarely technological. It is architectural. Both IT and business services are still treated as organizational agreements, defined in documents, governed by committees, and changed through projects.
Service as Software breaks this pattern. It defines an IT- or business service as a software-defined, executable, and continuously evolving capability that encapsulates functionality in code. A service is no longer implemented and handed over; it is owned, governed, and improved through software. This shift is foundational to standards such as SAFe®, TOGAF® 10, Open Agile Architecture™, Digital Practitioner (DPBoK™), and IT4IT®.
More importantly, it is essential for decision-driven and agentic enterprises.
Service as Software is the architectural expression of a value stream, realized as an executable, governable, team owned digital product.
Service as Software (SaS) represents a fundamental shift from software that supports human work to software that performs the work itself. It reverses the SaaS model: instead of tools for users, autonomous, AI-driven agents deliver complete outcomes. Powered by large language models, software now understands context, executes complex workflows, and replaces repetitive human effort.
This is not an incremental improvement in delivery but a redefinition of what software is expected to do, transforming it from an organizer of work into the worker itself (Atos, 2026). With this, Autonomous Business (Meelhuijsen, et al., 2025) is quickly becoming a reality.
A critical and essential architectural insight is often overlooked.
Processes do not create value. Decisions do.
Processes exist to sequence activities. They are necessary for flow but are inherently non-differentiating unless they directly contribute to consumer satisfaction. What consumers and customers experience as value is the outcome of knowledge-based decision-making: benefits, permits, pricing, eligibility, routing, personalization, prioritization, and resolution.
When enterprises optimize processes rather than decisioning, they create efficient bureaucracy. When they optimize decisioning, they create adaptive value. SaS starts with the premise that services exist to make and execute decisions at scale, safely, and repeatedly.
The Portfolio of Digital Open Standards (The Open Group, 2026) describes an enterprise organized around long-lived, autonomous teams that deliver value continuously within defined architectural guardrails. In such an enterprise, services cannot be implemented once and then operated by someone else. They must be deployable, versioned software units with clear ownership and feedback loops. with scope for continuous learning and improvements.
DPBoK™ reinforces this by shifting from projects to enduring digital products. Products integrate business behavior, software, and operations into a single lifecycle. When services are treated as software (i.e., products), architecture ceases to be a design-time activity and becomes a runtime-guided capability that is observable, testable and adaptable.
The TOGAF® 10 Standard reinforces this essential shift by reframing architecture governance as providing continuous monitoring and direction. Services defined in Business and Application Architecture deliver value only when realized as governable operational building blocks that embody TOGAF’s SaS paradigm:
Architecture is no longer something you describe and hope teams follow. It is something the system continuously enacts.
Conway’s Law tells us that systems mirror the communication structures of the organizations that build them. Traditional service models violate this law by spreading ownership across design, delivery, and operations. The result is predictable: slow change and brittle systems with complex interfaces.
SaS deliberately embraces Conway’s Law. By aligning service boundaries with team boundaries, coordination is reduced to APIs and events. Autonomy becomes structural rather than aspirational. Teams own decisions; services own outcomes.
Conway’s Law states that the structure of any system mirrors the communication patterns of the organization that builds it, meaning teams inevitably design solutions that reflect their own coordination, boundaries, and interactions.
At this point, SaS requires a crucial component: Rules as Code (Lindqvist, 2024). Rules as Code is the practice of expressing business rules, legislation, policies and regulations in an executable, version controlled form, rather than prose. This ensures rules are explicit, testable, traceable and enforceable at runtime. Without Rules as Code, services remain dependent on human interpretation of policy, or on opaque AI models that cannot explain or justify outcomes. With Rules as Code, legislation, policies and regulations become a first class architectural asset, deterministic and auditable, embedded directly in services.
The Rules as Code component naturally fits into Digital Decisioning (Taylor, 2019). Decision logic, whether deterministic (e.g., DMN or RuleSpeak) or probabilistic (e.g., AI or machine learning), is treated as a separate, explicit concern from the process flow.
In a SaS architecture:
Processes remain the source of waste: they route and sequence. Decisions create value. By making decisions explicit and executable, enterprises gain transparency, explainability and adaptability, all of which are especially critical in regulated and high-impact domains.
Agentic and AI-enabled services are often discussed as overlays on existing architectures. This approach fails. True agentic behavior requires services to observe, decide, act and learn autonomously within explicit guardrails. SaS provides the necessary conditions:
Without this foundation, AI remains an assistive tool. With it, AI becomes a responsible operational actor, safely embedded within enterprise architecture.
Service as Software across the IT4IT value streams
SaS turns IT4IT™ from a lifecycle model into a continuous value system. Here’s how it does it:
This is why IT4IT ceases to be a conceptual framework and becomes an operational reality.
SaS across business value streams
Business value streams express customer value creation, while IT4IT value streams operationalize the digital lifecycle that enables those value streams to be executed at scale.
Practical architectural implications are as follows:
Business journeys define value creation. In a SaS model, many steps of the business journey are moved into software, enabling them to be executed, governed, and evolved at scale.
SaS is the architectural convergence point for SAFe, TOGAF 10, Open Agile Architecture, DPBoK, IT4IT, Rules as Code and Digital Decisioning. By recognizing that value is created by decisions, enterprises reposition processes as supporting rather than driving, thereby elevating decisioning to a first-class concern.
Large language models (LLMs) and agentic AI give software a more human-like understanding, enabling it to autonomously handle complex workflows and serve as a consultant-in-a-box that delivers outcomes, not just tools.
Services that become executable, governable software products:
Architecture shifts from describing the future to governing the system as it operates. IT4IT becomes a continuous flow of work and value across the digital lifecycle. Agentic AI becomes viable at the enterprise scale. In a digital enterprise, value is not just automated; it is decided on a case-by-case basis. SaS brings those decisions to life.
Service as Software is the architectural pattern in which services become software defined value engines, governed by guardrails, driven by explicit decisioning, and capable of safe autonomy through agentic AI, while process is reduced to necessary but non value creating waste.
Wrapping up the solution: The way forward
In this article, we have discussed the following points that are integral to helping you and your organization shift from software that supports human work to SaS: software that performs the work itself.
Service as Software addresses a core transformation gap in businesses.
If you are looking for faster delivery, transparency, compliance, and scalable AI-enabled autonomy — all much needed for operating effectively in complex and regulated environments — your organization needs to start making executable decisions and embed them in governed, auditable, software-defined services.
Start today!
Connect with me, and let’s discuss how your organization can embrace this shift more quickly.
Posted: 16/06/26
Digital Agile Enterprise Architect & Next Generation Architecture Chapter Leader FMRC
View all blog posts
Leave a Reply