# Board Team Member

Meet the executive leadership team driving Gloture's global vision.

***

## Executive Leadership

| Name              | Title                   | Role                                  |
| ----------------- | ----------------------- | ------------------------------------- |
| **Harry Cameron** | Chief Executive Officer | Overall leadership, vision & strategy |
| **Lewis Collins** | Chief Operating Officer | Day-to-day operations & execution     |
| **Lilly Watsons** | Chief Financial Officer | Financial strategy & management       |
| **Eddie Leao**    | Chief Tech Officer      | Technology platform & infrastructure  |

***

## Harry Cameron — CEO

Leads the company's overall strategy and global expansion vision. Passionate about connecting excellent ideas and products from around the world to create value across borders.

***

## Lewis Collins — COO

Responsible for day-to-day operations across Gloture's global offices. Ensures seamless execution of campaigns, platform delivery, and client services.

***

## Lilly Watsons — CFO

Manages Gloture's financial operations, investor relations, and ensures sustainable growth through disciplined financial planning.

***

## Eddie Leao — CTO

Leads the development and maintenance of Gloture's technology platforms, including the Gloture App, member portal, and data infrastructure.

***

{% hint style="info" %}
Gloture's core team brings together professionals with deep experience across **Europe, North America, Japan, and Singapore** — enabling truly global campaign management.
{% endhint %}


---

# 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://gloture.gitbook.io/gloture/gloture-corp/company-profile/board-team-member.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.