Hiring a game developer or studio without checking references is like shipping a game without QA—you're asking for disaster. A developer's past work tells you far more about reliability, code quality, and communication than a portfolio website ever will.
Why References Matter in Game Development
Game development projects are complex, expensive, and deadline-sensitive. A studio that delivered a beautiful mobile game on time and under budget for one client is fundamentally different from one that missed deadlines or shipped with critical bugs. References give you direct insight into how a developer actually performs in real conditions—not their best-case scenario pitch.
References also reveal soft skills that matter enormously: whether the team communicates regularly, handles scope creep professionally, responds to feedback, or pivots when a feature isn't working. You want to know if they've shipped multiple projects successfully, not just one lucky win.
What to Ask References
Don't just tick a box and move on. Ask specific, open-ended questions that reveal patterns:
- Project scope and timeline: "What was the scope of the project they delivered? Did they hit their deadline? If not, why?"
- Budget adherence: "Did the final cost match the original estimate? Were there unexpected expenses?"
- Code quality: "Did you encounter bugs post-launch? How did they handle post-launch support?"
- Communication style: "How often did you hear from the team? Were updates transparent?"
- Team stability: "Did the same people work on the project throughout, or was there turnover?"
- Problem-solving: "When something went wrong—and something always does—how did they handle it?"
- Platform-specific performance: "If it's a mobile game, how did it perform on older devices? Console game? Did frame rate hold?"
Listen for hesitation or vague answers. A reference who struggles to give specifics may be protecting a mediocre relationship.
How Many References to Check
Aim for at least three references, ideally from different project types or platforms. If a developer has only done one game, that's a red flag in itself—they lack experience handling variety.
Ask specifically for:
- One recent project (within the last 12 months)
- One project of similar scope or budget to what you're planning
- One project in your target platform (if you're building for consoles, ask about console experience, not just PC)
Red Flags to Watch For
Certain patterns in reference conversations should trigger caution:
- References are vague about deadlines or budgets
- The studio won't provide more than one reference
- References mention "creative differences" repeatedly—sometimes legitimate, but watch for patterns
- High turnover is mentioned; losing key staff mid-project causes real problems
- References describe communication as "infrequent" or "only when we checked in"
- Post-launch support was minimal or nonexistent
- The same bug or issue appears in multiple referenced projects
Verify Their Portfolio Claims
Ask references to confirm specific details about games you've seen in the portfolio: launch dates, platforms, player count, revenue (if public), and critical reception. A studio might show you a game that wasn't actually their primary responsibility, or one that launched years ago with outdated tech.
For mobile games, check app store reviews and ratings yourself. For console or PC titles, look at metacritic and player forums. If a reference praises a game but players trashed it, that's misalignment.
Price Ranges and Reference Consistency
Game development costs vary wildly—a 2D mobile casual game might cost $15,000–$50,000, while an indie 3D title runs $100,000–$500,000+, and AAA-adjacent projects exceed $1M+. Ask references what their project cost and timeline. If a developer quotes you $30,000 for a scope that cost $200,000 elsewhere, that's either aggressive underbidding (risky) or misunderstanding scope.
Using Platforms to Streamline Checks
Checking references manually takes time. Platforms like Mercoly let you compare and find trusted game development providers in one place, with verified portfolios and transparent client feedback—saving you from cold-calling studios and hoping their references are honest.
Frequently Asked Questions
Q: Can I trust references a studio provides, or should I hunt for independent ones? A: Always ask for provided references first, but supplement by reaching out to clients listed in published case studies or press releases. Studio-provided references are naturally more favorable, but they're still valuable—just one data point.
Q: What should I do if a reference describes major scope creep? A: Scope creep is common in game development, but how it's handled matters. If the studio communicated changes transparently and charged fairly for additions, that's normal. If they absorbed extra work and the reference felt mismanaged, that's concerning.
Q: How far back should I look at a developer's project history? A: Prioritize the last 3–4 years. Technology and industry practices shift, so a successful game from 2015 doesn't guarantee current capabilities. However, older projects show consistency if the same team is still involved.
Start checking references today—your game's success depends on the team behind it.