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

David Waelchi

David Waelchi

Freelance full-stack developer for SMB clients

Full-depth AI personas

Why this persona fits the audience

Builds 2-4 client web apps at a time in VS Code as a solo freelance developer; keeps architecture notes, estimates, and dependency maps in Google Sheets and Notion, and often sketches flows in Figma before coding.

  • Age: 32
  • Location: Austin, TX, USA
  • Occupation: Freelance full-stack developer
  • Income: $145k-$175k USD, variable
  • Education: Bachelor's degree in computer science
  • Company size: 1 (self-employed)
  • Years in role: 7
“"The real satisfaction comes from building something solid that works, not just ticking boxes."”

David Waelchi, 32, has carved out a niche as a freelance full-stack developer in Austin, Texas, serving the needs of small to medium-sized businesses. He transitioned to freelance work seven years ago after a few years at a small tech startup, craving the autonomy and direct client relationships. His income typically ranges between $145k and $175k annually, a figure that fluctuates based on project availability and client budgets. Holding a Bachelor's degree in Computer Science, David possesses a strong foundational understanding of software engineering principles, which he constantly refines through self-study and practical application. His work philosophy is centered on delivering clean, maintainable code and ensuring smooth project handoffs, reflecting his high conscientiousness and desire for predictable workflows. He meticulously organizes project documentation, architectural notes, and dependency maps using tools like Google Sheets and Notion, and often visualizes user flows and component structures in Figma before committing to code. Recently, David decided to standardize his client onboarding process, creating a detailed questionnaire and initial discovery call framework to better define project scope and mitigate the common freelance problem of scope creep. He's also been exploring the potential of productized services, aiming to offer fixed-scope solutions for common SMB needs, a move driven by his value of independence and desire for more predictable income streams. While he enjoys the problem-solving aspect of his work, he's increasingly aware of the need to scale his impact beyond just billable hours, perhaps by developing reusable components or exploring more efficient development paradigms.

Background & daily life

A day in their life

David's typical weekday begins around 7:00 AM with coffee and a quick scan of Hacker News and his personal email. He then dives into his primary work, focusing on the most complex coding tasks for his current client projects, often using VS Code with a suite of extensions. Around midday, he takes a break for lunch and a short walk. The afternoon might involve client calls, documentation, or architectural planning using Figma and Notion. He aims to wrap up billable work by 6:00 PM, often followed by an hour of learning or personal coding, before preparing a simple dinner and relaxing. He's usually winding down by 10:30 PM.

Lifestyle

David lives a disciplined yet flexible life in Austin, balancing his demanding freelance work with a commitment to personal well-being. His rent is a significant portion of his income, but he prioritizes living in a walkable, vibrant neighborhood. He's not a big spender on material possessions, preferring to invest in experiences and his professional development. His income, while variable, affords him a comfortable lifestyle, though he's mindful of saving for future stability and potential investments. He enjoys exploring local breweries and dedicates weekend mornings to challenging trail runs in nearby nature preserves.

Work life

As a solo freelance full-stack developer, David's workday is a carefully managed exercise in efficiency and client satisfaction. He juggles 2-3 ongoing web application projects for small to medium-sized businesses, typically handling everything from initial client consultations to deployment and basic maintenance. His primary workspace is his home office, equipped with a powerful workstation and multiple monitors. Coworkers are non-existent in the traditional sense, though he maintains loose professional connections with other freelancers for occasional collaboration or advice. The pressure comes from managing client expectations, tight deadlines, and the constant need to acquire new business.

Relationships

David maintains a small circle of close friends, many of whom he met during university or through shared hobbies like trail running. His family lives out of state, and they communicate primarily through weekly video calls. Professionally, he relies on a few trusted developer contacts for informal peer review and occasionally refers work to specialists he trusts when a project requires it. His primary influence comes from industry thought leaders he follows online and technical communities.

How they decide

David is a methodical researcher. He thoroughly evaluates options, weighing pros and cons against his specific needs and existing workflows. He often consults documentation, reads reviews from trusted sources, and might even build small proof-of-concepts before committing to a new tool or approach. He values practicality and demonstrable value over hype.

How they sound

Speaks with a clear, measured cadence. Tends to be precise in his language, especially when discussing technical topics. Avoids excessive slang but might use developer jargon naturally. His tone is generally calm and rational, sometimes bordering on slightly formal in initial client interactions, but warms up with familiarity. He doesn't over-embellish or use hyperbole.

Personality traits

  • methodical
  • self-reliant
  • detail-oriented
  • pragmatic
  • introverted but polite
  • results-driven
  • observant
  • organized

Goals

  • Achieve a higher degree of recurring revenue through retainers or productized services.
  • Build a personal portfolio project that showcases advanced architectural patterns.
  • Develop a more robust system for client onboarding and project management.
  • Maintain a healthy work-life balance without sacrificing professional growth.
  • Become a recognized authority in a specific niche, like e-commerce backend architecture.

Problems & frictions

  • Inconsistent project pipeline leading to income fluctuation.
  • Scope creep on client projects despite defined contracts.
  • Balancing learning new technologies with billable client work.
  • The administrative overhead of running a solo business (invoicing, taxes, contracts).
  • Isolation inherent in solo freelance work.
  • Difficulty in accurately estimating complex, undefined project requirements upfront.

Values

  • independence
  • clean handoffs
  • working with small clients
  • predictable workflows
  • mastery of craft

Interests

  • API design
  • productized services
  • trail running
  • functional programming patterns
  • technical debt reduction
  • craft breweries

Media habits

  • Reads Hacker News and Reddit (r/webdev, r/cscareerquestions)
  • Listens to podcasts like Syntax.fm and The Changelog
  • Follows select developers on Twitter for technical insights
  • Watches YouTube tutorials on specific libraries/frameworks
  • Subscribes to newsletters on web development trends

Questions & answers

David Waelchi’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Glass Arc (https://www.glassarc.dev/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The main thing that would stop me from trying Glass Arc is the potential for it to introduce more complexity or unexpected behavior into my workflow, especially when I'm trying to maintain predictable project timelines. My current process involves extensive sketching in Figma and detailed notes in Notion before I even start coding, which gives me a high level of control. While I appreciate the idea of an autonomous architect, I'm concerned about how it integrates with my existing architectural planning and whether it might override my intended design. The pay-as-you-go 'Energy Credits' model is intriguing, but I'd need to understand the credit burn rate to estimate costs reliably. For now, I'd be willing to try it out if the initial credits are generous enough to explore its capabilities thoroughly without immediate financial commitment.
    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.