> For the complete documentation index, see [llms.txt](https://whitepaper.letmespeak.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.letmespeak.org/learn-and-earn-business-model/letmespeak-web3-vs-web2.md).
# LetMeSpeak Web3 vs Web2
As Duolingo put in its IPO report in August 2021:
"Online language learning is highly competitive, with low switching costs and consistent stream of new products and entrants, and innovation by competitors may disrupt our business."
We want to prove them right.
LetMeSpeak's Web3 approach offers a totally different value proposition to users:
* Get paid, instead of paying for learning.
* An open-ended ecosystem with new experiences, rather than a closed one.
* User-driven economy vs one fully determined by corporations.
Our strong USP and sustainable economic design can help achieve scale, retention and long-term viability for the LetMeSpeak metaverse.
Let's look at the basic differences in business models between LetMeSpeak.org (Web3) and Web2 learning platforms (eg Duolingo).
---
# 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://whitepaper.letmespeak.org/learn-and-earn-business-model/letmespeak-web3-vs-web2.md?ask=&goal=
```
`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.