# Core Team

**David Leroux**\
Chief Executive Officer

<div align="left"><figure><img src="/files/LQYuuR8BsDjjlONfaIsV" alt=""><figcaption></figcaption></figure></div>

David brings a feverish passion for web3 technology and medieval fantasy gaming. He has been a competitive MTG player as well as poker and MMORPGs. Our goal for Heroes of Hold'em and the ENEFTY vision is to perfectly blend the 3 to appeal to fans of all game types.

**Michael Haid**\
Chief Product Officer

![](/files/IZ9y48acOj08sgWkVPpt)

The serial entrepreneur. Michael has had a range of successful companies which include creating previous games. He has years of experience in the gaming industry which includes poker, sports betting, and fantasy sports.&#x20;

**Lee Francisco**\
Chief Technology Officer

![](/files/nkhLUaAkvA1CzgIoJFj3)

Lee's tech company which he founded and ran for 15 years was the proud recipient of the Michigan 50 companies to watch award! Being involved with several companies since then, he brings a wealth of experience and technical knowledge to the team.

**Ricky Pyne**\
Advisor

![](/files/bkSRMdoc5O87JrhWDuqm)

Ricky has been a professional poker player since 2005 and has been very successful in DFS since its inception. He finished 45th in the 2018 WSOP Main Event. His love for the game and knowledge of the overall gaming industry makes him a perfect placement to balance the fun-to-play with the more traditional aspects of poker.


---

# 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://heroesofholdem.gitbook.io/whitepaper/project/core-team.md?ask=<question>
```

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.
