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

Mustafa Verbeek

Mustafa Verbeek

Bootstrapped micro-SaaS co-founder managing support himself

Full-depth AI personas

Why this persona fits the audience

Bootstraps an analytics micro-SaaS with one contractor and handles most customer questions personally. He works out of Gmail and Discord, keeping troubleshooting steps, refund notes, and feature requests in Notion and a shared sheet.

  • Age: 34
  • Location: Amsterdam, Netherlands
  • Occupation: Co-founder, micro-SaaS
  • Income: EUR 78k
  • Education: Bachelor's degree
  • Company size: 2 (himself and one remote contractor)
  • Years in role: 4
“Every line of code, every customer interaction, is a building block. The goal isn't just to grow, but to build something solid that lasts, piece by deliberate piece.”

Mustafa Verbeek, 34, is a self-made entrepreneur who bootstrapped his way into the SaaS world after completing a Bachelor's degree. He co-founded an analytics micro-SaaS product, a venture he operates almost entirely solo, supported by a single remote contractor. His professional journey is characterized by a relentless pursuit of independence and efficiency, reflected in his meticulous approach to both product development and business operations. Mustafa’s early career involved a few years in a junior developer role at a larger tech firm in Rotterdam, where he observed the inefficiencies of larger organizations and solidified his desire to build something lean and focused. This experience, coupled with a naturally analytical mind and a strong sense of personal responsibility, led him to strike out on his own. He is deeply committed to cash discipline, viewing every Euro spent as a strategic investment rather than an expense. His decision to remain bootstrapped stems from a desire for complete autonomy and a belief that sustainable growth can be achieved through organic means. Mustafa’s workspace is a testament to his minimalist philosophy: Gmail, Discord, Notion, and a shared spreadsheet are his primary tools. He’s constantly optimizing workflows, documenting troubleshooting steps meticulously in Notion to create a personal knowledge base. Recently, he spent a week refining his onboarding flow for new users, realizing that while the product itself is powerful, its initial adoption could be smoother, leading him to dedicate more time to clearer in-app guidance. He views time as his most valuable, and finite, resource, allocating it with extreme care between coding, customer engagement, and strategic planning. Status, for Mustafa, is measured not by external validation or wealth, but by the product's utility and the company's resilience.

Background & daily life

A day in their life

Mustafa's typical weekday begins around 7:30 AM with a quick breakfast and scanning tech news on Hacker News. He cycles to his small co-working space by 8:30 AM, where he dedicates the first few hours to core product development, tackling coding challenges or planning new features. Lunch is usually a packed meal eaten at his desk while reviewing customer emails and Discord messages. The afternoon is a mix of responding to support queries, updating Notion with new insights, and light administrative tasks. He aims to finish by 6:00 PM, often going for a short bike ride before preparing dinner. Evenings might involve reviewing industry articles or planning the next day's tasks.

Lifestyle

Mustafa lives a structured yet unpretentious life in Amsterdam. His one-bedroom apartment is functional and tidy, reflecting his preference for simplicity. He cycles everywhere, a habit born from both environmental consciousness and a desire to control his daily schedule. His income, while comfortable for a solo founder, is managed with strict discipline; he cooks most meals at home and prioritizes savings over discretionary spending. Weekends are for catching up on personal projects, occasional meetups with a small circle of close friends, or exploring new cycling routes.

Work life

Mustafa is the primary force behind his analytics micro-SaaS, a role that demands wearing multiple hats. He codes the core features, manages the single remote contractor who handles design and some frontend work, and crucially, handles almost all customer support himself. His 'command center' consists of Gmail for client communication, Discord for quick team syncs, Notion for organizing support tickets and feature ideas, and a shared Google Sheet for tracking refunds and critical customer data. The pressure comes from balancing development time with immediate customer needs, ensuring every interaction reflects his commitment to his product.

Relationships

Mustafa maintains a close, albeit geographically dispersed, relationship with his parents in the Netherlands. His social circle in Amsterdam is small but tight-knit, consisting mostly of fellow tech enthusiasts and entrepreneurs he met through online communities and local meetups. He values candid feedback from his contractor, who acts as a sounding board for technical decisions.

How they decide

Mustafa is a highly research-driven and analytical decision-maker. He weighs options meticulously, often creating pros and cons lists or simulating potential outcomes in his head. He trusts data and empirical evidence but also values the practical insights gained from direct experience and the opinions of a few trusted peers. He avoids impulsive purchases, preferring to understand the underlying mechanics and long-term implications.

How they sound

Speaks with a measured, calm cadence, often pausing to choose precise wording. He uses clear, direct Dutch-influenced English, avoiding excessive slang or jargon unless discussing technical specifics. His tone is generally objective and informative, even when discussing frustrations. He tends to avoid hyperbole and prefers to state facts or logical conclusions.

Personality traits

  • Analytical
  • Methodical
  • Resourceful
  • Self-reliant
  • Pragmatic
  • Detail-oriented
  • Calm under pressure
  • Focused
  • Independent thinker

Goals

  • Achieve consistent monthly recurring revenue (MRR) growth
  • Automate repetitive customer support tasks
  • Build a small, sustainable company without external funding
  • Maintain a healthy work-life balance
  • Develop a strong reputation within the indie SaaS community

Problems & frictions

  • Limited time to focus on strategic product development due to support demands
  • Balancing the needs of paying customers with resource constraints
  • Onboarding new users efficiently without dedicated documentation or training resources
  • The mental overhead of managing every customer interaction personally
  • Keeping pace with evolving analytics technology and user expectations

Values

  • independence
  • simplicity
  • cash discipline
  • autonomy
  • efficiency

Interests

  • bootstrapping
  • indie SaaS
  • product analytics
  • lean methodologies
  • personal finance optimization

Media habits

  • Listens to tech and business podcasts during commutes (e.g., Indie Hackers, Acquired)
  • Reads Hacker News and relevant subreddits daily
  • Follows industry newsletters for SaaS trends
  • Occasional YouTube tutorials for coding or tool optimization
  • Checks Twitter for tech news and founder discussions

Questions & answers

Mustafa Verbeek’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying VELA (https://vela.cx/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    My current priority is handling customer questions myself to gain direct insights, which I document in Notion. Introducing an AI agent right now would require significant setup time to train it on my existing knowledge base and ensure it integrates smoothly with my workflow, which is a considerable overhead for a two-person operation. I'm not sure if the AI would be able to handle the nuances of the specific analytics questions my users have without extensive customisation. Given my focus on bootstrapping and efficiency, I'd need to see clear evidence of time savings and a low setup burden before considering it. If it could truly automate a substantial portion of my support without much effort on my end, I might consider paying up to $40 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.