# Team
### 👨‍💻 **Dan Wallbanks – CEO**
Dan is a seasoned crypto veteran who first bought Bitcoin 8 years ago. With a strong background in Product Design and Marketing, he recognized Bitcoin’s potential early on and now brings the same vision and passion to the emerging influence of AI agents and SocialFi.
[Follow Dan on X](https://x.com/Web3Wallbanks)\
[Follow Dan on LinkedIn](https://www.linkedin.com/in/web3wallbanks)
***
### **CoptersApples – Product Director**
With over 20 years of experience in the design industry, CoptersApples brings a distinctive style and vibrant energy to every project. Known for a sharp eye for design and a knack for crafting intuitive, user-centered experiences, CoptersApples excels at creating UX solutions that are both visually appealing and highly functional.
[Follow CoptersApples on X](https://x.com/CoptersApples)
***
### Sandstorm **– CTO**
Behind the tech is Sandstorm, a seasoned veteran in the development space with over five years of experience in blockchain and web3 technologies and over 20 in Web Development. Sandstorm has successfully built and deployed multiple crypto projects, ranging from decentralized applications (dApps) and smart contracts to NFT integrations and tokenized ecosystems.
***
### Avark - External Design Agency Partner
Avark, a tier 1 Web3 design agency, is partnering with us to support the team to scale to build a cutting-edge, consumer-facing community growth platform launchpad.
[Visit the Avark Website](https://www.avark.agency)
---
# 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://georgiaramsai.gitbook.io/georgiaramsai/about-project/team.md?ask=
```
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.