Project mentoring
Describe the game, current build and the decision you need help with. Mentoring scope can cover focus, production priorities and feedback; it does not guarantee investment or a publishing contract.
Bintangquest
Prepare a pitch
Describe the playable state, intended player and the team’s next production milestone. Separate completed work from planned features, and explain which support would make a practical difference to the project.
Details to check against your plan
Publishing readiness
A useful assessment considers audience, build stability and presentation materials. Rights, financial terms and distribution responsibilities require a separate agreement.
Showcase preparation
A short demo and a clear product description help people understand the experience. Confirm platform, audience and permissions before sharing unreleased material.
Pitch development
A pitch should explain the game, team responsibilities and what support is sought. Claims about traction, budgets and progress should come from the developer’s actual records.
A pitch built around what exists today
Describe the playable state, intended player and the team’s next production milestone. Separate completed work from planned features, and explain which support would make a practical difference to the project.
Clarify ownership and the materials available for review. Showcase, mentoring, distribution and investment have different commitments; discuss them separately rather than treating visibility as a publishing agreement.
A pitch is a decision document
Explain the core experience, intended audience, current build and the support you are asking for. Use actual development records for budgets, traction and milestones. A reviewer should understand what is playable now and what remains planned. Mentoring and readiness work can clarify that story without promising a publisher agreement, funding or international commercial success.
Show the core player experience before expanding the pitch into every planned feature. Explain what the current build demonstrates and which parts are still assumptions. Include a realistic next task and the evidence needed to evaluate it. This gives reviewers a clearer basis for feedback and helps the team decide which discussion belongs to production, mentoring or a separate commercial agreement. Return to those points before confirming so the scope is assessed on a consistent basis.
Introduce the project carefully
Start with a short description, team contact and development stage. A public build or pitch link is enough for the initial conversation. Do not send source code, confidential contracts or assets without agreeing a secure review process.