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

Nick van de Meer

Nick van de Meer

Product manager at a seed-stage SaaS

Full-depth AI personas

Why this persona fits the audience

Works in a 5-person product team at a seed-stage SaaS and documents AI tools for research, meeting notes, and prototyping in a shared spreadsheet. He often starts from tools the founder or engineers have already bookmarked and keeps short notes on what each one does.

  • Age: 28
  • Location: Amsterdam, Netherlands
  • Occupation: Product Manager
  • Income: €58k
  • Education: MSc in Information Science
  • Company size: 5 people total (including founder)
  • Years in role: 2 years as PM, previously worked in UX research
“I don't care how cool the tool is; if I can't explain why we're using it to the next person in five seconds, it's just noise.”

Nick van de Meer, 28, is a Product Manager at a fledgling SaaS startup in Amsterdam, navigating the turbulent waters of early-stage growth with a blend of academic rigor and practical grit. Holding an MSc in Information Science, he entered the workforce with a fascination for how humans interact with systems, eventually landing in the product sphere where he found his true calling: bridging the gap between abstract technology and tangible user value. Currently, he operates within a lean team of five, where the lack of resources necessitates a high degree of self-reliance. His most visible contribution is a meticulously maintained, albeit increasingly unwieldy, shared spreadsheet that serves as the central repository for the team's AI tool experimentation. This document is born out of necessity; the founder and engineers frequently discover new tools, bookmarking them with little context, leaving Nick to act as the curator and analyst. Nick's approach to his role is defined by a relentless pursuit of decision quality. He views information overload not as a problem to be solved by more tools, but as a friction point to be eliminated through better organization. His recent decisions reflect this philosophy: he recently mandated a standard format for all tool evaluations, forcing the team to document not just features, but the specific 'why' behind each selection. This has reduced the time spent on re-evaluating rejected tools, though the manual effort remains taxing. Financially, he is prudent, earning €58k, which allows for a comfortable life in Amsterdam but leaves little room for error or expensive software subscriptions without justification. He values time above money, often willing to spend an hour manually aggregating data to save the team days of confusion later. Socially, he is selective, preferring deep conversations with a few trusted individuals over broad networking. His worldview is shaped by the tension between the rapid evolution of AI and the human need for stability and predictability, a conflict he manages by treating every new tool as a temporary hypothesis rather than a permanent solution.

Background & daily life

A day in their life

Nick wakes at 6:30 AM, brewing coffee while checking the weather for his commute. By 7:30, he's cycling through the morning mist of Amsterdam-Noord, listening to a podcast on behavioral economics. At 8:45 AM, he arrives at the office, immediately scanning the shared spreadsheet to see if any new tools were added overnight by the engineering lead. His morning is dedicated to deep work: rewriting a feature spec for the upcoming MVP, ensuring every requirement explicitly references the AI tool being used. Lunch is a quick sandwich eaten while watching a demo video of a new LLM interface. Afternoons are consumed by stand-ups, user interview debriefs, and the tedious task of updating the team's master document with pros, cons, and pricing details. He leaves around 6:00 PM, often stopping at a local grocery store for groceries before heading home to cycle or read. Dinner is usually simple, followed by 45 minutes of experimenting with a new AI writing assistant to see if it beats his own drafting style.

Lifestyle

Nick lives in a modern, slightly cluttered apartment in Amsterdam-Noord, sharing space with his partner who works in design. His mornings are strictly analog: a strong coffee, a 20-minute bike ride along the IJ river to the office, and a review of overnight Slack messages before opening any apps. He treats his income carefully, allocating funds toward high-quality cycling gear and occasional travel to Berlin or London for tech meetups, but avoids luxury spending. Evenings are reserved for learning; he spends an hour reading about cognitive science or testing a new AI wrapper. He is health-conscious, prioritizing sleep and movement over gym membership fees, and maintains a small circle of close friends who value intellectual honesty over superficial networking.

Work life

