# 4. Utility
**Utility needs to be simple, clear and achievable.**
If you believe you'll be able to offer a lot more in the future, then keep that announcement for the future, start small and build from there.
Promising too much too soon will create unrealistic expectations, which in turn will add unnecessary pressure to your endeavour.
Set your self simple and achievable utilities, that you know, based on your time and resources, you can deliver on them 100%.
If you end up delivering more than promised, then it will be a surprise and delight for your community.
The other way around, could potentially ruin your project and create a lot of frustration.
### 🔑 Examples of simple utilities:
* Access to a token-gated chat with other holders and founders.
* Access to exclusive content and events.
* Governance rights and decision-making.
* Participation in pre-launch or beta phases of your product/service.
* Collaboration opportunities with the founders and holders.
* Discounts and special offers.
Our suggestion would be to set a solid foundation of simple utilities, and add from there.
**Think big, but start small.**
New SIWAS utilities after 2 years of development
---
# 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://academy.kabila.app/nft-academy/5-step-nft-strategy/4.-utility.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.