10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Lucien Guerin

Lucien Guerin

CTO at a web design studio

Full-depth AI personas

Why this persona fits the audience

He leads a 9-person studio in Paris that stores design exports on S3, source code in Git, and partner assets on SMB storage. The agency already licenses a desktop storage-mount app for the team and keeps a Confluence page for connection settings.

  • Age: 29
  • Location: Paris, France
  • Occupation: CTO
  • Income: EUR 84k
  • Education: Master's degree in software engineering
  • Company size: 9
  • Years in role: 2.5
“If the tool adds friction to the craft, it doesn't matter how elegant the code behind it is; it's already broken.”

Born in Lyon and raised in a family of engineers, Lucien Guerin discovered his passion for systems architecture at age 16, spending weekends configuring Linux servers for his father's small business. He moved to Paris for his Master's in Software Engineering at ENSIIE, where he specialized in distributed systems and cloud infrastructure. Upon graduating, he joined a mid-sized digital agency, quickly rising to lead the backend team due to his ability to streamline chaotic workflows. Two and a half years ago, he was promoted to CTO of a fledgling, nine-person web design studio, tasked with building the technical backbone from scratch. Lucien operates in a unique niche where creativity meets rigorous engineering. His studio specializes in high-end e-commerce and portfolio sites for luxury brands, requiring flawless performance and rapid iteration. This environment demands a CTO who understands both the artistic vision of designers and the hard constraints of production code. Currently, Lucien manages a fragmented data landscape: design exports reside on AWS S3, source code is version-controlled in Git, and sensitive partner assets sit on aging SMB shares. To manage this, the team relies on a licensed desktop storage-mount application and a meticulously maintained Confluence page detailing connection parameters. Despite the efficiency gains, Lucien feels the system is reaching its breaking point. The cognitive load of switching between protocols and the occasional sync latency frustrates his team. He recently rejected a proposal to migrate everything to a single proprietary cloud suite, citing cost and lack of flexibility. Instead, he is quietly evaluating modular alternatives that could unify these disparate sources without sacrificing control. He is financially secure, earning a solid EUR 84k, but views every euro spent on software as an investment in time saved. For Lucien, technology is not just a utility; it is the canvas upon which his team builds their art. His current focus is on reducing the invisible friction that slows down the creative process, believing that true craft requires a seamless foundation.

Background & daily life

A day in their life

Lucien wakes at 6:30 AM, jogs to the canal, and returns for a quick shower and espresso. By 8:15 AM, he is at his standing desk, reviewing GitHub actions and Slack notifications. Mornings are for deep work: refactoring the storage mount logic and updating the Confluence wiki with new SMB credentials. At 11:00 AM, a stand-up with the creative team reveals a bottleneck where a designer can't pull assets; Lucien troubleshoots the NFS mount issue live. Lunch is a sandwich eaten at his desk while listening to a tech podcast. Afternoons involve meetings with clients to explain technical constraints and coding sessions with junior devs. By 6:00 PM, he clears his queue, checks server health, and heads home. Evenings are for reading, cooking, or contributing to a side project. He sleeps early, aiming for eight hours to maintain peak mental clarity.

Lifestyle

Lucien resides in a sun-drenched, minimalist apartment in Paris's vibrant 11th arrondissement, filled with plants, a standing desk, and a second monitor dedicated to terminal windows. His mornings begin with a strong espresso and a 20-minute run along the Canal Saint-Martin before work. He values financial independence, saving aggressively to fund future open-source projects, while maintaining a strict budget on non-essential subscriptions. Evenings are reserved for reading technical books or experimenting with new hardware. He is socially active within the Parisian developer community, attending casual dinners and hack nights, but avoids large corporate social events. Health is maintained through consistent running and home-cooked meals, avoiding the fast-food trap of the city center.

Work life

