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
Give a promising game a clearer next chapter.
From a playable idea to a considered publishing conversation.
Developer support
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.
Protect the project while sharing it
Before sending a build or pitch, confirm who may access it and what rights are involved. Publishing discussions can cover responsibilities, revenue terms, territories and marketing scope; these belong in a negotiated agreement. A showcase opportunity and a commercial publishing deal are different outcomes and should never be presented as interchangeable.
The support model should distinguish creative feedback, production preparation and commercial discussions. A showcase can create visibility without establishing a distribution or funding agreement. Developers should know what materials are requested, how they may be used and which decision follows the review. Clear boundaries allow a team to discuss its next milestone without giving up control of the project through an unclear process. A clear description helps identify the next step and separate preparation from a confirmed commitment.
Prepare a pitch
Prepare your objective, preferred timing and the information needed to assess the scope. Avoid sending unnecessary personal data, passwords or material you do not have permission to share. If the enquiry concerns a minor, a parent or guardian should handle the arrangements.
Developer support
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.
Project milestones
Describe the playable idea
Describe the purpose, participants or project scope. This helps us select a suitable format rather than promise an outcome before understanding the brief.
Identify the project stage
Availability, price, timing and responsibilities are confirmed before the commitment. Browsing this website or sending an enquiry does not itself create an order or booking.
Prepare the pitch materials
The agreed plan defines the responsibilities, schedule and how changes are handled. Cancellation and concern-handling terms belong in the confirmation.
Discuss the next milestone
At the end, check the agreed scope and any information needed for continued use. A follow-up conversation does not automatically create another paid commitment.
A closer look at Bintangquest
Bintangquest focuses on a defined business purpose: indie game incubator and publishing support. We separate the offer, preparation and agreement so that visitors can understand the next step. A clear description is more useful than an unsupported promise about results, availability or experience.
An indie project can be promising while still needing a clearer production plan. A playable prototype, a pitch and a release-ready build answer different questions. Start by describing what exists today and what the team needs next. This makes a mentoring or publishing discussion more useful than a presentation that blends completed work with future ambition.
A small build with a clear creative direction.
An indie project becomes easier to discuss when a playable moment, a concise concept and an audience focus point in the same direction. These materials show how the idea behaves in practice.
Project preparation brings creative scope, production priorities and presentation together. A focused build provides a common reference for mentoring and publishing-readiness conversations.
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.