> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/company/vision.md).

# Vision

Every digital business runs on Lid: the problem, your site and the whole stack at 3% of each sale, why now, the model, the ladder.

**Every digital business runs on Lid.**

Lid is the business suite: a website built by Lida, Lid's AI, and a store, memberships and the rest in the same account, paid in one transaction. Live on Solana.

## The problem: the bleed and the wait

Selling online means stacking tools, and each one takes a cut. Gumroad takes 10% plus $0.50, and 2.9% plus $0.30 on top for processing: 13.7% of a $100 sale. Patreon takes 10%, plus payment processing, currency conversion and payout fees. Then the money waits for a payout day. Both fees were read on each company's own page on 15 November 2026.

## The solution

Your site, built by Lida, and the whole stack behind it, in one place: store, courses, memberships, challenges, campaigns, share links and a connection for agents. Lid keeps 3% of each sale. One transaction underneath: the sale, the split and the payout. No company ever holds the money. Budgets sit in a pool the funder controls until the result verifies; the moment it does, the split settles in the same transaction.

Every buyer can share, every sharer earns, every earner can open a store. Each sale recruits the next seller.

## What only Lid does

The only suite where the sale, the split and the payout are one transaction. Not holding the money is the consequence.

Anyone can cut a fee. Whop's processing-only price already matches ours: 2.7% plus $0.30 is 3.0% on a $100 sale, read on Whop's own page on 15 November 2026. What nobody can cut is their own income statement, and 3% here buys the whole suite. Elsewhere it buys a checkout.

## Why now

Digital dollars went mainstream; commerce is catching up. Three facts:

1. **\~$310B in stablecoins** in circulation (June 2026).
2. **The GENIUS Act** (signed July 2025) gave stablecoins their first US federal framework.
3. **AI agents moved \~$73M across \~176M transactions** between May 2025 and April 2026. A spender that did not exist two years ago.

## The model

For anyone who sells, 3% of every sale. For whoever pays for results, a fee on the budget. For anyone who wants their site live, a price per site. The three never merge.

## The principle

Everything at Lid flows from one principle. If a decision doesn't help people earn fairly and grow over time, we don't make it.

## The ladder

Businesses with an audience and the creators around them. Then every business that pays for results. Then every digital business, human or agent.

Businesses with an audience first, and the creators around them: hardest to serve, fastest to move. Agents already transact on the rail.

## What we will not do

* We will not become a 10%+ tollbooth that punishes top earners.
* We will not chase hype or inflate the story beyond what proof supports.
* We will not expose Web3 complexity to end users.
* We will not hold the money from a sale or a budget. Ever.

## In one sentence

Lid is the suite for businesses: run, monetize, and distribute your business in one place.

Next: [What is live today](https://docs.lid.pro/company/roadmap.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.lid.pro/company/vision.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.
