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

Moritz Pfeiffer

Moritz Pfeiffer

Freelance full-stack developer with multiple client repos

Full-depth AI personas

Why this persona fits the audience

Runs a solo freelancing practice in Berlin with two active client apps plus his own internal scripts. He uses Claude Code on a personal workstation, switches between repos often, and is usually the only person available to approve changes or answer follow-up questions.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Freelance full-stack developer
  • Income: €95k variable annual income
  • Education: Diplom-Informatik / equivalent
  • Company size: solo
  • Years in role: 12
“I didn't choose freelancing to be my own boss. I chose it to control the chaos.”

Moritz Pfeiffer cut his teeth at a Berlin startup building payment systems, where he developed a reputation for fixing 'unfixable' legacy code. After five years, he went solo, specializing in projects where others feared to tread. His two current clients are a testament to his niche: one needs him to maintain a codebase written in an obscure functional language, the other demands performant IoT code with zero downtime. His meticulous approach stems from a near-catastrophe in his early freelance days when an untested deployment caused a client €50,000 in losses - he still wakes up in sweats from that dream. The incident hardened his belief that 'client trust' means never having to explain production failures. His current workflow is a carefully balanced system of terminal multiplexers, git hooks, and voice-controlled approvals - anything to reduce context-switching. Recently, he's grown frustrated with the limitations of phone-based code review, especially when trying to approve changes during long bike rides. His personal automation scripts now account for 10% of his income, but he views them as 'guilt projects' - useful tools he should have built years ago. At 41, he's at peace with his 'forever freelancer' status, though he's become increasingly protective of his time. His ideal day involves no meetings, no Trello boards, and no poorly scoped 'urgent' requests. When he's not coding, you'll find him contributing to Rust modules or riding to lake chateaus for weekend retreats. His biggest professional fear isn't losing clients - it's outliving his technical edge. That's why he allocating 20% of each billable week to pure learning, though he'd never admit it publicly.

Background & daily life

A day in their life

Moritz starts at 6:30am with coffee and a quick check of urgent Slack messages. By 8am he's on his bike to the coffee shop where he'll spend 30 minutes reviewing yesterday's work. The first real work block is dedicating to the fintech client (he prefers starting with 'the messiest' project). Afternoon is reserved for the IoT backend, when his energy is lower but he can focus on infrastructure. He takes a 3pm break for cycling and returns to handle admin tasks with dull efficiency. Dinner is usually takeout eaten while watching Twitch streams of dev conferences. He winds down with small improvements to his personal scripting projects, often staying up later than he should.

Lifestyle

Moritz rents a top-floor loft in Neukölln with a tiny balcony where he grows chili peppers. His mornings begin with a 7km bike ride to a coffee roastery he refuses to name for fear of losing his 'regular' status. His wardrobe consists of 90% black shirts and jeans, all of which he hand-washes to avoid laundromats. Weekends are split between contribing to Rust crates and cycling along the Spree. He's frugal with big purchases but splurges on high-end mechanical keyboards. Social life revolves around a tight group of other indie devs who meet for 'code and coffee' sessions at a quiet corner spot. His biggest indulgence is a €1,200 espresso machine he convinces himself is 'professional equipment.'

Work life

Moritz alternates between two client projects - a fintech dashboard and an IoT backend - plus his own automation scripts. His workstation is meticulously configured with tmux sessions for each project, color-coded terminal profiles, and a strict git workflow he's evangelized to all clients. The biggest pressure is being the sole point of contact for urgent changes, often while commuting. He's recently adopted Claude Code for code review but finds himself constantly switching terminals to approve PRs on his phone. Recent frustration: a client's insistence on using Trello for task tracking despite his protests. His ideal workflow would let him preview code changes anywhere without compromising his local environment.

Relationships

His family in Hamburg checks in monthly but doesn't understand his work. His closest friends are fellow solo devs who share his appreciation for 'good tools.' He currently advises (but doesn't formally mentor) a junior developer at a local startup. His ex-wife handles his tax paperwork annually for a flat fee. The people who most influence him are maintainers of open-source projects he depends on, whose work ethic he profoundy respects.

How they decide

Methodical but not overly analytical - he'll research for a week, then make a decisison swiftly once he has a 'feel' for it. Prefers detailed documentation to sales pitches. Will abandon tools that don't prove their value within 4 weeks.

How they sound

Speaks in complete sentences with measured cadence. Avoids hedge words like 'probably' or 'maybe' in technical discussions. Will use sarcasm to deflect when frustrated. Pronounces 'Git' properly but says 'nope' when something fails instead of 'fails.' Uses German phrases when angry or amused. His emails are formal but his Slack messages are terse. Never says 'just' or 'quickly' about technical work.

Personality traits

  • Relishes solving arcane technical debt problems after hours
  • Keenly aware when clients underestimate the complexity of their requests
  • Will rewrite an entire module if it feels 'unclean' rather than patching
  • Maintains a pristine local development environment like a shrine
  • Prickly about poorly specified requirements but warms to clients who learn
  • Skeptical of buzzwords but tries new tools if they demonstrably save time
  • Cycles through productivity systems (currently in a 'taskwarrior + shell scripts' phase)
  • Deliberate about word choices in client emails to avoid misunderstandings
  • Hoards useful one-liners in a private gist collection
  • Will abort an entire debugging session if his coffee is subpar

Goals

  • Build a niche open-source tool that actually gets adopted
  • Reduce client dependency by 20% through better documentation
  • Complete the Berlin-Copenhagen bike ride next summer
  • Write a book about maintaining legacy systems
  • Cut back hours to 30/week by 2025

Problems & frictions

  • Clients who treat urgent fixes as 'quick tweaks' despite deep technical implications
  • Context-switching between repos breaks his flow
  • Berlin's rising costs make maintaining his ideal work-from-home space difficult
  • His perfectionism leads to underbilling for complex tasks
  • Frequent interruptions when testing changes on mobile devices

Values

  • independence
  • craftsmanship
  • client trust
  • delivery

Interests

  • open-source contributions
  • Berlin indie music scene
  • specialty coffee
  • long-distance cycling

Media habits

  • listens to tech podcasts during commutes (e.g., Changelog, Syntax)
  • reads Hacker News daily but skips fluff
  • follows German indie devs on Mastodon
  • avoids mainstream social media
  • maintains a low-key but meticulous blog about debugging war stories

Questions & answers

Moritz Pfeiffer’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at CodeMote (https://codemote.caste.work/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    CodeMote seems to solve a critical pain point for me: reviewing code and managing AI agents while I'm away from my desk. As a freelancer juggling multiple repos, being able to approve PRs, check diffs, and interact with Claude Code or other agents from my phone is a game-changer, especially during bike rides or when I'm not at my workstation. The promise of a direct encrypted tunnel without VPN or port forwarding aligns with my need for security and simplicity. My only reservation is whether the terminal experience and file browsing will be seamless enough for my workflow—some of my repos have arcane structures I'm picky about. At this stage, I'd be willing to try it, but given my current toolchain and the fact that I don't typically pay for productivity apps, my maximum acceptable price per month is $15 USD. Beyond that, I'd need to justify the cost against the time saved. If it proves indispensable, I might stretch to $20, but anything above that would need to show a significant return on investment.
    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.