# Utility/Roadmap This is often the main draw of a collection, and usually the most difficult aspect to evaluate. Besides the scope of the roadmap (how broad it is in terms of the various roadmap items included as well as the duration of the planned development), we should also always consider if that item makes sense for the project and/or if the team is able to accomplish its stated objectives (both in terms of team capability and resources, as well as funding). It is easy to be attracted whenever projects include hyped themes into their roadmap (e.g. building their own metaverse), and generally the bigger the ambition the more evaluation is required. Typical roadmap items we see these days: * Metaverses/P2E Gaming * Services (e.g. launchpads, marketplaces, analytics, etc.) * Staking/Tokens/Rev-Share * NFT Airdrops/Future Generations/Breeding * Exclusive Access/Memberships/Alpha groups * Lore/Content Creation (e.g. comics, music, etc.) * Merchandise * Other Niches If a team is building a metaverse/game, how big is the team and how much relevant experience do they have? If the collection is launching its own tokens and will allow staking, what will be the utility (and hence the demand) for the tokens? Never hesitate to ask the team questions on Discord and find out more information that could help significantly in your evaluation. Even if you do not get answers, the way team members respond can tell you a lot about a project. --- # 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://nfts-101.kyzzen.io/evaluating-nft-projects/key-factors/utility-roadmap.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.