> For the complete documentation index, see [llms.txt](https://preapproval-guide.imda.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://preapproval-guide.imda.gov.sg/vendors-exclusive-corner/share-emerging-technology-and-sme-insights.md).

# Share Emerging Technology & SME Insights

We welcome observations from vendors on new technologies, adoption trends, unmet SME needs and potential opportunities for programme improvement.

As technology evolves and SME needs change, IMDA wants to hear directly from vendors who are engaging with the market.

**Your insights can help IMDA:**

* **Shape future policies and initiatives** – Identify emerging trends and industry needs that may inform programme priorities and policy decisions.
* **Review and introduce solution categories** – Identify new technologies and SME needs that may not be adequately covered by existing pre-approved solution categories.
* **Review programme requirements** – Gather industry feedback to help us develop or refine requirements that remain relevant and practical.
* **Identify emerging SME needs** – Better understand the challenges SMEs face and opportunities to support their digitalisation.

**What have you noticed?**

Are SMEs asking for new solutions? Have you spotted an emerging technology, market trend or industry challenge that IMDA should know about?

Share your observations with us. Your inputs will help inform our ongoing industry monitoring and may be considered in future programme reviews and discussions.

**What can you share?**

* Emerging technologies gaining industry traction
* SME needs not adequately addressed by existing solutions
* New use cases or implementation challenges
* Industry developments that IMDA should be aware of

{% embed url="<https://form.gov.sg/6ae03ffee50b261e16b6c4f8>" %}


---

# 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://preapproval-guide.imda.gov.sg/vendors-exclusive-corner/share-emerging-technology-and-sme-insights.md?ask=<question>&goal=<user_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.
