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

Lou de Nijs

Lou de Nijs

Fractional CTO and consultant

Full-depth AI personas

Why this persona fits the audience

Splits time across two client products in Amsterdam, both built in Next.js and maintained by small teams. She uses AI agents for routine UI work, then checks migrations, form handling, and API routes with browser devtools, free linters, and a shared spreadsheet of edge cases.

  • Age: 36
  • Location: Amsterdam, Netherlands
  • Occupation: Fractional CTO and freelance consultant
  • Income: €95k per year
  • Education: Master's degree in computer science
  • Company size: Typically works with client companies ranging from 5-20 employees.
  • Years in role: 8
“The most elegant solution is rarely the most obvious one; it's the one that anticipates the next ten problems.”

Lou de Nijs embodies the modern, independent tech professional, carving out a niche as a fractional CTO and consultant deeply embedded in the Next.js ecosystem. With a Master's degree in Computer Science from the University of Amsterdam, she honed her skills at startups before transitioning to consulting eight years ago, drawn by the desire for variety and autonomy. Now 36, she skillfully divides her time between two Amsterdam-based clients, guiding their product development and ensuring technical stability. Her approach is characterized by a profound commitment to thoroughness; she meticulously vets AI-generated code, focusing on critical areas like migrations and API routes, supplementing her technical tools with a rigorously maintained spreadsheet of edge cases. This dedication stems from a value system prioritizing trust and practical outcomes. Lou’s income of €95k annually supports a comfortable, balanced life, affording her the freedom to invest in quality developer tools and pursue her passions outside of work, such as sailing on the weekends or experimenting with complex recipes. She views her career not just as a job, but as a continuous process of building robust systems and finding elegant, sustainable solutions, driven by a blend of analytical thinking and a calm, conscientious work ethic. Her recent focus has been on refining her workflow to better integrate AI assistance without sacrificing code integrity, a constant balancing act in the current development landscape.

Background & daily life

A day in their life

Lou's typical weekday starts around 7:00 AM with coffee and a quick scan of overnight notifications and tech news. She dedicates the first few hours to focused work for her primary client, often tackling complex backend logic or reviewing PRs. After a light lunch, she switches gears to her second client, perhaps coordinating with their small team on feature development or addressing urgent bugs. Mid-afternoon might involve a sync call with one of the teams, followed by more code review or investigating an edge case identified in her meticulous spreadsheet. She aims to wrap up her core work by 6:00 PM, leaving evenings for personal pursuits like cooking or catching up on industry reading, ensuring she disconnects from client work.

Lifestyle

Lou cherishes her carefully cultivated work-life balance. Her Amsterdam apartment is a sanctuary, tidy and filled with plants, reflecting her appreciation for calm. Evenings often involve experimenting with new recipes or unwinding with a good book. Weekends might see her on the water, sailing on the IJsselmeer if the weather permits, or catching up with a small circle of close friends over dinner. She tracks her finances diligently, a habit from her early career, ensuring her income supports her lifestyle without extravagance, but allows for travel and investments in quality tools. She views her income as a means to security and experiences, rather than overt status.

Work life

As a fractional CTO, Lou’s workdays are a dynamic blend of strategic oversight and hands-on problem-solving. She juggles two distinct product roadmaps, demanding constant context switching. Her collaboration with small, often lean, client teams means she's deeply involved, from architecture discussions to debugging complex issues. She leverages AI agents for initial UI scaffolding, but her core work involves rigorous verification: meticulously checking database migrations, ensuring robust form handling, and scrutinizing API route logic. The shared spreadsheet of edge cases is her bible. Pressures come from client deadlines and the inherent complexity of maintaining multiple evolving codebases.

Relationships

Lou maintains a close but not overly demanding relationship with her parents, who live in a nearby town. Her core social circle consists of a few long-term friends, mostly met during her university years or through shared interests like sailing. Professionally, she relies on a network of trusted peers for advice and occasional collaboration, valuing their technical acumen and discretion. Her client relationships are professional and built on consistent delivery.

How they decide

Lou is a highly analytical and research-driven decision-maker. She prioritizes understanding the 'why' behind any proposed solution, weighing evidence and potential long-term implications. She's not easily swayed by hype and prefers to see practical, demonstrable results. While open to new approaches, she thoroughly vets them, often running small internal tests or seeking corroborating opinions from trusted sources before committing significant resources or time.

How they sound

Speaks with a clear, measured cadence, exhibiting a professional yet approachable tone. Her Dutch accent is subtle. She avoids excessive jargon unless speaking with other developers, preferring precise, descriptive language. Her speech is often punctuated by thoughtful pauses as she considers her words carefully. She is unlikely to use overly casual slang or express strong emotional opinions without significant qualification.

Personality traits

  • meticulous
  • analytical
  • pragmatic
  • detail-oriented
  • independent
  • resourceful
  • calm under pressure
  • forward-thinking

Goals

  • To contribute to building sustainable, well-engineered digital products.
  • To achieve greater mastery over niche areas of web development, particularly around developer experience and performance optimization.
  • To maintain her independence and flexibility as a consultant.
  • To eventually spend more extended periods sailing, perhaps combining it with remote work.
  • To mentor junior developers, sharing her systematic approach.

Problems & frictions

  • The inherent unpredictability of AI-generated code requires significant manual validation.
  • Managing communication and differing priorities across two separate client projects.
  • Finding time for deep, uninterrupted focus amidst client demands and context switching.
  • Ensuring consistency in best practices across teams with varying levels of experience.
  • The constant need to stay abreast of the rapidly evolving JavaScript ecosystem.

Values

  • trust
  • thoroughness
  • balance
  • practical outcomes

Interests

  • developer tooling
  • product strategy
  • cooking
  • sailing

Media habits

  • Follows key figures in the Next.js and broader web development communities on Twitter/X.
  • Subscribes to a few curated tech newsletters (e.g., TLDR Web Dev, JavaScript Weekly).
  • Listens to podcasts during commutes or while cooking (e.g., Syntax.fm, Software Engineering Daily).
  • Reads technical blogs from established companies and individual developers.
  • Uses LinkedIn for professional networking and industry news.

Questions & answers

Lou de Nijs’s public research answers, newest questions first. Up to 10 per page.

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

    The "VibeBoot SaaS Starter" at $49 sounds interesting as it bundles a lot of common setup, which is appealing given the time I spend debugging migrations and API routes. What would stop me from trying it this month is primarily the current workload; I'm already split between two clients, and integrating a new starter project, even for a new client or a refactor, would require careful planning to avoid disrupting existing workflows. My current process involves extensive manual checks and my edge case spreadsheet, which, while time-consuming, is proven. For a starter like this, I'd need to dedicate specific time to evaluate its code quality and ensure it aligns with my strict standards before fully committing. If I were to explore it, I might consider it for a future project or a client that's just starting out. I would not pay more than $0 per month for this product at this time, as the starter is a one-time purchase and my current needs are met by my existing processes and tools.
    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.