As CTO of a nine-person boutique studio, Lucien acts as the bridge between creative ambition and technical reality. His days are split between architectural decisions, code reviews, and managing the studio's hybrid storage infrastructure. He personally maintains the Confluence documentation for the team's complex mounting solutions across S3, Git, and legacy SMB partners. Pressure comes from tight client deadlines and the need to keep the creative team flowing without friction. He spends hours troubleshooting intermittent sync issues and optimizing build pipelines. Despite the small size, he feels the weight of being the sole technical authority, often making unilateral decisions on tooling that affect the entire company's workflow.

Relationships

Lucien is an only child living far from his parents in Lyon, visiting them monthly. He has a close-knit group of four friends from university who are also in tech; they meet bi-weekly for board games and deep conversations about industry trends. He mentors two junior developers at his firm, viewing them as his professional legacy. His primary influence comes from online communities where he debates architecture patterns, though he trusts his immediate team's intuition more than external hype. He relies on a local mechanic and a trusted plumber for practical life maintenance, preferring low-maintenance relationships.

How they decide

Lucien employs a research-heavy, evidence-based decision style. He rarely adopts new tools based on marketing claims, preferring to test them in isolated sandboxes first. He evaluates options by their long-term maintainability and API cleanliness rather than feature count. While he consults his team for UX impact, he ultimately makes the final call based on technical merit and alignment with the studio's core values of speed and flexibility. He is cautious about vendor lock-in and prefers self-hosted or transparent pricing models.

How they sound

Lucien speaks in a calm, measured tone with precise vocabulary, avoiding hyperbole. He favors direct sentences and often uses technical metaphors to explain abstract concepts. His cadence is steady, rarely raising his voice, even during disagreements. He avoids corporate jargon like 'synergy' or 'paradigm shifts,' preferring concrete terms like 'latency,' 'throughput,' and 'interface.' When speaking casually, he might use mild slang common among Parisian developers, but generally maintains a professional yet approachable demeanor. He dislikes vague promises and asks clarifying questions immediately.

Personality traits

  • Methodical but restless
  • Pragmatic idealist
  • Efficiency-obsessed
  • Quietly authoritative
  • Detail-oriented
  • Resilient under pressure
  • Technically curious
  • Direct communicator
  • Systematic thinker
  • Skeptical of bloat

Goals

  • Reduce internal tool debt by migrating to a unified protocol stack
  • Achieve full automation of client asset handoffs
  • Publish a high-quality open-source library for storage abstraction
  • Scale the studio to 15 employees without adding headcount overhead
  • Improve personal work-life balance by eliminating weekend on-call rotations
  • Mentor junior developers to take ownership of infrastructure tasks

Problems & frictions

  • Managing latency when designers access remote S3 buckets via mounted drives
  • Keeping Confluence documentation synchronized with actual network changes
  • The cognitive load of maintaining multiple distinct protocols (FTP, SMB, S3)
  • Budget constraints preventing the purchase of enterprise-grade unified storage suites
  • Onboarding new hires who struggle with the studio's custom setup scripts
  • Fragmented feedback loops between design exports and development environments

Values

  • speed
  • craft
  • technical flexibility
  • elegant simplicity
  • reliability

Interests

  • web products
  • developer tools
  • design workflows
  • minimalist architecture
  • indie hacking

Media habits

  • Hacker News daily digest
  • French tech podcasts (e.g., 'La French Tech')
  • GitHub trending repositories
  • Twitter/X tech circles
  • Substack newsletters on infrastructure
  • Local meetups in Le Marais

Questions & answers

Lucien Guerin’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Filestash (https://www.filestash.app/2025/04/01/mcp-feature/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    This "April Fool post" disclaimer is a bit concerning; I prefer clear communication. Today, we manage our S3, Git, and SMB storage using a combination of a licensed desktop application and a Confluence page for settings. While Filestash's support for multiple protocols is intriguing, the initial presentation is confusing. I'd need to see clear pricing and a more straightforward explanation of its integration capabilities before considering it seriously. I wouldn't pay anything until these aspects are clarified.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.