PLAYER EVIDENCE. YOUR GAME’S CONTEXT.
See your game through an outside lens.
Your team chooses the reference games. GameDev Compass reads what their players value, reject and debate, then relates those signals to the game you are building. Get a report that challenges assumptions with evidence and speaks to your project, not a generic summary of someone else’s game.
You choose the reference gamesPublic Steam player reviewsConclusions tied to your project
ILLUSTRATIVE REPORT EXAMPLE VIEW
SAMPLE / AURORA PROTOCOL / STUDY
Where the planned experience meets player expectations
Project profile EXAMPLE ONLY
Selected player evidence
PROJECT CONTEXT
PLAYER EVIDENCE
Concept decisionsGame design benchmarkProduction prioritiesPublisher pitchMarketing positioningConcept decisionsGame design benchmarkProduction prioritiesPublisher pitchMarketing positioning
THE BLIND SPOT INSIDE EVERY TEAM
Your team knows the vision. What might it be too close to see?
Studios make hundreds of decisions with limited time. Public reviews of comparable games offer an outside perspective, but reading them one by one rarely reveals what applies to your concept, audience and scope.
When evidence stays fragmented
01
A few memorable reviews stand in for the broader sample
02
Strong opinions get mistaken for proven demand
03
Insights end as a list of complaints about other games
?
A reading grounded in your project
01
Compare praise, rejection and contradictions across your chosen games
02
Relate each signal to the experience and constraints you documented
03
Turn findings into a focused conclusion and, where available, project proposals
HOW THE STUDY WORKS
You choose the question and the references. The report does the connecting.
Control what enters the study, from your project context to the kinds of player reviews included. Every report states the sample it used.
01
Give the report your context
Describe your game’s vision, audience, loop, systems and scope in a structured profile. Write it yourself or use a PDF to draft the fields with AI.
A GDD is optional; you review the profile before using it.02
Choose what to investigate
Pick a report objective, one to six reference games and a positive, negative or mixed review focus. You can also prioritize by playtime and community votes.
The reference games are always your choice.03
Take a decision-ready reading
See patterns and exceptions, the relevant player evidence, and a conclusion connected to your project. The Explorer and Legend plans can also propose changes for your review.
Project proposals are applied only when you approve them.WHY YOUR PROJECT CHANGES THE ANSWER
A popular feature elsewhere is only useful if it fits your game.
Players may praise long progression in a reference RPG. If your game promises a short narrative journey, copying that grind could weaken the experience. The project profile gives the report your vision and scope, so it can discuss the difference.
YOUR PROJECT PROFILE
Game vision
Audience and references
Desired experience
Core loop
Mechanics and systems
Progression and retention
World and narrative
Positioning
Scope and constraints
Open decisions
YOUR GAME× PLAYER VOICES
Read the references through the game your team is building.
PROJECT-LED REPORT
01
What players praised or rejected in the selected games
02
Where that evidence supports or challenges your current choices
03
Which ideas fit the intended experience and production scope
04
What remains a hypothesis instead of a proven market demand
A DIFFERENT REPORT FOR EACH DECISION
The question changes the reading. It should change the answer too.
Each report has its own analytical focus, language and conclusion. Choose the job the study needs to do for your team.
CONCEPT01
Pre-production
Examine whether the promised experience, core loop and scope make sense beside player reactions to comparable games.
Concept tensions, opportunities and scope questions
DESIGN02
Game design benchmark
Identify principles behind mechanics players enjoyed or rejected, then assess how they might translate into your game.
Design ideas to adapt, test or avoid
BUILD03
Production
Look for recurring friction, quality expectations and systems worth protecting as the build takes shape.
Better-informed production priorities
PUBLISHER04
Pitch
Find a defensible way to explain the project’s position, references and differences to partners.
A clearer, evidence-aware project case
AUDIENCE05
Marketing insights
Hear the words players use for desired experiences, emotional hooks and objections in your chosen category.
Positioning and messaging grounded in player language
TRACEABLE PLAYER SIGNALS
Know what the conclusion is based on.
The report draws from public Steam reviews of the selected games and shows the size and limits of its sample. Relevant excerpts support the analysis in the report language.
01
Positive, negative or mixed
Investigate what players valued, what they rejected or the tension between both.
02
Playtime as context
Contrast early impressions with feedback from players who spent longer with a game.
03
Community votes
Prioritize reviews the community found useful or look beyond the most visible opinions.
04
Up to six references
Compare patterns and exceptions across the games you actually selected.
05
Readable excerpts
See selected player statements in the report language, with their meaning preserved.
06
Relevant market indicators
Use price, activity, playtime and review volume as context when they help answer the report’s question.
These are signals from a chosen sample, not proof of demand, sales or how every player will respond to your game.
Your team sees the game it intends to build. Players describe the experiences they actually had in the games you chose. Put those perspectives in conversation.
Give the next meeting a better starting point.
A conclusion linked to the project makes the study useful to the people who must make the call. It highlights what the evidence supports, what conflicts with the current plan and what still needs validation.
Indie founders: challenge scope and differentiation earlyDesign and production: discuss friction against the intended experienceMarketing teams: sharpen the promise with player languagePublishers and partners: examine the project case alongside its references
DEPTH THAT MATCHES THE DECISION
Start with a focused read. Go deeper when the decision demands it.
All levels use real player evidence. Higher tiers expand the sample and comparison, add game-by-game reading, and increase the depth of the project conclusion and proposals.
Scout
A focused synthesis and conclusion for one project
Explorer
Individual game readings and focused project proposals
Legend
Fuller evidence, deeper conclusion and broader supported proposals
THE PEOPLE BEHIND THE PRODUCT
Built by people who know game production and the work of bringing games to market.
We built GameDev Compass around a practical gap: teams need a way to hear players outside their own project and decide what that means for the game in front of them.
01
GAMEDEV COMPASS / 01
Rafael Giannella
Co-founder · Marketing, Communication & Game BusinessConnects communication, marketing, data, and business development to help studios position their projects, build communities, and turn market understanding into growth decisions.
Game marketingCommunication strategyBusiness development
View LinkedIn profile02
GAMEDEV COMPASS / 02
Eduardo Sugawara Enrietti
Co-founder · Structure, Production & Business IntelligenceConnects project structure, game production, and Business Intelligence to turn complex evidence into clear priorities and executable decisions for game teams.
Project structureGame productionBusiness Intelligence
View LinkedIn profileGame production and market communication meet in one question: what should this team do with the evidence it has?
BEFORE YOU START
The questions a game team should ask.
01Whose reviews does the platform analyze?+
Public reviews of the reference games you select. Your own released game can be one of those references if it has reviews, but the platform does not automatically collect private feedback or playtest data from your project.
02Is this an unbiased verdict on my game?+
It offers an outside perspective grounded in player statements rather than the studio’s internal narrative. Your selection of games and the available review sample still shape the result, so the report presents its scope and limitations instead of claiming objective certainty.
03Do I need a finished GDD or playable build?+
No. You can write a structured project profile manually. An optional PDF can help draft it, and you review the fields before using them as report context.
04Can I focus only on complaints or praise?+
Yes. A negative study goes deeper into rejection and things to avoid; a positive study examines valued experiences more closely. A mixed study balances both while keeping the report objective.
05Will the report change my project automatically?+
No. Where the plan supports project proposals, you decide whether to apply each one. The original project content stays under your control.
06Can I share the results with my team or a publisher?+
A completed report can be shared through a read-only link or exported as PDF. Private project proposals stay inside your account.
07What happens to the GDD I upload?+
The PDF is used to draft the structured project profile and is queued for deletion after processing. You review the profile before using it in a report. Reports are private unless you create a read-only sharing link.
08Does it replace playtesting or prove market demand?+
No. It helps form better questions and priorities from public evidence around reference games. Test your own game with players to validate how those insights translate to your project.
BRING AN OUTSIDE VIEW IN
Make the next decision with more than your team’s assumptions.
Start with the games you consider relevant. See what their players reveal, and what those signals could mean for the game you are building.