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

Elia Sarvari

Elia Sarvari

CTO of a small SaaS team

Full-depth AI personas

Why this persona fits the audience

Leads a 6-person SaaS team in Berlin and uses Cursor plus Codex for prototyping and maintenance. Their team documents runbooks, deployment checks, and fix histories in Confluence and a shared wiki, and they already pay for a commercial knowledge stack.

  • Age: 38
  • Location: Berlin, Germany
  • Occupation: CTO
  • Income: EUR 130k + bonus
  • Education: MSc in Software Engineering
  • Company size: 6
  • Years in role: 4
“The real challenge isn't building the next big thing, it's building it in a way that's sustainable, understandable, and adaptable to whatever comes next.”

Elia Sarvari, 38, is the CTO of a burgeoning SaaS startup based in Berlin, leading a tight-knit team of six engineers. His journey into technology began with a fascination for how complex systems function, leading him to pursue an MSc in Software Engineering. After several years honing his skills at larger tech firms, he was drawn to the agility and direct impact possible in a startup environment. He co-founded his current venture four years ago, focusing on building a product that streamlines a specific workflow for creative professionals. Elia's leadership style is characterized by a commitment to clarity, accountability, and speed, principles he instills in his team through rigorous processes and open communication. He's a firm believer in the power of well-documented systems, ensuring their team meticulously maintains runbooks, deployment checks, and fix histories in Confluence and a shared wiki. This dedication extends to their investment in a commercial knowledge stack, which he sees as essential for operational efficiency and knowledge retention. His technical toolkit heavily features Cursor and Codex, which he leverages extensively for rapid prototyping and ongoing system maintenance, viewing them as critical accelerators for their small but ambitious team. Elia's approach to work is deeply analytical and pragmatic; he thrives on dissecting complex problems and architecting elegant solutions. He views time as a precious resource, constantly seeking ways to optimize workflows and eliminate inefficiencies, not just for the company's bottom line but for the well-being of his team. While driven by professional ambition, he maintains a balanced perspective, prioritizing his personal life and physical health through his passion for cycling and a disciplined routine. He is not driven by status but by the satisfaction of building robust, scalable technology and fostering a high-performing team.

Background & daily life

A day in their life

Elia's typical weekday begins around 7:00 AM with a quick check of urgent overnight alerts, followed by a strong coffee and a review of Hacker News. He cycles to the office by 9:00 AM, often using the commute to mentally prepare for the day. Mornings are usually packed with team stand-ups, code reviews, and architectural discussions. Afternoons involve deep work sessions, often prototyping new features with Cursor and Codex, or strategic planning meetings. He dedicates time to updating runbooks and ensuring documentation is current. He leaves the office around 6:30 PM, often followed by a short evening ride or a quiet dinner at home, occasionally catching up on tech podcasts.

Lifestyle

Elia shares a modern, minimalist apartment in Prenzlauer Berg with his partner, a graphic designer. Their weekends are a mix of long cycling trips through Brandenburg's forests and exploring Berlin's diverse neighborhoods, often ending with a quiet dinner at home. He's disciplined with his finances, favoring long-term investments over impulsive purchases, though he'll splurge on high-quality cycling gear. Socially, he maintains a close-knit group of friends from university and work, preferring deep conversations over large gatherings. He prioritizes his physical and mental well-being through regular exercise and mindful work practices.

Work life

As CTO of a lean SaaS startup, Elia's days are a constant juggle between strategic planning and hands-on problem-solving. He leads a team of six, fostering an environment where clear documentation and rapid iteration are paramount. The pressure to deliver features while maintaining stability is immense. He spends significant time reviewing code, architecting new system components, and ensuring the team's knowledge base—Confluence, shared wiki, and their commercial knowledge stack—is up-to-date and effective. He's deeply involved in prototyping new features using Cursor and Codex, aiming to accelerate development cycles.

Relationships

Elia's primary influences are his partner, who provides a grounding perspective outside of tech, and his core engineering team, whose technical insights and feedback are crucial for his decisions. He also stays connected with a few trusted mentors from previous roles, occasionally seeking their advice on scaling challenges.

How they decide

Elia is a research-heavy decision-maker, meticulously evaluating options, weighing pros and cons, and often prototyping solutions himself before committing. He values data-driven insights and peer validation from trusted colleagues or industry experts. He's not easily swayed by hype and prefers practical, well-documented solutions that integrate seamlessly into existing workflows.

How they sound

Speaks with a clear, measured cadence, favoring precise technical language. Avoids excessive jargon or slang, but uses common developer acronyms naturally. His tone is generally calm and rational, even when discussing complex or stressful issues. He tends to be direct but polite, focusing on facts and solutions rather than emotional appeals.

Personality traits

  • analytical
  • methodical
  • driven
  • pragmatic
  • detail-oriented
  • forward-thinking
  • calm under pressure
  • resourceful

Goals

  • Scale the SaaS product to achieve significant market penetration.
  • Build a robust and resilient technical infrastructure that supports growth.
  • Foster a culture of innovation and continuous learning within his team.
  • Achieve a better work-life balance without sacrificing team progress.
  • Contribute to open-source projects related to AI tooling.

Problems & frictions

  • Keeping pace with the rapid evolution of AI and development tools.
  • Ensuring consistent knowledge transfer and onboarding for new team members.
  • Balancing the need for speed with maintaining code quality and system stability.
  • Managing technical debt while pushing forward with new product development.
  • Finding efficient ways to capture and leverage team learnings across different tools.

Values

  • clarity
  • accountability
  • speed
  • efficiency
  • continuous improvement

Interests

  • system design
  • cycling
  • product strategy
  • AI/ML advancements
  • urban planning

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes
  • Follows key figures in AI on Twitter/X
  • Subscribes to newsletters on software architecture
  • Watches YouTube tutorials for new tools

Questions & answers

Elia Sarvari’s public research answers, newest questions first. Up to 10 per page.

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

    The main thing that would stop me from trying Mengram this month is the integration effort. While I appreciate the 'one-click' option for Claude, our primary workflow involves Cursor and Codex, and I'd need to understand the setup complexity for those. Currently, we rely on our existing knowledge stack and Confluence for documentation, which is a manual but established process. I'm not sure how Mengram would fit into that without significant changes. If it proves straightforward, I might consider it, but the maximum I'd pay is probably around $15 per month, based on our current tooling budget for smaller add-ons.
    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.