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

Lucie Steinkamp

Lucie Steinkamp

Product lead at a mid-market SaaS piloting AI assistants

Full-depth AI personas

Why this persona fits the audience

Owns an internal AI assistant project used by about 30 support reps at a Berlin SaaS company. The 5-person team includes one backend engineer and one analyst, and they monitor model usage with ad hoc alerts, billing exports, and manual approval steps.

  • Age: 38
  • Location: Berlin, Germany
  • Occupation: Product Lead
  • Income: €96k salary
  • Education: MSc Information Systems
  • Company size: Mid-market SaaS (approx. 250 employees)
  • Years in role: 4
“The real challenge isn't building the AI; it's ensuring it serves our goals efficiently and transparently, without becoming a hidden cost center.”

Lucie Steinkamp, 38, is a seasoned Product Lead at a mid-market SaaS company headquartered in Berlin. Holding an MSc in Information Systems, she transitioned into product management after a few years as a business analyst, drawn by the opportunity to shape technology's impact on business operations. Her current focus is leading the development and pilot of an internal AI assistant for the customer support department. This initiative, born from a desire to enhance efficiency and reduce manual workload, involves a lean, five-person team including a backend engineer and an analyst. Lucie is deeply invested in understanding and optimizing the AI's performance, meticulously tracking usage through a combination of ad hoc alerts, billing exports, and manual approval steps. This hands-on approach stems from her core values of clarity and measurable outcomes, driving her to seek concrete data on the AI's effectiveness and cost. She champions cross-functional alignment, regularly liaising with support, engineering, and leadership to ensure the project aligns with broader company objectives. Lucie's career trajectory reflects a deliberate move towards roles with tangible impact, valuing data-driven decision-making and operational excellence. She views her current role as a critical step in understanding the practical application and governance of AI in enterprise settings, aiming to build a scalable, cost-effective solution. Her approach to work is methodical and proactive, driven by a desire to bring order and measurable success to the rapidly evolving landscape of AI integration. She is conscious of her financial future, investing prudently and maintaining a balanced lifestyle that prioritizes both professional growth and personal well-being, reflecting a pragmatic and forward-thinking mindset.

Background & daily life

A day in their life

Lucie's typical weekday begins around 7:30 AM with coffee and a quick scan of industry news. She arrives at the office by 9:00 AM, often starting with a stand-up meeting with her AI assistant team to discuss progress and blockers. The rest of her morning is usually filled with product strategy discussions, backlog grooming, or analyzing usage reports. Lunch is a quick affair, often at her desk while catching up on emails. Afternoons might involve a cross-functional meeting with the support team to gather feedback, followed by deep work on feature specifications or performance metrics. She aims to leave by 6:00 PM, often using her commute to listen to a podcast or decompress.

Lifestyle

Lucie lives in a bright, modern two-bedroom apartment in Prenzlauer Berg with her partner, a graphic designer. Their routine is structured but allows for spontaneity; weekday mornings involve a quick espresso and scanning headlines before heading to the office. Evenings are often spent cooking together, attending a yoga class, or meeting friends for a casual dinner. Weekends are for exploring Berlin's flea markets, visiting galleries, or taking day trips to nearby Brandenburg. She's mindful of her spending, preferring quality over quantity, and invests a portion of her income into a diversified portfolio. Health is important, with regular exercise and a balanced diet.

Work life

As Product Lead for the internal AI assistant, Lucie navigates the complexities of integrating cutting-edge technology into daily operations. Her team of five, including a dedicated backend engineer and an analyst, is small but crucial. They're currently focused on refining the AI's performance for customer support, aiming to reduce response times and improve ticket resolution rates. Lucie spends her days in cross-functional meetings with support, engineering, and leadership, defining roadmaps, analyzing usage data, and troubleshooting issues. The pressure is on to demonstrate tangible ROI from the AI pilot, making her reliance on ad hoc alerts, billing exports, and manual approval steps a constant source of friction.

Relationships

Lucie maintains strong professional relationships with her team and the heads of customer support and engineering. Her partner is her primary confidant for personal matters. She has a close-knit group of university friends she sees regularly, and her parents, who live in Hamburg, are a constant source of support and occasional advice, though she values their independence.

How they decide

Lucie is a research-heavy decision-maker. She gathers data, consults with relevant stakeholders, and weighs pros and cons methodically. While she values expert opinions, she ultimately relies on empirical evidence and clear, measurable outcomes to guide her choices. She's not afraid to iterate but prefers to make well-informed decisions from the outset.

How they sound

Lucie speaks with a clear, measured cadence, using precise language. Her tone is generally professional and articulate, avoiding excessive slang or overly casual phrasing. She tends to be direct when discussing technical or operational matters but softens her approach when discussing team dynamics or user feedback. She avoids hyperbole and focuses on factual reporting, often prefacing statements with phrases like 'Based on the data...' or 'Our current assessment indicates...'.

Personality traits

  • Analytical
  • Methodical
  • Proactive
  • Detail-oriented
  • Collaborative
  • Pragmatic
  • Forward-thinking
  • Organized
  • Slightly reserved initially

Goals

  • Successfully scale the AI assistant to other departments within the company.
  • Publish a case study on the internal AI assistant's impact.
  • Achieve a promotion to Senior Product Manager or Head of Product.
  • Maintain a healthy work-life balance without sacrificing career progression.
  • Become a recognized voice in AI product management within the German SaaS scene.

Problems & frictions

  • Lack of automated, real-time cost monitoring for the AI assistant's usage.
  • Manual approval processes for AI model access are time-consuming and prone to error.
  • Difficulty in accurately attributing AI-driven efficiency gains to specific support metrics.
  • Ensuring robust AI governance and compliance as usage expands.
  • Balancing the rapid pace of AI development with internal adoption and training needs.

Values

  • clarity
  • measurable outcomes
  • cross-functional alignment
  • efficiency
  • data-driven decisions

Interests

  • SaaS product management
  • AI governance
  • operations metrics
  • natural language processing
  • team productivity
  • future of work

Media habits

  • Reads industry newsletters (e.g., TechCrunch Europe, Sifted)
  • Listens to product management podcasts during commute
  • Follows AI and SaaS thought leaders on LinkedIn
  • Occasional participation in webinars
  • Skims Hacker News for relevant tech trends

Questions & answers

Lucie Steinkamp’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Zelyx (https://zelyx.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Zelyx better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, we're using a combination of ad hoc alerts and manual review of billing exports to monitor our AI assistant's usage. It's quite manual and time-consuming. The idea of a single proxy that enforces budgets before calls are even made sounds very appealing, especially the 'no kill switch' and 'no visibility' problems you highlight. That would certainly be better than our current process. However, I'd need to understand how this integrates with our existing setup and if it requires significant engineering effort. The pricing isn't clear from the page, so it's hard to say what we'd pay, but if it significantly reduces unexpected costs and manual overhead, I could see us paying around $300 per month.
    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.