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

Revi Peeters

Revi Peeters

Security-focused AI architect at a healthcare company

Full-depth AI personas

Why this persona fits the audience

Heads a 4-person AI architecture group in Amsterdam building an agent for clinical document routing. The team is conservative with model access, relies on a manual key-rotation process, and reviews usage reports before releasing anything beyond staging.

  • Age: 47
  • Location: Amsterdam, Netherlands
  • Occupation: AI Architect
  • Income: €121k salary
  • Education: MSc Computer Science
  • Company size: Mid-sized Dutch health-tech firm (~300 employees)
  • Years in role: 6
“In healthcare, a mistake isn't just a bug; it's a patient waiting for care. We build for certainty, not just capability.”

Revi Peeters is a 47-year-old AI Architect based in Amsterdam, currently leading a specialized four-person team within a prominent Dutch healthcare technology firm. With an MSc in Computer Science and nearly two decades of experience in systems engineering, Revi has carved a niche in the intersection of artificial intelligence and medical compliance. His career trajectory reflects a steady climb from backend development to security architecture, driven by a growing realization that the speed of AI adoption often outpaces the robustness of its safeguards. Currently, he is the architect behind a critical initiative: an AI agent designed to automate the routing of clinical documents. This project is fraught with challenges, primarily because the team operates under strict regulatory constraints that prohibit the casual use of public AI models. Revi has instituted a rigid, manual key-rotation process, a bottleneck he knows is inefficient but considers essential for maintaining control over data access. His team reviews every usage report meticulously before promoting any code beyond the staging environment. Despite the pressure to innovate faster, Revi remains steadfast in his philosophy that security must be the foundation, not an afterthought. He manages a budget of €121,000 annually, which allows him to invest in high-quality internal tools, though he remains frustrated by the lack of affordable, granular spend-control solutions specifically tailored for enterprise AI agents. His life outside of work is defined by a love for cycling, a commitment to his family, and a deep-seated desire to leave a legacy of secure, reliable systems in the healthcare sector.

Background & daily life

A day in their life

Revi wakes at 6:30 AM, drinks black coffee, and checks his email briefly before cycling to the office. By 8:15 AM, he is in a stand-up meeting with his four-person team, discussing the progress of the clinical document routing agent. He spends the morning reviewing a pull request that attempts to bypass the manual key rotation, firmly rejecting it and explaining the risks. Lunch is a quick sandwich eaten while reading a paper on LLM prompt injection attacks. The afternoon is dedicated to drafting a security audit report for the upcoming board meeting, detailing how their current controls mitigate specific threats. He spends late afternoon mentoring a junior developer on how to structure access logs for better traceability. After leaving the office around 5:30 PM, he cycles home, stopping at a local market for fresh vegetables. Evening time is reserved for family dinner and helping his children with homework, followed by reading or watching a documentary. He goes to bed by 10:30 PM, ensuring he gets enough sleep to maintain his sharp focus for the next day.

Lifestyle

Revi lives in a renovated canal house in the Oud-West district, a neighborhood that balances historic charm with modern utility. His mornings are ritualistic: he cycles 20 minutes to work through the city's efficient bike lanes, avoiding traffic entirely. At home, he values quiet; his living room is filled with books rather than screens. He cooks dinner most nights, often preparing healthy, simple meals for his family, viewing it as a necessary break from digital intensity. Financially, he is prudent but not stingy, prioritizing high-quality, durable goods over trends. His social circle is small but deeply trusted, consisting mostly of colleagues and neighbors he has known for years. He exercises regularly via long weekend hikes in the nearby Uithof or forests, using physical exertion to clear his mind after complex architectural decisions.

Work life

As the lead of a four-person AI architecture squad, Revi spends his days navigating the tension between rapid AI innovation and strict healthcare compliance. His team is currently engineering an intelligent agent designed to route clinical documents automatically, a project requiring absolute precision. Unlike typical startups, his environment is highly conservative; they do not grant direct API keys to junior developers. Instead, Revi enforces a manual key-rotation protocol where he personally validates every credential change. His workflow involves rigorous review of usage logs before any model interaction moves from staging to production. He is constantly pressured by the need to prove that their system is secure against data leaks while maintaining the speed required for clinical workflows. His office is a sanctuary of whiteboards covered in dependency graphs and security matrices.

