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

Matis Liebe

Matis Liebe

Devtools technical cofounder

Full-depth AI personas

Why this persona fits the audience

He is the technical cofounder of a Berlin devtools startup that currently has exactly three people total: him, another engineer, and a founder who handles sales. He spends most days on infrastructure, release engineering, and conversations with early adopters.

  • Age: 29
  • Location: Berlin, Germany
  • Occupation: Cofounder and Backend Engineer
  • Income: €58k draw + equity
  • Education: Dipl.-Ing. Informatik
  • Company size: 3
  • Years in role: 2
“The elegance of a system isn't just in its performance, but in how gracefully it handles complexity and change.”

Matis Liebe, 29, is a cofounder and backend engineer at a nascent devtools startup in Berlin, a city he chose for its vibrant tech scene and relatively affordable cost of living compared to other major European hubs. He holds a Dipl.-Ing. in Informatik from a respected German technical university, where he developed a deep appreciation for robust engineering principles and distributed systems. His early career involved a stint at a larger SaaS company, where he gained valuable experience in scaling infrastructure but grew frustrated with the slow pace of innovation and bureaucratic hurdles. This experience fueled his desire to build something from the ground up, prioritizing agility and technical excellence. He co-founded his current venture two years ago with a vision to streamline developer workflows, a mission he pursues with intense focus. His current role is demanding, requiring him to architect and maintain the core infrastructure, manage release engineering, and directly engage with the company's first wave of users. He lives frugally, drawing a modest salary that allows for essential living expenses and reinvestment into the company, with his primary financial focus being the equity stake he holds. He views time as a critical resource, constantly seeking ways to optimize his workflow and the company's processes to accelerate development without sacrificing quality. His technical decisions are guided by a commitment to long-term maintainability and privacy, often favoring open-source solutions and well-understood patterns over trendy, unproven technologies. He recently decided to invest significant effort into containerizing their core services to improve deployment consistency, a move that required him to deep-dive into Kubernetes configurations, a task he found both challenging and rewarding.

Background & daily life

A day in their life

Matis's typical weekday begins around 8:00 AM with a strong pour-over coffee. After reviewing overnight alerts and checking key metrics, he dives into coding, often focusing on a specific infrastructure task like optimizing database queries or refining the CI/CD pipeline. Around mid-morning, he might have a brief sync with the other engineer to discuss code reviews or upcoming tasks. Lunch is usually a quick, healthy meal prepared at home. The afternoon often involves a scheduled call with an early adopter to demo a new feature or troubleshoot an issue, followed by more coding or architectural planning. He aims to wrap up by 7:00 PM, though urgent issues can extend this. Evenings are for unwinding, perhaps reading sci-fi or tinkering with a personal coding project.

Lifestyle

Matis lives in a shared flat in Prenzlauer Berg, a compromise for now to keep costs down. His routine is heavily dictated by the startup's needs, but he carves out time for cycling on weekends, often exploring Brandenburg's forests. He's meticulous about his home coffee setup, grinding beans fresh each morning. Socially, he's more of a listener than a talker, preferring deep conversations with a few close friends over large gatherings. He's conscious of his spending, prioritizing investments in his skills and the company over immediate luxuries, though he occasionally splurges on a high-quality mechanical keyboard or a new sci-fi novel.

Work life

As the technical cofounder, Matis is deeply immersed in the operational backbone of their devtools startup. His days are a blend of hands-on coding for infrastructure improvements, setting up CI/CD pipelines, and optimizing deployment processes. He also dedicates significant time to engaging with their handful of early adopters, gathering feedback on usability and identifying critical bugs. The pressure is constant, stemming from the need to build a robust product with limited resources and a tiny team. He works closely with the other engineer on code reviews and architectural decisions, and frequently syncs with the sales-focused founder on user pain points and feature prioritization.

Relationships

Matis maintains a small circle of close friends, mostly fellow engineers he met during university or at previous tech meetups. His relationship with his co-founders is professional and collaborative, built on mutual respect for each other's roles. He stays in touch with his parents back in Bavaria, who are supportive but don't fully grasp the startup grind. His primary influence comes from respected figures in the open-source and distributed systems communities.

How they decide

Matis is a research-heavy and analytical decision-maker. He thoroughly investigates technical options, weighing pros and cons based on performance, maintainability, and long-term scalability. He often consults documentation, benchmarks, and community discussions before committing to a path. For strategic decisions, he relies on data and logical reasoning, preferring to avoid impulsive choices.

How they sound

Speaks with a measured, thoughtful cadence. Uses precise technical language when discussing work, but can switch to more casual German when talking with friends. Avoids hyperbole and overly emotional language. Tends to explain his reasoning thoroughly. Might use phrases like 'essentially,' 'from a systems perspective,' or 'the core challenge here is...' He's not one for small talk but is articulate when engaged on a topic he cares about.

Personality traits

  • analytical
  • detail-oriented
  • pragmatic
  • curious
  • methodical
  • reserved
  • driven
  • independent

