Jannes Konya

Why this persona fits the audience

He assembles case-study decks for sales calls by pulling from public LLM deployment writeups, vendor webinars, and an Excel tracker sorted by industry and architecture. His team already pays for a broader analyst subscription through work, but he still keeps his own list because the sales cycle needs very specific implementation details.

• Age: 38
• Location: Munich, Germany
• Occupation: Principal Solutions Architect
• Income: €105,000
• Education: Diplom-Informatik
• Company size: Enterprise (500+ employees)
• Years in role: 5

“The true value of a solution isn't just in its potential, but in the meticulous, verifiable steps taken to make it a reality for the customer.”

Jannes Konya, a 38-year-old Principal Solutions Architect based in Munich, Germany, has carved a niche for himself in the complex landscape of enterprise sales support. Holding a Diplom-Informatik, his career has been a steady progression through various technical roles, culminating in his current position where he leverages his deep understanding of cloud architecture and emerging technologies, particularly AI, to empower the sales force. His primary responsibility involves translating intricate technical capabilities into compelling narratives for potential clients. This means he spends a significant portion of his work life meticulously assembling case-study decks. He doesn't rely solely on marketing materials; instead, Jannes actively scours public LLM deployment writeups, attends vendor webinars, and maintains a highly detailed personal Excel tracker, meticulously sorted by industry and specific architectural patterns. While his team has access to a broader analyst subscription, Jannes finds it insufficient for the granular implementation details required to address specific client pain points during the sales cycle. This personal diligence stems from a core belief in providing technically credible and trustworthy information, which he sees as foundational to building lasting customer relationships. He is married with two children, and his life is structured around balancing the demands of his high-stakes role with family commitments. His income of €105,000 reflects his expertise and the critical nature of his contributions to enterprise sales. Jannes is driven by a desire for clarity and precision, viewing his role as a crucial enabler of informed decision-making for both his company and its clients. He is currently focused on understanding the practical, real-world deployment challenges and successes of generative AI across various sectors, a task that requires constant learning and adaptation in a rapidly evolving field.

Background & daily life

A day in their life

Jannes's typical weekday begins around 6:30 AM with a quick breakfast and reviewing urgent emails before his children wake. He commutes to the office by 8:30 AM, often listening to a tech podcast. His morning is usually dedicated to client calls, architectural design sessions, or deep dives into specific LLM deployment patterns for upcoming sales pitches. Lunch is a quick affair, often at his desk while reviewing documentation. The afternoon might involve collaborating with sales teams, refining technical proposals, or updating his internal Excel tracker with new findings. He aims to leave by 5:30 PM to be home for dinner with his family, though late-night client requests or urgent architectural reviews can sometimes extend his workday. Evenings are for family time, followed by an hour of personal study or reading.

Lifestyle

Jannes lives with his wife and two young children in a comfortable, modern apartment in a family-friendly neighborhood on the outskirts of Munich. Weekends are dedicated to family activities – park visits, visiting grandparents, or attending his children's football matches. He enjoys quiet evenings, often reading technical books or historical non-fiction. While he appreciates good food and the occasional craft beer, he's not extravagant with his spending, preferring to save for future family needs and long-term security. His routine is well-established, prioritizing efficiency to balance professional demands with personal life.

Work life

Jannes's role as a Principal Solutions Architect is demanding, requiring him to bridge the gap between complex technical solutions and enterprise client needs. His days are a mix of deep technical analysis, client-facing presentations, and internal collaboration. He spends significant time architecting cloud-native solutions, often involving AI and machine learning components. The pressure to deliver accurate, scalable, and secure designs is constant. He works closely with account managers and pre-sales engineers, ensuring technical feasibility aligns with business objectives. His primary toolset includes cloud provider consoles, diagramming software, and his meticulously maintained Excel tracker for LLM implementations.

Relationships

Jannes is married to Lena, a primary school teacher, with whom he shares a stable and supportive partnership. They rely on each other for managing household responsibilities and childcare. He has a close circle of long-time friends from university, with whom he occasionally meets for Stammtisch. Professionally, his closest collaborators are his sales team counterparts and a few senior architects within his own department.

How they decide

Jannes is a highly research-driven and cautious decision-maker. He meticulously gathers data, analyzes options from multiple angles, and seeks to understand the underlying technical principles before committing. He values evidence and proven methodologies, often cross-referencing information and consulting with trusted peers or internal experts. He is not prone to impulsive choices and prefers a structured approach to problem-solving.

How they sound

Speaks with a clear, measured cadence, favoring precise technical language. His tone is generally calm and professional, even when discussing complex or contentious topics. He avoids hyperbole and slang, preferring direct and factual communication. When explaining technical concepts, he often uses analogies to simplify them for a non-technical audience, but reverts to deep technical jargon when speaking with peers. He has a slight Bavarian accent that becomes more noticeable when he's relaxed or discussing a topic he's passionate about.