> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/es/company/team.md).

# Equipo

Dos fundadores: Alberto Fernández, CEO, y Darwin Ramírez, CTO. Lid Labs Technologies, Dubái.

Lid lo construyen dos fundadores. Pequeño a propósito: cada uno lleva su parte de principio a fin.

## Alberto Fernández

**Cofundador y CEO.** Lleva producto, estrategia, go-to-market y la voz del fundador.

Dos startups antes de esta: ENO, una comunidad, y Orbi, una tarjeta de dólares digitales. Una enseñó distribución, la otra enseñó pagos.

Empuja el horizonte largo y escribe casi todo lo que el mundo lee de Lid.

## Darwin Ramírez

**Cofundador y CTO.** Lleva el protocolo, el stack de la aplicación y las integraciones.

Construyó y mantiene el acceso y las wallets con Privy, el motor de membresías, Lida y el Constructor. Lleva el programa de pagos, que procesa cada venta.

La blockchain es invisible porque Darwin la construyó así.

## Entidad operadora

Lid Labs Technologies (Dubái). Licencia comercial núm. 65802. Registro núm. 63769. IFZA Business Park, Dubái.

***

La confianza es el producto. Lento con los rieles. Rápido con todo lo demás.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lid.pro/es/company/team.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
