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

Mark Vos

Mark Vos

Fractional CTO / independent consultant

Full-depth AI personas

Why this persona fits the audience

He works as a fractional CTO for two early-stage SaaS companies and maintains their Next.js codebases part-time. Both products use Supabase, and he spends recurring time on auth, billing, team management, and repo scaffolding before new hires can contribute.

  • Age: 38
  • Location: Amsterdam, Netherlands
  • Occupation: Fractional CTO / independent consultant
  • Income: €95k
  • Education: MSc Software Engineering
  • Company size: Works with early-stage startups (typically 2-10 employees)
  • Years in role: 5
“The real value is in building systems that don't just work today, but can gracefully evolve for years to come.”

Mark Vos, 38, operates as a fractional CTO and independent consultant from his base in Amsterdam. Holding an MSc in Software Engineering, he carved out a niche by focusing on early-stage SaaS companies, leveraging his expertise in Next.js and Supabase. His career trajectory wasn't a straight line; after a few years in traditional software development roles post-university, he recognized the growing demand for specialized, part-time technical leadership in the startup ecosystem. This led him to transition into consulting, offering his skills on a flexible basis. He deliberately chose this path for the autonomy it provides and the variety of challenges it presents. Mark's current engagements involve two distinct SaaS ventures. For one, he's deeply involved in refining their user authentication and team management features built on Supabase, ensuring a secure and scalable foundation. For the other, he's focused on architecting their billing system and setting up robust repo scaffolding to facilitate rapid team growth. He prioritizes reusable patterns and clean code, believing that well-structured systems are key to long-term success and efficient team collaboration. This philosophy extends to his personal life; he values his independence and carefully manages his time to balance demanding work with personal interests like sailing. He lives alone, maintaining a disciplined routine that allows for deep work while preserving mental space. Financially, he’s prudent, saving consistently, which provides a sense of security and allows him to be selective about the projects he takes on. He recently decided to invest more time in understanding modern DevOps practices to further streamline his clients' deployment pipelines, seeing it as a critical area for early-stage companies. His approach is characterized by a commitment to quality, a pragmatic view of technology, and a deep understanding of the pressures faced by lean, growing businesses.

Background & daily life

A day in their life

Mark's typical weekday starts around 7:30 AM with coffee and a quick scan of Hacker News and his project dashboards. He dedicates the morning, usually until noon, to focused coding and problem-solving for one of his client projects, often tackling complex auth or billing logic. After a simple lunch, he transitions to the second client, perhaps a code review, a sync with their product manager, or setting up new repository structures. Late afternoon might involve documentation, planning the next day's tasks, or a brief virtual meeting. He aims to wrap up by 6 PM, leaving evenings free for personal interests, exercise, or quiet relaxation before preparing for the next day.

Lifestyle

Mark lives a structured yet flexible life in Amsterdam. His apartment is minimalist and functional, reflecting his focus on efficiency. He values his independence, which extends to his work and personal time. Weekends often involve a mix of catching up on personal projects, planning his week, and occasionally meeting friends for a quiet drink or a walk along the canals. He enjoys sailing on the nearby lakes during warmer months, finding it a perfect escape to clear his head. Financially, he's comfortable and saves consistently, prioritizing long-term security over immediate gratification, but isn't afraid to invest in quality tools or experiences that enhance his productivity or well-being.

Work life

As a fractional CTO, Mark juggles the technical leadership for two distinct SaaS startups. His days are a blend of deep-work coding sessions on Next.js and Supabase, architectural discussions, and mentoring junior developers. He spends significant time ensuring robust authentication, seamless billing integration, and efficient team management workflows. A core part of his role involves setting up well-structured repositories and clear contribution guidelines, aiming for smooth handoffs as teams grow. The pressure comes from delivering high-quality, scalable solutions with limited resources and tight timelines, often requiring him to wear multiple hats beyond just coding.

Relationships

Mark maintains a small circle of close friends, mostly fellow tech professionals with whom he shares industry insights and occasional social outings. He has a good relationship with his parents, who live in a smaller town in the Netherlands, and calls them weekly. His professional network is built on mutual respect and shared technical interests, often interacting through online communities and occasional meetups.

How they decide

