Work
What we built, client by client.
What we built, why and how. Where it was measured, the result.

Grupo ILTCustoms brokerage and freight
The system now logs four out of five updates.
- 4 of 5
- updates are logged by the system
- 8 statuses
- in one record, where there were 29 lists on 4 boards
- Since July
- 2026, in operation
- What we did
- An operations tracking system. The team reports on WhatsApp, as always, and the system files each update under the right operation and watches every deadline.
- Why
- The status of each operation lived in chats and in 29 lists spread across 4 boards. Management could not see where each one stood.
- How
- The official WhatsApp API, with nothing new to install. One record with 8 statuses, author and time on every change, deadline alerts and a report to management twice a day.

ENNCOIndustrial electrical engineering and solar energy
From finding the plant to quoting the project.
- What we did
- ENNCO Hub, a system with two sides. The commercial side finds industrial plants, writes to them from dedicated inboxes and sorts every reply. The technical side quotes solar projects with their own calculator, runs the basic engineering and builds each project with materials, margin and purchase orders.
- Why
- Sales depended on the director following up in person, and calculations and prices lived in Excel workbooks.
- How
- A plant database built from public registries, their Excel calculator rebuilt and checked against their own examples, and six engineering tools in one place.

Emerino Real EstateLuxury real estate
A real estate and property management portal.
- What we did
- A bilingual portal: a catalog with filters and a map, voice search, agents who upload and manage their own listings, presale projects and property management for their Airbnb stays, with date requests that land in their panel.
- Why
- The demand was there, but the old site did not show the catalog and everything fell into a single WhatsApp, unqualified.
- How
- Listings migrated with AI, redirects from the old site to keep search rankings, and an email alert for every request.

Tour AmigoSoftware for tour operators
An internal assistant and an AI sales system.
- What we did
- Two systems. An AI SDR that prospected tour operators, DMCs and agencies, handled the replies and kept their CRM up to date. And an internal assistant that drafted release notes, client status updates and replies from their tickets and knowledge base.
- Why
- They needed more meetings with operators, and their team was putting those documents together by hand every week.
- How
- Rules to decide who to write to, a brake that paused sending when bounces rose, and pricing or objections always sent to a person. The assistant ran on company accounts only, with read-only access to tickets.
Epicure GreeceLuxury DMC in the Greek islands
A website that travelers and AI can read.
- What we did
- A new website, readable by people and by AI engines, with an assistant that takes trip requests and a panel for their team to handle each one. We are now building their demand generation engine.
- Why
- They needed buyers and AI assistants to find them, to receive the right request so they could quote fast, and to go out and find their buyers.
- How
- A machine layer (llms.txt and structured data), a migration that kept their search rankings and, for the engine, a verified list of companies, sequences and rules for each market.
What needs to work better?
Bring a process, a pilot or a question. You talk directly with the people who will build it.
Book a conversation
george@teckel-ai.comOpens Google Calendar in a new tab.
Message AVA on WhatsApp
AVA, Teckel’s AI, replies right away and books you with Jorge.