> For the complete documentation index, see [llms.txt](https://guide.geyser.fund/geyser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.geyser.fund/geyser-docs/your-project-guides/step-by-step-tutorials.md).

# Step-by-Step Tutorials

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>How to Launch Strong (and Avoid a Slow Start)</strong></td><td>A weak first 72 hours dramatically reduces long-term funding outcomes.</td><td></td><td><a href="/files/NeOyrKImDtaOWXpafjFv">/files/NeOyrKImDtaOWXpafjFv</a></td><td><a href="/pages/7IScjgjmcYT7Dchisggl">/pages/7IScjgjmcYT7Dchisggl</a></td></tr><tr><td><strong>How to write a great Story</strong></td><td>Stories aren't just a way to entertain. They bind us.</td><td></td><td><a href="/files/cizfRqAl26YojYNNsB6h">/files/cizfRqAl26YojYNNsB6h</a></td><td><a href="/pages/zTyB0ATqY54YdiLjZZ0A">/pages/zTyB0ATqY54YdiLjZZ0A</a></td></tr><tr><td><strong>How to leverage the power of Products</strong></td><td>Projects with products raise an average of 3.3 times more than those without.</td><td></td><td><a href="/files/KCoNA566DxK2qRYdSUv3">/files/KCoNA566DxK2qRYdSUv3</a></td><td><a href="/pages/8YvapNIP2OkqOtT3YD0V">/pages/8YvapNIP2OkqOtT3YD0V</a></td></tr><tr><td><strong>How to market your project</strong></td><td>Marketing isn't easy, but it's essential for the success of your project.</td><td></td><td><a href="/files/FdJvojWUqfoOSSPPEWBy">/files/FdJvojWUqfoOSSPPEWBy</a></td><td><a href="/pages/I5FgSyd5fqUf6pS7DXIY">/pages/I5FgSyd5fqUf6pS7DXIY</a></td></tr><tr><td><strong>How to Convert Supporters Into Long-Term Backers</strong></td><td>The real compounding effect comes from repeat supporters, word-of-mouth, and ongoing trust.</td><td></td><td><a href="/files/zGhvUDl4Ohuzsluq88T4">/files/zGhvUDl4Ohuzsluq88T4</a></td><td><a href="/pages/XxlRUD4JHv6m57CGSoMA">/pages/XxlRUD4JHv6m57CGSoMA</a></td></tr><tr><td><strong>Writing Impact Reports</strong></td><td>Impact reports are short but powerful updates that help your supporters stay connected.</td><td></td><td><a href="/files/YJ0wjJ8zco44JEDdOWYv">/files/YJ0wjJ8zco44JEDdOWYv</a></td><td><a href="/pages/FChvSy4YYIdbrB74wAx8">/pages/FChvSy4YYIdbrB74wAx8</a></td></tr></tbody></table>


---

# 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://guide.geyser.fund/geyser-docs/your-project-guides/step-by-step-tutorials.md?ask=<question>&goal=<endgoal>
```

`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.