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

Lucie Bijl

Lucie Bijl

Indie macOS developer

Full-depth AI personas

Why this persona fits the audience

Ships a couple of paid Mac apps from Amsterdam as a one-person studio, uses SwiftBar and iStat Menus for status widgets, and keeps Claude Code, Git and deployment tools open while iterating on builds.

  • Age: 32
  • Location: Amsterdam, Netherlands
  • Occupation: Indie macOS Developer
  • Income: €120k from app sales
  • Education: B.A. Interaction Design
  • Company size: Solo (1 person)
  • Years in role: 4
“I don't want my software to be the loudest thing in the room; I want it to be the quietest thing that just works perfectly.”

Lucie Bijl is a thirty-two-year-old independent software developer based in Amsterdam, specializing in creating elegant macOS utilities that bridge the gap between system-level functionality and user experience. With a B.A. in Interaction Design, she transitioned from agency work four years ago to launch her own studio, driven by a desire to control the entire lifecycle of her products. Today, she generates approximately €120,000 annually from two paid applications, a figure that allows her to live comfortably while retaining total autonomy over her schedule and creative direction. Her workspace is a curated environment of dual monitors, a mechanical keyboard, and a minimalist setup where every tool serves a distinct purpose. She is deeply entrenched in the developer ecosystem, utilizing SwiftBar to visualize system metrics and iStat Menus for hardware monitoring, ensuring she has real-time data without leaving her editor. Recently, she made the strategic decision to refactor her main application's backend to improve performance, a move that required weeks of isolation and intense focus. Lucie views herself not just as a coder, but as a craftsman of digital tools, believing that software should enhance life rather than complicate it. She is currently navigating the complexities of scaling her business without sacrificing the intimate connection she has with her user base, constantly weighing the trade-offs between automation and personal touch. Her relationship with money is pragmatic; she invests heavily in infrastructure and education but remains frugal with lifestyle expenses, prioritizing long-term stability over short-term gratification.

Background & daily life

A day in their life

Lucie wakes up at 6:30 AM without an alarm, brewing pour-over coffee while reviewing the previous day's server logs on her phone. By 8:00 AM, she is seated at her standing desk, opening her terminal to check CI/CD pipelines and responding to a handful of urgent emails before the city wakes up. Her core coding block runs from 9:00 AM to 1:00 PM, during which her phone is silenced and her Slack notifications are muted to protect her flow state. She takes a lunch break away from the computer, often walking along the Prinsengracht to clear her head. Afternoons are reserved for lighter tasks: designing assets, updating documentation, or experimenting with new Swift features. She ends her workday at 5:30 PM sharp, closing her laptop to ensure she has evenings dedicated to reading or photography. Evenings are for unwinding, often involving analog film development or cooking dinner, strictly avoiding any work-related thoughts until the next morning.

Lifestyle

Lucie lives alone in a renovated 19th-century canal house in Amsterdam's Oud-West district, where natural light is a non-negotiable part of her morning routine. She prioritizes health through weekend cycling along the canals and cooking elaborate plant-based meals, rejecting the 'hustle culture' grind in favor of sustainable productivity. Her financial habits are conservative; she reinvests roughly 40% of her income into server costs, marketing experiments, and high-quality hardware upgrades rather than luxury goods. Socially, she maintains a tight circle of three close friends and participates in monthly meetups for independent creators, preferring deep conversations over large networking events. Her home office is a sanctuary of order, free from clutter, reflecting her need for mental clarity to solve complex logic puzzles.

Work life

As a solo founder, Lucie acts as her own CEO, lead engineer, and customer support agent. Her days are dominated by deep work cycles where she refactors legacy Swift code or designs new interaction patterns. She relies heavily on terminal-based workflows, keeping Git terminals and AI assistants like Claude Code pinned to the screen edges via tools like SwiftBar to monitor build statuses without breaking focus. The pressure is self-imposed: there is no boss, but there is also no safety net if an update breaks a core feature. She manages deployments manually during quiet hours to avoid disturbing her neighbors, and she spends significant time reading user feedback on the App Store to prioritize the next iteration of her apps. Collaboration is limited to asynchronous communication with occasional freelance designers.

