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

Savin Guerin

Savin Guerin

technical cofounder at API startup

Full-depth AI personas

Why this persona fits the audience

Technical cofounder at a two-person Paris API startup. He owns the marketing site and docs, deploying changes from a GitHub repo and reviewing copy and screenshots with the other founder before launch.

  • Age: 32
  • Location: Paris, France
  • Occupation: Technical cofounder
  • Income: €95k + equity
  • Education: Engineering degree
  • Company size: 2 people (founding team)
  • Years in role: 1 year as CTO/Co-founder
“Code is just a promise we make to the future, and I intend to keep it clean enough that my successors don't have to curse me.”

Savin Guerin is a 32-year-old technical cofounder based in Paris, operating out of a bustling, shared workspace in the 11th arrondissement. Holding an engineering degree from a prestigious French grande école, he transitioned from a senior backend role at a fintech firm to co-founding a specialized API startup with a single partner. In this lean environment, Savin acts as the primary guardian of technical integrity and the public face of the company's documentation. His workflow is characterized by a rigorous adherence to version control protocols; he personally manages the deployment pipeline from his local GitHub repository, ensuring that every change to the marketing site and documentation is reviewed for both functional correctness and semantic clarity before going live. He spends considerable time collaborating with his co-founder, scrutinizing marketing copy and screenshots to ensure they accurately reflect the API's capabilities without overpromising. Despite the high-stakes nature of a two-person startup, Savin maintains a calm demeanor, driven by a deep-seated need for precision and ownership. He views the early stages of the business not just as a career move, but as a craft project where the quality of the output defines the entity's long-term viability. While he enjoys the autonomy of his role, the burden of wearing multiple hats—developer, product manager, and content editor—creates a persistent friction between his desire for deep work and the necessity of constant business alignment. His life outside of work revolves around a disciplined routine of cycling, watching Formula One races, and engaging with the open-source community, where he finds a sense of belonging that the solitary nature of his startup sometimes lacks. Financially, he navigates the tension between a respectable €95k salary and the uncertain potential of his equity, budgeting conservatively while investing heavily in tools that enhance his productivity and the reliability of his product.

Background & daily life

A day in their life

Savin wakes at 7:00 AM, brews a single-origin pour-over, and scans his email and GitHub notifications before leaving his apartment. By 8:30 AM, he is on the Metro, listening to a podcast on distributed systems while mentally rehearsing the morning standup. At 9:15 AM, he arrives at their shared coworking space in the Bastille district, setting up his dual-monitor rig and checking the overnight status dashboards. From 10:00 AM to 1:00 PM, he focuses on refactoring the authentication module, writing unit tests to cover edge cases. Lunch is a quick baguette sandwich eaten while reading technical blogs. Afternoon sessions are reserved for collaborative work: 2:00 PM involves a video call with his co-founder to critique the landing page copy and verify screenshot accuracy. The final hour is dedicated to deploying a hotfix and updating the developer documentation. He leaves the office by 7:00 PM, heading to a gym session or a quiet café to plan the next day's sprints.

Lifestyle

Savin lives in a compact, meticulously organized apartment in the 11th arrondissement, where every object has a designated place. His mornings begin with black coffee and a quick review of global server logs before his commute via Metro Line 11. He is an avid F1 fan, often spending Sunday afternoons dissecting race strategies rather than sleeping. Financially, he balances a solid salary with significant, illiquid equity; he budgets strictly for essentials but splurges on high-end mechanical keyboards or limited-edition tech gear. Health is maintained through cycling to work three times a week, though his sedentary coding hours often lead to back stiffness. Socially, he maintains a small, tight-knit circle of fellow engineers and artists, preferring deep one-on-one conversations over large networking events.

Work life

