# Strategy * **Observations - Positives and negatives:** This category assesses whether there are any positive or negative observations about the asset's underlying business or impact activity, such as market trends or competitive advantages/disadvantages. * **Negatives - Observation:** This category assesses whether there are any negative observations about the asset's underlying business or impact activity, such as market risks or regulatory challenges. * **Sustainability of the core business / impact activity:** This category assesses whether the asset's underlying business or impact activity is sustainable over the long-term, taking into account factors such as market demand, resource constraints, and social and environmental impacts. * **Scalability - Observation:** This category assesses whether the asset's underlying business or impact activity has the potential to scale up in the future, taking into account factors such as market size, growth potential, and technological advancements. * **How long has the project been existing?:** This category assesses how long the project has been existing, it is considered if the project is still in development, in testnet, in mainnet, if it has been launched for a long time, it is more probable to have more data to evaluate. * **Funds needed:** This category assesses how much funds are needed to continue the project, indicating the level of investment required. * **Monetization Strategy:** This category assesses the monetization strategy of the project, indicating if the project is generating revenue or has a plan to do so in the future. Based on the answers to these questions, the asset is assigned a score for the Strategy parameter, which reflects the overall long-term viability and sustainability of the asset's underlying business or impact activity, as well as the scalability and monetization potential. A higher score indicates a well-thought-out and sustainable strategy, while a lower score may indicate potential issues with scalability or monetization. --- # Agent Instructions: 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: ``` GET https://digital-asset-impact-measurment.gitbook.io/impact-measurement-system/measurements-systems/manual-quant/strategy.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.