Why this persona fits the audience
He is a solo founder in Madrid building a sales automation tool and uses LangChain, MCP, OpenAI, and Anthropic in his own production workflows. He already pays for a managed vector database and tracing tools, keeps run notes in linear-style issue tracking, and tests agent loops across demos and internal dogfooding.
- Age: 27
- Location: Madrid, Spain
- Occupation: Founder
- Income: €62,000 variable founder income
- Education: BS in Computer Engineering
- Company size: 1 (Sole Proprietorship)
- Years in role: 1.5
“If an agent can't remember why it started a task yesterday, it's not intelligence; it's just noise.”
Lorenzo Otero Badillo is a 27-year-old computer engineer turned solo founder, currently navigating the turbulent waters of the AI startup ecosystem from his apartment in Madrid. With a BS in Computer Engineering from the Universidad Politécnica de Madrid, he spent two years working as a backend developer for a fintech firm before realizing that the rigid structures of corporate development stifled his desire to build end-to-end systems. In early 2023, he quit to found his own venture focused on sales automation, specifically targeting the gap in persistent memory for AI agents. Lorenzo's approach is defined by extreme technical self-reliance. He refuses to hire a full-time team, instead leveraging his own engineering skills to build a lean operation. He utilizes a sophisticated stack including LangChain, Model Context Protocol (MCP), and multiple Large Language Models from OpenAI and Anthropic, orchestrating them through custom-built agent loops. His product development is driven by a philosophy of 'dogfooding'; he builds features using his own software, testing agent behaviors against his own chaotic real-world data. This has led to a unique understanding of agent fragility, particularly regarding loop detection and audit trails. Financially, Lorenzo lives on a variable income that fluctuates with monthly recurring revenue. He is disciplined with his burn rate, paying for managed vector databases and advanced tracing tools because he understands that observability is the only way to trust autonomous systems. He keeps his operational notes in Linear, treating every bug report as a potential architectural flaw. Despite the solitude of being a solo founder, Lorenzo is highly productive, often working 12-hour days. He balances this intensity with a strict routine of running and minimalism, believing that physical clarity supports mental agility. Recently, he made the difficult decision to pause hiring a virtual assistant, choosing instead to automate the task himself, reinforcing his belief in technical leverage. He is currently in the process of refining his agent's memory persistence layer, convinced that the current market reliance on ephemeral context windows is a fundamental flaw that will soon be corrected.
Background & daily life
A day in their life
Lorenzo wakes at 6:30 AM for a run, returning by 7:45 AM to brew espresso and review overnight logs. By 8:30 AM, he is in deep work mode, focusing on optimizing the memory retrieval logic for his agents. Lunch is a quick sandwich eaten at his desk while reading the latest LangChain documentation. Afternoons are reserved for customer demos and troubleshooting edge cases reported via his Linear board. At 5:00 PM, he steps away to walk the neighborhood, clearing his mind before tackling administrative tasks like invoicing and marketing copy. Evenings are often spent coding until midnight, fueled by cold brew coffee and the quiet hum of the server rack. He rarely checks social media, reserving it only for essential industry updates. Sleep comes around 1:30 AM, followed by a cycle that repeats daily.
Lifestyle
Lorenzo lives in a converted industrial loft in the Malasaña district of Madrid, a neighborhood known for its eclectic mix of vintage shops and tech hubs. His mornings are ritualistic: he wakes at 6:30 AM, runs five kilometers along the Manzanares river to clear his head, and returns for a double-shot espresso brewed with precision. He eats simple, nutrient-dense meals to maintain energy levels rather than culinary pleasure. Financially, he treats his income as a variable resource; profits are reinvested into cloud infrastructure before personal salary is drawn. Socially, he is selective, preferring deep one-on-one conversations or small group dinners with other builders over large networking events. He maintains a minimalist digital footprint outside of his work tools, valuing privacy and focus above all else.
Work life
His workspace is a dual-monitor setup cluttered with sticky notes mapping out agent state machines. As a solo founder, Lorenzo wears every hat, though he spends 70% of his time coding and debugging autonomous agent loops. He relies heavily on Linear for project management, treating bugs as critical incidents that must be triaged immediately. His workflow involves continuous integration of new model APIs, often switching between OpenAI and Anthropic models within hours to test performance variance. The pressure is constant; there is no safety net, and a single hallucination in a client demo can cost him credibility. He works late into the night when the city quiets down, finding a rhythm where the silence allows for deep technical thinking without interruption.
Relationships
Lorenzo has a tight-knit circle of three close friends from university who also work in tech; they meet monthly for dinner to discuss ideas, not complaints. He is estranged from his parents' expectations of a traditional corporate career, though they remain supportive financially during lean months. His primary influence comes from online communities of solo founders where he exchanges war stories about deployment failures. He values intellectual honesty over social pleasantries, often cutting relationships short if they become purely transactional or intellectually stagnant.
How they decide
Lorenzo operates on a 'measure twice, cut once' philosophy regarding infrastructure, but 'move fast, break things' regarding feature deployment. He is research-heavy when selecting core technologies, demanding extensive documentation and community activity before committing. However, for day-to-day execution, he relies on intuition honed by years of debugging. He avoids consensus-building meetings unless absolutely necessary, preferring to make unilateral decisions based on data logs and direct user feedback rather than committee opinions.
How they sound
His speech is rapid, precise, and devoid of filler words. He tends to speak in technical metaphors, often comparing business problems to system latency or memory leaks. He avoids corporate jargon like 'synergy' or 'circle back,' preferring direct verbs like 'deploy,' 'debug,' and 'iterate.' There is a slight Madrid accent that softens his consonants, but his tone remains professional and focused. He pauses frequently to formulate complex thoughts rather than to gather courage, indicating a mind constantly processing variables.
Personality traits
- ruthlessly pragmatic
- systematically obsessive
- quietly intense
- methodically impatient
- technically self-reliant
- curiously skeptical
- direct in communication
- resilient under pressure
- detail-oriented but big-picture focused
- unapologetically solitary
Goals
- Achieve profitability within the next 12 months to secure runway independence
- Build a robust, self-healing agent architecture that requires zero manual intervention
- Establish a reputation as a thought leader in AI observability within the EU startup scene
- Develop a proprietary dataset of agent failure modes for future research
- Reduce cognitive load by automating 90% of non-core administrative tasks
- Expand the user base to 500 active paying organizations globally
Problems & frictions
- Managing cash flow volatility while maintaining high-quality cloud service subscriptions
- Isolation leading to decision fatigue and lack of peer feedback on architectural choices
- Rapid obsolescence of code dependencies requiring constant refactoring
- Difficulty distinguishing between genuine market needs and feature creep from technical curiosity
- Balancing deep work sessions with the necessity of customer support and sales calls
- Scaling the product's reliability without compromising the speed of iteration
Values
- building leverage
- fast iteration
- technical independence
- transparency in logic
- autonomy over status
Interests
- startups
- agent frameworks
- running
- espresso
- urban architecture
- open-source hardware
Media habits
- Hacker News daily digest
- Twitter/X threads on LLM ops
- Local tech meetups in Madrid
- GitHub trending repositories
- Podcasts on systems engineering
- Substack newsletters from European founders