> For the complete documentation index, see [llms.txt](https://canopy-network.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://canopy-network.gitbook.io/docs/canopy-incubator/welcome-and-what-to-expect.md).

# Welcome & What to Expect

## Welcome Aboard

You’re accepted…how can you prepare for the program? Here's how to get started:

* [ ] **Define your MVP**: If you haven’t already, define your product and tokenomics MVP. Please prepare a doc, demo, and/or diagram demonstrating how your product should work. This will make collaboration with the incubator team more effective. 
* [ ] **Assess your needs**: Once you’ve defined the product, evaluate which areas you need support with. The incubator contributors can provide support across engineering, go-to-market, and tokenomics. The more detail you have, the better quality of support we can provide.
* [ ] **Prep your team**: Talk to your teammates about the program, share materials, prep your GitHub repos for external contributors, and invite your team into Canopy’s [Discord](https://discord.gg/CwsVjFBf). Note: Discord will be the primary method of communication with the Canopy team. 
* [ ] **Set up social media**: Canopy will support program builders with social media and blog posts highlighting all of the awesome projects. To get a head start, decide if you would like to feature your company’s X account, a founder’s X account, or maybe even the company’s website. This is completely optional, but a great way to boost engagement and grow credibility for your project. 
* [ ] **Complete our onboarding process**: We’ll be capturing critical information as a way to promote, track, and guide projects. Help us in quickly fulfilling requests. 

### What to Expect From Canopy

* **Assigned Coordinator**: Each participating team is typically assigned one or more contributors as program coordinators (e.g., technical, business/strategy). It’s the responsibility of these contributors to ensure engagement with their assigned team throughout the program.
* **Regular Check-Ins**: Coordinators are expected to establish a regular cadence of support. During these check-ins, they review the team’s progress, discuss any roadblocks, and set objectives for the next period based on the team’s recent updates or questions provided.
* **Ad Hoc Support**: Coordinators are available for ad hoc questions. Have a hurdle? Let us know!
* **SME (subject matter expert) & Networking**: Coordinators provide guidance in their area of expertise, but if a team needs help beyond their knowledge, coordinators are expected to connect the team with the right expert, either internal (within Canopy) or external contacts to help address specific needs. 
* **Tracking and Accountability**: Coordinators keep track of participants’ commitments and progress via internal tooling. Forget a conversation? We'll keep you accountable.