Charlemagne Brunet

Why this persona fits the audience

Works as a product manager at a Paris field-service SaaS company and regularly partners with a four-person CS/support pod. He helps turn internal SOPs, feature notes, and release details into searchable answers for the app's help widget and AI assistant, while routing unresolved cases back to the team.

• Age: 39
• Location: Paris, Île-de-France, France
• Occupation: Product Manager
• Income: €85k gross
• Education: M.Sc. in Engineering
• Company size: 150 employees
• Years in role: 5

“The real challenge isn't just building features; it's ensuring those features actually empower our users to solve their problems efficiently and reliably.”

Born and raised in Lyon, Charlemagne developed an early aptitude for understanding how systems work, a trait nurtured by his father, an engineer, and his mother, a librarian. This fascination led him to pursue an M.Sc. in Engineering at a reputable Parisian institution. After graduating, he spent a few years in a technical consulting role, where he honed his problem-solving skills and gained exposure to various business processes. He found himself increasingly drawn to the product side, enjoying the blend of technical understanding and strategic thinking required to shape software solutions. He joined his current company, a mid-sized SaaS provider for field services, five years ago as a Product Manager. His current role is pivotal, focusing on bridging the gap between internal knowledge and customer-facing support. He works closely with the Customer Success team, meticulously transforming internal Standard Operating Procedures, release notes, and technical documentation into easily digestible, searchable content for the in-app help widget and AI assistant. This involves a constant cycle of documentation, testing, and refinement, ensuring accuracy and relevance. A significant part of his responsibility is to identify and analyze cases where the automated help systems fall short, then architecting the process for routing these unresolved issues back to the CS pod for human intervention. He views this as critical for maintaining customer trust and operational efficiency. Charlemagne is married and lives a structured life in Paris, valuing both professional achievement and personal well-being. He approaches his career with a long-term perspective, prioritizing sustainable growth and impact over short-term gains. His income allows for a comfortable lifestyle, but he remains a pragmatic spender, focusing on investments and future security. He sees his work as a continuous process of improvement, driven by a desire for clarity and effectiveness in the tools he helps build.

Background & daily life

A day in their life

Charlemagne's typical weekday begins around 7:30 AM with a quick scan of overnight alerts and industry news over coffee. He commutes to the office by metro, often listening to a tech podcast. His mornings are usually dedicated to focused work: refining user stories, analyzing product usage data, or drafting documentation for new features. After a working lunch, he dedicates afternoons to meetings – typically a sync with the CS team to review unresolved tickets and discuss knowledge gaps, followed by a product roadmap discussion with engineering leads. He might spend an hour testing a new iteration of the AI assistant's responses or reviewing user feedback logs. He leaves the office around 6:30 PM, aiming to disconnect and enjoy his evening.

Lifestyle

Charlemagne lives in a comfortable, though not expansive, apartment in the 11th arrondissement of Paris with his wife, a graphic designer. Their routine is fairly structured, balancing demanding careers with a desire for quality of life. Evenings often involve cooking together, discussing their days, or catching up on reading. Weekends are for exploring the city's markets, visiting museums, or occasional cycling trips along the Seine. He's mindful of his health, aiming for regular exercise, and is generally prudent with finances, prioritizing long-term security over immediate gratification. Social life is a mix of close friends and occasional work-related events.

Work life

As a Product Manager at a growing field-service SaaS company, Charlemagne's days are a constant juggle. He's deeply involved in translating complex internal knowledge – from intricate Standard Operating Procedures for technicians to nuanced feature updates – into accessible, searchable content for the company's in-app help widget and AI assistant. This requires close collaboration with the four-person Customer Success and Support team, whose feedback is crucial. He spends significant time documenting, refining knowledge base articles, and ensuring the AI assistant provides accurate, cited answers. A key part of his role involves identifying when the automated systems fail and ensuring those unresolved issues are efficiently routed back to the CS team for human intervention, preventing customer frustration.

Relationships

Charlemagne is married to Sophie, a graphic designer, with whom he shares a close and supportive partnership. They often discuss work challenges and life decisions. His primary professional relationships are with his direct reports in product and the Customer Success team, particularly with the lead support agent, Amélie, who acts as a key liaison. He has a small circle of close friends from university, with whom he maintains regular contact.

How they decide

Charlemagne approaches decisions methodically. He gathers data, consults relevant stakeholders, and weighs potential impacts carefully. He prefers to understand the 'why' behind a problem before jumping to solutions, often sketching out system diagrams or flowcharts to visualize complex interactions. While he values input from his team and colleagues, the final decision often rests on a logical assessment of alignment with strategic goals and demonstrable customer impact.

How they sound

Speaks with a measured, clear cadence. His French is standard Parisian, with minimal slang, though he'll use technical jargon when appropriate with colleagues. He tends to be articulate and avoids overly emotional language, preferring to frame discussions around data and logic. He's not afraid to ask clarifying questions to ensure full understanding. He avoids hyperbole and focuses on concrete details.