Gametrax logo Gametrax

> Location & Signal

Static embed • Rome, Italy

Command Central

Our studio operates as a remote-first collective with a physical anchor in Rome. Use the channels below to initiate a secure transmission. All coordinates are verified for operational integrity.

Primary Channels

Operational Context

We are a studio of 12 specialists spread across 5 time zones. Our Rome hub serves as the creative anchor for collaborative sessions and client onboarding. All digital communication is encrypted and logged for project integrity.

> Decision Lens: Inquire Effectively

Before you reach out, use this checklist to align your inquiry with our specialization. This optimizes our response time and ensures we can provide meaningful feedback.

Problem Clarity

  • Define the specific gameplay gap
  • Identify your target player persona
  • Anchor in a current game or genre

Optimizes: Precision of analysis

Scope Alignment

  • Concept, UI audit, or art direction
  • One-time analysis or ongoing partnership
  • Estimated budget range (helpful)

Optimizes: Proposal relevance

Outcome Focus

  • What does success look like?
  • Any hard deadlines or milestones?
  • Current blockers or constraints

Optimizes: Solution fit

Trade-off: Depth vs. Speed

This checklist may take 2 minutes to review, but it prevents the most common pitfall: a vague inquiry that leads to a generic response or a declined project. We prioritize clients who have done their homework. If your idea is too nascent for this checklist, a paid discovery phase is our recommendation.

> Incoming Signal: Scenario 7-42

Context: A solo developer building a rogue-lite deckbuilder. Core loop is functional, but tutorial metrics show 68% drop-off in the first five minutes.

Inquiry Sent: "We need UI/UX design to reduce drop-off. Target: Premium mobile players. Budget: $15k, two-week sprint."

Our Response (within 4 hours): "We’ve worked on 3 similar mechanics-heavy games. The two-week sprint is viable for a UI audit and prototype. Let’s schedule a 20-minute call to review your current build and critical data points."

Outcome: The developer provided a screen-share session and a build. We delivered a prioritized list of 12 UI interventions, focusing on clarity of resource paths and mandatory player feedback. The project moved into a paid discovery phase.

What Made This Work

  • Specific Problem: Defined the drop-off point and target audience.
  • Budget & Timeline Clarity: Allowed us to scope immediately.
  • Technical Context: The build was available for review.

Generic inquiry: "Can you help us make our game better?" (Response time: 24h+)

> Post-Transmission Sequence

A transparent view of our response pipeline. This is a log, not a promise—variance is expected based on project load and complexity.

Auto-Reply (0-5 min)

A confirmation email with your project reference number. All future communications will cite this code.

Human Triage (24h)

A lead designer reviews your materials. If scope is unclear, we may request a 15-minute clarifying call.

Discovery Call (3-5 days)

If we proceed, a 30-minute paid discovery call ($250) to align on goals, constraints, and success metrics.

Proposal (3-5 days post-call)

A detailed proposal with scope, timeline, investment, and deliverables. No speculative work is generated.

Common Pitfalls

The Vague Brief

"Make it better" is unactionable. Without a target metric, we cannot measure success or propose a specific intervention.

Expecting Free Concepts

Our proposals are based on paid discovery. We do not perform speculative work as it compromises analysis integrity.

Instant Messenger Inquiry

We do not conduct project discussions via Discord/Slack. This policy ensures documentation and reduces communication overhead.

These constraints protect your project's scope and our team's focused work cycles.

Ready to Transmit?

Prepare your materials using the Decision Lens above. We review inboxes daily at 10:00 and 16:00 CET.

Open Email Composer

Will generate a template with placeholders.