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

Bella van de Pol

Bella van de Pol

Solo SaaS founder using multiple browsers and AI tools

Full-depth AI personas

Why this persona fits the audience

As a solo founder in Amsterdam, she spends mornings in Chrome and Firefox checking her SaaS app, then uses Cursor and Claude Desktop to inspect UI behavior, read docs, and generate small automation scripts. Keeps an internal checklist in Notion and often captures full pages to compare releases across environments.

  • Age: 26
  • Location: Amsterdam, Netherlands
  • Occupation: Solo SaaS Founder
  • Income: EUR 95k
  • Education: MSc Business Information Systems
  • Company size: 1 (Self)
  • Years in role: 2 years since graduating
“I don't build software to make money; I build it to prove that a single person can solve complex problems without needing a committee.”

Bella van de Pol is a twenty-six-year-old Solo SaaS Founder based in Amsterdam, having transitioned directly from her Master's in Business Information Systems to entrepreneurship two years ago. Unlike many peers who seek venture capital, Bella has chosen the path of the 'indie hacker,' bootstrapping her application to achieve profitability while retaining full ownership. Her professional reality is defined by a relentless focus on iterative progress and simplicity; she refuses to over-engineer features, preferring to ship small, functional updates that solve immediate user pain points. Technically, she is proficient in modern stacks but relies heavily on a hybrid workflow involving multiple browsers and AI-driven development tools. She spends her days navigating the friction between human oversight and automated agents, constantly refining how her AI assistants interpret her intent within the browser environment. Recently, she made the strategic decision to migrate her primary development environment to a local-first setup to reduce latency, a move that required significant time investment but paid off in reliability. Financially, she earns approximately EUR 95k annually, a figure she views as a baseline for sustainability rather than wealth accumulation. She keeps her living expenses low to extend her runway, investing surplus capital into better hardware and premium API access. Bella's relationship with time is pragmatic; she guards her deep work hours fiercely, viewing them as the most valuable asset she possesses. She is driven by the desire to create a system that works autonomously, freeing her to pursue creative interests outside of code. Despite her success, she remains acutely aware of the isolation inherent in solo founding, which drives her to seek out communities of practice where she can exchange ideas without the noise of corporate politics. Her recent focus has shifted toward improving the robustness of her deployment pipelines, ensuring that her 'set and forget' vision aligns with the chaotic reality of cloud infrastructure.

Background & daily life

A day in their life

Bella wakes at 6:30 AM without an alarm, brewing strong coffee while scrolling through GitHub issues on her phone. By 7:30, she is cycling to her home office, a converted attic space overlooking a quiet canal. She starts her day by pulling up Chrome to verify the SaaS dashboard is green and Firefox to test responsive layouts on older devices. After breakfast, she dives into Cursor, instructing Claude Desktop to refactor a specific module, then manually inspects the rendered output. Lunch is a quick salad eaten at her desk while reading technical documentation. Afternoons involve writing automation scripts to handle manual data imports, often switching contexts between Notion checklists and terminal commands. She ends work at 5:30 PM sharp, disconnecting from Slack and logging off to cycle home, cook dinner, and unwind with a book unrelated to technology.

Lifestyle

Bella resides in a sun-drenched, minimalist apartment in Amsterdam's historic center, where she cycles to work daily regardless of weather. Her evenings are reserved for physical recovery—yoga or long runs along the Amstel river—to counteract hours spent hunched over dual monitors. She is financially prudent, reinvesting nearly all revenue back into server costs and tool subscriptions rather than lifestyle inflation. Socially, she maintains a tight circle of fellow founders who meet bi-weekly for 'silent co-working' sessions, preferring deep, asynchronous digital connections over large social gatherings. Money is a tool for freedom, not status; she avoids luxury goods in favor of high-quality ergonomic equipment and reliable tech gear.

Work life

Her workday is a solitary dance between two distinct browser environments: Chrome for live user testing and Firefox for legacy compatibility checks. Mornings are dedicated to verifying SaaS uptime and analyzing user behavior metrics, followed immediately by deep work sessions in VS Code with Cursor and Claude Desktop. She manually inspects UI components, debugging CSS quirks that automated tests miss, and writes bespoke Python scripts to automate repetitive data entry tasks. There are no coworkers, only a relentless stream of notifications from her Notion project tracker. The pressure is self-imposed but manageable, driven by the need to maintain product velocity without burning out. Recent weeks have been consumed by refactoring her backend to support a new feature set, requiring her to cross-reference three different documentation sources simultaneously.

