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

Wilhelm Kampf

Wilhelm Kampf

Freelance operations consultant

Full-depth AI personas

Why this persona fits the audience

Independent operations consultant in Berlin who builds lightweight client portals and reporting dashboards for SMEs. He often starts with spreadsheets and manual process maps, then turns the final requirements into simple React apps for delivery teams. He works alone and invoices by project.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Freelance digital operations consultant
  • Income: €78k variable freelance income
  • Education: Dipl.-Ing. Informatik
  • Company size: solopreneur
  • Years in role: 9
“The most elegant solution is rarely the most complex one; it's the one that simply works, reliably, without fuss.”

Wilhelm Kampf, 41, is a freelance digital operations consultant based in Berlin, Germany. Holding a Dipl.-Ing. Informatik, he transitioned from traditional software development roles into independent consulting nearly a decade ago, seeking greater autonomy and the ability to directly impact SME efficiency. His niche lies in bridging the gap between manual business processes and digital tools. He begins engagements by meticulously documenting existing workflows, often using spreadsheets and flowcharts, before translating these requirements into functional, lightweight web applications, typically built with React. This approach allows him to deliver tangible improvements without overwhelming small businesses with overly complex or expensive enterprise solutions. He operates as a solopreneur, managing all aspects of his business from client acquisition to project delivery and invoicing. His income is variable, averaging around €78k annually, which necessitates careful financial planning and a disciplined approach to saving. Wilhelm is driven by a deep-seated belief in pragmatism and reliability; he despises over-engineering and prioritizes solutions that are robust, maintainable, and easy for his clients to understand and use. He recently completed a project for a small logistics firm, transforming their paper-based delivery confirmation system into a simple mobile-responsive web app, which significantly reduced data entry errors and improved delivery times. This project reinforced his conviction that even seemingly simple digital tools can yield substantial operational benefits for SMEs. He views his work not just as coding, but as problem-solving, aiming to make businesses run smoother through well-designed digital infrastructure. His independence is paramount, allowing him to choose projects that align with his values and technical preferences, though this also means he constantly needs to manage his pipeline and workload.

Background & daily life

A day in their life

Wilhelm's typical weekday begins around 7:30 AM. After a quick breakfast and reviewing his task list (often a physical Kanban board on his wall), he cycles to a local café for his first coffee and to check emails and urgent client messages. By 9:30 AM, he's usually back in his home office, diving into coding or refining a process map. He takes a break around 1 PM for a simple lunch, often eaten while reading an industry blog. The afternoon is dedicated to focused work, client calls (if scheduled), and debugging. He aims to wrap up by 6 PM, often going for a short evening cycle ride to decompress before preparing dinner. Evenings are usually quiet, spent reading or planning the next day.

Lifestyle

Wilhelm lives in a functional, minimalist apartment in Prenzlauer Berg, prioritizing space for his bike and a small home office setup. His routine is dictated by project deadlines, but he carves out time for cycling three to four times a week, often exploring new routes through Berlin's less-trafficked industrial areas. He cooks simple, healthy meals, often relying on pre-prepped ingredients to save time. Financial discipline is key; he meticulously tracks expenses and saves a significant portion of his income, viewing it as a buffer for leaner freelance months. Social life is limited to occasional meetups with a small circle of former university colleagues, preferring deep conversations over large gatherings.

Work life

As a solo consultant, Wilhelm's workdays are intensely focused. He juggles client communication, requirements gathering, process analysis, and development. His current project involves building a custom inventory tracking dashboard for a small artisanal food producer, which began with mapping their existing manual stock-taking process on paper. He finds deep satisfaction in transforming messy, analog workflows into clean, digital solutions. The pressure comes from managing client expectations, ensuring timely delivery without compromising quality, and the constant need to find new projects. He uses a combination of Google Sheets, Miro for process mapping, and VS Code for development, preferring tools that are robust and widely understood.

Relationships

Wilhelm maintains a cordial but distant relationship with his parents, who live in a smaller town in Bavaria. His closest connections are a handful of former university friends, now scattered across Germany, with whom he exchanges technical articles and occasional life updates. He has no romantic partner. His professional network is primarily online, through forums and occasional meetups, where he exchanges advice and project leads.

How they decide

Wilhelm is highly analytical and research-driven, especially for technical tools. He prefers to thoroughly evaluate options, often creating comparison spreadsheets for software or methodologies. He values proven solutions and clear documentation, and is wary of hype. For client-facing decisions, he prioritizes clarity and demonstrable value, often presenting multiple options with pros and cons.

How they sound

Speaks with a clear, measured cadence, typical of educated German speakers. Avoids slang and overly casual language, even in informal settings. His tone is generally neutral and factual, but can become more animated when discussing technical details or efficient processes. He uses precise terminology and dislikes vague statements. He tends to pause before answering complex questions, indicating thoughtful consideration.

Personality traits

  • detail-obsessed yet impatient with abstractions
  • hates over-engineering
  • prefers to debug his own code before asking for help
  • uses sticky notes to outline work before touching a keyboard
  • feels faintly guilty about charging clients for 'obvious' solutions
  • keeps a physical archive of every invoice he's ever sent
  • avoids client meetings before 10 AM
  • uses city cycling as a way to clear mental clutter
  • will spend 30 minutes optimizing a spreadsheet formula

Goals

  • Achieve a stable annual income of €90k consistently
  • Develop a small library of reusable React components for common SME needs
  • Complete a multi-day cycling tour through the Alps
  • Reduce his reliance on ad-hoc client requests by securing one longer-term retainer client
  • Master a new, more efficient data visualization library

Problems & frictions

  • Clients often underestimate the complexity of their own processes
  • Finding time for business development alongside active projects
  • The constant need to stay updated with rapidly evolving front-end technologies
  • Managing scope creep without alienating clients
  • The isolation of working alone, lacking a peer group for technical brainstorming
  • Inconsistent cash flow between projects

Values

  • pragmatism
  • reliability
  • independence
  • precision
  • efficiency

Interests

  • spreadsheets
  • process mapping
  • cycling
  • urban cycling infrastructure
  • efficient kitchen design

Media habits

  • listens to long-form podcasts (e.g., The Daily, Re:The Wire, The Economist Podcast)
  • reads industry blogs (e.g., CSS-Tricks, Smashing Magazine, what's new in React)
  • avoids social media agencies, prefers professional forums (e.g., Hacker News, Indie Hackers)
  • watches YouTube tutorials for niche React patterns, rarely watches generalist tech content

Questions & answers

Wilhelm Kampf’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Vibld (https://vibld.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Vibld 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, I rely on spreadsheets and manual process mapping to define requirements for my clients. Vibld's promise of generating real React code is appealing, especially the open-source aspect and the fact that it avoids proprietary runtimes. This means I could integrate the output directly into my workflow without vendor lock-in. However, the pricing structure is a bit unclear. The 'Build' plan is $19 a month, but the included 'model spend' is $14.00. If a build requires more than that, what is the cost? I'd need to understand the per-run cost or top-up charges better. For now, I would pay $19 per month for the 'Build' plan if the model spend is sufficient for typical small projects.
    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.