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

David Dickinson

David Dickinson

Founder-CTO at a seed-stage SaaS

Full-depth AI personas

Why this persona fits the audience

Co-founds a 7-person customer operations SaaS in Austin. He maintains the app’s OpenAI and Anthropic calls for drafting replies, extracting fields, and summarizing long tickets, and he reviews token spend with the engineer weekly. The team uses a mix of manual prompt edits and logging in a spreadsheet.

  • Age: 31
  • Location: Austin, TX, USA
  • Occupation: Founder and CTO
  • Income: $170k + equity
  • Education: BS Computer Science
  • Company size: 7
  • Years in role: 3
“The real magic isn't just building the AI; it's making it work efficiently and reliably under real-world pressure.”

David Dickinson, 31, is a Founder and CTO based in Austin, Texas, leading a 7-person customer operations SaaS startup. Armed with a BS in Computer Science, David has always been fascinated by the intersection of complex systems and practical application. His formative years were spent devouring programming books and participating in online coding competitions, honing a meticulous approach to problem-solving. He entered the workforce at a well-funded AI research lab, gaining invaluable experience in large-scale model deployment, but quickly felt the pull of building something of his own. This led him to co-found his current venture, driven by a belief that AI could fundamentally streamline customer support workflows. His current role is deeply hands-on; he personally manages the core AI integrations, meticulously optimizing prompts for OpenAI and Anthropic models to drive efficiency. This focus on capital efficiency is paramount, as he budgets closely and reviews token spend weekly with his engineer, Sarah. He recently decided against a more complex, multi-stage AI processing pipeline in favor of a simpler, single-API-call solution that yielded immediate cost savings, reflecting his bias for shipping quickly and iterating. His income of $170k plus equity allows for comfortable living, but significant portions are reinvested into the company or saved. He views time as his most precious resource, ruthlessly prioritizing tasks that directly impact product value or system stability. He constantly grapples with the tension between rapid innovation and the need for dependable, cost-effective infrastructure, making pragmatic trade-offs daily.

Background & daily life

A day in their life

David's day typically begins around 5 AM with a 6-mile trail run, returning home by 6:30 AM to walk Pixel and grab coffee. By 7:30 AM, he's at his home office, checking overnight system alerts and responding to urgent Slack messages. His mornings are usually dedicated to deep work: refining AI prompt strategies, reviewing Sarah's code commits, or architecting a new integration. After a quick lunch, often eaten at his desk, his afternoons involve a mix of virtual investor updates, customer support escalations, planning the next sprint, and a weekly sync with Sarah to review their AI token spend and performance metrics. He might log off around 7 PM, but often circles back for an hour or two after dinner if a critical issue arises or inspiration strikes.

Lifestyle

David rents a modern, two-bedroom apartment in South Austin, sharing it with a golden retriever named 'Pixel'. His income supports a comfortable but not extravagant lifestyle, prioritizing savings for future company growth or personal investment. Weekday mornings often start with a 5 AM trail run on the Barton Creek Greenbelt before the city gets too busy. Evenings are typically spent coding, reviewing metrics, or on investor calls. He enjoys exploring Austin's food truck scene on weekends and occasionally catches live music, but his social life often takes a backseat to the demands of his startup. He's disciplined with his finances, tracking expenses closely and favoring value over luxury.

Work life

As CTO, David is deep in the technical trenches of his customer operations SaaS. His days are split between architecting new features, managing the cloud infrastructure, and diving into the intricacies of their AI integrations. He personally oversees the OpenAI and Anthropic API calls, optimizing prompts and meticulously tracking token expenditure with his sole engineer, Sarah. Debugging production issues, especially those related to AI response quality or unexpected cost spikes, is a regular occurrence. The pressure to deliver value quickly to their early customers while keeping operational costs lean is constant. He relies heavily on Slack for internal communication and Jira for task tracking.

Relationships

David is primarily focused on his company, viewing his small team (especially Sarah, his engineer) as a close-knit unit. He maintains a cordial relationship with his co-founder, who handles sales and marketing. His parents, both academics, are supportive but don't fully grasp the startup grind. He has a few close friends from college, mostly in tech, with whom he shares industry insights and commiserates about startup life.

How they decide

David is highly analytical and research-driven, preferring to gather data and weigh pros and cons before making a significant decision. He values evidence and logic, often prototyping solutions or running small experiments to validate hypotheses. While he trusts his technical intuition, he's not overly impulsive and seeks consensus on major strategic shifts, though he ultimately makes the final technical call.

How they sound

Speaks clearly and precisely, with a moderate pace. Tends to use technical jargon naturally but can explain complex concepts in simpler terms when needed. Avoids hyperbole and overly casual slang, maintaining a professional yet approachable tone. His sentences are often structured logically, reflecting his analytical thinking. He rarely expresses strong emotions publicly, favoring a measured and objective delivery.

Personality traits

  • Analytical
  • Pragmatic
  • Detail-oriented
  • Proactive
  • Resourceful
  • Dedicated
  • Systematic
  • Calm under pressure

Goals

  • Achieve product-market fit and secure Series A funding within two years.
  • Build a robust, scalable, and cost-efficient AI-powered platform.
  • Develop a strong engineering culture focused on quality and speed.
  • Become a recognized voice in the AI-driven customer operations space.
  • Maintain a healthy work-life balance to prevent burnout.

Problems & frictions

  • Managing and predicting AI API costs effectively as usage scales.
  • Balancing rapid feature development with the need for system stability and reliability.
  • Hiring and retaining top engineering talent in a competitive market.
  • Ensuring AI-generated responses consistently meet quality standards without excessive manual oversight.
  • Finding time for strategic technical planning amidst daily operational demands.

Values

  • capital efficiency
  • shipping fast
  • reliable systems
  • data-driven decisions
  • long-term scalability

Interests

  • startup finance
  • product analytics
  • trail running
  • AI/ML advancements
  • competitive programming

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes/runs (e.g., Acquired, Lenny's Podcast)
  • Follows AI researchers on Twitter/X
  • Subscribes to newsletters on SaaS metrics and early-stage investing
  • Watches YouTube deep dives on specific technologies

Questions & answers

David Dickinson’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying AgentReady (https://agentready.cloud/) 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 main hesitation would be ensuring the "caveman" output doesn't strip essential nuance or context that our customers rely on. Today, Sarah and I manually review prompt outputs and occasionally adjust them. We also meticulously log token spend in a spreadsheet to track costs. While the promise of 40-60% cost reduction is attractive, I'd need to be convinced it doesn't negatively impact response quality or require significant re-engineering of our current prompt strategies. The current beta pricing of $0/month is ideal, but I'm unclear on what happens post-beta. If it scales with usage and maintains this level of cost savings, I'd consider paying up to $300 per month.
    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.