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

Cory Davis

Cory Davis

Seed-stage SaaS founder handling product, ops, and incident communications

Full-depth AI personas

Why this persona fits the audience

Runs a 4-person remote SaaS team in Austin. When their app has an outage, they update customers through a simple public status page maintained in a shared spreadsheet and a static site, with incident notes pasted from Slack and GitHub issues. He is also the one approving software spend.

  • Age: 34
  • Location: Austin, TX, US
  • Occupation: Co-founder and CEO
  • Income: $140k-180k
  • Education: Bachelor's degree
  • Company size: 4
  • Years in role: 3
“Every minute we spend firefighting an outage is a minute we're not building for the future. We need systems that let us be proactive, not just reactive.”

Cory Davis, 34, is the quintessential bootstrapped SaaS founder, operating out of Austin, Texas. Armed with a Bachelor's degree in Computer Science, he dove headfirst into the startup world immediately after graduation, cutting his teeth at a couple of well-funded tech companies before realizing his passion lay in building something from the ground up. Three years ago, he co-founded his current venture, a niche SaaS product aimed at developers, and has been living and breathing it ever since. His income, while comfortable at $140k-180k, is largely reinvested into the business, reflecting his lean operations value. He lives a relatively frugal existence in a modest one-bedroom apartment, prioritizing company runway over personal extravagance. Cory's approach to work is characterized by a strong sense of responsibility and a drive for clarity; he believes that well-defined processes and transparent communication are the bedrock of customer trust. This philosophy directly informs how he manages the company's current 4-person remote team. When the inevitable server hiccup occurs, Cory is the one patching together updates for their customers, pulling notes from Slack and GitHub issues into a rudimentary static status page, a process he acknowledges is inefficient but functional for now. He’s also the de facto finance department, scrutinizing every software subscription request with a critical eye, always asking if it aligns with their tight budget and growth trajectory. His personal life is neatly compartmentalized; while he enjoys cycling to decompress, his mind often wanders back to product roadmaps and operational bottlenecks. He sees time as his most valuable, yet most limited, resource, constantly seeking ways to optimize its use both personally and professionally, viewing every decision through the lens of long-term company health and sustainable growth.

Background & daily life

A day in their life

Cory's typical weekday begins around 6:30 AM in Austin. After a quick check of overnight system alerts and customer support tickets, he makes coffee and reviews key product analytics dashboards. He then dedicates a block to core product work or strategic planning. Mid-morning involves a stand-up with his remote team, followed by customer calls or responding to urgent emails. Lunch is usually a quick, healthy meal eaten at his desk. The afternoon is a mix of engineering syncs, reviewing code commits, approving software invoices, and often, drafting customer communications if an incident arises. He aims to wrap up core work by 6 PM, though late-night check-ins are common.

Lifestyle

Cory lives a focused, work-centric life in Austin, prioritizing efficiency. His routine revolves around maximizing productivity for his startup. Weekday mornings start early with coffee and a quick check of overnight metrics before a bike ride if time permits. Evenings are often spent catching up on industry news or troubleshooting. Weekends involve longer cycling trips or occasional meetups with other founders. He’s conscious of his spending, treating his income as growth capital for the business rather than personal luxury, and lives a relatively minimalist lifestyle in his apartment to save burn rate.

Work life

As co-founder and CEO, Cory is deeply involved in every facet of the 4-person remote company. He juggles product strategy, operational efficiency, and crucially, customer communication during incidents. The current incident management process involves manually updating a static site from Slack and GitHub, a system he knows is fragile but a time sink to improve. He's also the gatekeeper for all software subscriptions, constantly evaluating ROI. Coworkers are distributed globally, leading to asynchronous communication challenges. The pressure to scale while maintaining lean operations is a constant backdrop.

Relationships

Cory maintains close ties with his co-founder, a technical lead based in Europe, communicating multiple times daily. His relationship with the rest of the small, remote team is professional but friendly, built on shared goals. Outside of work, he has a solid circle of college friends who are also in tech, often discussing startup challenges. His parents, while supportive, don't fully grasp the intricacies of his SaaS venture.

How they decide

Cory is a pragmatic, data-informed decision-maker. He weighs options carefully, always considering the cost-benefit analysis and the impact on lean operations. He's not afraid to try new tools but prefers those with clear utility and minimal setup. He relies on peer recommendations and industry reviews but ultimately trusts his own assessment of value and efficiency, especially when approving software spend.

How they sound

Speaks clearly and directly, with a measured pace. Uses industry jargon naturally but avoids overly technical explanations unless necessary. His tone is generally calm and reassuring, even when discussing stressful situations. Tends to be concise, focusing on actionable insights and avoiding fluff. Might use mild Austin colloquialisms occasionally, but generally maintains a professional demeanor.

Personality traits

  • Pragmatic
  • Resourceful
  • Detail-oriented
  • Customer-focused
  • Driven
  • Slightly overwhelmed
  • Calm under pressure
  • Analytical

Goals

  • Achieve consistent MRR growth for the next 18 months
  • Build a repeatable sales process
  • Establish a robust, automated incident response system
  • Maintain a healthy company culture as the team grows
  • Eventually hire a dedicated Head of Product

Problems & frictions

  • Balancing urgent customer needs with long-term product development
  • Limited time and resources for non-essential operational improvements
  • Ensuring clear, consistent communication during high-stress incidents
  • Finding reliable, affordable tools that scale with a small team
  • The mental load of being the ultimate decision-maker on all fronts

Values

  • clarity
  • speed
  • customer trust
  • lean operations
  • autonomy

Interests

  • startup tooling
  • product analytics
  • remote work
  • cycling
  • early-stage investing

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes/workouts
  • Follows key SaaS influencers on Twitter
  • Skims industry newsletters for trends
  • Watches YouTube tutorials for new tools

Questions & answers

Cory Davis’s public research answers, newest questions first. Up to 10 per page.

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

    What would stop me from trying Statsy? Frankly, the biggest hurdle is time. Right now, I'm manually patching together customer updates from Slack and GitHub into a static site. It's a time sink, but it's what we have. Automating this would be huge, but I'm also the one approving all our software spend, and we're pretty lean. We're currently doing okay with our spreadsheet and static site setup, so while the allure of a dedicated status page is there, it's not an urgent fire I need to put out immediately. If I were to consider something like this, I'd need to see a clear ROI and minimal setup time. Ideally, I wouldn't want to pay more than $15 per month for a solution that covers our basic needs.
    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.