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

Raymond Dare

Raymond Dare

Seed-stage SaaS founder and CTO

Full-depth AI personas

Why this persona fits the audience

He leads a 5-person B2B SaaS team where an internal AI support agent tags tickets, posts urgent cases to Slack, and writes edge cases into a shared sheet; the notification path is stitched together with Zapier, Slack webhooks, and a couple of scripts.

  • Age: 34
  • Location: Austin, Texas, US
  • Occupation: Cofounder and CTO
  • Income: $180k total comp
  • Education: BS in Computer Science
  • Company size: 5
  • Years in role: 3
“We're building something that needs to be rock-solid, but we're doing it on a shoestring. Every decision has to be smart, efficient, and forward-thinking.”

Raymond Dare, 34, is the co-founder and CTO of a nascent B2B SaaS startup based in Austin, Texas. Armed with a BS in Computer Science from UT Austin, he co-founded his current venture three years ago with a vision to streamline complex workflows for businesses using AI. His background includes several years as a software engineer at a mid-sized tech firm, where he honed his skills in backend development and system architecture, but he always felt the pull of building something from the ground up. His income of $180k reflects his co-founder status and the demanding nature of his role. Raymond is married to Sarah, and they share a conscious approach to their finances, prioritizing long-term stability and experiences over immediate gratification; they live in a townhouse they're steadily renovating. His drive for autonomy and efficiency is evident in his work, where he meticulously crafts systems to maximize output with minimal overhead. He views time as a critical, non-renewable resource, constantly seeking ways to optimize his own workflow and that of his team. This frugality extends to tool selection, where he rigorously vets every subscription, preferring to leverage clever integrations and custom scripting over expensive, off-the-shelf solutions. His current focus is on stabilizing and scaling the company's internal AI support agent, a critical piece of infrastructure that, while functional, relies on a patchwork of Zapier, Slack webhooks, and custom scripts – a testament to his resourcefulness and pragmatic approach to problem-solving under tight constraints.

Background & daily life

A day in their life

Raymond's day starts around 6:00 AM with a quick check of overnight system alerts and critical support tickets, followed by a 30-minute spin class on his smart trainer. After a brief breakfast with his wife, he's at his home office by 7:30 AM. The morning is dedicated to deep work: coding new features or refining the AI agent's logic. After a quick lunch, he holds a stand-up meeting with his remote team, reviews pull requests, and tackles any urgent operational issues. His afternoon might involve architecting a new service or troubleshooting a production bug. He aims to wrap up by 6:00 PM, though urgent issues can extend this. Evenings are for family time, dinner, and perhaps an hour of reading tech news or listening to a podcast before bed.

Lifestyle

Raymond lives in a modern, slightly minimalist townhouse in South Austin with his wife, Sarah, a graphic designer. They're both focused on building their careers and enjoy a comfortable but not extravagant lifestyle. Weekends often involve long bike rides along the Barton Creek Greenbelt, followed by trying out new breweries or exploring local food trucks. They value experiences over material possessions, channeling most discretionary income into travel or home improvements. Raymond's routine is highly structured, prioritizing his work and fitness.

Work life

As CTO of a seed-stage SaaS company, Raymond juggles product development, infrastructure management, and a hands-on approach to problem-solving. His current focus is optimizing the AI support agent's workflow, which involves a convoluted but functional system of Zapier, Slack webhooks, and custom scripts. He's constantly scrutinizing tool costs, preferring robust open-source solutions or deeply discounted early-access programs. The pressure is on to scale efficiently, meaning every automation and process improvement directly impacts their runway and customer satisfaction.

Relationships

Raymond is married to Sarah, who provides a grounding influence and a different perspective outside of tech. His co-founders are his primary professional circle, sharing the intense startup journey. He has a small group of close friends from college, a few of whom are also in tech, offering a sounding board for technical challenges and career advice.

How they decide

Raymond is a methodical researcher. He weighs pros and cons carefully, often sketching out workflows and data flows before committing. He trusts empirical evidence and peer recommendations from reputable sources but is wary of hype. Cost-effectiveness and long-term maintainability are key factors in his decisions. He prefers to experiment with free tiers or trials before making significant commitments.

How they sound

Speaks clearly and deliberately, with a measured pace. Tends to use precise technical language when discussing work, but can simplify when explaining concepts to non-technical people. Avoids excessive jargon or slang, aiming for professionalism. His tone is generally calm and rational, even when discussing stressful situations. He often uses analogies to explain complex systems.

Personality traits

  • analytical
  • resourceful
  • driven
  • detail-oriented
  • pragmatic
  • slightly introverted
  • future-focused
  • calm under pressure

Goals

  • Achieve product-market fit and secure Series A funding
  • Build a highly scalable and reliable core product infrastructure
  • Mentor and grow the engineering team effectively
  • Maintain a healthy work-life balance despite startup demands
  • Contribute meaningfully to the open-source AI community

Problems & frictions

  • The current notification pipeline is brittle and prone to breaking
  • Balancing rapid feature development with technical debt reduction
  • Finding time for deep work amidst constant operational demands
  • Managing team bandwidth effectively without overspending on headcount
  • Ensuring the AI agent's outputs are consistently accurate and actionable

Values

  • reliability
  • speed
  • autonomy
  • frugality
  • efficiency

Interests

  • SaaS
  • automation
  • cycling
  • startup podcasts
  • AI development
  • scaling infrastructure

Media habits

  • Listens to podcasts during commutes and workouts
  • Reads industry newsletters and tech blogs daily
  • Follows tech influencers on Twitter/X
  • Watches YouTube tutorials for new tools/techniques
  • Checks Hacker News for relevant discussions

Questions & answers

Raymond Dare’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on DevHunt: Custom notification hub for AI agents and everything else - the product is a notification relay platform built for the AI era. It lets your AI agents,... 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.

    My biggest headache right now is the brittleness of our notification pipeline. It's a Frankenstein of Zapier, Slack webhooks, and custom scripts. When it breaks, which it does more often than I'd like, urgent support tickets get missed, and the team has to scramble to manually triage them. This is a significant time sink, costing us hours of developer time each week that could be spent on actual product development. We've tried adding more robust error handling and monitoring, but it feels like we're just patching a fundamentally unstable system.
    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.