Corvus Belli Experience
The public face of Corvusphere.
Corvus Belli Experience is the public-facing side of Corvusphere, designed to serve both new and existing players.
For new players, it provides a path into the games and the communities around them: discovering a game, learning how to play, finding other players and taking the first steps into the hobby.
For existing players, it provides a public place to discover and access the things they need to keep playing: tournaments, competitive rankings, overall statistics, scenarios, resources and community content.
The challenge was therefore broader than acquisition. It was about creating a coherent experience around the player, regardless of where they are in their journey.
- Role
- Engineering Lead · Product Direction
- Focus
- Product Strategy · UX · Web Engineering · Architecture
- Company
- Corvus Belli
The challenge
The project started with a simple brief: build a new public website.
The difficult part was defining what that website should actually be.
Corvus Belli has several games, a large amount of content and an established player community. New players need a way into the hobby, while existing players need practical ways to find tournaments, follow competitive seasons, explore rankings and statistics, discover scenarios and resources, and connect with the community.
Rather than treating these as separate websites or disconnected sections, I helped shape the experience around the player and the things they are trying to accomplish.
That meant understanding the different journeys through the site and creating a structure where discovery, content, community and competitive play naturally connect.
From discovery to competition
For someone discovering Corvus Belli for the first time, the experience needs to answer a different set of questions:
- What are these games?
- Which one is right for me?
- How do I learn to play?
- Where can I find other players?
- How do I get started?
For an existing player, the questions are different:
- Where is the next tournament?
- Who's leading the rankings?
- Which scenarios are available?
- What resources do I need?
- Where is the community?
The experience brings these needs together in a single public platform, combining editorial content with practical tools, competitive data and community-driven information.
Each game has its own menu sections for tournaments, scenarios and resources, each with its own search and filters, rather than a single global search box. The idea is the same: helping players find what they need without having to guess where that information lives.
The result is a platform that supports the entire journey: from discovering a game, to joining its community, to becoming an active competitive player.
From an open brief to a product
One of the most interesting parts of the project was that the brief didn't arrive as a finished product definition.
There was no complete content strategy or clearly defined acquisition journey waiting to be implemented.
I helped research the games, understand the barriers facing new players, structure the information and define the journey the site should provide.
I then worked closely with marketing to turn that direction into the final content and experience.
My role therefore went beyond engineering. I helped define what the product needed to accomplish before deciding how to build it.
My role
I led the technical development of the platform while also pushing the product direction forward.
That meant working across product, UX and engineering: defining the information architecture, shaping the user journeys, challenging assumptions about how the site should work and translating those decisions into the technical implementation.
I worked closely with marketing throughout the process, combining their expertise in communication with a product and technical perspective on how that content should work as part of the overall experience.
The result is a platform where content, UX and technology are designed around the same objective rather than existing as separate layers.
Engineering
Behind the experience is a modern web platform supporting content, search, analytics, media and integrations with the wider Corvusphere ecosystem.
The engineering work includes:
- Web application architecture and development
- Server-side rendering and performance
- Content management and publishing
- Search and content discovery
- Competitive data, rankings and overall statistics
- Media and asset handling
- Analytics and product measurement
- Integration with Corvusphere and other Corvus Belli services
- Infrastructure and production operations
The technology is deliberately in service of the experience.
The interesting engineering problem is building a platform that can support editorial, competitive and community-driven content while remaining useful to people at very different stages of their relationship with the games.
What I'm proud of
The part I'm most proud of is the coherence of the experience.
Rather than treating the website as a collection of pages and destinations, we designed it around the needs of the player.
A newcomer can discover a game and find a path into the hobby. An experienced player can arrive looking for a tournament, check the current competitive standings, explore statistics, find a scenario or resource, and get where they need to go.
Those are very different journeys, but they belong to the same ecosystem.
For me, that is what makes Experience different: it is not simply a website presenting information. It is a product designed around the different ways people interact with the games and their communities.
Contact
Let's talk.
Open to conversations about architecture, platforms and teams. The fastest way to reach me is LinkedIn.
