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

Jolina Mögenburg

Jolina Mögenburg

Agency lead for custom ecommerce builds

Full-depth AI personas

Why this persona fits the audience

She leads a 6-person web studio in Berlin that ships headless commerce sites for local retailers, with client work split between bespoke JavaScript code, shared spreadsheets for SKU mapping, and recurring maintenance tickets.

  • Age: 35
  • Location: Berlin, Germany
  • Occupation: Agency lead, ecommerce engineering
  • Income: €70k–€95k salary + profit share
  • Education: MSc computer science
  • Company size: 6
  • Years in role: 5
“The beauty of a well-architected system isn't just in its immediate function, but in how gracefully it can evolve.”

Jolina Mögenburg, 35, is the driving force behind a boutique web development studio in Berlin, specializing in custom headless e-commerce solutions for local businesses. Holding an MSc in Computer Science, her career path has been a deliberate progression from hands-on coding to agency leadership. She founded her current agency five years ago, building it from the ground up with a focus on delivering high-quality, maintainable code. Her studio, now a team of six, thrives on tackling complex projects that require bespoke JavaScript development, often integrating with existing client systems and managing intricate SKU data through shared spreadsheets – a process she finds increasingly inefficient. Jolina's approach is deeply rooted in her values of structure, client service, and clean code, believing that a solid technical foundation is paramount for long-term business success. She is particularly drawn to the elegance of design systems and actively contributes to open-source projects in her spare time. Her income reflects her expertise and the profitability of her agency, with a salary in the €70k–€95k range supplemented by profit sharing. Jolina recently made a strategic decision to invest in better project management tooling to streamline client communication and internal workflows, aiming to reduce the friction caused by manual data handling and recurring maintenance tasks. She sees technology not just as a tool for building websites, but as a means to create sustainable, scalable business operations for her clients and her own company. Her personal life is balanced by a passion for mountain biking and exploring Berlin's vibrant food scene, providing a necessary counterpoint to the intense focus her work demands.

Background & daily life

A day in their life

Jolina's weekday typically begins around 7 AM with a strong coffee and a quick scan of Hacker News and industry Slack channels. By 8:30 AM, she's at her desk, reviewing the previous day's deployment logs and responding to urgent client emails. The morning is often dedicated to code reviews, architectural discussions with her team, and client calls to clarify project requirements or provide updates. Lunch is usually a quick, healthy meal at her desk or a walk to a nearby cafe. Afternoons involve strategic planning, onboarding new projects, and tackling complex technical challenges that require her direct expertise. She aims to wrap up by 6:30 PM, often followed by an evening session of personal coding or catching up on industry blogs.

Lifestyle

Jolina lives in a bright, minimalist apartment in Prenzlauer Berg, filled with plants and a few carefully chosen art pieces. Her routine is structured: early mornings often involve a quick bike ride or a run along the Spree before diving into work. Weekends are a mix of intense coding sessions for personal projects or client deep-dives, and exploring Berlin's diverse culinary scene with friends. She's recently taken up home brewing, enjoying the precise, scientific process. Financial discipline is key; she saves diligently, viewing it as a tool for future independence and business growth, rather than immediate luxury.

Work life

As the lead of her 6-person agency, Jolina's days are a constant juggle between client management, technical oversight, and team coordination. Her team specializes in headless commerce for Berlin-based retailers, a niche that demands both robust backend solutions and intuitive frontend experiences. Much of her time is spent architecting solutions, reviewing code for quality and maintainability, and troubleshooting complex integration issues. The reliance on shared spreadsheets for SKU mapping is a persistent, low-level friction point she's actively looking to streamline, alongside optimizing their recurring maintenance ticket workflow.

Relationships

Jolina maintains a close-knit circle of friends, many from her university days, who share her intellectual curiosity and appreciation for Berlin's cultural offerings. Her parents, both academics, instilled a strong work ethic and value for continuous learning. Within the agency, she fosters a collaborative environment, relying on her senior developer for technical sparring and her project manager for client communication.

How they decide

Jolina approaches decisions methodically. She gathers data, weighs pros and cons, and often consults with her senior team members or trusted peers in the developer community. She values solutions that are robust, maintainable, and offer long-term efficiency, even if the initial setup requires more effort. She's not impulsive but will act decisively once a clear path forward is established.

How they sound

Speaks with a clear, measured cadence, often using precise technical terminology without being overly jargonistic. Her tone is generally calm and professional, but can become more animated when discussing complex technical challenges or innovative solutions. She avoids hyperbole and prefers direct, factual communication. Occasional use of German colloquialisms when speaking informally with her team.

Personality traits

  • Analytical
  • Pragmatic
  • Detail-oriented
  • Resourceful
  • Calm under pressure
  • Independent
  • Forward-thinking
  • Direct communicator

Goals

  • Scale the agency to a 10-person team within three years
  • Develop a proprietary framework for headless commerce deployments
  • Achieve greater work-life balance through process automation
  • Mentor junior developers and foster a strong team culture
  • Become a recognized expert in e-commerce architecture

Problems & frictions

  • Client expectations often outpace realistic timelines for custom builds
  • Managing the overhead of bespoke JavaScript development versus off-the-shelf solutions
  • Onboarding new clients who are accustomed to simpler, less scalable systems
  • The constant need to stay ahead of rapidly evolving web technologies
  • Balancing billable client work with internal R&D and team development

Values

  • structure
  • client service
  • clean code
  • independence
  • efficiency

Interests

  • design systems
  • mountain biking
  • Berlin food
  • open-source
  • craft beer brewing

Media habits

  • Reads Hacker News daily
  • Follows key figures in JS/frontend on Twitter
  • Listens to tech podcasts during commutes
  • Subscribes to newsletters on web development trends
  • Watches YouTube tutorials for specific coding challenges

Questions & answers

Jolina Mögenburg’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Storecraft (https://storecraft.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Storecraft better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, we manage SKU mapping with shared spreadsheets, which is quite inefficient, and handle maintenance tickets manually. Storecraft's 'Commerce As Code' approach sounds intriguing, especially the flexibility in databases and cloud deployment. It could potentially streamline our bespoke JavaScript development significantly. However, I'd need to understand the actual effort involved in migrating our current data and workflows, and whether it genuinely simplifies the recurring maintenance rather than just shifting it. The AI integration is also interesting, but its practical application for our clients needs to be clear. I wouldn't pay for a solution that introduces more complexity than it solves.
    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.