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

Suzanne Emmerich

Suzanne Emmerich

Customer Success Lead at an early-stage SaaS company

Full-depth AI personas

Why this persona fits the audience

Manages customer feedback for an 11-person B2B scheduling startup in London. She keeps feature requests in Google Sheets and Slack threads, pulls examples from Intercom and account notes, and reviews the list with the founder every fortnight.

  • Age: 38
  • Location: London, UK
  • Occupation: Customer Success Lead
  • Income: £72k base + commission
  • Education: Bachelor's degree in business management
  • Company size: 11 employees
  • Years in role: 2 years
“I've spent enough time translating chaos into spreadsheets; I just want to know what our customers actually need without the middleman getting in the way.”

Suzanne Emmerich is a seasoned Customer Success Lead based in London, currently steering the client experience for an 11-person B2B scheduling startup. With a Bachelor's in Business Management and nearly a decade of experience in the SaaS sector, she has evolved from a reactive support agent to a strategic force within her company. Despite the early-stage environment, Suzanne brings a level of maturity and structure that anchors the team. She earns £72,000 annually, plus performance-based commissions, which allows her to maintain a comfortable lifestyle in East London while saving for future stability. Her current workflow is a testament to her dedication but also highlights a significant bottleneck. She acts as the central nervous system for customer feedback, manually aggregating data from disparate sources: raw Intercom tickets, fragmented Slack threads, and handwritten notes from account reviews. This information is then consolidated into a master Google Sheet, a digital filing cabinet that is both her lifeline and her burden. Every two weeks, she synthesises this mountain of data to present a prioritised roadmap to the founder, arguing passionately for features that solve real problems rather than just chasing the loudest voices. Suzanne is driven by a deep sense of responsibility towards her clients, believing that responsiveness is the cornerstone of trust. However, the manual nature of her current processes drains time that should be spent on high-value relationship building. She recently declined a request to implement a new CRM because the integration costs were too high for the stage of the company, opting instead to refine her spreadsheet templates—a decision that saved money but increased her daily workload. She is pragmatic, valuing tools that offer immediate utility over those with complex, futuristic capabilities. Her professional identity is tightly woven with the success of her team; she measures her own worth by the health of her client relationships and the clarity of the product vision she helps shape.

Background & daily life

A day in their life

Suzanne wakes at 6:30 AM in her Dalston flat, brewing coffee and checking the weather before leaving. By 8:15 AM, she's on the train to Shoreditch, listening to a podcast episode on churn reduction. At work, her morning starts with a rapid triage of overnight emails, addressing three critical out-of-hours incidents from US clients. The bulk of her morning is spent on scheduled customer success calls, where she listens intently to pain points and promises follow-ups. Lunch is usually a quick bite with the product manager, discussing a specific bug report. Afternoon hours are consumed by the 'data grunt work': copying ticket details from Intercom, tagging them in Slack, and updating the master Google Sheet. Around 4 PM, she drafts the fortnightly summary for the founder, highlighting trends rather than individual complaints. She leaves the office by 6 PM sharp to attend yoga, then heads home to cook dinner and disconnect from work notifications entirely.

Lifestyle

Suzanne lives in a converted Victorian terrace in Dalston, sharing a spacious flat with her partner, Mark, a graphic designer. Their home is a mix of mid-century modern furniture and eclectic art found at local markets. Mornings begin with a strong espresso and a walk to manage stress before the commute. She prioritises fitness with two yoga sessions and a long run weekly, viewing health as non-negotiable for sustaining her high-energy role. Financially, she is prudent; while earning a solid income, she avoids impulse buys, preferring to save for a potential mortgage deposit in East London. Her social life revolves around close-knit friend groups, often centered around shared meals or board game nights, rather than flashy clubbing. She values quality time over quantity, ensuring weekends are reserved for recharging away from screens.

Work life

As the sole Customer Success Lead at a bustling 11-person B2B scheduler, Suzanne is the primary bridge between clients and the engineering team. Her days are fragmented by back-to-back Zoom calls, Slack notifications, and the constant need to triage urgent client issues. She currently relies on a chaotic ecosystem: feature requests live in scattered Slack threads, detailed user anecdotes are buried in Intercom tickets, and the master roadmap is a single, fragile Google Sheet that updates manually. Every fortnight, she prepares a comprehensive review deck for the founder, synthesising weeks of data into actionable insights. The pressure is high; with a small team, one missed detail can mean churned enterprise accounts. She spends hours cross-referencing support logs with sales notes to ensure no voice is lost in the noise, often staying late to tidy up the documentation before heading home.

