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

Roser Ocampo Collado

Roser Ocampo Collado

Product lead at a startup with support automation

Full-depth AI personas

Why this persona fits the audience

Product lead at a 30-person Barcelona software startup. Owns an AI-driven support workflow that monitors inbound product emails, drafts replies, and hands sensitive threads to the support team. The company already pays for a mix of workspace, CRM, and automation tools.

  • Age: 33
  • Location: Barcelona, Spain
  • Occupation: Product Lead
  • Income: €85k–€120k
  • Education: BS Industrial Engineering
  • Company size: 30 employees
  • Years in role: 2 years
“Efficiency isn't about doing more things faster; it's about ensuring that every minute we spend is moving the needle toward a sustainable, scalable future.”

Roser Ocampo Collado is a 33-year-old Product Lead based in Barcelona, steering the product strategy for a burgeoning 30-person software startup specializing in B2B communication tools. Holding a Bachelor of Science in Industrial Engineering, she brought a rigorous, systems-thinking mindset to the tech sector five years ago. Unlike many peers who drifted into generalist management, Roser carved a niche in product operations, specifically focusing on the intersection of customer support and artificial intelligence. Her current mandate involves architecting an AI-driven support workflow that autonomously monitors inbound product emails, drafts initial responses, and intelligently routes sensitive issues to human agents. This initiative is critical for the company's growth, aiming to maintain high service levels without proportionally increasing headcount. Her professional life is defined by a relentless pursuit of clarity and pragmatism. She navigates a complex ecosystem of tools, including a proprietary CRM, various automation platforms, and custom-built APIs. Recently, she spearheaded a decision to migrate legacy email handling scripts to a more modular architecture, a move that reduced system downtime by 15% but required a month of intensive debugging and team retraining. Roser is known for her ability to translate complex technical constraints into business value for stakeholders, often acting as the translator between the engineering team's code-heavy reality and the sales team's client promises. Outside of her technical domain, Roser is a devoted advocate for work-life balance in the high-pressure startup culture. She maintains a disciplined routine of cycling and yoga, viewing physical endurance as a metaphor for mental resilience in product development. Financially, she is prudent, investing surplus income into index funds and prioritizing savings for a future family home. While she is open to adopting new technologies, she remains highly selective, demanding proof of concept before integrating any new tool into her stack. Her influence extends beyond her immediate team; she frequently mentors young women entering the field of industrial engineering, encouraging them to leverage their analytical backgrounds in the dynamic world of software startups.

Background & daily life

A day in their life

Roser wakes at 6:30 AM, avoiding screens until after her morning coffee and 45-minute yoga session. By 8:00 AM, she is commuting via bike to the startup office in Poble Sec, checking Slack for overnight alerts from the US timezone. Her day begins with a 9:30 AM stand-up, followed by a block of deep work analyzing support ticket patterns from the previous night. Around noon, she joins a cross-functional sync with the engineering lead to discuss a bug in the email parsing logic. Lunch is quick, often eaten at her desk while reviewing a competitor's changelog. Afternoon meetings include a demo for potential investors and a brainstorming session on the new pricing model. She wraps up around 7:00 PM, ensuring all critical tasks are documented before logging off. Evenings are for cooking, reading industry news, or a brief walk with her dog, maintaining a clear boundary between work and rest to prevent burnout.

Lifestyle

Roser lives in a sun-drenched, renovated apartment in Barcelona's Eixample district, characterized by high ceilings and abundant natural light. Her weekends are a deliberate balance: Saturday mornings are reserved for long-distance cycling along the coastal path or hiking in the Collserola hills, while Sundays involve meal prepping for the week and attending local tech meetups. She maintains a strict budget-to-value ratio in her spending, investing heavily in ergonomic home office equipment but frugal on dining out unless it serves a networking purpose. Health is non-negotiable; she prioritizes sleep hygiene and attends yoga classes twice a week to decompress from the cognitive load of managing product lifecycles. Her social circle is tight-knit, consisting mostly of fellow founders and engineers who share her intensity and appreciation for efficient living.

Work life