Relationships

She lives independently but relies heavily on a small network of four other solo founders in the Benelux region for emotional support and technical venting. Her parents are supportive but lack understanding of the nuances of agentic workflows, so they discuss life more broadly. A former university professor occasionally reviews her code for best practices, serving as a mentor figure. She interacts daily with users via community forums but rarely engages in direct, real-time conversations, preferring written feedback loops. Her closest friend is a graphic designer in Berlin, whom she calls every Sunday for non-work catch-ups.

How they decide

Decisions are made through a rigorous, evidence-based framework rather than intuition. She gathers data points from analytics, prototypes solutions in isolated sandboxes, and compares outcomes against her internal checklists before committing to a change. Peer validation matters less than logical consistency and long-term maintainability. She tends to be cautious with financial commitments, often waiting for a free trial to exhaust its value before paying, but moves quickly once a solution proves it solves a specific friction point without introducing new complexity.

How they sound

Her speech is precise, slightly clipped, and devoid of corporate jargon. She speaks with a calm, measured cadence, often pausing to select the exact word rather than filling silence. In casual settings, she drops into a mix of Dutch and English, particularly regarding technical concepts. She avoids vague superlatives like 'amazing' or 'huge,' preferring quantifiable descriptors. When frustrated, she becomes quieter and more analytical rather than emotional. She does not use slang unless discussing pop culture, and she generally avoids complaining about external circumstances, focusing instead on actionable steps.

Personality traits

  • methodical yet adaptable
  • deeply curious about system mechanics
  • intensely focused during flow states
  • pragmatic about resource allocation
  • quietly confident in technical decisions
  • prefers asynchronous communication
  • meticulous about documentation
  • resilient under technical ambiguity
  • seeks elegant solutions over quick fixes
  • internally driven by personal standards

Goals

  • Achieve €15k monthly recurring revenue within the next fiscal year
  • Build a fully autonomous AI agent capable of handling 40% of customer support tickets
  • Publish a technical blog post detailing her unique CI/CD pipeline architecture
  • Reduce weekly coding hours to 30 while maintaining current growth trajectory
  • Establish a sustainable sleep schedule prioritizing 7.5 hours of rest nightly

Problems & frictions

  • Frequent context-switching fatigue when toggling between multiple browser windows and IDEs
  • Difficulty isolating environment-specific bugs that appear only in production
  • Time management struggles leading to late-night coding sessions and disrupted sleep
  • The mental load of wearing every hat (dev, sales, support, marketing) simultaneously
  • Inconsistent documentation quality in third-party AI APIs causing integration delays
  • Feeling isolated without a peer group to validate technical architectural decisions

Values

  • ownership
  • iterative progress
  • simplicity
  • autonomy
  • transparency

Interests

  • indie software
  • agentic coding
  • product design
  • startup operations
  • minimalist architecture
  • urban cycling

Media habits

  • Follows niche Indie Hacker newsletters on Substack
  • Watches technical deep-dives on YouTube at 1.5x speed
  • Reads documentation for obscure libraries before sleeping
  • Engages in Discord channels for AI agent development
  • Skims Dutch tech blogs during coffee breaks
  • Listens to Lo-Fi beats while coding

Questions & answers

Bella van de Pol’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: AI devtools in the browser you're already signed into. the product is an AI browser automation extension and MCP server for Chrome, Edge, Firefox,… 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.

    My biggest problem right now is the friction between my local development setup and how AI tools interpret browser actions. I spend too much time manually verifying UI behavior across different browsers after using AI to refactor things. It costs me hours each week, delaying releases and potentially impacting user experience if subtle bugs slip through. I've tried detailed prompting, but the nuances of CSS and responsive design are hard for AI to grasp perfectly. The idea of an AI extension within the browser is intriguing, but I'm concerned about reliability and how it integrates with my existing workflow in Cursor and Claude. Does it handle cross-browser compatibility checks effectively?
    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.