New services and business processes are created from the service intercepted and created this way. These services and processes on the one hand may be displayed on the end-user portals or may be the basis for additional, new complex services and processes.

Applications and services created in adherence to SOA principles are fully reusable and services within the organization are present only in one copy. In case a business process needs a service (for instance input of a user event record into the CRM system), then it retrieves the necessary service from the company register and deploys it via the interface described there. The developer and the designer can take for certain that the given service is a tested, properly operating version because other business processes are also deploying it already. Moreover, if the implementation of that given service is modified, it remains completely concealed from the business processes using it, only the interface needs to remain unchanged or the enterprise service bus needs to hide it.

One of the major benefits of the service-oriented architecture is that it does not require the transformation of the existing enterprise infrastructure, but builds on the existing components and services. Accordingly, the SOA implementation may just as well be gradual, when SOA-based business processes can operate parallel with the existing, non-SOA-based processes.