Contact & Intake
Send a brief. We'll read it.
We don't do generic contact forms. If you're building a game, you need focused feedback. Here’s how to reach us and what we need to know.
Status: Active
We are currently reviewing new partnerships for Q3 2026. Project inquiries for Q4 and beyond are welcome.
Direct Line
Bypass the noise. Use this.
Note: We prioritize email for all initial contact. This creates a written record and allows our team to review your brief thoroughly before a call.
Media Kit
Password required
High-res logos, key art, and studio b-roll are available for press. If you're covering Brandaxo, request access and we'll send credentials.
Project Brief
Fill this out. Seriously.
The best briefs get the fastest, most useful responses. Answering these questions helps us understand if we're a fit and lets us give you better advice upfront.
Describe your game concept in 200 words. What is the player's primary action and reward?
Attach 3-5 reference images (mood boards, similar games, concept art). What visual tone are you aiming for?
Target platform (iOS, Android, PC, Console), engine preference (Unity, Unreal, Custom), and performance targets.
A realistic range (e.g., $50k–$100k) and desired launch window (e.g., Q2 2027).
Solo developer, funded indie, or established studio? What’s your current progress?
What specific challenge or opportunity led you to reach out? This helps us tailor our feedback.
Decision Lens: What We Optimize For
Optimizes For
- Clear, concise communication
- Reference material (art, games)
- Defined constraints (platform, budget)
Sacrifices
- Speed for vague briefs
- Detail for "open-ended" questions
- Free consulting without a defined project
Changes Our Mind
- Complete portfolio of shipped titles
- Clear IP ownership & legal framework
- Alignment on risk tolerance
Our Berlin Base
Our creative hub in Kreuzberg.
We are a remote-first team, but our core collaboration happens here. The studio is designed for deep work and focused playtests.
Accessibility
The building is wheelchair accessible. Please inform us of any specific needs when scheduling a visit.
Time Zone
We operate on CET (UTC+1). Our core collaboration hours are typically 9:00 – 18:00.
Kreuzberg, Berlin
Process
What Happens Next
No black box. Here's the exact timeline from inbox to estimate. We designed this to respect your time and ours.
Step 1: Acknowledgment
You receive an auto-acknowledgment email with a ticket number within 1 hour.
Step 2: Initial Review
Our lead developer reviews your brief for fit and scope. This takes 2–3 business days.
Step 3: Discovery Call
If it's a fit, we'll send a Calendly link for a 30-minute call to dig deeper.
Step 4: Rough Estimate
Based on the call, we provide a rough scope & estimate. This takes 5–7 business days.
Common Pitfall: Vague Briefs
Inquiries without references, clear platforms, or budget ranges often lead to a delayed response (or a 'not a fit' email). Taking 10 extra minutes to detail your vision increases your reply rate significantly.
Scenario Vignette
"I sent my brief on Tuesday. What happened next?"
Tuesday, 10:17 AM: Kai, a solo developer, emails a one-paragraph description of his physics-based puzzle game. No references, no platform listed.
Tuesday, 11:05 AM: He gets an auto-acknowledgment with ticket #AXO-782.
Friday, 2:30 PM: After review, the response lands. "Kai, thanks for reaching out. We can't provide useful feedback on the brief as presented. Please provide 1) 3 references of puzzle games you admire, 2) Target platform (mobile/PC), and 3) Your core mechanic in one sentence."
Result: The cycle starts over. The initial delay wasn't a lack of interest—it was a lack of data.
The Fix
A proper brief with references, platform, and a one-sentence core loop would have moved Kai to the top of the review queue. The "Project Brief" section above is designed to prevent this exact delay.
Revisit the Brief TemplateReady to start the conversation?
Use the direct line for partnerships or the project brief for a new development inquiry. We read every word.
Constraints & Boundaries
Assumptions
- You own the IP or have rights to collaborate.
- Budget is defined or reasonably estimable.
- You have a playable prototype or deep design doc.
Boundaries
- We do not work for revenue-share only.
- We do not provide free consulting or spec work.
- We do not engage with NSFW or gambling content.
What Changes Us
- Verifiable track record on similar projects.
- Clear legal framework for IP & payment.
- Alignment on post-launch support expectations.