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

Cary Kiehn

Cary Kiehn

CTO-cofounder at a tiny remote SaaS team

Full-depth AI personas

Why this persona fits the audience

He leads a 3-person remote SaaS team in Denver and is responsible for release notes from the repo. He writes up the GitHub pushes, drops them into a spreadsheet for the part-time marketer, and sometimes schedules the resulting posts himself in Meta Business Suite.

  • Age: 46
  • Location: Denver, Colorado, US
  • Occupation: CTO and cofounder, SaaS
  • Income: US$165k + equity
  • Education: Master's degree in computer science
  • Company size: 3 employees (including himself)
  • Years in role: 4
“I don't care how flashy the feature is if the underlying system collapses under load.”

Cary Kiehn is a seasoned technologist who transitioned from a senior engineering role at a mid-sized enterprise to co-founding a lean SaaS venture four years ago. Holding a Master's degree in Computer Science from a top-tier university, Cary brings a wealth of architectural experience to his small team. Currently based in Denver, he operates as the technical backbone of a three-person organization, where he wears multiple hats ranging from lead developer to systems administrator and, unexpectedly, chief marketing officer for release communications. Despite his high earning potential and equity stake, Cary maintains a frugal lifestyle, driven by a desire to maximize the company's runway and minimize unnecessary overhead. His professional life is defined by a relentless pursuit of efficiency and order. However, this drive is currently tested by the chaotic reality of being a generalist in a specialized field. He spends hours each week manually curating GitHub commit history, translating cryptic technical jargon into digestible marketing copy, and navigating the complexities of third-party social media scheduling tools. This bottleneck is a source of significant frustration, as it diverts valuable time from the system design and strategic planning that originally drew him to entrepreneurship. Cary is a man of few words but many actions, valuing tangible results over empty promises. He is currently exploring ways to streamline his operational workflows, seeking solutions that offer robust reliability without introducing new layers of complexity or cost. His recent decision to audit his entire tech stack reflects his growing impatience with fragmented processes that threaten the stability of the business he helped build.

Background & daily life

A day in their life

Cary wakes at 6:00 AM and runs until 7:00 AM, returning to brew a pot of coffee and review overnight server logs. By 8:30 AM, he joins the team's daily stand-up via Zoom, where he discusses the progress of the new API integration. From 9:30 AM to 12:00 PM, he focuses on deep work, writing complex SQL queries and refactoring the user dashboard. At lunch, he steps away for a walk to clear his head. In the afternoon, he tackles the dreaded task of reading through the last week's Git commits, extracting key features, and pasting them into the master spreadsheet. He spends the final hour troubleshooting a minor bug reported by a client and manually scheduling a few social media posts for the upcoming Friday release. He leaves his desk at 5:30 PM sharp, shutting down his laptop to spend the evening with his family.

Lifestyle

Cary lives in a modest but well-maintained Craftsman-style home in Denver's Highlands neighborhood, just blocks from the light rail. His mornings begin with a strict routine: 6:00 AM coffee, a 30-minute run along the South Platte River, and checking his email before the house wakes up. He is married to Elena, a graphic designer, and they have an eight-year-old son who plays soccer on weekends. Cary manages his finances conservatively; despite his high income, he avoids luxury spending, preferring to reinvest savings into their retirement accounts or emergency funds. He enjoys mechanical keyboard building as a tactile hobby that satisfies his need for precision. Socially, he is selective, preferring deep one-on-one conversations over large gatherings, often meeting friends for dinner once a month rather than weekly happy hours.

Work life

As the CTO of a three-person remote SaaS startup, Cary is the primary architect of their codebase and the de facto product manager. His days are split between writing core backend logic, debugging production issues, and managing the company's public face. A significant portion of his week is consumed by the manual process of translating raw GitHub commit messages into readable release notes. He copies these logs into a shared Google Sheet, where a part-time contractor formats them for marketing. Occasionally, when the contractor is unavailable, Cary personally drafts the copy and schedules it via Meta Business Suite. The pressure is constant; with only two other people, there is no buffer for error, and every missed deployment or delayed announcement feels like a direct hit to the company's credibility.

Relationships

Cary relies heavily on his wife, Elena, for emotional grounding and household management. He maintains a small circle of former colleagues from his previous role at a mid-sized tech firm, mostly connected via LinkedIn. He has a trusted relationship with his part-time marketer, though the lack of a formal workflow creates friction. He is not deeply involved in local community organizations, viewing his time as a scarce resource reserved for family and the business. His decision-making is rarely influenced by peer reviews; he trusts data and personal experience over industry trends.

How they decide

Cary approaches decisions with a cautious, analytical mindset. He gathers data, constructs a logical framework, and evaluates risks before committing. He is skeptical of 'magic bullet' solutions and prefers incremental improvements backed by clear evidence. While he is open to new ideas, he requires a low barrier to entry for testing and a high certainty of reliability before integrating anything into his production environment. He values transparency and accountability above all else in any partnership.

How they sound

Cary speaks in a measured, deliberate tone, often using precise terminology. He avoids slang and hyperbole, preferring factual statements over emotional appeals. When discussing work, he tends to focus on the 'how' and 'why' rather than the 'what.' He frequently pauses to think before answering, ensuring his responses are accurate. He does not use buzzwords like 'synergy' or 'disrupt,' finding them distracting. His speech pattern reflects his background in engineering: structured, logical, and efficient.

Personality traits

  • Methodical
  • Pragmatic
  • Detail-oriented
  • Reserved
  • Systematic
  • Self-reliant
  • Anxious about downtime
  • Process-driven
  • Low-maintenance socializer
  • Frustrated by inefficiency

Goals

  • Achieve consistent monthly recurring revenue growth without increasing headcount
  • Refactor the legacy authentication module to improve security and speed
  • Automate all non-core engineering tasks to free up coding time
  • Build a sustainable work-life balance that allows for weekend hiking trips
  • Establish the company as a reliable player in the specific niche market
  • Prepare the codebase for a potential acquisition or Series A funding round

Problems & frictions

  • The manual transcription of commit logs is time-consuming and prone to human error
  • Inconsistent communication channels between the technical team and the part-time marketer
  • Lack of immediate feedback loops on how marketing content performs
  • Difficulty finding reliable tools that integrate cleanly with their existing stack
  • Feeling overwhelmed by the administrative burden of being a 'generalist' founder
  • Uncertainty about whether the current release cadence matches customer expectations

Values

  • control
  • reliability
  • focus
  • accountability
  • transparency

Interests

  • system design
  • release management
  • spreadsheets
  • business software
  • hiking
  • mechanical keyboards

Media habits

  • Skims GitHub activity feeds daily
  • Reads niche technical newsletters (e.g., Hacker News, TLDR)
  • Uses LinkedIn primarily for industry networking
  • Avoids TikTok/Instagram Reels unless required for work
  • Listens to productivity podcasts during commutes
  • Checks Meta Business Suite manually for post status

Questions & answers

Cary Kiehn’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying MarketMee (https://marketmee.app/) 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 core issue is the manual effort involved in translating commits into release notes. Today, I copy GitHub pushes into a spreadsheet for our part-time marketer, and sometimes I schedule the posts myself. The idea of automating this is appealing, especially if it can read the commits directly and generate content. However, I'm concerned about the accuracy and the need for approval before publishing. My process involves careful review, and I'd need to ensure this tool doesn't just push out unvetted content. The description mentions "review and approve," which is good, but I'd need to understand the workflow precisely. I'd be willing to pay $30 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.