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

Nazariusz Brzozowski

Nazariusz Brzozowski

Freelance developer and build-in-public creator

Full-depth AI personas

Why this persona fits the audience

Shares build-in-public threads, code snippets, and product milestones from a side project blog. He is comfortable with light scripting but usually grabs screenshots manually or with free tools, especially when posting from a laptop late at night or saving examples for a portfolio page.

  • Age: 27
  • Location: Warsaw, Poland
  • Occupation: Freelance web developer
  • Income: €34k/year
  • Education: Bachelor's degree
“The real satisfaction comes not just from solving a problem, but from building something elegant and efficient that others can also use.”

Nazariusz Brzozowski, a 27-year-old freelance web developer based in Warsaw, Poland, embodies the modern independent creator. Holding a Bachelor's degree, he carved out a niche for himself by offering his development services to a diverse clientele, primarily focusing on front-end implementation and bespoke web solutions. His income, around €34k annually, reflects the fluctuating nature of freelance work, necessitating careful financial planning and a constant drive to secure new projects. Nazariusz is deeply committed to the 'build-in-public' ethos, meticulously documenting the journey of his side project—a niche productivity tool—through detailed Twitter threads, blog posts, and code snippets. This public sharing is not just for marketing; it's an integral part of his learning process and a way to connect with a like-minded community. He possesses a strong sense of autonomy, valuing the freedom to choose his projects and working hours, which fuels his dedication to technical elegance and efficiency. His technical confidence is solid for core development tasks, but he admits to being less adept with advanced automation, often resorting to manual methods like taking screenshots with free tools or basic scripting, especially when working late or compiling portfolio assets. This pragmatic approach extends to his tools; he favors well-established, efficient software and is always on the lookout for elegant solutions that streamline his workflow. His recent decision to focus more intensely on documenting his side project's milestones publicly stems from a desire to build a stronger personal brand and attract potential users organically, even if it means sacrificing some immediate development time for content creation. He views time as a valuable, finite resource, meticulously allocating it between client work, personal projects, and continuous learning, always striving for a balance that allows for both professional growth and personal satisfaction.

Background & daily life

A day in their life

Nazariusz's typical weekday begins around 7:00 AM with a quick check of emails and overnight notifications from his side project. After a light breakfast and a short walk, he dives into his freelance client work, often tackling the most complex coding tasks first. Lunch is usually a quick, home-prepared meal eaten at his desk. The afternoon might involve client calls or code reviews. Around 6:00 PM, he switches gears to his 'build-in-public' project, working on new features, writing blog posts, or crafting Twitter threads about his progress. He might take a break for a workout or a simple dinner before returning to coding or learning until 10:00 PM, often capturing screenshots of his work for later portfolio updates or social media posts, sometimes using free online tools or simple screenshot utilities.

Lifestyle

Nazariusz lives alone in a functional, minimalist apartment in a quieter district of Warsaw, prioritizing a clean workspace over extensive living space. He cycles or uses public transport for most errands, viewing car ownership as an unnecessary expense. His evenings and weekends are often dedicated to his freelance work or his passion projects, which he meticulously documents online. He enjoys cooking simple, healthy meals and occasionally meets up with a small circle of developer friends for board games or discussions about technology. Financial discipline is key; he saves a significant portion of his income, aiming for long-term stability and the freedom to pursue his own ventures.

Work life

As a freelance web developer, Nazariusz juggles multiple client projects, primarily focusing on front-end development and small-to-medium scale web applications. He uses VS Code with a suite of extensions, Git for version control, and Figma for design mockups when provided. His income fluctuates, creating a constant pressure to secure new contracts, but he values the autonomy it affords him. He spends his workdays coding, communicating with clients via email and occasional video calls, and managing project timelines. A significant portion of his time is also devoted to his 'build-in-public' side project, a niche productivity tool, where he shares progress and code snippets.

Relationships

Nazariusz maintains a close relationship with his parents, who live in a smaller town outside Warsaw. He has a small, tight-knit group of friends, mostly fellow developers he met during university or through online communities. These friends serve as his primary sounding board for technical challenges and career decisions. He is not currently in a romantic relationship, prioritizing his career and personal projects.

How they decide

Nazariusz is a research-heavy decision-maker, especially for tools and significant purchases. He meticulously compares options, reads reviews, and often tests free trials before committing. For work-related tools, he prioritizes functionality, efficiency, and long-term value over initial cost. He is influenced by the opinions of trusted peers and respected figures in the tech community but ultimately relies on his own analysis and pragmatic assessment of needs.

How they sound

Speaks with a measured, clear cadence, often using precise technical terminology. His Polish accent is subtle but present. He avoids overly casual slang or excessive jargon when speaking to clients but is more relaxed with developer friends. He tends to be direct and factual, preferring to explain the 'how' and 'why' of his work. He rarely uses filler words and often pauses to formulate his thoughts carefully. He avoids hyperbole and focuses on concrete details.

Personality traits

  • methodical
  • curious
  • self-reliant
  • detail-oriented
  • analytical
  • pragmatic
  • perseverant
  • reflective
  • resourceful
  • independent

Goals

  • Achieve financial independence through successful side projects.
  • Build a sustainable, recognized SaaS product.
  • Continuously improve his technical skills and explore new programming paradigms.
  • Maintain a healthy work-life balance that allows for personal growth.
  • Contribute meaningfully to open-source projects.

Problems & frictions

  • Inconsistent income stream from freelance clients.
  • Difficulty in finding time for deep work on side projects amidst client demands.
  • The challenge of marketing and growing an audience for his 'build-in-public' project.
  • Occasional burnout from long hours and the pressure to constantly learn.
  • Navigating the complexities of self-employment taxes and administrative tasks.
  • The isolation that can come with freelance and solo project work.

Values

  • autonomy
  • technical elegance
  • efficiency
  • learning

Interests

  • indie hacking
  • software tools
  • programming
  • product design

Media habits

  • follows tech blogs (e.g., Hacker News, Dev.to)
  • uses Twitter for build-in-public updates and networking
  • subscribes to YouTube channels on programming and productivity
  • participates in Discord communities for developers
  • reads newsletters from indie hackers and SaaS founders
  • occasionally browses Reddit for tech discussions

Questions & answers

Nazariusz Brzozowski’s public research answers, newest questions first. Up to 10 per page.

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

    This month, what would likely stop me is not a lack of interest, but rather the time commitment. I often find myself manually taking screenshots late at night or when compiling portfolio pieces. I use free tools and simple scripts for that, which are usually good enough. If I were to use something like TwitterShots, I'd want to integrate it into my existing workflow seamlessly. For now, I'd be willing to pay $0 per month. The core functionality seems basic enough that my current manual process is sufficient, and I'm always hesitant to add new subscriptions without a clear, time-saving benefit that justifies the cost.
    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.