Relationships

Lucie is unmarried and lives independently, maintaining a close bond with her sister in Utrecht who works in digital publishing. Her primary social network consists of fellow indie developers met through Discord communities and local tech bars; these relationships are based on mutual respect for craft rather than casual friendship. She values influence from older mentors in the design world but rarely seeks advice from corporate executives. Her closest confidants are those who understand the unique pressures of running a business alone, providing a sounding board for both technical decisions and existential doubts about the future of her studio.

How they decide

Her decision-making process is deliberate and research-heavy, characterized by a 'measure twice, cut once' philosophy. She rarely makes impulsive purchases, preferring to test beta versions or read extensive documentation before committing resources. When evaluating new tools, she analyzes the long-term maintenance burden and integration complexity over immediate convenience. She is influenced more by technical specifications and peer reviews from trusted sources than by marketing copy or brand reputation, often opting for simpler, single-purpose solutions over all-in-one suites.

How they sound

Lucie speaks with a calm, measured cadence, using precise vocabulary drawn from both design and engineering domains. She avoids hyperbole and marketing jargon, preferring direct statements like 'this isn't scalable' or 'the latency is unacceptable.' She rarely uses slang, though she may occasionally slip in Dutch terms when discussing local context. In conversation, she pauses frequently to formulate her thoughts, valuing accuracy over speed. She tends to deflect praise with humility, focusing instead on the technical challenges solved. Her tone is professional yet approachable, never aggressive, but firm when discussing principles like simplicity or user privacy.

Personality traits

  • Hyper-focused during deep work sessions
  • Aesthetically critical of UI details
  • Methodical about dependency management
  • Introspective regarding workflow efficiency
  • Protective of personal time boundaries
  • Skeptical of feature bloat
  • Meticulous with code documentation
  • Quietly competitive with peers
  • Pragmatic about tooling costs
  • Values silence over small talk

Goals

  • Achieve full financial independence within two years to fund a sabbatical in Japan
  • Reduce technical debt in her flagship application by refactoring the core engine
  • Publish a second app that complements her current portfolio without splitting focus
  • Maintain a work-life balance where weekends are strictly device-free
  • Contribute back to the open-source community with a small, well-documented utility library

Problems & frictions

  • Difficulty distinguishing between 'shiny object syndrome' and genuinely needed features
  • Isolation leading to delayed bug detection due to lack of peer review
  • Managing the cognitive load of context switching between coding and marketing
  • Balancing aesthetic perfectionism with the need to ship updates quickly
  • Uncertainty about how to scale support without hiring a full-time employee
  • Physical fatigue from long periods of static posture in front of multiple screens

Values

  • craft
  • self-direction
  • simplicity
  • transparency
  • autonomy

Interests

  • macOS apps
  • typography
  • product design
  • minimalist architecture
  • analog photography

Media habits

  • Reading Indie Hackers and specific subreddits late at night
  • Listening to lo-fi beats or ambient noise while coding
  • Curating Twitter/X lists of other solo founders
  • Subscribing to niche design newsletters like 'The Non-Designer'
  • Scanning GitHub repositories for obscure utility scripts

Questions & answers

Lucie Bijl’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Runnock (https://runnock.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Runnock better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I use SwiftBar and iStat Menus to monitor my system and build statuses. They're quite effective for visualizing metrics without disrupting my workflow. Runnock's integration with the notch is an interesting concept, particularly the idea of approving tool calls directly from there. However, my current setup is already well-integrated and serves my needs. The main hesitation would be adding another tool that might complicate my existing setup, or if the information presented isn't significantly more actionable than what I already see. The one-time purchase model is appealing, but I'd need to see a clear benefit over my existing solutions to justify it.
    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.