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

Enzo Bos

Enzo Bos

solo developer-freelancer

Full-depth AI personas

Why this persona fits the audience

Builds small AI utility sites for clients and his own directories from Amsterdam using React, Notion, and a paid Webflow workspace. He tracks feature lists, launch checklists, and copy fragments in Trello, then stitches the site together himself rather than using a fully packaged workflow.

  • Age: 36
  • Location: Amsterdam, Netherlands
  • Occupation: freelance developer
  • Income: €84k
  • Education: MSc in software engineering
  • Company size: 1 (self-employed)
  • Years in role: 8
“The real value is in understanding how the pieces fit together, not just in having the pieces.”

Enzo Bos, 36, is a freelance developer based in the vibrant city of Amsterdam. Holding an MSc in Software Engineering, he carved out his niche after realizing his passion lay not just in coding, but in building functional, elegant digital tools. His journey into freelancing was driven by a desire for autonomy and the freedom to pursue projects that aligned with his meticulous nature. He built his current professional setup incrementally, starting with basic tools and gradually investing in paid services like Webflow as his client base and income grew to a comfortable €84k annually. Enzo’s core philosophy revolves around precision and independence; he believes in crafting solutions from well-understood components rather than relying on monolithic, opaque platforms. This is evident in his choice of tech stack: React for custom front-ends, Notion for structured data and planning, and Webflow for efficient site assembly, all managed meticulously via Trello. He actively develops his own AI utility websites and niche product directories, viewing them as both portfolio pieces and potential passive income streams. This approach reflects a long-term perspective on his career, prioritizing sustainable growth and deep technical mastery over rapid, superficial gains. He recently made a conscious decision to invest in a premium Webflow plan to gain access to more advanced custom code capabilities, allowing him to bridge the gap between design needs and his development expertise without compromising his clean architecture principles. His relationship with time is disciplined, and money is seen as a resource for security and future freedom, rather than an end in itself.

Background & daily life

A day in their life

Enzo's weekday typically begins around 7:30 AM with a strong black coffee and a review of Hacker News. He's at his desk by 8:30 AM, diving into client work – perhaps refining a React component or updating content on a Webflow site. Mid-morning involves checking emails and responding to urgent client requests. After a simple lunch, often prepared the night before, he dedicates a couple of hours to his personal AI utility projects, iterating on features or planning new directory additions. Late afternoon is for administrative tasks like invoicing or updating Trello boards. He aims to wrap up by 6:00 PM, usually going for a cycle or preparing dinner, followed by an evening of reading tech blogs or working on a personal coding challenge.

Lifestyle

Enzo enjoys a quiet, ordered life in his Amsterdam apartment, filled with plants and well-organized shelving. His weekdays are intensely focused on work, with evenings dedicated to unwinding through coding personal projects or exploring new tech. He's not a big spender, prioritizing savings and investing, viewing his income as a tool for future independence rather than immediate gratification. Socially, he prefers small, meaningful interactions over large gatherings, cherishing deep conversations with a few close friends. He cycles everywhere, embracing the city's infrastructure and enjoying the fresh air, which aids his general well-being.

Work life

As a solo developer, Enzo's workdays are a constant juggling act between client projects and developing his own niche AI utility sites and directories. He lives and breathes React for front-end development and uses Notion extensively for project management and content planning. His workflow involves meticulously detailing features and launch steps in Trello, then constructing sites piece by piece in Webflow, leveraging its paid features for customizability. He resists overly packaged solutions, preferring to integrate tools himself for greater control and elegance. The pressure is self-imposed: to deliver high-quality, performant sites efficiently and maintain his independent streak.

Relationships

Enzo maintains a close, supportive relationship with his parents, who live in a smaller town in the Netherlands. His social circle is small but tight-knit, consisting of a few university friends and fellow developers he occasionally meets for coffee or drinks. These connections offer intellectual sparring and emotional support, but he primarily relies on his own judgment for professional decisions.

How they decide

Enzo is highly analytical and research-driven. He meticulously evaluates options, weighing pros and cons against his core values of precision and efficiency. He prefers to understand the underlying mechanics of a tool or service before committing, often spending considerable time experimenting or reading documentation. He is not easily swayed by hype and values proven utility over novelty.

How they sound

Speaks with a calm, measured cadence. His English is fluent but retains a slight Dutch directness; he avoids excessive slang or overly casual language in professional contexts. He tends to explain technical concepts clearly and logically, often using analogies to illustrate complex points. He is articulate and precise, rarely using filler words. He dislikes hyperbole and prefers factual statements.

Personality traits

  • methodical
  • self-reliant
  • detail-oriented
  • analytical
  • patient
  • observant
  • resourceful
  • calm under pressure

Goals

  • Achieve a level of passive income from his directory sites that allows for more project flexibility.
  • Refine his AI utility site offerings to become a recognized specialist in a particular niche.
  • Maintain a sustainable work-life balance without burnout.
  • Continue learning and mastering new frontend technologies and AI integrations.
  • Potentially acquire a small, established online business that aligns with his technical skills.

Problems & frictions

  • The constant need to prospect for new clients while managing existing ones.
  • Balancing the development of personal projects with client deadlines.
  • Keeping up with the rapid pace of AI advancements and tool proliferation.
  • The inherent loneliness and lack of immediate peer feedback in solo freelancing.
  • Occasional friction with clients who have unrealistic expectations about AI capabilities or timelines.

Values

  • precision
  • independence
  • clean architecture
  • efficiency
  • craftsmanship

Interests

  • React
  • Webflow
  • product directories
  • AI utilities
  • no-code tools (as components)
  • performance optimization

Media habits

  • Reads Hacker News daily
  • Subscribes to specific dev newsletters (e.g., React Status, Webflow Digest)
  • Watches YouTube tutorials on advanced React patterns or Webflow tips
  • Listens to tech podcasts during commute/errands
  • Occasional lurker on Reddit tech subreddits

Questions & answers

Enzo Bos’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 DevHunt: the product AI- AI Tools Website Builder Platform - the product is a platform for building AI tool websites, designed to help users effortlessly create and customize... 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 me is differentiating my own AI utility sites from others. While this platform aims to build AI tool websites, I already use React and Webflow to build mine, and I'm quite efficient. My concern is whether this platform offers a truly novel approach or just a faster way to do what I already manage. The time cost is in evaluating these kinds of tools instead of building. I've found that stitching together existing components, like I do with React and Notion, gives me more control and leads to a cleaner architecture than a fully packaged workflow.
    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.