X-ITM services are grouped around useful customer outcomes, not disconnected technical menus. Each route keeps scope, approvals and evidence visible.
The marketplace should present X-ITM services as outcome routes, not a loose list of technical tasks. A customer should be able to choose the result they want and understand what proof or access is needed next.
A service only becomes active work once scope, access, approvals and evidence are clear. This keeps commercial conversations connected to real technical delivery.
The customer starts an engagement, describes an outcome, or enters the workspace when there is already authorised context.
Use the marketplace to select a delivery route, then move into assessment or a governed workspace before private systems or provider actions are used.
Run a diagnostic, describe the outcome, review integrations, check trust controls, or ask support to route the request.
These are live customer-facing entry points. Each card explains what the route is for, what the customer gets, and the next safe action.
