What's your next game's first five minutes?
Tell us about your project. We read every submission within two business days and respond with actionable next steps, not canned replies.
Tip: For urgent matters, start your subject line with "[URGENT]".
Our Collaboration Framework
A transparent roadmap from first contact to handoff.
Discovery Call
30-minute video chat to align on vision, scope, and technical feasibility. No cost, no pressure.
Proposal & Scope
Detailed document outlining deliverables, phased timeline, and investment. Includes a built-in 'phase gate' review.
⚠️ Constraint: We avoid 'indefinite' timelines. Every phase has a measurable milestone.
Pre-Production
Lock in art style guides, core mechanics, and technical architecture. The blueprint is final.
Production Sprints
Bi-weekly builds. We use a shared dashboard (e.g., Jira, Notion) for complete transparency on progress and blockers.
Polish & Launch
Final QA, platform submission, and documented post-launch support. We define 'done' together.
Process Glossary: The Diglino Lens
- Soft Launch
- A controlled release to a limited audience (e.g., 10k users) to gather telemetry before a global push. We view this as a risk-mitigation tool, not a marketing event.
- Global Release
- Full-scale launch with all marketing live. This is where we expect stable metrics; the soft launch de-risks this.
- Production Sprint
- A two-week work block with a fixed output goal (e.g., 'UI for three menu screens'). Not a 'crunch' period; velocity is sustainable.
- Phase Gate
- A formal review checkpoint before moving to the next funding tranche. Prevents scope creep and forces a go/no-go decision.
Scenario Vignette
"A founder comes to us with a polished pitch deck and no code. We schedule a Discovery Call to discuss their first-playable timeline. It's clear they've budgeted for 6 months, but their scope (open world, procedural generation) suggests 12. We use the Scope document phase to help them re-prioritize features into a Minimum Viable Product (MVP) that can launch in 8. This transparency in timeline is what builds trust."
Open Project Focus & Trade-offs
Current collaborations we are actively seeking, and the explicit constraints that define a fit.
Currently Seeking
- → Art Direction Partner: For a narrative-driven puzzle game. Must excel in 2D hand-drawn style and environmental storytelling. Trade-off: We prioritize art cohesion over rapid asset variety.
- → Technical Lead: For optimizing a Unity pipeline for a mid-core mobile title. Focus on memory management and frame rate stability.
Open For (Principles)
- • Publishing Inquiry: We focus on games with a strong, replayable core loop and a clear, player-first monetization strategy (not predatory).
- • Technical Partnerships: We collaborate on R&D for engine-specific tools (Unreal/Unity) that solve a recurring problem in our pipeline.
Not a Fit (Trade-offs We Won't Make)
To maintain quality and focus, we decline specific project types. This isn't a judgment on the work, but an alignment on our studio's capacity and expertise.
- Pure asset creation (characters, environments) without a full project context.
- Porting legacy titles (pre-2015) due to technical debt and platform compliance.
- Hyper-casual clones with no unique mechanic or retention hook.
"We are looking for partners who are obsessed with the player's first five minutes."
The Diglino Standard: Communication & Robustness
Method Note: Evaluating a Partner
When we evaluate a potential partner, we look for three specific signals of robustness, not just technical skill. This method is how we assess our own fit for a project.
- 1. Process Transparency
- Can they articulate their phased approach and the decision gates between them? A clear process protects both parties from scope creep.
- 2. Constraint Awareness
- Do they mention trade-offs? (e.g., "We built X, but it caused Y, so now we do Z.") This indicates real experience, not theoretical planning.
- 3. Communication Cadence
- Is there a defined rhythm (bi-weekly syncs, shared dashboard) or is it ad-hoc? Predictable updates reduce anxiety and allow for course correction.
Response & Logistics
- Response Time: We acknowledge all inquiries within 2 business days. A detailed response may take up to 5 days.
- Channels: Email and scheduled video calls (Zoom, Google Meet). We do not use social media DMs for business.
- File Sharing: We use secure, cloud-based platforms (Google Drive, Frame.io, Perforce) for all asset exchange.
Micro-Scenario
"You sent a proposal two days ago and haven't heard back. Before you panic: check your spam folder. If nothing, send a single, polite follow-up email with 'Re:' in the subject. Our inbox is managed by a human, not a bot. A polite nudge is appreciated."
Studio Context
We are based in Warsaw, Poland. Our team is fluent in English and operates on Central European Time (CET/CEST). All meetings are scheduled with clear agendas and shared notes.