> 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/company/team.md). # Team Two founders: Alberto Fernández, CEO, and Darwin Ramírez, CTO. Lid Labs Technologies, Dubai. Lid is built by two founders. Lean by design: each of us owns our part from start to finish. ## Alberto Fernández **Co-Founder and CEO.** Owns product, strategy, GTM, and the founder voice. Two startups before this: ENO, an 80,000-member community, and Orbi, a digital-dollar card. One taught distribution, the other taught payments. Drives the long horizon and writes most of what the world reads from Lid. ## Darwin Ramírez **Co-Founder and CTO.** Owns the protocol, the application stack, and integrations. Built and owns sign-in and wallets with Privy, the memberships engine, Lida, and cashing out to a bank account, which is being built. Owns the payment program, which has carried every sale so far with 0 funds lost and 0 attribution errors. The blockchain is invisible because Darwin built it that way. ## Operating entity Lid Labs Technologies (Dubai). Trade Licence No. 65802. Registration No. 63769. IFZA Business Park, Dubai. *** Trust is the product. Move slow on the rails. Move fast on the rest. --- # 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/company/team.md?ask=&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.