DE · EN

Call us

apiVersion: soultec.ch/v1kind: Servicemetadata: name: customer-success-manager locale: en labels: group: consulting capability/managed-services: 3.23 capability/strategy: 3.54 capability/architecture: 2.93 annotations: source: src/content/services/en/customer-success-manager.md route: /en/services/customer-success-manager/ schema: /nerd/schema/services.json markdown: /en/services/customer-success-manager.mdspec: title: Customer Success group: consulting order: 1 tags: [managed-services, strategy, architecture] summary: >- One named contact across the whole lifecycle. Their most frequent contribution is retiring licences you are already paying for. photo: two-in-conversation photoNeed: >- A customer conversation across a table, both people visible, notes not laptops stub: false draft: false sections: - heading:

What a CSM is

body: | A named contact and adviser who stays with you across the whole lifecycle of your infrastructure, from introduction through to continuing development. Not an escalation contact, but someone who knows the estate before anything goes wrong. - heading:

What it is actually good for

body: | The practical benefit is usually not the advice, it is the clearing up. Software moves on, and features that needed a separate product three years ago are included in the contract you already hold. Finding those point solutions and retiring them is the most common saving that comes out of this. Then there is the proactive half: raising problems before they escalate, and keeping the estate current continuously rather than renewing it in a project every three years. - heading:

When it pays

