Use case integration process
Last updated on
To shift from a product-centric view to a solution-oriented catalog, the STACKIT Marketplace features a dedicated Use Case Catalog. This catalog translates real-world business challenges into concrete, implementable solutions powered by STACKIT technology and its partner ecosystem.
As a partner or vendor, you can publish a use case to showcase the industry value of your services, demonstrate successful deployment scenarios, and reach buyers directly through their business needs.
Onboarding process
Section titled “Onboarding process”Collaborate with the STACKIT Partner Management team to bring your use case to the STACKIT Marketplace.
-
Submit your request
Go to the Use Case Catalog, locate the Reach customers tile, and select Share your usecase to open the contact form. Enter your contact details and a brief outline of your core idea.
-
Consultation and review
A STACKIT Partner Manager contacts you to discuss your proposal, clarify requirements, and provide guidance on content structure.
-
Content delivery
Provide the detailed information and assets for the use case according to the structured content framework. For details, see Content requirements.
-
Creation and final approval
The Partner Manager creates the use case detail page in the STACKIT Marketplace. You review the draft together and give final approval.
-
Go-live
After approval, STACKIT publishes the use case and makes it visible to all customers.
Content requirements
Section titled “Content requirements”To ensure a high-quality experience for marketplace customers, structure each use case around clear business metrics, target audiences, and high-level architecture. When you prepare your content, provide the following building blocks:
Core framework
Section titled “Core framework”- Use case title: A short, business-oriented, and compelling headline.
- Industry and line of business: Clear positioning so that the right audience finds your scenario.
- Customer business problem: A clear description of the pain points, risks, or missed opportunities your customers typically face.
- Target persona or buying center: The people who benefit most or make the purchase decision, for example, COO, Head of Manufacturing, or CIO.
- Proposed solution: An explanation of how the combination of STACKIT technology and your partner services solves the problem.
- Solution architecture (high-level): A conceptual overview that shows how the components interact. You don’t need detailed technical diagrams for the initial version.
- Business value and outcomes: Measurable business impact and key performance indicators (KPI) in areas such as cost reduction, efficiency gains, risk mitigation, growth, or reduced energy consumption.
- Implementation scope and timeline: An overview of typical project phases and the expected duration of the deployment.
Delivery and ownership details
Section titled “Delivery and ownership details”- Partner ownership: The responsible system integration (SI) partner and any involved independent software vendors (ISV).
- Optional assets: Additional supporting materials, such as white papers, flyers, or customer reference quotes, to enrich the detail page.