Goals

  • Build a stable, scalable platform that early adopters love.
  • Achieve product-market fit within the next 18 months.
  • Continuously learn and master new backend technologies and system design principles.
  • Maintain a healthy work-life balance, even as the startup grows.
  • Contribute meaningfully to the open-source community.

Problems & frictions

  • Balancing infrastructure scaling needs with immediate feature development demands.
  • Limited bandwidth for deep R&D due to operational responsibilities.
  • Onboarding new users effectively with minimal documentation.
  • The inherent uncertainty and financial precarity of an early-stage startup.
  • Finding time for personal learning projects outside of urgent startup tasks.

Values

  • technical elegance
  • fast iteration
  • learning
  • privacy
  • autonomy

Interests

  • open source
  • cycling
  • home coffee
  • science fiction
  • distributed systems

Media habits

  • Hacker News
  • Ars Technica
  • The Pragmatic Engineer newsletter
  • various tech podcasts (e.g., Syntax, Changelog)
  • YouTube channels on system design and programming

Questions & answers

Matis Liebe’s public research answers, newest questions first. Up to 10 per page.

  1. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: The One-Person Company.

    This product, Agent Teams, promises to automate key functions like product development, growth, and operations by using AI agents. As the technical cofounder of a three-person startup, this sounds appealing, especially the idea of "agents manage agents" and "you lead the company." My biggest bottleneck is often balancing infrastructure needs with feature development, and freeing up my time from operational tasks could be invaluable. However, the specifics of how these agents "carry product forward" or "connect market research" are unclear. It feels like a significant leap to delegate these to AI, and I'd need to understand the level of oversight and the potential for errors, especially with our limited resources. The $199/month price is within reason for a small team, but the core functionality needs to be proven.
    View answer & full research →
  2. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Teams for Startups of 1–5 People.

    The primary concern is the actual reliability and integration of these AI teammates into our existing workflow. While the concept of AI support for product, growth, and operations is appealing, I need to understand how seamlessly they integrate with our current systems and how much oversight is truly required. The biggest blocker would be if these agents introduce more complexity or require significant manual configuration, negating the intended efficiency gains. I'd need to see concrete examples or perhaps a trial period demonstrating how they handle tasks, share context, and adhere to our priorities without constant intervention. The claim of "no per-seat fees" is interesting, but the base $199/month plan for one agent feels like a significant upfront cost for an unproven capability.
    View answer & full research →
  3. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: AI Teams for Startups of 1–5 People.

    I would investigate further. The concept of AI teammates for product, growth, and operations is intriguing for a small team like ours, especially with the promise of parallel work and shared context. However, the core challenge for us is balancing infrastructure scaling with immediate feature demands, and I'm not yet convinced how these AI agents would directly alleviate that specific bottleneck. My most important unanswered question is about the level of integration and customization available for backend infrastructure tasks – can these agents truly handle complex release engineering or CI/CD pipeline optimization, or are they more suited for higher-level product or marketing tasks? The price of $199/month is certainly within reach, but the value proposition needs to be clearly demonstrated for our specific technical needs.
    View answer & full research →
  4. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: AI Teams for Startups of 1–5 People.

    This product seems to offer AI teammates for specific functions like product development, growth, and operations, which could be interesting for a small team like ours. It might help offload some of the repetitive tasks or provide additional bandwidth. However, I'm unclear on how well these agents would integrate with our existing infrastructure and CI/CD pipelines. The idea of "persistent files, memory, and tools" for each agent is promising, but the practical implementation and the level of customization are not entirely clear from this page. I'd need to understand how much actual technical oversight is required and if it can truly work in parallel without creating more coordination overhead than it saves.
    View answer & full research →
  5. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: One Founder, a Company of Agents.

    From a systems perspective, the biggest concern is data privacy and security. We're handling sensitive user data, and relying on a third-party AI team for core operations requires a very high degree of trust. Ensuring that our users' information and our proprietary codebase remain secure and private is paramount. Additionally, the operational costs, while appearing reasonable at first glance with the $199/month starting price, need to be thoroughly evaluated against our current lean budget. I'd need to see detailed documentation on data handling, encryption protocols, and compliance certifications, as well as a clear breakdown of how costs scale with actual usage and complexity before considering adoption. Without that assurance, the risk is simply too high.
    View answer & full research →
  6. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: One Founder, a Company of Agents.

    I would investigate further. While the concept of an AI team handling product, growth, and operations is intriguing, my primary concern as a backend engineer is understanding the technical underpinnings. The main reason for further investigation is to gauge the actual technical capabilities and integration potential. The most important unanswered question is how these agents handle complex, nuanced tasks and data security, especially since our company prioritizes long-term maintainability and privacy.
    View answer & full research →
  7. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: One Founder, a Company of Agents.

    This product seems to offer AI agents to handle tasks like product development, growth, and operations. For my startup, this could potentially offload some of the significant overhead associated with customer support and onboarding, which are currently consuming a lot of my time with early adopters. The unclear part is how these agents integrate with existing systems and the actual level of autonomy they possess. I'm also concerned about the quality and consistency of AI-generated work, especially in a sensitive area like customer feedback.
    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.