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

Lisann Bolm

Lisann Bolm

Project manager at a small web studio

Full-depth AI personas

Why this persona fits the audience

She oversees delivery for a six-person digital studio building brochure sites and campaign microsites for regional brands. The developers usually implement HTML or WordPress forms, and she keeps track of which client forms go to inboxes, Slack channels, or webhook-based CRM workflows.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Project manager at a web studio
  • Income: €54k
  • Education: Vocational training plus a BA
  • Company size: 6 employees
  • Years in role: 5 years
“The most satisfying part of my job is when a complex system clicks into place, and everything just works smoothly for the client.”

Lisann Bolm's journey into project management began not with a traditional computer science degree, but through a vocational training program in office management, followed by a Bachelor's degree in Communication Studies. This blend of practical, administrative skills and a deeper understanding of messaging and audience has proven invaluable in her current role at a small Berlin-based web studio. For the past five years, she's been the linchpin for a team of six, specializing in building brochure websites and campaign microsites for regional businesses. Her specific expertise lies in managing the often-overlooked but critical aspect of form submissions. She meticulously orchestrates the data flow from HTML and WordPress forms, ensuring that client-submitted information lands precisely where it needs to go – whether that's a direct email inbox, a team-specific Slack channel for immediate notification, or a more complex webhook integration into a client's CRM system. This requires a constant, detailed oversight, a deep understanding of her developers' workflows, and a proactive approach to anticipating potential integration hiccups. Lisann is driven by a strong sense of order and accountability; she believes that well-defined processes are the bedrock of successful project delivery. She recently championed a small internal initiative to standardize the documentation for form submission endpoints, a move that has already reduced minor errors by about 15%. Her income of €54k reflects her professional standing and the value she brings to the studio, allowing her a comfortable life in Berlin while still maintaining a mindful approach to savings for future travel and personal development. She sees time as a valuable, finite resource, and her focus is on maximizing efficiency and minimizing wasted effort, both for herself and her team.

Background & daily life

A day in their life

Lisann's typical weekday starts around 7:30 AM with coffee and a quick check of urgent emails. By 9 AM, she's at her desk, reviewing the project board and prioritizing tasks. The morning is often filled with client calls to discuss ongoing microsite projects or review design mockups. Around lunchtime, she might take a short walk or grab a quick bite from a local bakery. The afternoon is dedicated to coordinating with her developers, clarifying requirements for form integrations, and ensuring data is flowing correctly to client inboxes or Slack channels. She spends time documenting processes and updating project timelines. Her workday usually wraps up around 6 PM, after a final check of critical project statuses.

Lifestyle

Lisann lives in a well-organized, light-filled apartment in Prenzlauer Berg with her partner, a graphic designer, and their two rescue cats. Weekday evenings are often spent preparing healthy meals, tending to their small balcony herb garden, or catching up on industry podcasts. Weekends are for exploring Berlin's flea markets, visiting galleries, or taking short trips to nearby Brandenburg. She values routine and predictability, which helps her manage the inherent chaos of agency life. Financially, she's pragmatic, saving consistently for future travel and home improvements, avoiding impulsive purchases.

Work life

Lisann's days are a constant juggle of client calls, developer coordination, and task management. She's the primary point person for their small studio's six clients, ensuring brochure sites and campaign microsites are delivered on time and within budget. Her core responsibility involves managing the flow of data from client-submitted HTML forms. This means meticulously tracking whether form submissions should land in a specific client's inbox, a dedicated Slack channel for quick team alerts, or be pushed via webhook into a client's CRM system. She often finds herself troubleshooting form submission issues, clarifying requirements, and managing client expectations, especially when integrations become complex.

Relationships

Lisann has a stable, supportive relationship with her partner, who understands the pressures of creative work. Her closest friends are a mix of former colleagues and people she's met through Berlin's design scene. She values their honest feedback and shared experiences. Within the studio, she's respected by the developers for her clear communication and by the clients for her reliability.

How they decide

Lisann is a methodical decision-maker. She gathers information, weighs pros and cons, and often consults with her team or trusted peers before committing. She prefers solutions that offer clarity and reduce complexity, and she's not afraid to invest time in understanding the implications of a choice.

How they sound

Lisann speaks with a clear, measured cadence. Her tone is generally calm and professional, but can become more animated when discussing project successes or creative solutions. She avoids overly casual slang, preferring precise language. She's not one for hyperbole, sticking to factual descriptions. When explaining technical concepts, she aims for clarity and avoids jargon where possible, especially with clients.

Personality traits

  • meticulous
  • proactive
  • calm under pressure
  • detail-oriented
  • collaborative
  • resourceful
  • methodical

Goals

  • To streamline the studio's internal processes for handling form submissions.
  • To foster stronger, long-term relationships with key clients.
  • To take on more strategic project oversight rather than day-to-day task management.
  • To travel to Scandinavia and experience their design culture firsthand.
  • To contribute to the local design community by mentoring junior project managers.

Problems & frictions

  • The manual tracking of form submission destinations is prone to human error, leading to missed client communications.
  • Developers sometimes implement forms without fully considering the backend integration, creating extra work for her.
  • Client requests for immediate updates on form submissions can be difficult to fulfill without a centralized system.
  • Balancing the demands of multiple small clients with limited resources is a constant challenge.
  • Keeping up with the evolving landscape of web technologies and integration methods requires continuous learning.

Values

  • order
  • accountability
  • team coordination
  • efficiency
  • client satisfaction

Interests

  • client services
  • website operations
  • local design events
  • travel
  • urban gardening

Media habits

  • Industry blogs on web development and UX
  • Podcasts about project management and digital trends
  • Local Berlin news and event listings
  • LinkedIn for professional networking

Questions & answers

Lisann Bolm’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Html (https://html.contact/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Html 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).

    Currently, we manually track where each client's form submissions should go – emails, Slack, or CRM via webhooks. It's prone to errors, and developers sometimes implement forms without considering the integration, which creates extra work. Your service, Html, sounds like it could automate this by turning plain HTML forms into email notifications, Slack updates, and webhooks. The idea of "no backend to build" is appealing, as it would save us development time. However, I'm curious about how robust the webhook integrations are, especially for more complex CRM workflows. If it handles all our current destinations reliably and simplifies the process, that would be a significant improvement. I'd be willing to pay up to $15 per month for this service, provided it truly streamlines our current manual tracking and reduces errors.
    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.