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

Kerry Kreiger

Kerry Kreiger

indie SaaS founder managing AI-assisted product workflows

Full-depth AI personas

Why this persona fits the audience

Runs a one-person SaaS in Austin and uses Claude, GPT, and a few automation tools to draft support replies, write onboarding copy, and test internal prompts. He regularly estimates token spend for low-volume production calls and for short bursts of experimentation before sharing budgets with a contractor.

  • Age: 34
  • Location: Austin, Texas, US
  • Occupation: Indie SaaS founder
  • Income: $160k draw equivalent, variable
  • Education: B.S. Computer Science
  • Company size: 1
  • Years in role: 4
“The goal isn't to build the most complex system, it's to build the one that reliably solves a problem and doesn't break the bank.”

Kerry Kreiger, 34, embodies the modern indie SaaS founder, navigating the lean startup landscape from his base in Austin, Texas. Armed with a B.S. in Computer Science, he carved out his niche by building a one-person software company focused on streamlining AI workflows. His early career involved several stints at larger tech firms, where he grew disillusioned with bureaucratic slowdowns and the perceived inefficiency of large teams. He craved the autonomy and direct impact of building something himself. This led him to strike out on his own four years ago, initially bootstrapping with personal savings and a fierce commitment to self-reliance. He established his current SaaS product, which offers tools to help developers and businesses better manage and optimize their use of AI models, particularly focusing on cost and efficiency. His core philosophy revolves around shipping quickly and maintaining financial clarity, tenets that directly influence his operational decisions. He's particularly adept at integrating and leveraging AI tools like Claude and GPT to augment his solo capabilities, using them for everything from drafting support replies and onboarding copy to testing internal prompts and refining marketing materials. This reliance on AI is balanced by a pragmatic approach to budgeting; he meticulously tracks API usage, often creating detailed spreadsheets to estimate token expenditure for both low-volume production needs and experimental bursts before allocating funds to his occasional contractor. This past quarter, he made a conscious decision to invest in a more robust prompt engineering framework, recognizing it as a critical bottleneck for scaling his AI-driven features, a move that involved significant upfront time investment but promised long-term efficiency gains. He views money as a resource to be managed prudently, ensuring his $160k annual draw is sustainable and allows for reinvestment in the business. His relationship with time is one of deliberate allocation, prioritizing tasks that directly contribute to product value or operational efficiency, and consciously carving out time for learning and strategic thinking.

Background & daily life

A day in their life

Kerry's weekday begins around 6:30 AM with coffee and a review of overnight system alerts and customer support tickets. He dedicates the early morning to deep work, coding or refining core product features. By 9 AM, he’s engaging with his AI tools, drafting email responses, iterating on onboarding flows, or running prompt tests for new marketing copy. Lunch is usually a quick, healthy meal he prepared at home. The afternoon involves more tactical tasks: responding to complex support issues, analyzing usage metrics, planning the next sprint, and meticulously tracking his AI token spend for the week. He often logs off around 7 PM, though he might check in again later if a critical issue arises.

Lifestyle

Kerry lives in a modest but well-organized condo in South Austin, preferring proximity to his co-working space and good coffee shops over expansive living. He's a creature of habit, waking early to tackle his most demanding tasks before the AI tools are fully engaged for the day. His social life is a mix of occasional meetups with fellow founders and quiet nights spent tinkering or reading. He's diligent about tracking his personal burn rate, ensuring his draw keeps pace with his business's fluctuating revenue, and often cooks simple, healthy meals to save money and time.

Work life

As a solo founder, Kerry's workday is a constant juggling act between product development, customer support, marketing, and financial management. He leverages Claude and GPT extensively for tasks like drafting initial versions of blog posts, generating customer support responses, and refining onboarding copy. He meticulously tracks API usage, creating spreadsheets to estimate token spend for different AI models and prompt complexities, especially before onboarding new features or running experimental campaigns. He recently contracted a freelance developer for a complex integration, carefully vetting their proposals and budget before signing off.

Relationships

Kerry is single and lives alone, but maintains a strong, albeit geographically distant, relationship with his parents back in Michigan. His closest professional connections are online, through founder communities on Discord and Twitter. He occasionally meets up with a few other Austin-based indie hackers for coffee or coworking sessions, valuing their shared experiences and pragmatic advice.

How they decide

Kerry approaches decisions methodically. He gathers data, runs small-scale tests or simulations (often using AI for analysis), and weighs the pros and cons against his core values of efficiency and financial prudence before committing. He's not impulsive but also avoids analysis paralysis by setting clear deadlines for his decision-making process.

How they sound

Speaks with a clear, measured cadence, often using precise technical language but capable of simplifying when explaining concepts to less technical individuals. He avoids hyperbole and overly casual slang, preferring directness. His tone is generally calm and rational, even when discussing challenges. He tends to use phrases like 'essentially,' 'from a practical standpoint,' and 'it boils down to.'

Personality traits

  • Analytical
  • Resourceful
  • Detail-oriented
  • Independent
  • Forward-thinking
  • Methodical
  • Pragmatic
  • Focused

Goals

  • Achieve sustainable MRR growth to $50k without external funding.
  • Develop a robust internal knowledge base for AI prompt optimization.
  • Automate 80% of customer support inquiries within the next year.
  • Build a small, curated community around his product's niche.
  • Maintain a healthy work-life balance, dedicating weekends to personal projects and relaxation.

Problems & frictions

  • Managing AI API costs without sacrificing performance or features.
  • The ever-present risk of vendor lock-in with AI providers.
  • Finding reliable, cost-effective external help for specialized tasks.
  • Balancing rapid feature development with the need for robust testing.
  • The mental overhead of being solely responsible for every business function.

Values

  • shipping quickly
  • financial clarity
  • pragmatism
  • self-reliance
  • efficiency

Interests

  • AI product tooling
  • startup metrics
  • indie software
  • systems design
  • prompt engineering

Media habits

  • Podcasts on AI and startups (e.g., Lex Fridman, Acquired)
  • Hacker News, Reddit (r/SaaS, r/artificialintelligence)
  • Tech newsletters (e.g., TLDR, Exponential View)
  • YouTube for tool reviews and tutorials
  • Twitter for developer/founder discourse

Questions & answers

Kerry Kreiger’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Claude Effort Calculator (https://claudeeffort.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Claude Effort Calculator 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).

    Right now, I'm essentially using spreadsheets to track my token spend. I manually input estimated token counts for different tasks and models, then calculate potential costs. It's tedious, but it works. What would make a tool like this better is if it could somehow integrate directly with my API usage logs, or at least offer more granular predictive analysis beyond just effort levels, perhaps factoring in prompt complexity. As is, it feels like a slightly more automated version of what I'm already doing. I wouldn't pay for this; I'd stick with my spreadsheets for now.
    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.