> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/pricing-experiences/pricing-experiences-overview/price-test-common-use-cases/the-straddle.md).

# The Straddle

Increase and decrease the price of every product by 10%. This is a great place to start as it will give you a look at elasticity across the board. If you don't want to start with your entire store, pick a few products or a collection to test first and iterate from there. Check out this [case study](https://blog.intelligems.io/intelli-blog/drive-conversions-revenue-through-price-decreases) on a brand who recently ran this type of test on their main collection and found that the lower price group generated nearly a 40% lift in conversion rate which yielded a 15% increase in revenue.

*What this test design might look like:*

|               | **Control Price** | **+10%** | **-10%** |
| ------------- | ----------------- | -------- | -------- |
| **Product A** | $10               | $11      | $9       |
| **Product B** | $20               | $22      | $18      |

{% hint style="info" %}
The Control Group should almost always be equal to what is currently live on the site - keeping one group consistent will keep your baseline consistent, giving you the most actionable results.
{% 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 by asking a question.

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

```
GET https://docs.intelligems.io/pricing-experiences/pricing-experiences-overview/price-test-common-use-cases/the-straddle.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.