Founding Deployment Strategist. I build the pilot-to-production systems for Revenue AI startups, which is the stretch where most of them stall.
26 years in enterprise sales: VP Sales EMEA at ABBYY LS, CCO at RedLab, now founder and CEO at SalesAI. 54 enterprise deployments, and in the last three years 200+ AI pilots launched or rescued.
Based in Valencia, Spain. Open to roles here or remote.
Most of my production code lives in private repos. What I can open, I put here.
SalesAI - Revenue Intelligence platform. The approach we sell is Managed Revenue Growth: a proprietary LLM sits on a sales knowledge graph of 70+ entity nodes, pulls 19 entities out of every customer conversation, writes them back into the CRM, and turns that into a forecast, a risk list and a coaching plan for each rep. Speech analytics answers how the call went. The graph answers where the money is.
tourdecastles.com - 890+ castle pages in three languages, built by one person. A 23,700-note research vault, a Wikidata import, a graph indexer, and a grounding gate that refuses to publish a claim without a source. Runs on Cloudflare free tier. The CRM behind it runs there too.
smartsales.ai - my English writing on revenue architecture, and the EN/ES content engine that ships it.
- Knowledge graphs over messy human data: entity extraction, ontology design, grounding gates, health metrics you can put in CI.
- Revenue systems: CRM as an event pipeline (firehose into D1), anonymous-to-contact stitching, an AI SDR that runs outbound without a human in the loop.
- Claude Code as an operating system: skills, memory architecture, crons. One founder running sales, marketing and product on it.
- Sales methodology as code. MEDDIC, SPICED and BANT are not slides for me, they are schemas.
They are not a portfolio. They are one argument in three parts: what is true (the knowledge graph), what happened (the behaviour layer), and how one person executes against both (the skills).
All three were built before there was a business model to justify them, which is the point. The reasoning: Designing for Optionality.
- smartsales.ai - Revenue Architecture, in English.
- LinkedIn - shorter notes from the room, not from the deck.
TypeScript, React, Node. Cloudflare Workers, D1, KV, R2. Python. Postgres. Claude API and MCP servers. Wikidata and SPARQL. GitLab CI, Kubernetes, Supabase.