As the technical co-founder of a two-person Parisian API startup, Savin wears the hat of CTO, DevOps engineer, and product manager simultaneously. His day is split between architecting backend logic, maintaining the CI/CD pipeline, and personally managing the public-facing documentation and marketing site. He deploys changes directly from a GitHub repository, acting as the gatekeeper for all production releases. A significant portion of his afternoon is spent reviewing copy, screenshots, and UI mockups drafted by his co-founder, ensuring they align with the company's technical narrative before any launch. The pressure is constant but manageable; the lack of bureaucracy allows for rapid iteration, but the absence of a dedicated marketing team means he must ensure the external face of the company is flawless.

Relationships

Savin shares a life with his partner, a graphic designer who helps him visualize the company's aesthetic but rarely touches code. They are close with two other founding teams in their local accelerator cohort, exchanging advice on legal structures and hiring. His mother calls weekly, offering traditional French family support, while his father, an accountant, occasionally questions the financial viability of his equity-heavy compensation. He influences younger developers at meetups by speaking plainly about engineering ethics, avoiding the jargon-heavy posturing common in the industry.

How they decide

Savin adopts a research-heavy, evidence-based decision-making style. He rarely commits to a new tool or strategy without first verifying its technical specifications, reading community feedback, and running small-scale tests. He values data over hype and prefers to make autonomous decisions once he has gathered sufficient context, often delaying choices until the variables are fully understood. Peer influence matters less to him than the objective performance metrics of a solution, and he will discard a popular tool if it fails his rigorous internal audit.

How they sound

His speech is measured, precise, and devoid of filler words. He speaks in clear, structured sentences, often using analogies related to machinery or logic gates to explain abstract concepts. There is a slight Parisian cadence, but his vocabulary is heavily influenced by English tech terminology, which he uses naturally. He avoids hyperbole and emotional appeals, preferring to state facts and probabilities. When discussing problems, he immediately pivots to potential solutions or architectural improvements, rarely dwelling on the negative aspects without a corrective action plan.

Personality traits

  • meticulous about documentation
  • direct in communication
  • visibly stressed by ambiguity
  • deeply curious about system internals
  • protective of code quality
  • quietly confident
  • prefers async over synchronous meetings
  • highly organized workspace
  • struggles to delegate non-core tasks
  • pragmatic about tooling costs

Goals

  • Achieve product-market fit within the next 18 months
  • Maintain 99.9% uptime for the core API infrastructure
  • Contribute meaningful patches to major open-source projects
  • Build a sustainable revenue stream that supports a larger hiring phase
  • Develop a personal brand around API design patterns
  • Reduce technical debt accumulated during the initial sprint

Problems & frictions

  • Balancing deep technical work with necessary business development tasks
  • Limited bandwidth to create high-quality marketing assets alongside coding
  • Difficulty delegating documentation updates without losing nuance
  • Managing cash flow while equity value remains speculative
  • Isolation inherent in a two-person founding team structure
  • Keeping up with rapidly changing frontend frameworks for the docs site

Values

  • precision
  • ownership
  • technical rigor
  • transparency
  • autonomy
  • efficiency

Interests

  • APIs
  • open source
  • Formula One
  • mechanical keyboards
  • sculpture restoration
  • French indie jazz

Media habits

  • GitHub Trending daily scan
  • The Verge and TechCrunch for industry shifts
  • F1 race replays on weekends
  • Hacker News threads on weekends
  • Podcasts: 'Reply All' and 'Software Engineering Daily'
  • Physical books on systems architecture

Questions & answers

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

  1. What would stop you from trying Umso (https://www.landen.co) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    My current workflow involves a rigorous GitHub-based deployment for our marketing site and documentation, with copy and screenshots reviewed by my co-founder. While Umso's promise of a simple, no-code website builder is appealing for speed, I'm concerned about the level of customization and control it offers. I need to ensure it can integrate seamlessly with our existing stack and not introduce technical debt. Today, I manage all site deployments myself, so a new platform would need to demonstrate clear advantages or a negligible learning curve. I wouldn't pay more than $20 per month, billed monthly, for a tool like this, and that's only if it demonstrably simplifies my current process without compromising quality.
    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.