# Why Build Variational

In 2021, [co-founders Lucas Schuermann and Edward Yu](/getting-started/core-contributors.md) left their roles managing one of crypto’s largest OTC desks to launch a proprietary trading firm. After spending two years integrating with and providing liquidity to nearly every major CEX and DEX, the structural limits of existing trading venues became obvious:

* **Relying on order books makes bringing new markets on-chain a slow, subsidy-fueled grind.** Exchanges are forced to pay millions in subsidies and rebates to external market makers just to bootstrap basic liquidity.
* **The exchange model inherently leaks value**, resulting in a continuous outflow of capital from the platform to external market makers.
* **Institutional OTC and customized derivatives trading remains largely manual**, often settled entirely off-chain via chat groups.

Variational was built to solve this infrastructure problem. Funded by trading profits, Lucas and Edward set out to build a new type of trading venue that vertically integrates liquidity provisioning. By integrating its own primary market maker that connects directly to CEX, DEX, and TradFi liquidity, Variational bypasses the slow grind of bootstrapping isolated order books and ends extraction from the platform by external market makers.


---

# 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.variational.io/getting-started/why-build-variational.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.