Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.esportshub.io/llms.txt

Use this file to discover all available pages before exploring further.

The customer stories page is where we publish the proof: how individual orgs, creators, and brands have used Esports Hub services and what they got out of it. Each story includes the team, the work, the timeline, and the outcome.

Browse customer stories

Real-world case studies from the orgs and creators we’ve worked with.

​
What’s in a story

Every entry on the page is a short case study with the same shape:
  • Who, the org, creator, or brand. Photo, social links, scene/region.
  • What we did, contracts, social media management, Discord bots, websites, partnerships, mentoring. Often more than one.
  • Timeline, when the work happened and how long it took.
  • Outcome, what changed for them. Impressions added, contracts closed, members signed, hours saved. Concrete numbers where we have permission to share them.
If a story has a logo lockup, follower count, or revenue figure, the customer signed off on us publishing it. Anything sensitive is summarised in ranges instead of exact numbers.

​
How to become a featured story

If you’ve been a customer for a meaningful chunk of time and have a result worth showing, the partnerships team will sometimes reach out to ask if you want a case study. You can also raise your hand by:
  1. Opening a Partnership Inquiry ticket on Discord
  2. Mentioning the case study interest in the message
  3. Sharing a one-paragraph summary of the work and the outcome
We don’t pay for stories or expect you to write the copy yourself. The Esports Hub team writes the case study, sends it to you for approval, and publishes once you’ve signed off.

​
Anonymized results

If the work was confidential (contracts that include NDAs, sensitive sponsor arrangements, etc.) we can publish an anonymized version with the org name replaced. These appear on the page tagged as anonymous and use sector-typical figures instead of exact ones. For most public-facing work (social media management, websites, Discord bots) the customer’s name is part of what makes the story useful, so we encourage non-anonymous publication when the customer is comfortable with it.