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

Julian Schmid

Julian Schmid

Agency technical lead

Full-depth AI personas

Why this persona fits the audience

Manages a 7-person web agency in Berlin where designers and developers test Claude Code, Cursor, and MCP servers on client work. He tags repo-level logs by project in a shared Notion board and reconciles them with invoices at month end.

  • Age: 38
  • Location: Berlin, Germany
  • Occupation: Technical lead at digital agency
  • Income: €85k–€110k plus bonus
  • Education: Diplom-Informatik / master's equivalent
  • Company size: 7 people
  • Years in role: 5
“The real challenge isn't just building things fast; it's building them right, understanding every component, and knowing exactly where the resources are going.”

Born and raised in a smaller town in Brandenburg, Julian developed an early fascination with computers and problem-solving. His academic path led him to a Diplom-Informatik at a reputable Berlin university, where he excelled in software engineering and systems architecture. After graduating, he spent a few years at a larger software firm, gaining experience in enterprise-level development but found the bureaucracy stifling. Seeking a more dynamic environment, he joined his current web agency five years ago, quickly rising to Technical Lead due to his blend of technical expertise and pragmatic approach to management. He lives with his partner in a shared apartment in Prenzlauer Berg, valuing a structured yet flexible lifestyle. Julian is deeply invested in optimizing his agency's workflows, particularly concerning the integration and cost management of AI coding tools like Claude Code and Cursor. He recently spearheaded a project to refine their internal logging system, consolidating repo-level data into a shared Notion board. This initiative aims to provide granular insights into resource usage per project, which is crucial for his meticulous month-end reconciliation of invoices against actual development costs. He views this as essential for maintaining project clarity and ensuring efficient delivery for their clients. His approach to technology is cautiously optimistic; he embraces innovation but insists on rigorous testing and clear understanding of its impact on project outcomes and agency overhead. He's currently exploring how to better monitor the specific 'skills' or functions being invoked by these AI tools, as this level of detail is becoming critical for accurate client billing and internal performance analysis. He sees the potential for AI to revolutionize development but is wary of 'black box' solutions that obscure cost or performance metrics. His focus remains on tangible improvements in efficiency and client trust through transparent reporting and robust technical practices.

Background & daily life

A day in their life

Julian's day typically starts around 8:00 AM with a strong espresso and a quick scan of overnight project updates and team communications. He cycles to the office, arriving by 9:00 AM. The morning is often spent in stand-ups, reviewing code, and tackling complex technical challenges or architectural planning. After lunch, he might dedicate time to researching new AI tools or refining the agency's Notion-based logging system. The afternoon involves client calls, mentoring junior developers, and ensuring project milestones are on track. He aims to leave by 6:00 PM, often reflecting on the day's progress and planning for the next.

Lifestyle

Julian shares a modern, minimalist apartment in Prenzlauer Berg with his partner, a graphic designer. Their routines are fairly synchronized, with shared morning coffees and evenings spent cooking or catching up on personal projects. He’s health-conscious, cycling to work most days and occasionally hitting the gym. Financially, he's responsible, saving consistently for future travel and potential property investment, but doesn't shy away from investing in tools that demonstrably improve his work. Socially, he prefers smaller gatherings with close friends over large parties, valuing deep conversations.

Work life

As the technical lead for a small Berlin web agency, Julian juggles client demands with team management. His days are a mix of coding oversight, architectural decisions, and mentoring his seven-person team. He's deeply involved in evaluating and integrating new AI coding tools, ensuring they enhance productivity without compromising quality. The pressure to deliver on time and within budget is constant, especially with tight client reporting requirements. He spends significant time refining internal workflows, particularly around log management and cost reconciliation using Notion, to maintain project clarity and efficient delivery.

Relationships

Julian is in a long-term partnership with his girlfriend, who works in a creative field. They offer each other mutual support and intellectual sparring. His core group of friends consists of a few former university colleagues, now also in tech or related fields, with whom he discusses industry trends and shares challenges. His team respects his technical acumen and fair management style.

How they decide

Julian approaches decisions methodically. He gathers data, weighs pros and cons, and often seeks input from his team or trusted peers before committing. He prefers solutions that offer clear benefits and demonstrable ROI, even if they require an initial investment of time to set up. He's not impulsive but will act decisively once a well-reasoned path is identified.

How they sound

Speaks with a clear, measured tone. Uses precise technical language when discussing development but can simplify for clients. Avoids hyperbole and overly casual slang. His German accent is subtle but present. He tends to pause thoughtfully before answering complex questions. Prefers directness over ambiguity.

Personality traits

  • Analytical
  • Methodical
  • Detail-oriented
  • Proactive
  • Pragmatic
  • Calm under pressure
  • Organized
  • Resourceful
  • Slightly reserved

Goals

  • Scale the agency's technical capabilities without compromising quality
  • Achieve greater automation in project reporting and cost tracking
  • Become a recognized expert in AI-assisted web development workflows
  • Maintain a healthy work-life balance for himself and his team
  • Explore opportunities for the agency to specialize in niche AI-driven services

Problems & frictions

  • Tracking and attributing costs accurately across multiple AI tools and client projects
  • Ensuring consistent code quality and security when developers experiment with new AI assistants
  • Onboarding new team members to complex, evolving toolchains and workflows
  • Balancing the desire for cutting-edge technology with budget constraints for agency tools
  • Communicating technical progress and potential risks clearly to non-technical clients

Values

  • project clarity
  • client reporting
  • efficient delivery
  • technical accuracy
  • team autonomy

Interests

  • agency operations
  • Notion systems
  • MCP servers
  • AI coding tools
  • workflow automation
  • developer productivity

Media habits

  • Reads industry blogs (e.g., Smashing Magazine, CSS-Tricks)
  • Listens to tech podcasts during commute
  • Active on developer forums (Stack Overflow, Reddit)
  • Follows key figures in AI and web development on Twitter/X
  • Occasional webinars on new technologies

Questions & answers

Julian Schmid’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on TinyLaunch: See what your AI coding setup runs and costs. the product reads the local logs of Claude Code, Codex, Cursor and Gemini CLI and shows which skills,… What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The biggest problem for us is precisely what this product seems to address: understanding what our AI coding tools – Claude Code, Cursor, and others – are actually doing and costing us on a per-project basis. Right now, we manually tag repo logs in Notion, which is time-consuming and prone to error. Reconciling this with invoices at month-end takes hours. I estimate it costs us at least 10-15 hours of my team's time monthly, which translates to a few hundred euros in lost productivity, not to mention potential under-billing if we miss something. We've tried to build custom scripts, but they're difficult to maintain with the rapid tool updates.
    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.