> For the complete documentation index, see [llms.txt](https://where2-world.gitbook.io/where2.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://where2-world.gitbook.io/where2.world/about-us/our-team.md).

# Our Team

## Who we are.

Our task force consists of experienced storytellers, entrepreneurs and visionaries.

<figure><img src="/files/OIrxG9hD0tmdRuhS8A3C" alt=""><figcaption></figcaption></figure>

Great progress is made when change makers come together, each giving their best in their respective areas. We set the example for the change we want to bring with this dApp. We believe in decentralization, individual freedom, and empowering our community.

### Expertise

* 10 years of experience building location based apps
* 250.000 Dollars already invested
* Running MVP
* 40 brands, 120+ influencers & artists with a combined sum of 1.2M potential users
* Established connections to hotel-chains, restaurants & businesses

We are leaders in business development, international business and marketing Web3 gurus. Our board of advisors include Eduardo Abreau, the VP of Blockchain and Digital Assets at MasterCard and Joe Rotondi the Co-Founder of Unit-Network.


---

# 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://where2-world.gitbook.io/where2.world/about-us/our-team.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.