Maya Kuijpers

Why this persona fits the audience

Manages support operations for an Amsterdam marketplace SaaS and coordinates a five-person team. She keeps articles and internal policies organized in Help Scout Docs and adjacent spreadsheets, while also aligning responses used in the app's chat and help flows.

• Age: 45
• Location: Amsterdam, Netherlands
• Occupation: Support Operations Manager
• Income: €82k gross
• Education: BA in Management
• Company size: SaaS startup, 45 employees
• Years in role: 3

“If the answer isn't the same in the chat as it is in the email, we haven't solved the problem; we've just created confusion.”

Born in Rotterdam and raised in a household that valued discipline and practical education, Maya Kuijpers developed an early affinity for systems and order. Holding a BA in Management from Erasmus University, she entered the corporate world in the mid-2000s, where she quickly distinguished herself by turning chaotic administrative processes into streamlined workflows. Over the last two decades, she navigated the shift from traditional call centers to modern digital support ecosystems, eventually landing in her current role as Support Operations Manager for a growing Amsterdam-based marketplace SaaS. At 45, Maya is the operational backbone of her department, tasked with the unglamorous but critical work of ensuring that every customer interaction feels seamless. Her current reality is defined by a tension between legacy processes and emerging technologies. While the company invests heavily in AI-driven chatbots, Maya remains the guardian of truth, manually bridging the gap between these new tools and the static, reliable documentation her team depends on. She currently relies on a hybrid system of Help Scout Docs and complex, nested spreadsheets—a patchwork solution that works but consumes hours of her week. Her professional life is marked by a relentless pursuit of consistency. She recently led a initiative to standardize tone-of-voice guidelines across all support channels, a project that required negotiating with both engineers and customer success managers. Despite her high conscientiousness, she struggles with the pace of change in the SaaS industry, often feeling that her team's ability to scale is bottlenecked by the lack of automated synchronization between their content repository and live chat interfaces. Financially stable and independent, she views her income not just as a salary but as a resource to build a secure future, carefully allocating funds toward her home renovations and retirement planning. To her colleagues, she is the calm center of the storm; to her customers, though unseen, she is the invisible force ensuring they get the right answer, every time.

Background & daily life

A day in their life

Maya arrives at the office by 8:15 AM, immediately checking the overnight ticket queue and the health dashboard for the support platform. By 9:00 AM, she leads a brief stand-up with her five agents, focusing on blockers rather than status updates. The bulk of her morning is spent in Help Scout Docs, meticulously editing a cluster of articles regarding a recent pricing update, then manually copying those changes into a master Excel sheet that tracks approval dates. Lunch is a quick sandwich eaten at her desk while reviewing a spreadsheet of customer sentiment trends. Afternoon meetings involve coordinating with the Product team to ensure their new feature launch doesn't break existing FAQ logic. She spends the final hour auditing the chatbot's suggested responses against her internal knowledge base, flagging inconsistencies for the engineering team. She leaves by 5:30 PM, ensuring her task board is cleared before closing her laptop.

Lifestyle

Maya lives in a sunlit, minimalist apartment in Oud-West, renovated with clean lines and natural wood, reflecting her preference for order. Her routine is rhythmic: she cycles to work regardless of weather, treating the commute as mental decompression. Evenings are reserved for reading non-fiction or walking her dog along the canals. Financially, she is prudent, prioritizing savings and low-debt living over luxury experiences. Socially, she maintains a tight circle of colleagues and old university friends, preferring deep conversation over large gatherings. She values health through consistent movement rather than gym intensity, often cooking simple, nutritious meals at home.

Work life

As the sole architect of support operations, Maya manages a delicate ecosystem of documentation, ticket routing, and agent training within a fast-paced SaaS environment. Her days are split between reviewing agent performance metrics in Help Scout and manually updating spreadsheets that track policy changes not yet integrated into the main knowledge base. She faces constant pressure to reduce response times without sacrificing accuracy, often acting as the bridge between technical developers and customer-facing agents. Recent weeks have been consumed by aligning the new in-app chatbot responses with existing static articles, a process currently reliant on tedious cross-referencing between disparate systems.

Relationships

Her professional network is robust, anchored by a close-knit team of five support agents who rely on her structure. At home, her partner is an architect who shares her appreciation for design efficiency but prefers more creative chaos. She stays connected with her parents in Utrecht via weekly video calls, maintaining a traditional sense of family duty. While she has many acquaintances in the Amsterdam tech scene, she reserves her deepest trust for a small group of peers from her early career who understand the specific pressures of scaling support teams.

How they decide

Methodical and risk-averse. Maya gathers data from multiple sources before committing to a change, often running small pilots or A/B tests internally. She relies heavily on peer recommendations and case studies that demonstrate long-term stability rather than flashy features. She avoids impulsive decisions, preferring to wait until a solution is proven to integrate seamlessly with existing workflows. Trust is earned through demonstrable reliability and clear ROI, not marketing promises.

How they sound

Her speech is precise, efficient, and devoid of unnecessary filler words. She speaks with a soft, steady Dutch accent, favoring direct statements over hedging. In professional settings, she uses industry terminology like 'knowledge gaps,' 'ticket deflection,' and 'version control' naturally. She avoids hyperbole and emotional language, preferring facts and data points to support her arguments. When frustrated, she becomes quieter and more analytical rather than raising her voice, often pausing to restructure her thoughts before responding.