body: | When the estate is large enough that nobody holds all of it in their head, and when years pass between projects. That gap is exactly where licences end up running that nobody can account for.status: corpus: 267 solutions: - {ref: solutions/vmware/vmware-cloud-service-provider, score: 0.34} - {ref: solutions/hpe/hpe-server, score: 0.34} - {ref: solutions/ibm, score: 0.34} - {ref: solutions/ibm/ibm-power10, score: 0.34} alsoLike: - {ref: services/enterprise-architecture, score: 0.67} - {ref: services/it-strategie, score: 0.67} - {ref: posts/vmware-license-changes-2025, score: 0.41} experts: - {ref: experts/valentina-cicmak, score: 0.28} - {ref: experts/matthias-frech, score: 0.25} - {ref: experts/mike-schmid, score: 0.23}

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "customer-success-manager", "locale": "en", "labels": { "group": "consulting", "capability/managed-services": "3.23", "capability/strategy": "3.54", "capability/architecture": "2.93" }, "annotations": { "source": "src/content/services/en/customer-success-manager.md", "route": "/en/services/customer-success-manager/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/customer-success-manager.md" } }, "spec": { "title": "Customer Success", "group": "consulting", "order": 1, "tags": [ "managed-services", "strategy", "architecture" ], "summary": "One named contact across the whole lifecycle. Their most frequent contribution is retiring licences you are already paying for.", "photo": "two-in-conversation", "photoNeed": "A customer conversation across a table, both people visible, notes not laptops", "stub": false, "draft": false }, "sections": [ { "heading": "

What a CSM is

", "body": "A named contact and adviser who stays with you across the whole lifecycle of your\ninfrastructure, from introduction through to continuing development. Not an escalation\ncontact, but someone who knows the estate before anything goes wrong." }, { "heading": "

What it is actually good for

", "body": "The practical benefit is usually not the advice, it is the clearing up. Software moves on,\nand features that needed a separate product three years ago are included in the contract\nyou already hold. Finding those point solutions and retiring them is the most common saving\nthat comes out of this.\n\nThen there is the proactive half: raising problems before they escalate, and keeping the\nestate current continuously rather than renewing it in a project every three years." }, { "heading": "

When it pays

", "body": "When the estate is large enough that nobody holds all of it in their head, and when years\npass between projects. That gap is exactly where licences end up running that nobody can\naccount for." } ], "status": { "corpus": 267, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.34" }, { "ref": "solutions/hpe/hpe-server", "score": "0.34" }, { "ref": "solutions/ibm", "score": "0.34" }, { "ref": "solutions/ibm/ibm-power10", "score": "0.34" } ], "alsoLike": [ { "ref": "services/enterprise-architecture", "score": "0.67" }, { "ref": "services/it-strategie", "score": "0.67" }, { "ref": "posts/vmware-license-changes-2025", "score": "0.41" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.28" }, { "ref": "experts/matthias-frech", "score": "0.25" }, { "ref": "experts/mike-schmid", "score": "0.23" } ] }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "customer-success-manager"locale = "en"[metadata.labels]group = "consulting""capability/managed-services" = "3.23""capability/strategy" = "3.54""capability/architecture" = "2.93"[metadata.annotations]source = "src/content/services/en/customer-success-manager.md"route = "/en/services/customer-success-manager/"schema = "/nerd/schema/services.json"markdown = "/en/services/customer-success-manager.md"[spec]title = "Customer Success"group = "consulting"order = 1tags = ["managed-services", "strategy", "architecture"]summary = "One named contact across the whole lifecycle. Their most frequent contribution is retiring licences you are already paying for."photo = "two-in-conversation"photoNeed = "A customer conversation across a table, both people visible, notes not laptops"stub = falsedraft = false[[sections]]heading = "

What a CSM is

"body = '''A named contact and adviser who stays with you across the whole lifecycle of yourinfrastructure, from introduction through to continuing development. Not an escalationcontact, but someone who knows the estate before anything goes wrong.'''[[sections]]heading = "

What it is actually good for

"body = '''The practical benefit is usually not the advice, it is the clearing up. Software moves on,and features that needed a separate product three years ago are included in the contractyou already hold. Finding those point solutions and retiring them is the most common savingthat comes out of this.Then there is the proactive half: raising problems before they escalate, and keeping theestate current continuously rather than renewing it in a project every three years.'''[[sections]]heading = "

When it pays

"body = '''When the estate is large enough that nobody holds all of it in their head, and when yearspass between projects. That gap is exactly where licences end up running that nobody canaccount for.'''[status]corpus = 267[[status.solutions]]ref = "solutions/vmware/vmware-cloud-service-provider"score = "0.34"[[status.solutions]]ref = "solutions/hpe/hpe-server"score = "0.34"[[status.solutions]]ref = "solutions/ibm"score = "0.34"[[status.solutions]]ref = "solutions/ibm/ibm-power10"score = "0.34"[[status.alsoLike]]ref = "services/enterprise-architecture"score = "0.67"[[status.alsoLike]]ref = "services/it-strategie"score = "0.67"[[status.alsoLike]]ref = "posts/vmware-license-changes-2025"score = "0.41"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.28"[[status.experts]]ref = "experts/matthias-frech"score = "0.25"[[status.experts]]ref = "experts/mike-schmid"score = "0.23"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>customer-success-manager</name> <locale>en</locale> <labels> <group>consulting</group> <entry key="capability/managed-services">3.23</entry> <entry key="capability/strategy">3.54</entry> <entry key="capability/architecture">2.93</entry> </labels> <annotations> <source>src/content/services/en/customer-success-manager.md</source> <route>/en/services/customer-success-manager/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/customer-success-manager.md</markdown> </annotations> </metadata> <spec> <title>Customer Success</title> <group>consulting</group> <order>1</order> <tags> <item>managed-services</item> <item>strategy</item> <item>architecture</item> </tags> <summary>One named contact across the whole lifecycle. Their most frequent contribution is retiring licences you are already paying for.</summary> <photo>two-in-conversation</photo> <photoNeed>A customer conversation across a table, both people visible, notes not laptops</photoNeed> <stub>false</stub> <draft>false</draft> </spec> <sections> <section> <heading>

What a CSM is

</heading> <body>A named contact and adviser who stays with you across the whole lifecycle of yourinfrastructure, from introduction through to continuing development. Not an escalationcontact, but someone who knows the estate before anything goes wrong. </body> </section> <section> <heading>

What it is actually good for

</heading> <body>The practical benefit is usually not the advice, it is the clearing up. Software moves on,and features that needed a separate product three years ago are included in the contractyou already hold. Finding those point solutions and retiring them is the most common savingthat comes out of this.Then there is the proactive half: raising problems before they escalate, and keeping theestate current continuously rather than renewing it in a project every three years. </body> </section> <section> <heading>

When it pays

</heading> <body>When the estate is large enough that nobody holds all of it in their head, and when yearspass between projects. That gap is exactly where licences end up running that nobody canaccount for. </body> </section> </sections> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/vmware/vmware-cloud-service-provider</ref> <score>0.34</score> </item> <item> <ref>solutions/hpe/hpe-server</ref> <score>0.34</score> </item> <item> <ref>solutions/ibm</ref> <score>0.34</score> </item> <item> <ref>solutions/ibm/ibm-power10</ref> <score>0.34</score> </item> </solutions> <alsoLike> <item> <ref>services/enterprise-architecture</ref> <score>0.67</score> </item> <item> <ref>services/it-strategie</ref> <score>0.67</score> </item> <item> <ref>posts/vmware-license-changes-2025</ref> <score>0.41</score> </item> </alsoLike> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.28</score> </item> <item> <ref>experts/matthias-frech</ref> <score>0.25</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.23</score> </item> </experts> </status></manifest>

Service · consulting

Customer Success

One named contact across the whole lifecycle. Their most frequent contribution is retiring licences you are already paying for.

Topics Managed Services 3.23 Strategy 3.54 Architecture 2.93

04Solutions

03Capabilities

267Corpus

What a CSM is

A named contact and adviser who stays with you across the whole lifecycle of your infrastructure, from introduction through to continuing development. Not an escalation contact, but someone who knows the estate before anything goes wrong.

What it is actually good for

The practical benefit is usually not the advice, it is the clearing up. Software moves on, and features that needed a separate product three years ago are included in the contract you already hold. Finding those point solutions and retiring them is the most common saving that comes out of this.

Then there is the proactive half: raising problems before they escalate, and keeping the estate current continuously rather than renewing it in a project every three years.

When it pays

When the estate is large enough that nobody holds all of it in their head, and when years pass between projects. That gap is exactly where licences end up running that nobody can account for.