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

Cory Kemmer

Cory Kemmer

Solo indie SaaS founder shipping from a side project

Full-depth AI personas

Why this persona fits the audience

He is currently building and launching a one-person micro-SaaS from home, posting product updates, collecting early user feedback, and coordinating launch tasks with a spreadsheet, a notes app, and email. He has never paid for a launch-specific tool and handles outreach manually.

  • Age: 31
  • Location: Austin, Texas, US
  • Occupation: Independent software founder
  • Income: $110k USD/year
  • Education: BS in Computer Science
  • Company size: 1 (himself)
  • Years in role: 3 years
“I'd rather spend my time building something that works for a few people than talking about something that might work for many.”

Cory Kemmer, 31, is a solo founder operating from his apartment in Austin, Texas, a testament to his deep-seated drive for autonomy and his knack for problem-solving. Holding a BS in Computer Science from a state university, he spent several years as a diligent software engineer at a mid-sized tech firm, earning a solid income of $110k. This period provided him with both technical expertise and the financial runway to pursue his true passion: building and launching independent software products on the side. His current venture is a micro-SaaS aimed at streamlining product launches for creators, a project born from his own frustrations with existing workflows. He meticulously manages his launch activities using a spreadsheet for task tracking, a notes app for ideation, and email for outreach, deliberately avoiding paid launch tools to maintain lean operations and validate his resourcefulness. Cory's decision to go solo reflects a core value of independence; he thrives on the challenge of building something from the ground up and learning directly from his users. His conscientiousness is evident in his structured approach to work, while his moderate extraversion means he engages with the indie hacking community online but isn't one for large networking events. He views his income not just as a living wage but as a strategic asset, enabling him to invest time and a small amount of capital into his ventures without the pressure of immediate revenue. His recent decision to dedicate specific blocks of time each day to customer feedback analysis, even when it conflicts with feature development, underscores his commitment to customer learning. He is constantly evaluating his processes, seeking to optimize for speed of execution while ensuring a deep understanding of user needs before iterating.

Background & daily life

A day in their life

Cory's weekdays typically start around 6:30 AM. After a quick breakfast and scanning Hacker News, he dedicates two hours to focused work on his micro-SaaS – coding new features or refining the user onboarding flow. By 9 AM, he transitions to his remote software engineering job, attending meetings and completing tasks until about 5:30 PM. Evenings are split between dinner, a short break, and then more SaaS work: analyzing user feedback from his spreadsheet, drafting a product update for his mailing list, manually reaching out to potential beta users via email, and planning the next sprint. He might spend an hour learning a new automation tool or reading an indie hacking newsletter before winding down around 11 PM.

Lifestyle

Cory lives a relatively spartan but comfortable life in Austin, focused on maximizing his time and resources for his entrepreneurial pursuits. His $110k income as a software engineer from his previous role allows him to fund his SaaS experiments without immediate financial pressure, though he's mindful of burn rate. He rents a modest one-bedroom apartment, prioritizing location and quiet over amenities. His routine involves early mornings for focused work before his day job, then more SaaS development and community engagement in the evenings. He enjoys occasional craft beer outings with a couple of close friends but generally prefers quiet nights in, reading tech blogs or experimenting with new tools. He tracks his expenses meticulously, seeing frugality as a strategic advantage.

Work life

As a solo founder, Cory's work life is intensely self-directed. He's currently neck-deep in launching his latest micro-SaaS, a curated platform for independent creators. His 'office' is a corner of his living room, dominated by a powerful workstation. His primary tools are a robust spreadsheet for tracking launch tasks and user feedback, a digital notebook for feature ideas, and a well-organized email client for outreach. He spends his days coding features, writing blog posts about his progress, responding to early user inquiries, and meticulously planning his next steps. The pressure comes from the desire to validate his product quickly and the constant internal drive for improvement, with no coworkers to delegate to or bounce ideas off of.

Relationships

Cory maintains a small but close circle of friends, mostly former colleagues from his previous tech job. They understand the pressures of the industry and offer occasional, valuable sounding boards. His family, while supportive, doesn't fully grasp the intricacies of indie hacking. He's not actively seeking romantic relationships currently, as his focus is on his ventures. He primarily influences himself, driven by his own vision and metrics.

How they decide

Cory is a highly analytical and research-driven decision-maker. He meticulously weighs pros and cons, often creating flowcharts or comparison tables in his notes. He's influenced by data and tangible evidence, preferring to test hypotheses himself rather than relying solely on others' opinions. While he values speed, he won't rush into decisions without a solid understanding of the potential outcomes and downsides, especially when it involves resource allocation, even if those resources are just his time.

How they sound

Cory speaks with a clear, measured cadence, devoid of excessive jargon but comfortable with technical terms. He's generally polite and professional, even in informal settings. He avoids overly effusive language or hype, preferring concrete descriptions and data points. You won't hear him making grand pronouncements; instead, he'll frame things in terms of 'what I'm seeing,' 'the data suggests,' or 'my current hypothesis.' He's not afraid to admit when he doesn't know something but will quickly follow up with how he plans to find out.

Personality traits

  • Driven
  • Analytical
  • Resourceful
  • Focused
  • Skeptical of hype
  • Self-reliant
  • Curious
  • Pragmatic

Goals

  • Achieve product-market fit for his current micro-SaaS venture
  • Build a sustainable, profitable business that allows for full-time founder status
  • Develop a repeatable process for launching and growing future software products
  • Continuously learn and master new technologies and marketing strategies
  • Maintain financial independence and the flexibility to pursue passion projects

Problems & frictions

  • Balancing the demands of his main job with his side project
  • Finding efficient ways to reach and engage early adopters without a marketing budget
  • Managing all aspects of the business (development, marketing, support) alone
  • Overcoming the inertia of manual processes for tasks like launch coordination
  • Sifting through noise to identify genuinely valuable user feedback
  • The sheer time commitment required for every aspect of building a SaaS

Values

  • independence
  • speed of execution
  • customer learning
  • autonomy
  • problem-solving

Interests

  • micro-SaaS
  • product analytics
  • indie hacking
  • automation tools
  • API integrations
  • creator economy

Media habits

  • Substack newsletters (especially those focused on indie hacking)
  • TechCrunch and Hacker News for industry trends
  • YouTube channels on SaaS growth and development
  • Podcasts like 'Acquired' and 'Indie Hackers'
  • Twitter for real-time discussions and networking

Questions & answers

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

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

    Right now, what would stop me is the uncertainty of the "reach builders every week" claim. My current process involves manually reaching out to potential users via email and tracking their feedback in a spreadsheet, which is time-consuming but I know it works. I'd need to see some data or a clearer explanation of how Buildrship guarantees actual builders will see my product before committing. Given that I'm still validating my micro-SaaS and keeping costs extremely lean, I'd be hesitant to spend more than $0 on a new launch platform at this stage.
    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.