> For the complete documentation index, see [llms.txt](https://help.datamidsouth.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.datamidsouth.org/data-at-innovate-memphis/partner-with-us.md). # Partner with us ### Partnership Models We collaborate flexibly with governments, nonprofits, funders, and researchers. You can partner with us as a: * **Data Contributor** → share your data to strengthen the region’s collective knowledge * **Analytic Partner** → commission analysis, research, or products tailored to your needs * **Research Collaborator** → co-design pilots or cross-sector data projects * **Funding Partner** → invest in Memphis’ civic data infrastructure and innovation capacity **→ However you partner, we make your data work harder for your mission.** *** #### 🧠 Why Partners Choose Data Midsouth Because we bridge the gap between **technical excellence** and **real-world impact**. Because we understand that **data is only powerful when people can use it**. And because we believe collaboration — not competition — is how Memphis wins. *** #### 📩 Let’s Work Together **Ready to see what your data can do?** Partner with the Data Midsouth Team at Innovate Memphis. 📧 🌐 datamidsouth.org 💬 Follow us on LinkedIn | @InnovateMemphis --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.datamidsouth.org/data-at-innovate-memphis/partner-with-us.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.