Major update to chorus.services platform
- Extensive updates to system configuration and deployment - Enhanced documentation and architecture improvements - Updated dependencies and build configurations - Improved service integrations and workflows 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
115
brand-assets/packs/investor/kit.md
Normal file
115
brand-assets/packs/investor/kit.md
Normal file
@@ -0,0 +1,115 @@
|
||||
An investor pack (or investor pitch kit) is more business-focused than a media pack. Its goal is to **convince investors that your project is viable, scalable, and worth funding**. Since you’re a solo indie developer, it should also realistically communicate risk and show how you plan to manage it. Here’s what you should include:
|
||||
|
||||
---
|
||||
|
||||
### **1. Cover / Intro**
|
||||
|
||||
* Project name and logo.
|
||||
* Tagline or short mission statement.
|
||||
* Eye-catching visuals (game screenshot, concept art, or prototype GIF).
|
||||
|
||||
---
|
||||
|
||||
### **2. Executive Summary**
|
||||
|
||||
* 1–2 paragraphs summarizing the project.
|
||||
* Why the project exists (problem/opportunity).
|
||||
* What makes it unique or innovative.
|
||||
* Current status (alpha, prototype, pre-launch).
|
||||
* Funding needs and what the investment will achieve.
|
||||
|
||||
---
|
||||
|
||||
### **3. The Problem / Opportunity**
|
||||
|
||||
* Define the gap your project fills.
|
||||
* Why this matters now (market trends, audience demand).
|
||||
* Evidence of market interest (community size, early sign-ups, beta testers, Steam wishlists, social media engagement).
|
||||
|
||||
---
|
||||
|
||||
### **4. The Solution / Product**
|
||||
|
||||
* Game description: genre, mechanics, art style.
|
||||
* Unique selling points: what makes it stand out.
|
||||
* Screenshots, concept art, or short gameplay clips.
|
||||
* Current development stage and roadmap.
|
||||
|
||||
---
|
||||
|
||||
### **5. Market Analysis**
|
||||
|
||||
* Target audience: demographics, interests, gaming habits.
|
||||
* Market size and growth potential (cite reliable sources).
|
||||
* Competitor analysis: similar games or projects, and why yours is better/different.
|
||||
|
||||
---
|
||||
|
||||
### **6. Business Model**
|
||||
|
||||
* How you plan to generate revenue:
|
||||
|
||||
* Game sales, subscriptions, in-app purchases, DLC, merchandising, crowdfunding.
|
||||
* Pricing strategy.
|
||||
* Any partnerships or distribution plans (Steam, Epic, App Store, etc.).
|
||||
|
||||
---
|
||||
|
||||
### **7. Development Roadmap**
|
||||
|
||||
* Milestones and expected outcomes (don’t need specific release dates if you prefer flexibility).
|
||||
* Short-term and long-term goals.
|
||||
* Key dependencies (tools, tech, contractors, platforms).
|
||||
|
||||
---
|
||||
|
||||
### **8. Team**
|
||||
|
||||
* Yourself (skills, experience, past projects).
|
||||
* Any collaborators, contractors, or advisors.
|
||||
* Highlight your ability to execute solo or with minimal overhead.
|
||||
|
||||
---
|
||||
|
||||
### **9. Financials**
|
||||
|
||||
* High-level budget: development costs, marketing, platform fees, potential salaries.
|
||||
* Funding sought and equity offered (if relevant).
|
||||
* Revenue projections (conservative estimates are fine).
|
||||
* Burn rate and runway.
|
||||
|
||||
---
|
||||
|
||||
### **10. Risk Assessment**
|
||||
|
||||
* Key risks (solo development, tech challenges, market competition).
|
||||
* How you plan to mitigate them (contingency plans, outsourcing, phased releases).
|
||||
|
||||
---
|
||||
|
||||
### **11. Call to Action**
|
||||
|
||||
* What you want from the investor (funding, mentorship, networking).
|
||||
* How they can engage or follow progress.
|
||||
|
||||
---
|
||||
|
||||
### **12. Optional Extras**
|
||||
|
||||
* Prototype or playable demo link.
|
||||
* Press clippings or community engagement metrics.
|
||||
* Early screenshots, animations, or concept art.
|
||||
* Testimonials from players or testers.
|
||||
|
||||
---
|
||||
|
||||
**Tips for a solo developer:**
|
||||
|
||||
* Be honest about being solo—investors respect transparency if you frame it as a lean, efficient operation.
|
||||
* Focus on traction and proof-of-concept rather than big projections that aren’t grounded.
|
||||
* Visuals are key—show them what you’re building.
|
||||
* Keep it concise: investors often skim decks quickly; 10–15 slides or pages is ideal.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user