> For the complete documentation index, see [llms.txt](https://guida-2.gitbook.io/guida-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guida-2.gitbook.io/guida-docs/getting-started/your-first-strategy.md).

# Your First Strategy

A strategy in Guida is simply a set of rules that says *when* to act, *what* to do, and *how much* to risk. This page walks through building one from a plain-English idea into a complete, running strategy.

## Start with an intent

Every good strategy starts as a sentence. Yours might be:

> *"I think ETH is a long-term hold, but I want to buy more aggressively on sharp dips and lock in gains when it runs."*

That single intent already contains three of the four building blocks of any strategy. Let's make them explicit.

## The anatomy of a strategy

Every Guida strategy is built from four parts:

| Part                  | Question it answers                  | Example                                  |
| --------------------- | ------------------------------------ | ---------------------------------------- |
| **Trigger**           | *When* should something happen?      | "When ETH drops 5% in 24 hours"          |
| **Action**            | *What* should happen?                | "Buy $100 of ETH"                        |
| **Sizing**            | *How much* is involved?              | "$100 per trigger, max $1,000 total"     |
| **Exit & guardrails** | When do I take profit or cut losses? | "Take profit at +12%, stop-loss at −20%" |

You can combine multiple triggers with **AND / OR** logic, add a **take-profit** and **stop-loss**, cap your **maximum spend**, and set an **expiry** so a strategy stops itself after a set period.

## Building it in Guida

### 1. Describe it

Type your intent in natural language. Guida parses it into structured rules and shows you exactly what it understood — so there are no surprises. For example, the intent above might become:

* **Trigger:** ETH price falls ≥ 5% within any 24-hour window
* **Action:** Buy $100 of ETH
* **Take-profit:** Sell the position when it's up 12%
* **Stop-loss:** Exit if the position falls 20%
* **Max spend:** $1,000 total across the strategy
* **Expiry:** Runs for 90 days unless you stop it

### 2. Review and refine

Read back the rules Guida generated. This is the most important habit to build: **always confirm the strategy says what you meant.** Adjust any number or condition directly — tighten the dip threshold, raise the take-profit, shorten the expiry.

### 3. Add guardrails

Even a simple strategy should have limits. At minimum, set a **maximum spend** so the strategy can never commit more than you intend, and a **stop-loss** so a position can't run away from you. Guardrails are covered in depth in [Risk Management](/guida-docs/core-concepts/risk-management.md) and [Risk Controls](/guida-docs/features/risk-controls.md).

### 4. Name and save it

Give the strategy a clear name (*"ETH dip-buyer + profit ladder"*) so it's easy to find, compare, and share later.

## Tips for a strong first strategy

* **Start simple.** One trigger, one action, a take-profit and a stop-loss. You can always add complexity after you've watched it run.
* **Be specific about size.** Vague sizing is how portfolios get overexposed. Always set a max spend.
* **Think about the exit first.** Most people obsess over entries. Your exit rules — when you take profit and when you cut losses — usually matter more.
* **Don't skip testing.** However good it looks on paper, prove it. That's the next step.

***

**Next:** [Testing Your Strategy →](/guida-docs/getting-started/testing-your-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 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://guida-2.gitbook.io/guida-docs/getting-started/your-first-strategy.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.