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

Cedric Pouros

Cedric Pouros

Product manager using AI tools in a small B2B team

Full-depth AI personas

Why this persona fits the audience

He is the product manager at a 9-person SaaS startup and routinely prototypes workflows with one designer and two engineers. He checks model outputs in notebook drafts, Slack bots, and internal tools, and his team already experiments with a mix of frontier models, open-source wrappers, and manually maintained prompts.

  • Age: 36
  • Location: Berlin, Germany
  • Occupation: Product manager
  • Income: $95k-$130k
  • Education: Master's in business and technology
  • Company size: 9 people
  • Years in role: 4
“Every line of code, every model inference, every user interaction is a data point. The challenge is connecting them all to build something truly valuable, not just technically interesting.”

Born and raised in a smaller town outside Munich, Cedric developed an early fascination with how technology could solve complex problems. He pursued a Master's in Business and Technology, which provided a strong foundation in both strategic thinking and technical understanding. His early career involved a stint at a large German automotive manufacturer, where he gained experience in structured product development but felt constrained by corporate bureaucracy. Seeking more agility and impact, he moved to Berlin five years ago and joined a burgeoning SaaS startup. Two years ago, he transitioned into his current role as Product Manager, focusing intently on integrating AI capabilities into their B2B offering. He was instrumental in championing the team's current experimental approach to LLMs, arguing that embracing cutting-edge, albeit less stable, models could provide a competitive edge. He recently championed a decision to allocate a small portion of their cloud budget to experimenting with a new, highly capable frontier model via API, despite the higher per-token cost, believing its superior output quality for specific tasks justified the investment over a cheaper, open-source alternative they manually maintained. Cedric views his role as a constant balancing act: pushing the boundaries of what's possible with AI while ensuring the team consistently ships reliable, impactful features that resonate with their customer base. Time is his most precious commodity, and he meticulously guards it, optimizing his routines to maximize deep work and minimize distractions. While status isn't his primary driver, he derives significant satisfaction from building successful products and solving challenging problems, seeing his equity stake as a tangible measure of his contribution.

Background & daily life

A day in their life

Cedric's typical weekday begins around 7 AM with coffee and a check of overnight build statuses and key metrics. After his run and breakfast, he dives into team stand-ups, followed by deep work sessions: refining user stories, analyzing A/B test results for a new AI feature, or testing prompt variations for a customer support bot. Lunch is often a quick affair at his desk while reviewing industry news. The afternoon might involve a product strategy meeting with the CEO, a virtual sync with a potential integration partner, or pair-prompting with an engineer on a complex workflow. He aims to wrap up by 6:30 PM, often spending the evening catching up on reading or prepping for the next day.

Lifestyle

Cedric lives in a bright, minimalist Kreuzberg apartment, shared with his partner, an architect. His mornings often start with a strong pour-over coffee he grinds himself, followed by a quick run through Tempelhofer Feld, listening to podcasts. Weekends involve exploring Berlin's markets, tending to his small balcony herb garden, and occasionally meeting friends for craft beer. He’s conscious about his health and finances, investing steadily and prioritizing experiences over material possessions, though he does appreciate well-designed tools that simplify his life.

Work life

As a PM at a lean SaaS startup, Cedric's days are a whirlwind of strategy, execution, and rapid iteration. He works closely with a designer and two engineers, translating ambitious product goals into tangible features. The team’s current focus is integrating AI agents for internal workflow automation, meaning Cedric spends considerable time evaluating LLM outputs, crafting prompts, and testing prototypes in various interfaces, from Jupyter notebooks to custom Slack bots. The pressure is always on to ship quickly and demonstrate clear ROI, especially as they navigate a competitive landscape with limited resources.

Relationships

Cedric maintains a close, collaborative relationship with his co-founders and small team, viewing them as partners in the startup's journey. He stays in touch with former colleagues from larger tech firms, occasionally seeking advice. His partner offers a grounding perspective outside the tech bubble. Socially, he has a core group of friends from university, many of whom are also in tech or related fields.

How they decide

Cedric is a data-informed pragmatist. He researches thoroughly, weighing pros and cons, but ultimately prioritizes solutions that demonstrably move the needle on key metrics. He values peer recommendations within trusted circles and is willing to experiment with new approaches if the potential upside is significant and the risk is manageable, especially if it involves tools that promise greater efficiency.

How they sound

Speaks clearly and deliberately, with a slight German accent that becomes more pronounced when he's passionate or explaining a complex topic. He uses precise language, avoiding excessive jargon unless discussing technical specifics with engineers. Tends to be direct and focused in conversation, often summarizing points to ensure clarity. He avoids overly casual slang but is comfortable with industry-standard acronyms.

Personality traits

  • Analytical
  • Pragmatic
  • Proactive
  • Detail-oriented
  • Collaborative
  • Resourceful
  • Forward-thinking
  • Driven
  • Slightly impatient with inefficiency

Goals

  • Successfully launch and scale the startup's core AI product.
  • Develop a reputation as a product leader in the AI-driven B2B SaaS space.
  • Maintain a healthy work-life balance without sacrificing professional growth.
  • Continuously learn and master new AI technologies.
  • Achieve financial independence through equity in the startup.

Problems & frictions

  • Balancing the rapid pace of AI development with the need for stable, production-ready features.
  • Managing limited engineering resources to implement complex AI integrations.
  • Articulating the value proposition of AI-powered features to less technical stakeholders.
  • Ensuring data privacy and security as AI models become more integrated.
  • Keeping up with the sheer volume of new AI research and tools emerging daily.
  • The inherent unpredictability of frontier model outputs.

Values

  • shipping
  • clarity
  • collaboration
  • measurable impact
  • efficiency

Interests

  • product strategy
  • AI prototypes
  • startup news
  • running
  • ethically sourced coffee
  • urban gardening

Media habits

  • Reads Hacker News and TechCrunch daily
  • Listens to AI/startup podcasts during runs (e.g., Lex Fridman, Acquired)
  • Follows AI researchers and product leaders on Twitter/X
  • Skims newsletters from Y Combinator and specific AI labs
  • Watches YouTube tutorials on LLM fine-tuning and prompt engineering

Questions & answers

Cedric Pouros’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://asterwise.dev/ (Aster by AsterWise) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core concept of "intelligent auto-routing" for AI models is intriguing, especially the idea of matching tasks to the most suitable model to balance cost and performance. However, the page doesn't immediately clarify *how* this routing works in practice for someone like me, who prototypes workflows with a small engineering team. I'd leave if I couldn't quickly grasp the practical integration or see concrete examples relevant to our use cases, like automating internal tools. To sign up, I'd need to see a clear, simple API integration guide and perhaps a sandbox environment to test the routing logic with our own prompt variations. The claims about cost savings and task success are compelling, but I’d need more than "unverified estimates" to be convinced.
    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.