> For the complete documentation index, see [llms.txt](https://docs.bloom.xyz/bloom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloom.xyz/bloom/w/why-web3.md).

# Why Web3?

We’re not here to pretend to be a game company or metaverse company. We know what we’re good at, and that is scaling brands.

Apparel and fashion are arenas that we have succeeded in before.
 With the realization that the future of fashion is going to be digital, we took this challenge head-on.

Building a Web3 brand is very different from building a traditional Web2 brand.

How so?

In Web2, you build a product and then find a way to bootstrap the growth of that product to an audience or community.

In Web3, the process is reversed.

We have an eager, supporting, and strong-willed community who is here to help us bootstrap the growth of BLOOM, and we couldn’t be more grateful.

Thank you for sticking around and joining us on this massive undertaking.

We’re in this together 🤝 and again… you hold the manuscript.


---

# 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://docs.bloom.xyz/bloom/w/why-web3.md?ask=<question>&goal=<endgoal>
```

`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.