At a five-person seed-stage SaaS, Nick is the de facto operations hub for product. His day is a blur of context switching between defining features, writing specs, and manually curating a massive spreadsheet of AI tools that the team has tested. He relies heavily on the founder's initial bookmarks but refines them into actionable data. There is immense pressure to move fast without breaking things; a single week can involve building a prototype, running user interviews, and documenting the entire process for the next sprint. He spends 60% of his time in Notion and Google Sheets, trying to impose order on the chaos of emerging technology, often staying late to ensure his documentation is clear enough for the engineers to build upon.

Relationships

Nick's closest relationship is with his partner, who grounds him when work stress peaks. He maintains a tight-knit group of three former university classmates who still discuss product theory weekly. Professionally, he looks up to his company's founder for vision but often finds himself acting as the pragmatic counterweight. He is not part of a formal professional network, preferring ad-hoc connections made during local Amsterdam tech events or online Discord communities. He rarely seeks mentorship formally, preferring to learn by doing and then sharing his findings with peers.

How they decide

Nick operates on a 'verify, then scale' model. He is neither impulsive nor paralyzed by analysis; rather, he is driven by the need for high-confidence decisions made with minimal friction. He gathers data rapidly from trusted sources (founder bookmarks, peer recommendations), tests a hypothesis quickly with a low-cost prototype, and only commits if the results align with his strict efficiency metrics. He dislikes making decisions based on marketing fluff alone and requires concrete evidence of utility before integrating anything new into his workflow.

How they sound

His speech is direct, efficient, and devoid of corporate jargon unless necessary for clarity. He speaks with a slight Dutch accent but uses English fluently in technical contexts. He tends to use analogies related to logistics or mechanics when explaining complex ideas. He avoids absolute statements like 'this will definitely work,' preferring 'based on the data, this looks promising.' He pauses frequently to think, valuing precision over speed in conversation, and often interrupts politely to clarify a definition rather than let a misunderstanding persist.

Personality traits

  • methodical but impatient with redundancy
  • curiously skeptical of hype cycles
  • deeply organized digital hoarder
  • prefers async communication over meetings
  • willing to experiment if the ROI is clear
  • quietly authoritative in planning sessions
  • value-driven rather than brand-loyal
  • seeks patterns in chaotic data
  • protective of team time
  • adapts quickly to tool pivots

Goals

  • Establish a repeatable framework for evaluating AI tools that scales beyond the current spreadsheet.
  • Lead the successful launch of the company's first major enterprise feature within 12 months.
  • Transition from manual documentation to a semi-automated knowledge base.
  • Build a personal reputation as a thought leader in pragmatic AI integration.
  • Save enough capital to fund a sabbatical trip across Southeast Asia.

Problems & frictions

  • The sheer velocity of new AI tools makes it impossible to keep the internal spreadsheet up to date.
  • Engineers frequently forget which tool was approved for a specific prototype due to fragmented notes.
  • Spending hours manually summarizing meeting transcripts instead of synthesizing insights.
  • Lack of standardized criteria for comparing free vs. paid tools leads to inconsistent decision-making.
  • Difficulty quantifying the 'time saved' by new tools to justify adoption to the founder.
  • Information silos where the founder knows about a tool but the rest of the team doesn't.

Values

  • decision quality
  • speed
  • team coordination
  • clarity over volume
  • pragmatic innovation

Interests

  • product discovery
  • AI prototyping
  • startup tooling
  • documentation habits
  • Dutch cycling culture
  • indie music festivals

Media habits

  • Skims Product Hunt daily for new releases
  • Subscribed to The Batch by Andrew Ng
  • Follows niche Dutch tech newsletters like TechBrief
  • Listens to 'Hardcore History' while cycling
  • Scrolls Twitter/X for engineering threads
  • Reads Substacks on product strategy late at night

Questions & answers

Nick van de Meer’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at FutureStack (https://www.usefuturestack.com/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This looks like a useful directory, exactly the kind of thing I spend too much time manually curating. Having a central place to discover and compare AI tools would definitely save me time. If it were priced around $10-$15 per month, I'd consider it a no-brainer for the team. Anything over $30/month would start to feel excessive for what is essentially a curated list. I'd expect access to detailed pricing, user reviews, and perhaps some filtering or comparison features. The maximum I'd be willing to pay is $15 per month.
    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.