> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/tutorials/9.-grid-strategy.md).

# 9. Grid strategy

Turn sideways price action into profit with a ladder of buy and sell orders.

{% embed url="<https://drive.google.com/file/d/1ckm6BZvC9hlm4zEgRiZZDdY4_ldr-h8s/preview>" %}

Most tokens spend most of their time moving sideways. A grid turns that chop into profit. It places buy orders on a ladder below the price and sell orders above it. Each time the price crosses a rung and comes back, you keep the gap between the two rungs.

### What you'll learn

* How a grid earns from volatility instead of direction
* Setting your investment and price range, or letting Surge suggest one
* Choosing the number of grid levels (rungs)
* Reading the live economics before you deploy
* Tracking rungs, cycles and profit while it runs

### Create a Grid strategy

1. Click **New Strategy** and choose **Grid**.
2. Pick your pair and DEX.
3. Enter your total investment. The grid holds about half in ADA and half in the token, so it can buy on dips and sell on rallies.
4. Set the price range, either in ADA or as a percentage. Or click **Suggest** and Surge will propose a range based on recent volatility over 7, 30 or 180 days.
5. Use the slider to set the **number of grids**.
6. Set **slippage** and a **boundary buffer**.
7. Check **Live Economics** and the ladder preview, then deploy.

### Key settings

| Setting         | What it does                                                                                                                     |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Price range     | The lower and upper prices the grid trades between                                                                               |
| Number of grids | More rungs means smaller, more frequent profits. Surge caps the count based on pool depth, so every rung is still worth trading. |
| Boundary buffer | Keeps the grid working a little beyond your range                                                                                |
| Slippage        | The maximum price movement you'll accept on each fill                                                                            |

### Live Economics

This is the key number. It shows the net profit per completed cycle, after every fee and a safety buffer. If it's negative, widen the spacing between rungs or invest more per rung.

### While it runs

* **Grid profit:** realized profit from completed cycles
* **Total P\&L:** your overall result, including open positions
* **Price band:** a live marker showing which rung the price is in
* **Rungs tab:** every level, with what it holds, how many cycles it has completed, and its profit
* **Replay:** see how your grid traded against past price moves

### Good to know

* **Grids like ranges.** If the price breaks well outside your range, the grid stops cycling until the price comes back. Pick a range that matches how the token actually trades.
* **Never deploy at a negative per-cycle profit.** Fix the spacing first.
* **Keep the Surge tab open.** Trades are signed in your browser. Turn on Keep display awake in Settings.

### Next

[10. Rule-Based strategy](/tutorials/10.-rule-based-strategy.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.surgecardano.com/tutorials/9.-grid-strategy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.