Internal R&D: a consumer social platform with tournament hosting for a gaming audience

The challenge

Most of our work is delivered inside a client's estate, against a client's roadmap. That record proves we can extend and support someone else's platform. It does not, on its own, prove we can take a consumer product from a blank page.

gameit365 was our own answer to that. No client, no external brief, no inherited codebase. The subject we chose was gaming: a social platform for players, with tournament hosting built alongside the social features.

The subject was chosen for the engineering it forces. A social product depends on how identity, content and interaction between users hold together. A tournament adds state that participants watch closely, because entries, fixtures and results are contested by the people using them.

What we built

• A social platform for a gaming audience, built in-house from a blank page rather than assembled on a client's existing system.
• Tournament hosting: creating a competition, taking entries, and progressing it through to a result.

The product is no longer in service and is retained as a reference build.

How we worked

Self-directed internal research and development. No client, no external stakeholders, no commercial deadline. Scope and priorities were set internally.

Outcomes

• Consumer product capability held in-house. We specified, designed and built a social product ourselves, rather than extending one a client already owned.
• Competitive tournament mechanics built and working: competition creation, entry handling and progression to a result.
• Direct experience of consumer social product design, which is a different problem from the enterprise and B2B systems that make up most of our client work.
• No usage, revenue or performance figures are published for this product. It was internal R&D and is archived.