> For the complete documentation index, see [llms.txt](https://code-collective.gitbook.io/launch-flow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://code-collective.gitbook.io/launch-flow/get-started/quick-start.md).

# Quick start

Here's the fastest path to scheduling a price-change launch from start to finish.

1. From the Launch Flow dashboard, select **Schedule a launch**.
2. Choose the products (and/or collections) you want to change.
3. Set the new price for each selected item. Launch Flow will record the current price as the snapshot before anything changes.
4. Pick the **start date and time** for the change to go live.
5. *(Starter and Growth plans)* Optionally set an **end date and time** — when it arrives, Launch Flow restores the original prices (auto-rollback).
6. Review the summary and save. Your launch now appears in the dashboard as *Scheduled*, and fires automatically at the time you chose.

{% hint style="success" %}
**Test with one product first.** Schedule a single low-stakes product a few minutes out to watch the full cycle — go live, then roll back — before you build a large sale.
{% endhint %}


---

# 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://code-collective.gitbook.io/launch-flow/get-started/quick-start.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.