Mayson Aalbers

Why this persona fits the audience

Supports a 110-person wholesaler in Rotterdam and handles data hygiene across Dynamics 365, a warehouse app, and customer service tools; the current setup uses a mix of native connectors, flat-file imports, and a few custom scripts maintained by one developer.

• Age: 37
• Location: Rotterdam, Netherlands
• Occupation: Application Administrator
• Income: €61k
• Education: Bachelor's degree in computer science
• Company size: 110 employees
• Years in role: 5

“The real challenge isn't just making things work, it's making them work reliably, day in and day out, without constant fuss.”

Mayson Aalbers, 37, is an Application Administrator at a midsize wholesaler based in Rotterdam. His journey into IT administration began with a Bachelor's degree in Computer Science from a Dutch university, where he developed a strong foundation in programming and system architecture. After a few years in a junior support role, he found his niche in managing complex business applications, particularly ERP and CRM systems. For the past five years, he has been instrumental in maintaining the operational integrity of his current employer's IT landscape. His role is critical, supporting approximately 110 employees by ensuring seamless data flow across their Dynamics 365 ERP, a specialized warehouse management application, and various customer service tools. This task is made challenging by the company's current integration strategy, which relies on a patchwork of native connectors, manual flat-file imports, and a handful of custom scripts. These scripts, the backbone of some critical data exchanges, are maintained by a single, overworked developer, a situation Mayson finds increasingly precarious. He is deeply committed to 'orderliness' and 'transparency' in data management, believing that accurate, accessible information is the bedrock of efficient business operations. His 'technical resilience' value drives him to seek robust, long-term solutions, even within the constraints of a modest IT budget. He recently spent weeks meticulously documenting the current data flows and identifying recurring points of failure, a proactive step towards advocating for more sustainable integration methods. This effort, while time-consuming, is part of his broader goal to move away from reactive firefighting towards a more stable and automated system architecture. His income of €61k allows for a comfortable but not extravagant lifestyle, reinforcing his pragmatic approach to technology investments. He views his work not just as a job, but as a puzzle to be solved with precision and logic, ensuring the company's operational gears turn smoothly.

Background & daily life

A day in their life

Mayson's typical weekday begins around 7:00 AM with a strong coffee and a quick scan of tech news. He arrives at the office by 8:30 AM, immediately checking system logs and any overnight data import statuses. The morning is often spent addressing urgent data discrepancies or assisting the warehouse team with inventory system queries. After a simple lunch, he dedicates a few hours to maintaining the existing data pipelines, which might involve troubleshooting a failed flat-file import or reviewing the performance of a Dynamics 365 connector. He often spends the last hour of his workday documenting processes or researching potential solutions for recurring data hygiene issues, before cycling home around 5:30 PM.

Lifestyle

Mayson leads a structured and quiet life in Rotterdam. His apartment is meticulously organized, reflecting his professional values. Weekends are often spent on long cycling routes, exploring the flat Dutch landscape, or sometimes venturing into the city's less-trafficked industrial areas with his camera. He enjoys cooking simple, healthy meals and is a regular at a local specialty coffee shop for his morning espresso. While not overly social, he maintains a small circle of close friends, mostly from his university days or cycling club. He prioritizes financial stability, saving diligently for future investments and potential travel.

Work life

As the primary administrator for a midsize wholesaler, Mayson is the go-to person for all things related to their core business systems. His days are consumed by ensuring data flows smoothly between Dynamics 365, their warehouse management system, and customer service platforms. This involves constant monitoring, troubleshooting data discrepancies, and managing the import/export processes. The reliance on a mix of native connectors, manual flat-file uploads, and a few custom scripts means a significant portion of his time is spent on maintenance and manual intervention, often working around limitations. He collaborates closely with the single developer who maintains the custom scripts, a relationship built on mutual respect for each other's technical domains.

Relationships

Mayson's closest relationships are with a few long-term friends from his university computer science program and his cycling club. He values their practical advice and shared interests. His interactions with colleagues are professional and task-oriented; he's respected for his reliability but isn't one for office gossip or extended social events. His parents, who live in a smaller town in Friesland, are proud of his career but don't fully grasp the technical intricacies of his role.

How they decide

Mayson is a cautious and research-driven decision-maker. He thoroughly evaluates options, weighing technical feasibility, long-term stability, and cost-effectiveness. He prefers to gather as much information as possible, often creating spreadsheets to compare features and potential impacts, before committing to a course of action. He trusts his own technical judgment but will consult with the company's developer or external IT forums if a problem falls outside his immediate expertise.

How they sound

Mayson speaks with a clear, measured cadence, typical of educated Dutch professionals. His tone is generally calm and factual, avoiding slang or overly casual language. He tends to be precise in his explanations, sometimes using technical terms without much preamble, assuming a certain level of understanding. He rarely expresses strong emotions and prefers to stick to the facts of a situation. He might pause to formulate his thoughts before answering complex questions.