build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | format run

$ soultec get service/customer-success-manager -o yaml$ soultec get service/customer-success-manager -o json$ soultec get service/customer-success-manager -o toml$ soultec get service/customer-success-manager -o xml$ python3 customer-success-manager.pyPS> ./customer-success-manager.ps1$ go run customer-success-manager.go$ node customer-success-manager.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: customer-success-manager locale: en labels: group: consulting capability/managed-services: 2.65 capability/strategy: 2.87 capability/architecture: 2.51 vendor/vmware: 0.98 vendor/omnissa: 1.99 vendor/hpe: 1.99 vendor/lenovo: 4.66 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 audience: [enterprise, provider] order: 1 tags: [managed-services, strategy, architecture] vendors: [vmware, omnissa, hpe, lenovo] 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. The remit reaches past the technology. It includes an analysis of your current licence estate and, where it makes sense, training for your team. The products covered are the ones we work with: VMware, Omnissa, HPE and Lenovo. - 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: 315 solutions: - {ref: solutions/vmware/vmware-cloud-service-provider, score: 0.49} - {ref: solutions/hpe/hpe-server, score: 0.49} - {ref: solutions/hpe/hpe-server/hpe-synergy, score: 0.49} - {ref: solutions/omnissa/workspace-one/workspace-one-assist, score: 0.49} alsoLike: - {ref: services/lizenzmanagement, score: 0.63} - {ref: services/enterprise-architecture, score: 0.62} - {ref: posts/vmware-license-changes-2025, score: 0.55} experts: - {ref: experts/dario-doerflinger, score: 0.42} - {ref: experts/marco-mattei, score: 0.37} - {ref: experts/steven-rodenburg, score: 0.32} search: /en/search.json
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "customer-success-manager", "locale": "en", "labels": { "group": "consulting", "capability/managed-services": 2.65, "capability/strategy": 2.87, "capability/architecture": 2.51, "vendor/vmware": 0.98, "vendor/omnissa": 1.99, "vendor/hpe": 1.99, "vendor/lenovo": 4.66 }, "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", "audience": [ "enterprise", "provider" ], "order": 1, "tags": [ "managed-services", "strategy", "architecture" ], "vendors": [ "vmware", "omnissa", "hpe", "lenovo" ], "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.\n\nThe remit reaches past the technology. It includes an analysis of your current licence\nestate and, where it makes sense, training for your team. The products covered are the ones\nwe work with: VMware, Omnissa, HPE and Lenovo." }, { "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": 315, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.49" }, { "ref": "solutions/hpe/hpe-server", "score": "0.49" }, { "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.49" }, { "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.49" } ], "alsoLike": [ { "ref": "services/lizenzmanagement", "score": "0.63" }, { "ref": "services/enterprise-architecture", "score": "0.62" }, { "ref": "posts/vmware-license-changes-2025", "score": "0.55" } ], "experts": [ { "ref": "experts/dario-doerflinger", "score": "0.42" }, { "ref": "experts/marco-mattei", "score": "0.37" }, { "ref": "experts/steven-rodenburg", "score": "0.32" } ], "search": "/en/search.json" }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "customer-success-manager"locale = "en"[metadata.labels]group = "consulting""capability/managed-services" = 2.65"capability/strategy" = 2.87"capability/architecture" = 2.51"vendor/vmware" = 0.98"vendor/omnissa" = 1.99"vendor/hpe" = 1.99"vendor/lenovo" = 4.66[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"audience = ["enterprise", "provider"]order = 1tags = ["managed-services", "strategy", "architecture"]vendors = ["vmware", "omnissa", "hpe", "lenovo"]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[[spec.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.'''[[spec.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.The remit reaches past the technology. It includes an analysis of your current licenceestate and, where it makes sense, training for your team. The products covered are the oneswe work with: VMware, Omnissa, HPE and Lenovo.'''[[spec.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 = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-service-provider"score = "0.49"[[status.solutions]]ref = "solutions/hpe/hpe-server"score = "0.49"[[status.solutions]]ref = "solutions/hpe/hpe-server/hpe-synergy"score = "0.49"[[status.solutions]]ref = "solutions/omnissa/workspace-one/workspace-one-assist"score = "0.49"[[status.alsoLike]]ref = "services/lizenzmanagement"score = "0.63"[[status.alsoLike]]ref = "services/enterprise-architecture"score = "0.62"[[status.alsoLike]]ref = "posts/vmware-license-changes-2025"score = "0.55"[[status.experts]]ref = "experts/dario-doerflinger"score = "0.42"[[status.experts]]ref = "experts/marco-mattei"score = "0.37"[[status.experts]]ref = "experts/steven-rodenburg"score = "0.32"
<?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">2.65</entry> <entry key="capability/strategy">2.87</entry> <entry key="capability/architecture">2.51</entry> <entry key="vendor/vmware">0.98</entry> <entry key="vendor/omnissa">1.99</entry> <entry key="vendor/hpe">1.99</entry> <entry key="vendor/lenovo">4.66</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> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>1</order> <tags> <item>managed-services</item> <item>strategy</item> <item>architecture</item> </tags> <vendors> <item>vmware</item> <item>omnissa</item> <item>hpe</item> <item>lenovo</item> </vendors> <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> <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.The remit reaches past the technology. It includes an analysis of your current licenceestate and, where it makes sense, training for your team. The products covered are the oneswe work with: VMware, Omnissa, HPE and Lenovo. </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> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/vmware/vmware-cloud-service-provider</ref> <score>0.49</score> </item> <item> <ref>solutions/hpe/hpe-server</ref> <score>0.49</score> </item> <item> <ref>solutions/hpe/hpe-server/hpe-synergy</ref> <score>0.49</score> </item> <item> <ref>solutions/omnissa/workspace-one/workspace-one-assist</ref> <score>0.49</score> </item> </solutions> <alsoLike> <item> <ref>services/lizenzmanagement</ref> <score>0.63</score> </item> <item> <ref>services/enterprise-architecture</ref> <score>0.62</score> </item> <item> <ref>posts/vmware-license-changes-2025</ref> <score>0.55</score> </item> </alsoLike> <experts> <item> <ref>experts/dario-doerflinger</ref> <score>0.42</score> </item> <item> <ref>experts/marco-mattei</ref> <score>0.37</score> </item> <item> <ref>experts/steven-rodenburg</ref> <score>0.32</score> </item> </experts> <search>/en/search.json</search> </status></manifest>
# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "customer-success-manager", "locale": "en", "labels": { "group": "consulting", "capability/managed-services": 2.65, "capability/strategy": 2.87, "capability/architecture": 2.51, "vendor/vmware": 0.98, "vendor/omnissa": 1.99, "vendor/hpe": 1.99, "vendor/lenovo": 4.66, }, "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", "audience": ["enterprise", "provider"], "order": 1, "tags": ["managed-services", "strategy", "architecture"], "vendors": ["vmware", "omnissa", "hpe", "lenovo"], "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\n" "infrastructure, from introduction through to continuing development. Not an escalation\n" "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,\n" "and features that needed a separate product three years ago are included in the contract\n" "you already hold. Finding those point solutions and retiring them is the most common saving\n" "that comes out of this.\n" "\n" "Then there is the proactive half: raising problems before they escalate, and keeping the\n" "estate current continuously rather than renewing it in a project every three years.\n" "\n" "The remit reaches past the technology. It includes an analysis of your current licence\n" "estate and, where it makes sense, training for your team. The products covered are the ones\n" "we work with: VMware, Omnissa, HPE and Lenovo." ), }, { "heading": "

When it pays

",
"body": ( "When the estate is large enough that nobody holds all of it in their head, and when years\n" "pass between projects. That gap is exactly where licences end up running that nobody can\n" "account for." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.49", }, { "ref": "solutions/hpe/hpe-server", "score": "0.49", }, { "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.49", }, { "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.49", }, ], "alsoLike": [ { "ref": "services/lizenzmanagement", "score": "0.63", }, { "ref": "services/enterprise-architecture", "score": "0.62", }, { "ref": "posts/vmware-license-changes-2025", "score": "0.55", }, ], "experts": [ { "ref": "experts/dario-doerflinger", "score": "0.42", }, { "ref": "experts/marco-mattei", "score": "0.37", }, { "ref": "experts/steven-rodenburg", "score": "0.32", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))
# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'customer-success-manager' locale = 'en' labels = [ordered]@{ group = 'consulting' 'capability/managed-services' = 2.65 'capability/strategy' = 2.87 'capability/architecture' = 2.51 'vendor/vmware' = 0.98 'vendor/omnissa' = 1.99 'vendor/hpe' = 1.99 'vendor/lenovo' = 4.66 } annotations = [ordered]@{ 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 = [ordered]@{ title = 'Customer Success' group = 'consulting' audience = @('enterprise', 'provider') order = 1 tags = @('managed-services', 'strategy', 'architecture') vendors = @('vmware', 'omnissa', 'hpe', 'lenovo') 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 = @( [ordered]@{ 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.'@ } [ordered]@{ 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.The remit reaches past the technology. It includes an analysis of your current licenceestate and, where it makes sense, training for your team. The products covered are the oneswe work with: VMware, Omnissa, HPE and Lenovo.'@ } [ordered]@{ 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 = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/vmware/vmware-cloud-service-provider' score = '0.49' } [ordered]@{ ref = 'solutions/hpe/hpe-server' score = '0.49' } [ordered]@{ ref = 'solutions/hpe/hpe-server/hpe-synergy' score = '0.49' } [ordered]@{ ref = 'solutions/omnissa/workspace-one/workspace-one-assist' score = '0.49' } ) alsoLike = @( [ordered]@{ ref = 'services/lizenzmanagement' score = '0.63' } [ordered]@{ ref = 'services/enterprise-architecture' score = '0.62' } [ordered]@{ ref = 'posts/vmware-license-changes-2025' score = '0.55' } ) experts = @( [ordered]@{ ref = 'experts/dario-doerflinger' score = '0.42' } [ordered]@{ ref = 'experts/marco-mattei' score = '0.37' } [ordered]@{ ref = 'experts/steven-rodenburg' score = '0.32' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32
// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "customer-success-manager", "locale": "en", "labels": map[string]any{ "group": "consulting", "capability/managed-services": 2.65, "capability/strategy": 2.87, "capability/architecture": 2.51, "vendor/vmware": 0.98, "vendor/omnissa": 1.99, "vendor/hpe": 1.99, "vendor/lenovo": 4.66, }, "annotations": map[string]any{ "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": map[string]any{ "title": "Customer Success", "group": "consulting", "audience": []any{"enterprise", "provider"}, "order": 1, "tags": []any{"managed-services", "strategy", "architecture"}, "vendors": []any{"vmware", "omnissa", "hpe", "lenovo"}, "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": []any{ map[string]any{ "heading": "

What a CSM is

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

What it is actually good for

",
"body": "The practical benefit is usually not the advice, it is the clearing up. Software moves on,\n" + "and features that needed a separate product three years ago are included in the contract\n" + "you already hold. Finding those point solutions and retiring them is the most common saving\n" + "that comes out of this.\n" + "\n" + "Then there is the proactive half: raising problems before they escalate, and keeping the\n" + "estate current continuously rather than renewing it in a project every three years.\n" + "\n" + "The remit reaches past the technology. It includes an analysis of your current licence\n" + "estate and, where it makes sense, training for your team. The products covered are the ones\n" + "we work with: VMware, Omnissa, HPE and Lenovo.", }, map[string]any{ "heading": "

When it pays

",
"body": "When the estate is large enough that nobody holds all of it in their head, and when years\n" + "pass between projects. That gap is exactly where licences end up running that nobody can\n" + "account for.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/vmware/vmware-cloud-service-provider", "score": "0.49", }, map[string]any{ "ref": "solutions/hpe/hpe-server", "score": "0.49", }, map[string]any{ "ref": "solutions/hpe/hpe-server/hpe-synergy", "score": "0.49", }, map[string]any{ "ref": "solutions/omnissa/workspace-one/workspace-one-assist", "score": "0.49", }, }, "alsoLike": []any{ map[string]any{ "ref": "services/lizenzmanagement", "score": "0.63", }, map[string]any{ "ref": "services/enterprise-architecture", "score": "0.62", }, map[string]any{ "ref": "posts/vmware-license-changes-2025", "score": "0.55", }, }, "experts": []any{ map[string]any{ "ref": "experts/dario-doerflinger", "score": "0.42", }, map[string]any{ "ref": "experts/marco-mattei", "score": "0.37", }, map[string]any{ "ref": "experts/steven-rodenburg", "score": "0.32", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}
// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "customer-success-manager", locale: "en", labels: { group: "consulting", "capability/managed-services": 2.65, "capability/strategy": 2.87, "capability/architecture": 2.51, "vendor/vmware": 0.98, "vendor/omnissa": 1.99, "vendor/hpe": 1.99, "vendor/lenovo": 4.66, }, 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", audience: ["enterprise", "provider"], order: 1, tags: ["managed-services", "strategy", "architecture"], vendors: ["vmware", "omnissa", "hpe", "lenovo"], 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\n" + "infrastructure, from introduction through to continuing development. Not an escalation\n" + "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,\n" + "and features that needed a separate product three years ago are included in the contract\n" + "you already hold. Finding those point solutions and retiring them is the most common saving\n" + "that comes out of this.\n" + "\n" + "Then there is the proactive half: raising problems before they escalate, and keeping the\n" + "estate current continuously rather than renewing it in a project every three years.\n" + "\n" + "The remit reaches past the technology. It includes an analysis of your current licence\n" + "estate and, where it makes sense, training for your team. The products covered are the ones\n" + "we work with: VMware, Omnissa, HPE and Lenovo.", }, { heading: "

When it pays

",
body: "When the estate is large enough that nobody holds all of it in their head, and when years\n" + "pass between projects. That gap is exactly where licences end up running that nobody can\n" + "account for.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/vmware/vmware-cloud-service-provider", score: "0.49", }, { ref: "solutions/hpe/hpe-server", score: "0.49", }, { ref: "solutions/hpe/hpe-server/hpe-synergy", score: "0.49", }, { ref: "solutions/omnissa/workspace-one/workspace-one-assist", score: "0.49", }, ], alsoLike: [ { ref: "services/lizenzmanagement", score: "0.63", }, { ref: "services/enterprise-architecture", score: "0.62", }, { ref: "posts/vmware-license-changes-2025", score: "0.55", }, ], experts: [ { ref: "experts/dario-doerflinger", score: "0.42", }, { ref: "experts/marco-mattei", score: "0.37", }, { ref: "experts/steven-rodenburg", score: "0.32", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 74 lines · YAML · validated at build# 113 lines · JSON · validated at build# 111 lines · TOML · validated at build# 133 lines · XML · validated at build# 127 lines · Python · read back at build, equals the JSON record# 124 lines · PowerShell · read back at build, equals the JSON record# 133 lines · Go · read back at build, equals the JSON record# 118 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/customer-success-manager.md

Service · consulting

Customer Success

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

04Solutions
03Capabilities
04Vendors
315Corpus
Two colleagues in conversation

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.

The remit reaches past the technology. It includes an analysis of your current licence estate and, where it makes sense, training for your team. The products covered are the ones we work with: VMware, Omnissa, HPE and Lenovo.

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.

Experts for this

Maybe you? Take a look at our open roles.

You might also like