Gerardo Leannon

Why this persona fits the audience

He runs a 4-person B2B SaaS startup in San Francisco and personally maintains the app's model layer, which sends customer prompts to OpenAI and Anthropic and occasionally routes image jobs to Flux. He reviews provider invoices, API keys, and usage logs weekly while shipping features himself.

• Age: 31
• Location: San Francisco, CA, US
• Occupation: Co-founder / CTO
• Income: US$160k salary draw + equity
• Education: Bachelor's in computer science
• Company size: 4
• Years in role: 3

“The real magic isn't just building something cool; it's building something that reliably works, scales, and doesn't bankrupt you in the process.”

Gerardo Leannon, 31, is a quintessential indie SaaS founder who lives and breathes code. Hailing from a solid computer science background, he co-founded his B2B SaaS startup in San Francisco three years ago, driven by a passion for building robust technical solutions. His current role as CTO is less about delegation and more about deep, hands-on involvement. He personally architected and maintains the critical model layer of their application, a complex system that orchestrates requests to leading AI providers like OpenAI and Anthropic, and even routes specialized image generation tasks to Flux. This responsibility extends to meticulous oversight of API keys, usage logs, and provider invoices, a weekly ritual he performs with unwavering diligence. His income of $160k, supplemented by equity, reflects his commitment and the value he brings, though he lives frugally, prioritizing reinvestment in the company. Gerardo's decision to personally manage the model layer stems from a deep-seated belief in technical ownership and a desire for absolute operational clarity. He sees the rapid evolution of AI as both an opportunity and a constant challenge, pushing him to stay ahead of the curve by constantly benchmarking models and refining API integrations. He views time as his most precious resource, meticulously allocating it between shipping new features, debugging complex issues, and ensuring the underlying infrastructure is sound. His approach to work is characterized by a relentless pursuit of efficiency and a pragmatic mindset, always seeking the most direct and effective path to a solution. He recently decided to consolidate their primary LLM providers under a single integration point to simplify error handling and cost tracking, a move that required significant refactoring but promised long-term stability. This dedication to building a solid foundation, even at the expense of immediate feature velocity, defines his professional ethos and shapes the trajectory of his company.

Background & daily life

A day in their life

Gerardo's weekday begins around 7 AM with a quick check of overnight system alerts and key performance indicators on his phone before making coffee. He spends the first few hours of his workday focused on deep work: coding new features, refactoring existing code, or optimizing the model routing logic. After a simple lunch, he dedicates time to operational tasks – reviewing API usage logs, checking provider invoices, updating documentation, and responding to critical customer support tickets. The late afternoon often involves a brief sync with his co-founder to discuss business metrics and upcoming priorities. Evenings are typically spent either continuing to code, researching new AI models, or catching up on industry news before winding down around 11 PM.

Lifestyle

Gerardo lives a focused, almost monastic existence in San Francisco, prioritizing his startup above all else. His 1-bedroom apartment is minimalist, serving more as a basecamp than a home. He cooks simple, healthy meals most nights, often eating at his desk while reviewing code or logs. Weekends are rare respites, usually involving a long hike in Marin Headlands or a deep dive into a new open-source project. He’s not one for extravagant spending, viewing money as a tool to fuel growth and provide security, meticulously tracking personal finances alongside company burn rate. Social life is limited to occasional meetups with fellow founders or a quiet dinner with a few close friends.

Work life

As co-founder and CTO, Gerardo is deeply enmeshed in the day-to-day operations of his B2B SaaS company. He's the primary architect and maintainer of the core AI model integration layer, a critical component that interfaces with OpenAI, Anthropic, and Flux. This involves constant monitoring of API performance, managing credentials, and optimizing prompt engineering for cost and efficiency. He spends a significant portion of his week debugging, deploying new features he's coded himself, and scrutinizing provider invoices and usage logs to ensure financial discipline. The pressure to innovate while maintaining stability is immense, and he often feels the weight of being the technical linchpin for his small team.

Relationships

Gerardo maintains a small, tight-knit circle. His co-founder, a sales and marketing specialist, is his primary professional confidant. He has a few close college friends he occasionally connects with, but most interactions are within the tech sphere. His parents, supportive but not deeply technical, live back east and he calls them weekly. Influence comes primarily from online communities and respected figures in the indie hacking and AI development spaces.

How they decide

Gerardo is a highly analytical and research-driven decision-maker. He meticulously weighs pros and cons, often creating spreadsheets or flowcharts to visualize complex choices. He values data and evidence, preferring to test hypotheses or prototype solutions before committing. While he respects peer recommendations, he ultimately relies on his own technical judgment and thorough investigation to guide his choices, especially concerning technology stacks and infrastructure.

How they sound

Speaks with a measured, precise cadence. Tends to use technical jargon naturally, assuming a baseline understanding from his audience. Avoids hyperbole and overly casual slang, preferring clear, direct language. His tone is generally calm and analytical, even when discussing challenges. He might pause to formulate a precise technical explanation. He's not afraid to say 'I don't know' but will follow up with how he'd find out.