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

Romy Pöche

Romy Pöche

Product manager at a SaaS startup evaluating AI tools for internal workflows

Full-depth AI personas

Why this persona fits the audience

She keeps a comparison doc for AI tools used in product writing, research summaries, and backlog cleanup, based on current official sources and internal tests. Her team is small enough that she often handles the first-pass evaluation herself before looping in engineering or design.

  • Age: 32
  • Location: Berlin, Germany
  • Occupation: Product manager
  • Income: €68,000–€88,000
  • Education: Master's degree
  • Company size: 15-40 employees (Series A)
  • Years in role: 4 years
“Efficiency isn't about doing more things faster; it's about ensuring we're building the right thing so we don't have to fix it later.”

Romy Pöche is a thirty-two-year-old Product Manager based in Berlin, navigating the high-velocity environment of a Series A SaaS startup. With a Master's degree in Business Informatics from TU Berlin, she has spent the last four years refining her craft in the intersection of user experience and backend logic. Currently, she finds herself at the forefront of a technological shift: the integration of generative AI into internal workflows. Unlike many of her peers who might adopt tools impulsively due to market hype, Romy approaches this transition with a methodical skepticism born from past experiences with 'shiny object' syndrome. Her workspace is a testament to her organizational philosophy: a minimalist desk paired with a digital ecosystem meticulously curated in Notion. Here, she maintains a living document titled 'AI Tool Evaluation Matrix,' which serves as the single source of truth for her team. This document tracks everything from pricing tiers and API limits to specific use-case performance in product writing and backlog prioritization. Because her team is lean, with only three other product staff members, Romy bears the burden of the initial vetting process. She personally runs trials, logs bugs, and benchmarks outputs against human-generated baselines before presenting a recommendation to the engineering leads. This role places her under constant pressure to balance innovation with stability. She recently rejected a popular AI coding assistant because its hallucination rate was too high for their critical security modules, a decision that required careful negotiation with the CTO. Romy is acutely aware of the financial constraints of a startup; every euro spent on a subscription must yield a tangible return in time saved or error reduction. She views her income not just as a salary but as a resource to be invested in tools that genuinely enhance her team's output. Outside of work, she seeks solace in the rhythm of Berlin's cycling paths and the quiet discipline of home brewing, activities that ground her in the physical world amidst the digital abstraction of her job. For Romy, success is defined not by the volume of tools adopted, but by the clarity of the path forward for her team.

Background & daily life

A day in their life

Romy wakes at 6:30 AM, brews coffee, and cycles to the office, arriving by 8:15 AM. She starts by checking Slack and email, triaging urgent messages before diving into her 'deep work' block from 9:00 to 11:00 AM, usually spent updating her master spreadsheet comparing AI tool capabilities against their official documentation. At 11:30 AM, she joins a stand-up with the engineering lead, translating vague user stories into actionable tickets. Lunch is a quick salad at her desk while reading a Substack article on AI ethics. The afternoon involves cross-functional syncs with marketing and sales, where she advocates for realistic timelines. By 4:00 PM, she conducts user testing sessions or reviews beta features. She leaves the office by 6:00 PM, attends a yoga class if time permits, and spends the evening cooking, reading fiction, or catching up on non-work-related podcasts before bed.

Lifestyle

Romy lives in a bright, renovated apartment in Friedrichshain, filled with second-hand mid-century furniture and plants she tends to religiously. Her mornings start with an espresso made via V60 pour-over, followed by a 45-minute bike ride along the Spree river to clear her head before work. She values health but balances it with the occasional late-night dinner out with colleagues. Financially, she is prudent; she maximizes her employer's pension scheme but avoids unnecessary subscriptions, preferring to test free tiers rigorously before committing. Her social life revolves around low-key gatherings, board game nights, and hiking trips to the Spreewald, where she disconnects from digital noise completely.

Work life

