---
title: Customer Success
description: Customer Success provides a central contact model for adoption, value realization, and cross-team coordination.
sidebar:
  label: Overview
  order: 0
source_url: "https://framework.stackit.cloud/migration/run/customer-success/overview/"
source_file: "docs/migration/run/customer-success/overview.mdx"
---

## Understanding the Customer Success module

Customer Success is an optional module for programs that want a dedicated coordination role
for adoption and outcome realization in Run.

A Customer Success Manager can act as central contact point between customer stakeholders,
platform teams, support channels, and operating governance.

{/* vale off */}
## Customer Success at STACKIT
{/* vale on */}

At STACKIT, Customer Success Managers proactively support customers in maximizing value and outcomes to ensure long-term satisfaction and retention.

Core responsibilities include guiding customers across the full customer journey, analyzing customer needs, solving issues proactively, and identifying growth potential to develop the business relationship strategically.

Customer Success serves as the customer contact on a meta level and as interface to all other STACKIT domains.

Through regular feedback loops and proactive communication, Customer Success ensures satisfaction while also acting as an escalation instance toward top-level management for strategic alignment.

## Typical responsibilities

- **Adoption orchestration**: Align enablement activities, usage growth, and service onboarding.
- **Outcome tracking**: Connect technical run metrics to business success indicators.
- **Cross-team coordination**: Reduce friction between support, operations, platform, and customer stakeholders.
- **Improvement prioritization**: Convert recurring issues and value opportunities into clear backlog priorities.

## Optional engagement flow

<Steps>

1. Define success outcomes and stakeholder map for the run period.
2. Establish regular cadences for service health, adoption, and value tracking.
3. Coordinate escalations and follow-up actions across customer and provider teams.
4. Review delivered outcomes and adjust priorities for the next operating cycle.

</Steps>

## Typical outputs

<CardGrid>
  <Card title="Outcome dashboards">
    Shared visibility across reliability, adoption, and business-relevant service KPIs.
  </Card>
  <Card title="Coordinated action backlog">
    Prioritized follow-up actions across support, operations, and service improvement.
  </Card>
  <Card title="Stakeholder alignment">
    Clear communication lines and decision cadence for run-related evolution topics.
  </Card>
</CardGrid>

## Boundary to adjacent modules

- Customer Success does not replace incident ownership in [Support](/migration/run/support/overview/).
- It complements daily run in [Operate](/migration/run/operate/overview/).
- It can start during handover and scale after [Operating Model Handover](/migration/migrate/operating-model-handover/overview/).