Mark is a deliberate decision-maker. He thoroughly researches options, weighing pros and cons based on technical merit, long-term maintainability, and alignment with project goals. He values evidence and practical application over hype, often seeking out case studies or community consensus before committing to a particular approach or tool. He's not impulsive and prefers to avoid rushed decisions, especially when they involve core architecture or significant refactoring.

How they sound

Speaks with a measured, clear cadence. His English is fluent with a subtle Dutch accent, avoiding slang or overly casual language in professional contexts. He tends to be direct and factual, preferring to explain the 'why' behind his technical recommendations. He uses precise terminology and avoids hyperbole, often pausing to formulate his thoughts carefully. He’s not one for small talk but is polite and professional.

Personality traits

  • methodical
  • detail-oriented
  • independent
  • pragmatic
  • resourceful
  • analytical
  • calm under pressure
  • observant
  • patient

Goals

  • Achieve a sustainable work-life balance with predictable income
  • Contribute meaningfully to a few select open-source projects
  • Build a small, passive income stream from a personal SaaS tool
  • Maintain and improve his sailing skills
  • Become a recognized expert in scalable SaaS architectures for early-stage companies

Problems & frictions

  • Balancing the demands of two different client projects simultaneously
  • Onboarding new developers effectively into existing, complex codebases
  • Ensuring consistent code quality and security across projects
  • Managing client expectations regarding timelines and feature scope
  • Finding time for deep learning and staying ahead of rapidly evolving tech stacks
  • The inherent uncertainty of startup funding and project longevity

Values

  • reusable systems
  • flexibility
  • clean handoffs
  • long-term maintainability
  • autonomy

Interests

  • open source
  • product strategy
  • sailing
  • Next.js
  • DevOps practices
  • API design

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes (e.g., Syntax.fm, Software Engineering Daily)
  • Follows key developers and projects on GitHub and Twitter
  • Subscribes to newsletters on modern web development and SaaS trends
  • Watches YouTube tutorials for specific technical challenges

Questions & answers

Mark Vos’s public research answers, newest questions first. Up to 10 per page.

  1. Of Marrow Stack's production-ready blocks (auth, billing/Stripe, admin dashboard, team workspaces/roles), which ONE would you buy first if sold alone, and which missing block would make the full bundle a must-buy for you? Explain briefly.

    If Marrow Stack sold blocks individually, I'd first purchase the Auth System. It's a recurring need for my clients, and given my experience with Supabase, seeing it's wired up is a good sign. The missing piece that would make the full bundle indispensable is a robust, opinionated Admin Dashboard. While I can scaffold one, a production-ready, well-integrated admin panel that handles user management, roles, and possibly basic analytics would significantly accelerate development for early-stage companies. The "SaaS Starter Bundle" looks promising, but I'd need to see the admin dashboard capabilities.
    View answer & full research →
  2. For Marrow Stack's production-ready Next.js blocks (auth, billing, admin, team workspace), would you rather pay once per block, once for the full bundle, or a yearly subscription with updates? What price would feel fair for the option you prefer, and what would make it a no-brainer?

    As a fractional CTO, I spend considerable time on auth, billing, and team management for early-stage SaaS companies using Supabase. The idea of pre-built blocks for these core functions is appealing, especially if they're ORM agnostic, as I use Supabase directly. A one-time purchase per block or for a bundle makes the most sense for my clients' budgets, avoiding recurring costs. For a comprehensive bundle like the SaaS Starter, I'd consider paying up to $499. For it to be a no-brainer, clear documentation on integration with Supabase and examples of customization would be essential.
    View answer & full research →
  3. What do you use today instead of Marrow Stack (https://marrowstack.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Marrow Stack 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).

    Currently, for my clients, I build out auth, team management, and billing systems from scratch using Supabase, and repository scaffolding is done through custom scripts and internal guidelines. Your Marrow Stack's 'Auth System' and 'Billing & Subscriptions' blocks look interesting, especially since they are Supabase-ready and typed. The main advantage would be the speed of implementation, potentially saving days of work. However, I'd need to evaluate how easily these blocks integrate with existing, potentially complex, codebases. The security defaults are a plus, but I'd still want to review them thoroughly. The biggest deterrent would be a lack of flexibility or if the blocks introduce too much opinionation that conflicts with our established patterns. I would be willing to pay up to $150 per month, but that would depend heavily on the breadth of blocks available and their customization options.
    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.