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

Finn Bosman

Finn Bosman

indie SaaS founder

Full-depth AI personas

Why this persona fits the audience

Runs a small SaaS with a 3-person team and is extending a Docs add-on that sits beside the core web app. The add-on already has Stripe billing and a Supabase-backed account table, maintained in the same repository.

  • Age: 34
  • Location: Amsterdam, Netherlands
  • Occupation: Indie SaaS founder
  • Income: €110k
  • Education: MSc Software Engineering
  • Company size: 3
  • Years in role: 7
“The real magic happens when you solve a problem so well, users almost forget it's software.”

Finn Bosman has been immersed in software development since his teenage years, a passion that culminated in an MSc in Software Engineering from Delft University of Technology. After a brief stint at a large tech consultancy, he felt the pull towards building something more personal and direct. Seven years ago, he founded CodexFlow Solutions, initially a solo venture, which has since grown into a lean three-person operation. His core belief is in building tools that genuinely simplify complex workflows for other professionals. The company's main product, a web-based documentation manager, has found a steady niche. Finn is currently channeling significant energy into a new Google Docs add-on, a strategic move to diversify and capture a broader market. This project involves complex integrations, including Stripe for recurring billing and Supabase for managing user data, all housed within the same repository as the core app for efficiency. He lives with his partner in Amsterdam, valuing their shared life but also fiercely protecting his work focus. His income of €110k allows for a comfortable lifestyle, but he prioritizes reinvesting in the business and saving for long-term stability over ostentatious spending. Finn is driven by a desire for craftsmanship and the satisfaction of creating elegant, functional software. He is deeply influenced by the indie hacking community, drawing inspiration and practical advice from shared experiences. His recent decisions have been heavily geared towards validating the market demand for the Docs add-on, pushing it from concept to a monetized product with a tight deadline, a testament to his conscientiousness and drive to deliver.

Background & daily life

A day in their life

Finn's typical weekday begins around 7:30 AM with a cycle to a local café for coffee and a quick review of overnight analytics and urgent support tickets. He's at his co-working space by 9:00 AM, starting with a daily stand-up call with his two team members. The core of his morning is dedicated to deep work: coding new features for the Docs add-on, refactoring existing code, or debugging. Lunch is usually a quick affair at his desk or a walk in Vondelpark. Afternoons involve responding to customer emails, planning the next development sprint, and perhaps a brief call with a potential integration partner. He aims to wrap up by 6:30 PM, though late nights do happen when a critical bug arises or a deadline looms.

Lifestyle

Finn lives in a spacious, light-filled apartment in Amsterdam's Oud-West district with his partner, an architect. Their routine is balanced: mornings often start with a quick cycle to a local café for coffee and checking urgent emails before heading to their small co-working space. Evenings are for cooking together, occasional visits to indie film screenings, or deep dives into coding challenges. While his income is comfortable, he's not flashy, preferring to reinvest profits or save for future business expansion and a potential down payment on a home. He values his downtime intensely, seeing it as essential for maintaining focus and creativity.

Work life

As the founder and lead developer of 'CodexFlow Solutions', Finn juggles product strategy, coding, customer support, and team management for his three-person company. His core product is a web app for managing project documentation, and he's currently heavily invested in launching a new add-on module for Google Docs, which requires integrating payment processing via Stripe and managing user accounts with Supabase. The pressure to deliver a polished, stable add-on is significant, especially with their competitor recently updating their offering. His days are split between focused coding sessions, daily stand-ups with his remote team (a designer and a junior developer), and analyzing user feedback from early testers.

Relationships

Finn's primary relationship is with his partner, who provides a grounding influence and support system. He has a close-knit group of university friends, a few of whom are also in tech and serve as informal sounding boards for business ideas. His small team, though remote, has developed a good rapport through regular video calls and shared project goals. He doesn't actively seek broad social influence but is respected within a niche online community of indie SaaS builders.

How they decide

Finn is a methodical researcher and a pragmatist. He deeply analyzes available information, weighs pros and cons, and often seeks input from trusted peers or online communities before committing to a significant decision, especially regarding technology choices or strategic pivots. He values evidence and tangible results over hype.

How they sound

Speaks with a clear, measured cadence, often with a slight Dutch accent that softens English vowels. His tone is generally calm and focused, avoiding overly casual slang but comfortable using technical jargon when appropriate. He tends to articulate his thoughts logically, often pausing to consider the best phrasing. He's not one for hyperbole, preferring precise language and factual descriptions.

Personality traits

  • Analytical
  • Driven
  • Methodical
  • Resourceful
  • Detail-oriented
  • Calm under pressure
  • Pragmatic
  • Independent
  • Adaptable

Goals

  • Achieve consistent month-over-month revenue growth for the Docs add-on.
  • Build a robust, scalable architecture that supports future feature expansion.
  • Maintain a healthy work-life balance without sacrificing business progress.
  • Become a recognized, trusted voice in the micro-SaaS community.
  • Eventually hire a dedicated product manager to free up his technical focus.

Problems & frictions

  • Balancing rapid feature development for the new add-on with maintaining the stability of the core product.
  • Finding and retaining talented remote developers who align with their company culture.
  • Managing customer expectations around feature timelines and bug fixes.
  • The constant need to stay updated with rapidly evolving developer tools and platforms.
  • Scaling infrastructure efficiently without incurring excessive costs.

Values

  • focus
  • leverage
  • customer feedback
  • autonomy
  • craftsmanship

Interests

  • micro-SaaS
  • Stripe
  • Docs add-ons
  • indie hacking
  • developer tooling
  • European tech scene

Media habits

  • Reads Hacker News daily
  • Listens to Indie Hackers Podcast during commutes
  • Follows specific SaaS founders on Twitter/X
  • Subscribes to a few curated tech newsletters
  • Watches YouTube tutorials on new programming frameworks

Questions & answers

Finn Bosman’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of ShipAddons (https://shipaddons.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make ShipAddons 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).

    Right now, we're building our Google Docs add-on from scratch, integrating Stripe and Supabase ourselves. It's a significant chunk of work. ShipAddons promises to handle a lot of that initial setup, which is appealing. The main benefit would be speed to market, getting us past the boilerplate faster so we can focus on our unique features. The main concern would be how well it integrates with our existing architecture and whether it introduces unnecessary complexity or dependencies we can't manage. The $49 one-time purchase price seems reasonable for the potential time savings, especially if it's as production-ready as they claim. I'd be willing to pay $49 for lifetime access.
    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.