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

Natan de Bruijn

Natan de Bruijn

Indie SaaS founder

Full-depth AI personas

Why this persona fits the audience

He compares hosting for his startup's app, documentation site, and blog using a spreadsheet, Reddit threads, and a competitor review site his cofounder bookmarked. He is part of a three-person team, so most vendor research stays lightweight and internal.

  • Age: 31
  • Location: Utrecht, Netherlands
  • Occupation: Founder of an indie SaaS company
  • Income: €74k
  • Education: Master's degree in software engineering
  • Company size: 3
  • Years in role: 4
“The beauty of building something yourself is you get to define every layer, but that also means you're responsible for every layer.”

Natan de Bruijn, 31, is a co-founder of an indie SaaS company based in Utrecht, Netherlands. Holding a Master's degree in Software Engineering from Delft University of Technology, he possesses a strong analytical and technical foundation. His journey into entrepreneurship began after several years working as a backend developer at a mid-sized tech firm, where he grew frustrated with the limitations of existing tools and saw an opportunity to build something better. He co-founded his current venture four years ago with two like-minded individuals, driven by a shared vision to create elegant developer tools. His current income of €74k reflects the early-stage nature of the business; a significant portion of his personal finances are tied up in the company's growth. Natan embodies a blend of high conscientiousness and openness, meticulously planning while remaining receptive to new ideas and approaches. He values autonomy deeply, relishing the freedom to shape his company's technical direction and product roadmap. His current focus is intensely practical: optimizing the company's hosting infrastructure. He's meticulously comparing options for their app, documentation site, and blog, using a detailed spreadsheet, cross-referencing insights from Reddit threads, and consulting a review site bookmarked by his co-founder. This research is lightweight, as the three-person team handles most vendor evaluations internally. This hands-on approach to infrastructure is a direct consequence of their bootstrapped status, forcing him to balance cost-efficiency with the critical need for reliability and scalability. He sees this as a fundamental part of building a sustainable business from the ground up, a challenge he embraces with methodical determination.

Background & daily life

A day in their life

Natan's typical weekday starts around 8:00 AM with a strong coffee and a quick scan of Hacker News and his company's monitoring dashboards. He then dives into coding for a few hours, focusing on a specific feature or bug fix. After a brief team sync-up via Slack around 11:00 AM, he dedicates time to his current research project: comparing cloud hosting providers. This involves poring over documentation, running cost estimations in his spreadsheet, and reading user reviews. Lunch is usually a quick, healthy meal prepared at home. The afternoon might involve more coding, code reviews, or planning the next development sprint. He often wraps up around 6:30 PM, but might log back in later if a critical issue arises or inspiration strikes.

Lifestyle

Natan lives in a comfortable, modern apartment in Utrecht, shared with his partner, a graphic designer. His income allows for a stable life, but he's not extravagant, prioritizing savings for the business and future investments. Evenings are often spent coding, reading tech articles, or occasionally meeting friends for a craft beer at a local 'bruin café'. He cycles everywhere, valuing the health benefits and environmental aspect. Weekends might involve a hike in the nearby national park or a visit to a tech meetup, but often he's drawn back to his laptop, driven by the startup's momentum.

Work life

As a co-founder of a three-person indie SaaS company, Natan's work life is a constant juggle. His primary focus is on the technical architecture and product development, but he's also deeply involved in operational decisions, including infrastructure. The team relies heavily on shared Google Sheets for tracking tasks and vendor comparisons, supplemented by Slack discussions. He feels the pressure to keep costs low while ensuring scalability and reliability, which drives his current deep dive into hosting solutions. His days are a mix of coding sprints, debugging sessions, reviewing pull requests from his co-founder, and strategic planning.

Relationships

Natan's closest relationships are with his two co-founders, with whom he shares a deep professional bond built on mutual respect and shared vision. He maintains a strong connection with his partner, who provides emotional support and a grounding influence. His parents, both retired teachers, are proud but don't fully grasp the intricacies of his startup world. He has a small circle of close friends from university, some of whom are also in tech, providing a sounding board for ideas.

How they decide

Natan is a methodical researcher. When faced with a significant decision, especially regarding technical infrastructure or vendor selection, he gathers data from multiple sources. He'll create spreadsheets to compare features, pricing, and performance metrics, cross-referencing with community discussions on platforms like Reddit and Hacker News. He values peer recommendations but ultimately trusts his own analysis and the team's collective technical judgment.

How they sound

Natan speaks with a clear, measured cadence, typical of Dutch professionals. His English is fluent but carries a subtle, pleasant accent. He tends to be precise and avoids hyperbole, preferring factual statements. He uses technical jargon naturally when discussing work but can simplify complex concepts when explaining them to non-technical people. He's not overly casual, avoiding slang unless it's common in tech circles, and generally maintains a professional yet approachable tone.

Personality traits

  • analytical
  • methodical
  • detail-oriented
  • resourceful
  • patient
  • independent
  • pragmatic
  • curious

Goals

  • Achieve product-market fit and sustainable revenue growth for his SaaS.
  • Build a robust, scalable, and cost-effective technical infrastructure.
  • Maintain a healthy work-life balance despite startup demands.
  • Contribute meaningfully to the developer tools ecosystem.
  • Eventually hire a dedicated operations or infrastructure specialist.

Problems & frictions

  • Balancing the need for reliable infrastructure with a tight startup budget.
  • Finding the optimal hosting solution that scales without breaking the bank.
  • Time constraints – needing to wear multiple hats (developer, ops, researcher).
  • Ensuring documentation and the app are always performant and available.
  • The inherent uncertainty and pressure of running a bootstrapped startup.

Values

  • focus
  • autonomy
  • iteration
  • efficiency
  • long-term vision

Interests

  • SaaS
  • developer tools
  • product documentation
  • cloud infrastructure
  • lean startup methodologies

Media habits

  • Hacker News
  • Indie Hackers forum
  • specific tech newsletters (e.g., TLDR, Software Lead Weekly)
  • YouTube channels on software development and entrepreneurship
  • podcasts like 'Acquired' and 'Syntax.fm'

Questions & answers

Natan de Bruijn’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Review Signal (https://ReviewSignal.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).

    Right now, my team and I are deep in the weeds comparing hosting providers using our own detailed spreadsheet and cross-referencing Reddit discussions. I've spent a good chunk of time on this already, and honestly, the site doesn't immediately offer a different approach that feels significantly more efficient than what we're doing. It seems to focus more on individual user reviews, whereas we need to evaluate technical specs and scalability for our app, documentation, and blog. I'm not looking to pay for reviews or comparisons at this stage; we're trying to keep costs as low as possible. The pricing isn't clear on what you offer for detailed comparison beyond what's publicly available.
    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.