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

Dies Willems

Dies Willems

CTO at a small analytics startup

Full-depth AI personas

Why this persona fits the audience

Acts as CTO for a five-person analytics startup in Amsterdam. He keeps visual checks in a lightweight flow built from free screenshot tools, GitHub issues, and a release checklist for a weekly deploy cadence. He maintains the setup himself and keeps the process easy for the rest of the team.

  • Age: 37
  • Location: Amsterdam, Netherlands
  • Occupation: CTO
  • Income: €125k
  • Education: MSc in Software Systems
  • Company size: 5
  • Years in role: 3
““The best solution is often the one you don't have to think about too much. It just works, quietly, in the background.””

Born and raised in Utrecht, Dies developed an early fascination with how systems work. He excelled in mathematics and science, leading him to pursue a Master's degree in Software Systems at Delft University of Technology. During his studies, he was drawn to the elegance of efficient code and well-designed architectures, often contributing to open-source projects in his spare time. After graduating, he worked for several years at a larger tech firm in Amsterdam, gaining experience in building scalable backend systems. However, the bureaucratic pace and lack of direct impact felt stifling. Three years ago, he was presented with the opportunity to join a nascent analytics startup as their CTO. He embraced the challenge, seeing it as a chance to build something from the ground up with a small, agile team. He is deeply committed to the company's vision but is also acutely aware of their financial constraints. This drives his preference for lean, cost-effective tooling and processes. He believes strongly in empowering his team with autonomy, and his role is as much about enabling them as it is about direct technical contribution. Dies is not driven by status or wealth accumulation; his satisfaction comes from solving complex problems elegantly and seeing the product succeed through efficient, well-managed development. He views his current setup – a mix of free tools and carefully chosen open-source components – as a testament to pragmatic engineering, demonstrating that high quality doesn't always require a massive budget.

Background & daily life

A day in their life

Dies's typical weekday starts around 7:30 AM with coffee and scanning Hacker News. He arrives at the small startup office by 9:00 AM. His morning is often spent coding new features for their analytics platform or debugging issues reported by users. After a simple lunch, he dedicates time to refining their deployment pipeline, checking GitHub issues, and ensuring the weekly release checklist is up-to-date. He might have a brief sync with his co-founders or lead developer to discuss progress. The late afternoon often involves reviewing code, planning the next sprint, and ensuring the free screenshot tools are functioning correctly for visual checks. He typically leaves around 6:00 PM, cycling home to unwind.

Lifestyle

Dies shares a canal-side apartment in the Jordaan with his partner, a graphic designer. Their evenings are typically quiet, often involving cooking together or watching documentaries. Weekends might include cycling to Haarlem or exploring a new exhibition. He's diligent about his budget, appreciating good value and avoiding unnecessary expenses. While not overtly social, he values his close circle of friends, often meeting for a casual beer or a board game night. He prioritizes mental and physical well-being, aiming for a balance between intense work focus and restorative downtime.

Work life

As CTO of a tiny analytics startup, Dies is deeply hands-on. His days are a blend of strategic thinking and tactical execution, often involving coding, architecting new features, and maintaining the team's development infrastructure. He works closely with the other four team members, fostering an environment where everyone feels empowered to contribute. The pressure comes from delivering weekly releases and ensuring the platform remains stable and scalable on a shoestring budget. He spends significant time optimizing workflows and automating repetitive tasks, seeing it as crucial for the company's survival and growth.

Relationships

Dies has a stable, long-term relationship with his partner, who provides a grounding influence. His core professional relationships are with his four startup colleagues, with whom he shares a collaborative and respectful dynamic. He also maintains contact with former university classmates and colleagues, forming a small network for technical discussions and occasional advice.

How they decide

Dies is a methodical decision-maker. He researches thoroughly, often comparing free and open-source options first. He weighs cost-effectiveness against potential time savings and the complexity of implementation and maintenance. He’ll seek input from his team if a decision impacts them directly, but ultimately trusts his technical judgment and experience. He prefers solutions that integrate well and minimize disruption.

How they sound

Speaks with a calm, measured cadence. Uses clear, precise language, avoiding jargon unless explaining a technical concept. His Dutch accent is subtle but present. He is direct and factual, preferring to explain the 'why' behind his decisions. He rarely uses slang or overly casual expressions in professional contexts, but can be more relaxed with close colleagues. He steers clear of hyperbole or overly emotional language.

Personality traits

  • pragmatic
  • detail-oriented
  • resourceful
  • self-reliant
  • calm under pressure
  • methodical
  • observant
  • understated

Goals

  • Scale the analytics platform to serve 1,000 paying customers within two years.
  • Establish a robust, automated CI/CD pipeline that requires minimal manual intervention.
  • Achieve a consistent 99.9% uptime for the production environment.
  • Contribute back to an open-source project relevant to their tech stack.
  • Maintain a sustainable work-life balance without sacrificing innovation.

Problems & frictions

  • Limited budget for essential development and testing tools.
  • Balancing rapid feature development with maintaining robust quality assurance.
  • The overhead of managing and updating self-hosted infrastructure.
  • Ensuring comprehensive visual regression testing across diverse browser/device combinations.
  • Onboarding new developers quickly to the existing codebase and tooling without extensive training.

Values

  • simplicity
  • budget discipline
  • team autonomy
  • efficiency
  • clarity

Interests

  • analytics platforms
  • GitHub issues
  • release checklists
  • system design
  • devops tooling
  • open source communities

Media habits

  • Reads Hacker News daily
  • Follows key figures on Twitter (X)
  • Listens to technical podcasts during commute
  • Scans newsletters from industry blogs
  • Watches YouTube tutorials for new tools

Questions & answers

Dies Willems’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: The batteries-included platform for visually testing and reviewing your UI; it's even self-hostable! Connect your codebase with our many integrations and dramatically increase your test coverage in minutes. 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 we face is ensuring comprehensive visual regression testing across different browsers and devices. Our current setup, using free screenshot tools and manual checks, is time-consuming and prone to errors. It costs us significant developer time each week, diverting us from building new features, and I worry we miss subtle UI regressions that could impact user experience, potentially affecting customer trust. We've tried scripting some basic checks, but it's fragile and difficult to maintain with our small team and limited budget.
    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.