Global D2C Leader: Internal knowledge platform for 1,200 employees across 30+ countries. From concept to global launch in under 3 months.

The Challenge

Growth at the company’s speed produces a specific and often underestimated problem, where institutional knowledge becomes a liability as fast as it becomes an asset. With over 1,200 employees operating across time zones, languages, and functions, the coordination mechanisms that worked at 200 people no longer scaled. Internal wins, process decisions, and operational learnings were being shared through ad hoc Teams messages and unstructured email threads, which are formats that capture nothing for anyone who wasn’t in the room. For a remote-first, cross-functional organization, this wasn’t a minor inconvenience. When teams can’t access shared context, they duplicate work, misalign on decisions, and lose the compounding benefit of organizational learning. The faster the enterprise grew, the more expensive each knowledge gap became. The company recognized it needed a centralized, scalable knowledge platform, specifically somewhere structured knowledge could live, be searched, be contributed to, and grow alongside the organization. The platform had to feel culturally aligned with the brand, being playful and human rather than corporate and clinical. And it had to drive genuine adoption and not passive availability. The client approached Gradion as a strategic partner to co-create this system, not just to build software, but to design a knowledge environment that people would actually use.

The Approach

Gradion started by observing rather than specifying. Rather than arriving with predefined wireframes or a standard knowledge base template, the team spent the design sprint understanding how the client’s people naturally connect and share across functions and geographies. Every feature that followed came from that listening. The solution delivered had four defining characteristics. First, structured and persistent knowledge spaces, where content is organized, tagged, and surfaced across teams, effectively converting tribal knowledge into shared, searchable assets. Second, a gamified content engine, where publishing, reacting, and commenting earned badges and visibility, creating a feedback loop that rewarded contribution and made knowledge-sharing a habit rather than an obligation. Third, personal digital avatars, which gave the platform a human and playful identity distinct from a generic enterprise tool. Fourth, a co-designed UI developed with the company's teams through rapid iteration cycles that drove adoption because features mapped to real behavior. The technical stack was built for scale from the start, utilizing Nuxt2 and VueJS on the frontend, with NestJS, PostgreSQL, and OpenSearch on the backend, all deployed on AWS. Agile delivery with Scrum methodology kept the team aligned throughout. The timeline was deliberately compressed, consisting of four weeks of design sprint and rapid prototyping, followed by seven weeks of development to MVP. Full launch across multiple countries followed shortly after.