> For the complete documentation index, see [llms.txt](https://docs.dappradardao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dappradardao.com/dappradar-dao-report-2024/marketing-efforts/challenges-and-strategic-adjustments-for-2025.md).
# Challenges & Strategic Adjustments for 2025
As the DappRadar DAO continues its marketing evolution, several key areas require adaptation:
* Scaling contributor engagement: Increasing the number of active contributors from 4 to 6 in Q2 and Q3 2025, with compensation adjustments to align with growth targets.
* Expanding the Ambassador/OG Program: Allocating a dedicated token pool to incentivize OG community members and broaden outreach across ecosystems.
* AI integration and branding impact: The inclusion of AI in DappRadar’s product suite is expected to drive an increase in RADAR holders and PRO members. This shift will require:
* Enhanced community engagement strategies to retain newcomers.
* New initiatives to convert new users into long-term holders and PRO members.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.dappradardao.com/dappradar-dao-report-2024/marketing-efforts/challenges-and-strategic-adjustments-for-2025.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.