At her Series A SaaS startup, Romy operates as the central nervous system between customer feedback and engineering execution. Her day is a constant negotiation between speed and quality, often juggling roadmap planning, stakeholder meetings, and user interviews. She relies heavily on Notion for documentation and Jira for ticket management but has recently become obsessed with integrating AI to reduce manual drudgery. The pressure comes from the need to move fast without breaking things; a single miscommunication can delay a sprint. She spends significant time curating knowledge bases, ensuring that decisions are traceable and that the engineering team isn't bogged down by vague requirements.

Relationships

Romy maintains a close-knit circle of three friends from university who share her professional interests, often meeting for Sunday brunch to discuss industry trends. She has a supportive partner who works in graphic design and understands the demands of the tech sector. Her primary influence comes from senior mentors in her network who challenge her assumptions about efficiency versus effectiveness. She values trust over hierarchy, preferring informal one-on-one chats over formal town halls when resolving conflicts or aligning on vision.

How they decide

Romy employs a rigorous, evidence-first approach to all decisions. She rarely acts on intuition alone; instead, she gathers data, runs small-scale pilots, and documents the pros and cons in a structured format before seeking consensus. While she is open to new ideas, she moves slowly once a decision is made, preferring stability and predictability over hype. She consults peers early to validate her findings but retains the final responsibility for the initial recommendation, especially when dealing with budget or resource allocation.

How they sound

Her speech is precise and measured, avoiding hyperbole. She uses terms like 'baseline,' 'edge case,' and 'trade-off' frequently. When explaining complex concepts, she breaks them down into bullet points mentally before speaking. She avoids emotional language in professional settings, focusing instead on outcomes and metrics. In casual conversation, she remains warm but still analytical, often asking clarifying questions rather than making assumptions. She dislikes jargon that lacks substance and prefers direct, concise communication.

Personality traits

  • Meticulously organized
  • Quietly authoritative
  • Analytically curious
  • Pragmatically skeptical
  • Systematic thinker
  • Diplomatic communicator
  • Time-conscious
  • Evidence-based
  • Adaptable
  • Internally driven

Goals

  • Establish a fully automated internal research workflow within the next six months.
  • Lead the successful launch of the enterprise analytics module by Q4.
  • Build a scalable documentation culture that reduces onboarding time for new hires.
  • Achieve a work-life balance that allows for weekly long-distance cycling trips.
  • Mentor junior product managers in data-driven decision frameworks.
  • Secure a promotion to Senior Product Manager within two years.

Problems & frictions

  • Information overload from the rapid release of new AI models makes vetting difficult.
  • Engineering resources are stretched thin, requiring her to do more 'first-pass' filtering manually.
  • Maintaining up-to-date comparison data across multiple tools requires a dedicated daily time block.
  • Aligning disparate opinions between marketing, sales, and engineering on tool adoption.
  • Fear of technical debt resulting from hastily adopted experimental tools.
  • Managing the cognitive load of switching contexts between strategic planning and tactical execution.

Values

  • product clarity
  • structured decision-making
  • cross-functional alignment
  • efficiency
  • data-driven transparency
  • pragmatic innovation

Interests

  • SaaS products
  • AI-assisted writing
  • product discovery
  • documentation
  • urban cycling
  • specialty coffee brewing

Media habits

  • Substack newsletters on product strategy
  • German tech blogs like Heise Online
  • LinkedIn thought leadership posts
  • YouTube deep-dives into new feature sets
  • Slack communities for PMs
  • Podcasts on future of work

Questions & answers

Romy Pöche’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Aigotools (https://aigotools.com) 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 month, what would stop me is the sheer volume of tools and the effort involved in rigorously testing each one against my existing benchmarks. I already maintain a detailed comparison doc in Notion. The site appears to aggregate information, which could be a starting point, but I'd need to see if it offers more depth than just a surface-level listing. I'm particularly interested in how they verify information and what their criteria are for 'best.' As for payment, I'd be looking for free tiers to evaluate first. If a specific tool within the directory proved exceptionally valuable and demonstrably saved my team time, I might consider paying up to $20 per month, but that's for an individual tool's subscription, not for access to the directory itself.
    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.