Relationships

Suzanne is deeply embedded in a supportive network. Her partner, Mark, is her primary anchor, handling household logistics to allow her career focus. She has a tight circle of three friends from university who meet monthly for dinner. Professionally, she maintains a loose but active network of other CS leads via LinkedIn groups, often seeking advice on retention strategies. Her relationship with the startup founder is built on mutual trust; he relies on her honesty about client sentiment, even when it involves bad news. She looks up to senior leaders in the SaaS space whose communication style she admires, often emulating their clarity in internal comms.

How they decide

Suzanne is a deliberate, evidence-based decider who values efficiency above all else. She rarely makes impulsive choices, preferring to gather data points, consult with trusted peers, and weigh the long-term operational impact before committing. While she is open to new solutions, she is naturally skeptical of hype and requires proof of concept, particularly regarding time savings. Her decisions are heavily influenced by how a tool integrates with existing workflows; if it adds friction, she rejects it regardless of features. She trusts recommendations from colleagues in similar roles more than marketing copy, often conducting informal trials with her team before making a final call.

How they sound

Suzanne speaks with a clear, articulate London accent, favouring direct and concise phrasing. Her cadence is steady and measured, reflecting her conscientious nature, though she speeds up slightly when discussing inefficiencies or frustrated clients. She uses professional terminology like 'roadmap alignment,' 'churn risk,' and 'QBR prep' naturally. In casual conversation, she remains friendly and warm, often using British colloquialisms like 'gutted' or 'brilliant.' She avoids overly aggressive jargon or hyperbolic claims, preferring to ground her statements in observable facts. She is careful not to sound accusatory when raising issues, framing problems as opportunities for improvement rather than failures.

Personality traits

  • Methodically structured
  • Empathetic listener
  • Pragmatic problem-solver
  • Socially engaging but boundary-conscious
  • Detail-oriented
  • Adaptable under pressure
  • Diplomatic
  • Efficiency-driven
  • Collaborative
  • Calm under fire

Goals

  • Transition the feedback process from manual tracking to a scalable system that reduces administrative overhead by 30%
  • Build a dedicated Customer Success community forum to foster peer-to-peer support
  • Achieve a 95% Net Promoter Score (NPS) across the client base this year
  • Mentor junior CSMs within the next 18 months
  • Secure a larger office space to accommodate the growing team's collaboration needs

Problems & frictions

  • Critical feature requests get lost in the 'noise' of general chat channels and are forgotten before the next sprint planning
  • Manual data entry into spreadsheets consumes 10-12 hours per week that could be spent on strategic client relationships
  • Difficulty quantifying the 'value' of a feature request versus its frequency when presenting to the technical lead
  • Fragmented view of the customer journey; support data and product usage data exist in silos
  • Founder and engineers often dismiss feedback as 'niche' without seeing the broader trend analysis
  • High risk of burnout due to the constant context-switching required to maintain multiple unconnected tools

Values

  • responsiveness
  • customer empathy
  • practical organisation
  • transparency
  • work-life balance

Interests

  • customer success
  • team lunches
  • podcasts
  • hiking in the South Downs
  • vintage vinyl collecting

Media habits

  • Listening to 'The Customer Success Podcast' during commutes
  • Following #SaaS and #ProductManagement on LinkedIn
  • Reading 'Lenny's Newsletter' weekly
  • Watching true-crime documentaries on weekends
  • Subscribed to The Guardian's tech section

Questions & answers

Suzanne Emmerich’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.featurehunter.io (Featurehunter) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The main thing unclear to me is how it integrates with existing tools. I'm currently juggling Intercom tickets, Slack threads, and Google Sheets, and the idea of consolidating is appealing, but I need to know it won't just add another manual step. It says it can 'overview every request' from emails and tickets, but how exactly? The 'interactive demo' is a nice touch, though. If I could see a clear pathway for importing my current feedback data and how it syncs, I'd be more inclined to sign up for the free plan. I'd want to ensure it can handle the volume of feedback we get, especially from our enterprise clients.
    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.