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

Robin de Vries

Robin de Vries

Bootstrapped startup product engineer

Full-depth AI personas

Why this persona fits the audience

Works on a 2-person product team in Amsterdam where he switches between Claude Code and Cursor for feature work. He maintains a small spreadsheet of MCP server usage and estimated cost because the company keeps tooling budgets tight.

  • Age: 29
  • Location: Amsterdam, Netherlands
  • Occupation: Product engineer
  • Income: €58k–€76k
  • Education: Bachelor's degree in software engineering
  • Company size: 2
  • Years in role: 4
“You can't build something sustainable if you're bleeding money on invisible infrastructure costs.”

Born and raised in a town just outside Utrecht, Robin developed an early fascination with how things work, which naturally led him to computers and programming. He pursued a Bachelor's in Software Engineering at a Dutch university, where he met his current co-founder. After graduating, he worked briefly at a larger tech firm but felt stifled by the bureaucracy and lack of direct impact. Seeking more autonomy and a faster pace, he partnered with his friend to launch their current venture, a bootstrapped startup focused on a niche software product. He thrives on the challenge of building something from scratch with limited resources, embracing the 'lean spending' ethos. His role as a product engineer means he's constantly evaluating and adapting his toolkit, currently favoring AI coding assistants like Claude Code and Cursor for their productivity gains. However, the company's tight budget forces him to maintain a vigilant watch over costs, meticulously tracking server usage in a detailed spreadsheet—a task he sees as a necessary evil. He values ownership and the tangible satisfaction of shipping code that works. While driven and focused, Robin isn't overly ambitious for status or wealth; his primary goals revolve around building a stable, successful product and achieving a comfortable, efficient lifestyle. He often finds himself optimizing workflows and tooling, driven by a desire for efficiency and control over his technical environment. His decision-making is heavily influenced by pragmatism and a desire to avoid unnecessary complexity or expense, reflecting his deep-seated belief in lean principles.

Background & daily life

A day in their life

Robin's weekday starts around 7:30 AM with coffee and a quick scan of Hacker News. He cycles to the small office by 9 AM. The morning is typically spent deep in code, tackling a specific feature using either Claude Code or Cursor, depending on the task complexity. He dedicates a portion of his lunch break to updating the cost spreadsheet, noting down recent MCP server activity. Afternoons involve code reviews, refining existing features, or brainstorming solutions with his co-founder. He leaves the office around 6 PM, cycling home. Evenings are for personal projects, reading technical articles, or catching up on a podcast, usually winding down by 10:30 PM.

Lifestyle

Robin lives a fairly minimalist life in Amsterdam, prioritizing experiences and utility over material possessions. His days are structured, with a dedicated focus on work and personal development. He cycles everywhere, enjoying the city's infrastructure. Evenings are often spent coding on personal projects, exploring new open-source tools, or unwinding with a craft beer and a podcast. Social life is moderate; he has a close-knit group of friends from university and occasionally attends local tech meetups, but values his downtime. He's conscious of his spending, always looking for value and avoiding unnecessary expenses.

Work life

As a product engineer at a tiny bootstrapped startup, Robin wears many hats, but his core focus is feature development. He juggles Claude Code and Cursor daily, adapting to whichever tool feels more efficient for a given task. The biggest constraint is budget; every euro spent on tooling is scrutinized. This has led him to meticulously track server usage in a shared spreadsheet, a task he finds both tedious and necessary. He works closely with his co-founder, who handles the business side. The pressure is always on to ship features quickly and reliably, with limited resources demanding maximum output.

Relationships

Robin maintains strong ties with his university friends, who are now scattered across various tech companies. He communicates with his family weekly via phone. His primary professional influence comes from his co-founder, who shares the entrepreneurial drive. He also follows a few influential developers online whose opinions on tooling and architecture he respects.

How they decide

Robin is a pragmatic researcher. He'll weigh the pros and cons carefully, often looking for data or evidence to support a decision. He's influenced by efficiency gains and clear cost-benefit analyses, especially when budgets are tight. He trusts peer recommendations from technically sound sources but is inherently skeptical of marketing hype. He tends to favor solutions that offer transparency and control.

How they sound

Speaks with a calm, measured tone. Uses precise technical language when discussing work, but can be more conversational with friends. Avoids hyperbole and overly enthusiastic claims. Often uses Dutch interjections like 'ja' or 'ach' sparingly in casual conversation. His speech is direct and to the point, rarely wastes words.

Personality traits

  • Resourceful
  • Detail-oriented
  • Focused
  • Pragmatic
  • Quietly confident
  • Independent
  • Slightly restless
  • Skeptical of hype

Goals

  • Build a product that achieves sustainable profitability
  • Become a more proficient full-stack developer
  • Achieve a better work-life balance without sacrificing progress
  • Contribute meaningfully to an open-source project
  • Save enough for a down payment on a small apartment in Amsterdam

Problems & frictions

  • Constantly balancing feature velocity with tooling costs
  • Lack of dedicated QA resources leading to manual testing burden
  • Uncertainty about the long-term scalability of current infrastructure
  • Difficulty in predicting and controlling cloud service expenses
  • Finding time for deep technical learning amidst rapid development cycles

Values

  • lean spending
  • ownership
  • shipping
  • efficiency
  • pragmatism

Interests

  • bootstrapped startups
  • spreadsheets
  • MCP tools
  • open-source development
  • urban cycling
  • craft beer

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commute
  • Follows key figures on X (formerly Twitter)
  • Occasional dives into technical blogs
  • Uses Reddit for niche discussions

Questions & answers

Robin de Vries’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: See what your AI coding setup runs and costs. the product reads the local logs of Claude Code, Codex, Cursor and Gemini CLI and shows which skills,… 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.

    The biggest problem is definitely the uncertainty around cloud costs. We're a small startup with a tight budget, so every euro counts. I spend a fair amount of time manually tracking server usage for tools like Claude Code and Cursor in a spreadsheet. It's tedious, and I worry we might be overspending without realizing it, or worse, that unexpected spikes could hit us hard. I've tried to be diligent with the spreadsheet, but it's reactive, not proactive. Knowing what my AI coding setup actually *runs* and *costs* in real-time, as this product claims, sounds incredibly useful for controlling expenses.
    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.