Slack agent
Natural-language questions over internal databases, answered in Slack. Built with Hermes.
hours → minutesper answered question
43.36° N · 8.41° W — Galicia, Spain
Agents answering real customers, evals scored against real photographs, and the tooling that got a nine-engineer team shipping this way.
Natural-language questions over internal databases, answered in Slack. Built with Hermes.
hours → minutesper answered question
Customer support outside business hours, with escalation to a human when the agent is not sure.
real customerslive in production
Accuracy benchmark for a pipeline that extracts expiry dates and supplier lot numbers — scored against real photographs, not clean data.
measuredagainst real photos
A shared Claude Code setup: context files (CLAUDE.md, AGENTS.md), skills, hooks, slash commands and subagents, tuned for how the team actually works.
9engineers using it daily
Lead-classification chatbot (Chatwoot + n8n) and a nightly qualification pipeline running unattended.
400qualified leads
Food traceability and APPCC compliance for hospitality, built end to end with AI tooling: FastAPI + PostgreSQL backend, Expo/React Native apps, authentication, an OCR pipeline, an Astro site, and billing.
Internal platform covering stock, orders, support and integrations — one system across sales, assembly and support.
Notes from running AI systems in production — first posts are in the works.
How to know whether an agent actually works — task-level evaluation, not vibes.
Shaping what a model sees: context files, skills, and the tooling around them.
What survives contact with real users, and what quietly breaks.
Head of Software Engineering at Innogando — agrotech/IoT, maker of RUMI, GPS collars used by thousands of farmers. I joined when the whole company was ten people; today I lead a nine-person team across product, data and infrastructure, and I still write code.
Infra footnote: Kubernetes on GKE, GitOps via ArgoCD, CI/CD pipelines.