Partner Success

Partner onboarding, enablement, and ongoing support resources.

Welcome to the Partner Success resources for Stash partners. This section will cover onboarding, enablement, and ongoing support workflows.

At Stash, Partner Success is more than support — it’s a strategic partnership focused on helping your business integrate successfully, optimize performance, and grow over time.

Our approach blends structured onboarding, clear communication, dedicated points of contact, and a performance-driven process to ensure lasting value beyond go-live.

What partnering with Stash means

Partnering with Stash means working with a team that:

  • Aligns with your business goals
  • Provides proactive insights, not just reports
  • Supports both technical and strategic needs
  • Collaborates with your team to maximize monetization and efficiency

Rather than a typical “partner success” experience, Stash delivers ongoing performance partnership tailored to your product and roadmap.

Onboarding & integration

Start of onboarding

Onboarding begins with:

  • A dedicated Slack (or Discord) channel

  • A formal kickoff call

  • Introductions to your Stash team:

    • Account Manager
    • DevEx (Developer Experience) Engineer
    • Product Performance Lead

These initial steps ensure clear alignment and expectations from day one.

What to expect

During onboarding you will receive:

  • A structured integration walkthrough
  • A go-live plan with milestones
  • SLA clarity and contact protocols
  • Guidance tailored to your product and monetization model

Common Integration Misconceptions

Studios often assume:

  • Integration is purely technical
    → In reality, it also drives monetization architecture.
  • We only provide reporting
    → We provide recommendations and growth strategy.
  • All product decisions are partner-driven
    → We proactively contribute ideas and optimizations.

Reference Guides

For technical details, see:

  • Webshop Integration Guide
  • Stash Pay Integration Guide
  • Launcher Integration Guide

These guides support your technical team while the Partner Success team focuses on partnership and outcomes.

Channels we support

We primarily use:

  • Slack
  • Discord (as needed)

Email threads can also be used for formal discussions or escalations.

Response Mechanisms

  • Submit questions or issues in Slack
  • We create internal tickets and track resolution
  • We aim to support your timezone where possible

Your dedicated Account Manager and DevEx Engineer are your go-to contacts for coordination and troubleshooting.

Ongoing performance & growth

After launch, Partner Success transitions to performance partnership.

What this means

We run a continuous optimization loop:

Baseline → Diagnose → Prioritize → Experiment → Measure → Iterate → Repeat

This process ensures we not only report on performance, but actively help you improve it.

Engagement Cadence

  • Weekly or bi-weekly performance readouts
  • KPI reviews and planning
  • Prioritized experiment planning

What We Need From You

To hit the ground running, we ask for:

  • A single internal owner (PM or LiveOps Manager)
  • Clear KPI definitions
  • Authority to execute shared strategies

How We Prioritize Work

We prioritize initiatives by:

  • Business impact
  • Friction reduction
  • Experiment speed and cost
  • Highest value segments

A/B Testing

Our A/B testing process includes:

  • Hypothesis definition
  • Success metric selection
  • Audience segmentation
  • Runtime and guardrails
  • Results publication in performance readouts

Recommendations vs reporting

Stash provides both:

  • Clear performance reporting
  • Actionable recommendations
    • Offers
    • Loyalty mechanics
    • Player communications
    • Monetization levers

This ensures insights are directly tied to impact.

Feature requests & roadmap collaboration

Can you request features?

Yes — we welcome partner requests.
These are evaluated through a collaborative prioritization framework based on:

  • Urgency
  • Potential impact
  • Overall platform alignment

What does “access” mean?

When partners ask about access, it can include:

  • Dashboard access
  • Analytics and metric visibility
  • API/Dev portal access
  • Dedicated reporting

The specifics can vary depending on partner setup and needs.

How is this guide?