# Vision

Bet2Invest was created with a simple goal: **transform sports betting from a guessing game into a transparent, data-driven process**. Most "tipster platforms" focus on selling predictions without proving their accuracy. They often use recreational bookmakers as their odds source, *leading to inconsistent or even manipulated results*. This leads to frustration, mistrust, and long-term losses for users.

**Our vision is fundamentally different.** We believe tipster tracking should rely only on indicators that reflect real, repeatable edge. On Bet2Invest, every pick is certified using official Pinnacle odds, every result is tracked automatically, and no manual editing or manipulation is possible. This establishes a level of honesty the industry has long been missing.

We also prioritize the metrics that actually predict long-term performance. We focus on long-term results, **Closing Line Value (CLV)** and **CLEV without the bookmaker margin**, **consistent bankroll management through fixed 1-unit (1%) sizing**, and **market liquidity**. A tipster with extremely low liquidity is not realistically followable by many bettors; a high-performing tipster must also operate in markets that followers can access without killing the price. These principles treat betting the same way an investor analyses a financial asset: evaluating sustainability, risk, volatility, and scalability.

**Automation is also part of this vision**. Human delays often destroy the value of a good bet, so we offer an optional automated betting system that executes picks instantly on Pinnacle. This turns analysis into consistent execution and ensures users capture the actual edge generated by tipsters.


---

# Agent Instructions: 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:

```
GET https://docs.bet2invest.com/getting-started/vision.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
