> For the complete documentation index, see [llms.txt](https://help.foreverfanmusic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.foreverfanmusic.com/courses/fast-track-your-spotify-rollout-boost-streams.-gain-real-fans./hype-presave-rollout-1m+-streams.md). # Hype Presave Rollout (1M+ Streams) {% embed url="" %} **Building hype for a release as a non-superstar artist with indie resources is the focus of this case study. In this video we dive into a real-life example of a brand new artist's first song release, with strategies that can be applied to bigger artists as well.** The artist, Fash, reached out in April 2020 and was able to go from 10,000 streams to over 1.2 million streams in a short period, following a blueprint that lowered his risk of failure and increased his opportunity for success. Let’s dive in to how he did it. --- # 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://help.foreverfanmusic.com/courses/fast-track-your-spotify-rollout-boost-streams.-gain-real-fans./hype-presave-rollout-1m+-streams.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.