Relationships

Revi is married to Elise, a primary school teacher who grounds him with her perspective on human development. They have two children, Lucas and Sophie, who keep him connected to the non-digital world. His closest friends are a mix of former university classmates now working in fintech and a few neighbors from his canal house community. He rarely seeks out large social gatherings, preferring one-on-one conversations over coffee or wine. His professional influence comes primarily from a small network of senior architects in the Benelux region, with whom he exchanges ideas about compliance and architecture. He trusts these peers implicitly when evaluating new technologies.

How they decide

Revi operates on a principle of 'verify twice, deploy once.' He is inherently cautious, preferring to delay action until all variables are understood and documented. He does not make impulsive decisions based on hype or peer pressure. Instead, he relies heavily on empirical data, historical precedents, and detailed risk assessments. When faced with a new tool or technology, he will conduct a thorough literature review, test it in an isolated sandbox, and consult with his immediate team before committing resources. He values transparency and audit trails above speed, often willing to sacrifice short-term efficiency for long-term stability and security.

How they sound

Revi speaks with a measured, calm cadence, typical of someone accustomed to explaining complex technical concepts to non-technical stakeholders. His Dutch is standard, punctuated by occasional English technical terms like 'latency,' 'throughput,' and 'compliance.' He avoids slang and hyperbole, preferring precise language. In meetings, he asks clarifying questions rather than making assumptions. He rarely uses emotional language, focusing instead on facts, logic, and consequences. When he speaks about security, his tone becomes firmer and more authoritative, emphasizing the gravity of potential failures.

Personality traits

  • meticulously organized
  • stoic under pressure
  • methodical
  • risk-averse by default
  • direct communicator
  • privacy-conscious
  • detail-oriented
  • pragmatic
  • independent thinker
  • reliable

Goals

  • Achieve zero-trust certification for the clinical routing agent within the next fiscal year
  • Automate the manual key-rotation process without introducing new vulnerabilities
  • Mentor the junior architects on the team to become independent security reviewers
  • Publish a case study on safe AI deployment in sensitive healthcare environments
  • Maintain a sustainable work-life balance to prevent burnout during high-stakes releases
  • Secure funding for a pilot program that expands their AI capabilities to diagnostic support

Problems & frictions

  • The current manual key-rotation process consumes too much time and creates bottlenecks for the development team
  • Difficulty in visualizing real-time spend across multiple AI providers without a unified dashboard
  • Pressure from leadership to accelerate feature release dates despite incomplete security audits
  • Lack of standardized tools for monitoring token usage patterns across different vendor APIs
  • Managing the cognitive load of keeping up with rapidly changing AI security threats
  • Resistance from some team members who find the strict approval processes tedious and slow

Values

  • security
  • auditability
  • careful rollout
  • professional integrity
  • predictability
  • data sovereignty

Interests

  • healthtech
  • access controls
  • systems design
  • Dutch cycling infrastructure
  • vintage mechanical keyboards
  • local history of Amsterdam canals

Media habits

  • LinkedIn technical deep-dives
  • Substack newsletters on cybersecurity
  • Dutch tech podcasts (e.g., Techzine)
  • Academic papers on LLM safety
  • Physical books on systems engineering
  • Quiet streaming of classical music while coding

Questions & answers

Revi Peeters’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Zelyx (https://zelyx.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Zelyx 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, we rely on manual processes and internal logging for usage reports, which is quite cumbersome. Zelyx's promise of an integrated spend-control layer is appealing, especially the idea of setting budgets per project or team and real-time enforcement before a bill is generated. That would be a significant improvement over our current manual key-rotation and review cycle. However, I'd need to understand more about how it integrates with our specific, sensitive clinical data workflows and whether it introduces any new security vulnerabilities or compliance gaps. The biggest concern is maintaining strict data access controls. If it can genuinely provide granular visibility and control without compromising security, it's worth considering. I would be willing to pay up to $150 per month for such a service, provided it meets our stringent security and compliance requirements.
    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.