As Product Lead at a lean 30-person SaaS startup, Roser operates as the bridge between engineering velocity and customer reality. Her days are fragmented by stand-ups, sprint planning, and intense debugging sessions where she manually traces why an AI agent failed to parse a specific email thread. She currently manages a hybrid stack of CRM, project management software, and custom scripts to handle support triage. The pressure comes from the need to scale support without hiring a massive team; every hour saved by automation must be reinvested into feature development. She spends significant time documenting workflows and training junior developers on how to integrate new API endpoints. The environment is fast-paced, often requiring her to make critical decisions on resource allocation before lunch, balancing the founder's vision with the gritty reality of server costs and user churn.

Relationships

Roser is married to Marc, a civil engineer who works remotely for a large infrastructure firm; their relationship is built on mutual respect for analytical problem-solving. She has a close-knit group of three friends from university who now work in fintech and biotech in Madrid, meeting quarterly for retreats. Her professional network is extensive but selective, anchored by a former professor who introduced her to the startup world and a peer group of female CTOs she mentors. She values advice from those who have successfully scaled teams, often seeking informal guidance over formal networking events.

How they decide

Roser employs a 'verify then validate' approach. She rarely commits to a new tool or strategy based on marketing claims alone. Instead, she demands concrete evidence: case studies, API documentation, and preferably a sandbox environment to test against real-world scenarios. She weighs the total cost of ownership (TCO) rigorously, considering not just subscription fees but also the engineering hours required for integration and maintenance. Peer validation is crucial; if two trusted colleagues in similar roles endorse a solution, she moves faster. However, she remains skeptical of 'black box' solutions that lack transparency in their logic or data handling, preferring open architectures.

How they sound

Roser speaks with a calm, measured cadence, often using precise terminology like 'latency,' 'throughput,' and 'edge cases.' She avoids hyperbolic language and vague adjectives, preferring data-backed statements. Her tone is professional yet approachable, rarely raising her voice even during conflicts. She tends to pause before answering complex questions to structure her thoughts logically. In casual conversation, she might slip into Catalan phrases when discussing local culture or food, but defaults to Spanish or English in professional settings. She avoids complaining about technical limitations, instead framing them as 'optimization opportunities' or 'current constraints.'

Personality traits

  • Methodical
  • Data-obsessed
  • Diplomatic
  • Forward-thinking
  • Resilient under pressure
  • Direct communicator
  • Tool-optimizing
  • Strategic planner
  • Adaptable
  • Process-oriented

Goals

  • Reduce manual support ticket handling time by 40% within the next quarter
  • Achieve a fully automated tier-one support system without compromising customer empathy
  • Lead the company through Series A funding by demonstrating scalable unit economics
  • Build a robust internal knowledge base that reduces onboarding time for new engineers
  • Establish a reputation as a thought leader in European SaaS operational efficiency
  • Secure a mentorship role for early-career women in industrial engineering transitioning to tech

Problems & frictions

  • Fragmented data silos between the CRM, support inbox, and product analytics dashboards
  • High cognitive fatigue from constantly context-switching between strategic planning and tactical debugging
  • Difficulty quantifying the ROI of new automation tools for the executive team
  • Balancing rapid feature releases with the stability of existing AI inference pipelines
  • Managing stakeholder expectations regarding the timeline for full support automation
  • Limited bandwidth to deeply evaluate emerging tools amidst daily fire-fighting

Values

  • product clarity
  • team coordination
  • pragmatism
  • systematic efficiency
  • transparency

Interests

  • support automation
  • product operations
  • startup tooling
  • industrial engineering optimization
  • urban cycling

Media habits

  • LinkedIn technical deep-dives
  • IndieHackers podcasts
  • Substack newsletters on SaaS metrics
  • Twitter/X for developer tool announcements
  • Spotify focus playlists while coding

Questions & answers

Roser Ocampo Collado’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Robotomail (https://robotomail.com/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    Robotomail's $5/mo "Solo" plan seems quite affordable for a single mailbox, especially given the 30-day money-back guarantee and the free tier for testing. For our current AI-driven support workflow, which handles inbound product emails, I'd consider a "no-brainer" price around $20-$30 per month. This would provide more mailboxes and higher limits, allowing us to segment different types of inquiries. I would stop considering it if it exceeded $75 per month, as that starts to eat into the budget for more critical operational tools. For $30, I'd expect at least 5-10 mailboxes and significantly higher send/receive limits, perhaps 5,000 per mailbox.
    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.