Illustrative engagement. A representative scenario showing how we approach this kind of work in video games. It does not describe a specific client; outcomes are described qualitatively.
Industry overview
What is shaping video games
Game studios and publishers need player insight from concept to live operations, through playtests, monetisation research and market sizing.
- Mobile gaming reaches very wide audiences
- Playtesting reduces costly late changes
- Monetisation must feel fair to players
Client background
A game studio, working in India. This is an illustrative engagement: a representative scenario showing how we approach this kind of work, not a named client project.
- Organisation
- A game studio
- Sector
- Video games
- Team engaged
- IT & Development
- Services
- Website development, SEO services
Client challenge
The studio needed a launch site.
Research objectives
- Deliver on the brief: a website for a game launch.
- Define requirements and success criteria the solution would be tested against.
- Deliver a reliable, secure solution the team can run and extend.
Target audience
Scope: Website.
Audiences we typically reach in video games
PlayersPaying playersLapsed playersStreamers and creatorsParents of young gamers
Geographic coverage
Coverage: India. Market: India.
- India
Research methodology
An iterative delivery approach: discovery, design, build and test in short cycles, with the client reviewing each step.
- 1Brief
- 2Launch site
- 3Insight
We built a fast site with trailers and pre-registration.
Website developmentSEO services
Sampling strategy
- Users and stakeholders from every affected team took part in discovery workshops and acceptance testing.
Data collection
- Requirements were gathered through workshops, process walk-throughs and a review of existing systems and data.
Data quality & validation
- Peer code review on every change
- Automated and manual testing
- User-acceptance testing with the client
- Release checklist and rollback plan
Data analysis
- Usage and performance monitoring after launch
- Defect and support-ticket trends
- Process time before and after
Key findings
- Make it easy to sign up.
Recommendations
- Build on the core insight: make it easy to sign up.
- Track adoption and support tickets, and plan the next release from real usage.
Business impact
- Pre-registrations grew.
Impact is described qualitatively.
Deliverables & next steps
- Deployed solution with documentation and handover
- Support and maintenance plan
- Repeat the measure after changes are in place to track progress.
- A natural follow-on question: is monetisation working and fair?