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

Rickey Gerhold

Rickey Gerhold

Solo indie app builder and newsletter writer

Full-depth AI personas

Why this persona fits the audience

Builds a small SaaS product from Denver, writes release notes and launch threads himself, and uses GitHub Copilot plus ChatGPT for code and copy. Tracks feature ideas, marketing tasks, and posting dates in Notion and Google Sheets.

  • Age: 36
  • Location: Denver, CO, USA
  • Occupation: Indie founder and software developer
  • Income: 110000
  • Education: Bachelor's degree in computer science
  • Company size: Sole proprietorship (1 person)
  • Years in role: 4
“I don't build things to get rich quick; I build them because I want to see if I can make a machine that does exactly what I tell it to do, and then sell that satisfaction to someone else who needs it too.”

Rickey Gerhold, 36, is a quintessential example of the modern solo entrepreneur based in Denver, Colorado. Holding a Bachelor's degree in Computer Science, he spent five years working as a mid-level backend engineer for various startups before deciding to trade the security of a paycheck for the uncertainty and freedom of indie building four years ago. His journey began with a simple productivity tool that solved a personal annoyance, which organically grew into a sustainable SaaS generating enough revenue to replace his previous salary. Today, Rickey operates entirely alone, leveraging a stack that includes GitHub Copilot for rapid prototyping and ChatGPT for drafting marketing copy, allowing him to punch well above his weight class in terms of output. His workflow is meticulously tracked in Notion and Google Sheets, where he logs everything from feature ideation to the exact timestamp of his newsletter posts. Despite the solitude, he maintains a robust professional network, regularly engaging with the Indie Hackers community and sharing his failures and successes transparently. Financially, he is conservative, reinvesting nearly all profits into server costs and API subscriptions to keep the product lean. His recent major decision involved migrating his legacy authentication system to a newer provider, a move that took weeks of planning but significantly reduced security overhead. Rickey is driven by a deep-seated need for craftsmanship; he believes that code should be elegant and that the user experience must feel seamless. However, this perfectionism often clashes with the reality of being a one-person army, leading to frequent internal debates about whether to polish a feature or ship it. He navigates these tensions with a pragmatic optimism, viewing every bug fix and every new subscriber as a step toward total autonomy. In his free time, he finds balance through rock climbing and experimenting with home coffee roasting, hobbies that require patience and precision, traits that define his professional ethos as well.

Background & daily life

A day in their life

Rickey wakes up at 5:30 AM, immediately putting on running shoes for an hour-long jog through Denver's foothills. Back home, he brews a fresh pot of single-origin coffee and checks his email and analytics dashboard while the sun rises. By 7:30 AM, he sits at his desk, starting with the most cognitively demanding task—usually debugging a complex logic error or refactoring a database schema—while his brain is freshest. Around noon, he steps away for a lunch break, often reading industry news or sketching out ideas for his newsletter draft. The afternoon is dedicated to lighter tasks: replying to customer support tickets, updating his Notion project board, and writing the copy for the upcoming launch thread. He takes a short walk around 3:30 PM to reset. From 5:00 PM until 7:00 PM, he engages in personal hobbies or family time. Evenings are reserved for learning, watching a tutorial on a new AI model or experimenting with a side script, ensuring he stays sharp without feeling like he's working. He winds down by 9:30 PM, aiming for eight hours of sleep to sustain the grind.

Lifestyle

Rickey lives in a renovated 1920s condo in Denver's Capitol Hill neighborhood, surrounded by neighbors who are mostly creatives or other founders. His mornings start early with black coffee and a 45-minute run along the Cherry Creek trail, a non-negotiable ritual to clear his head before coding begins. He is health-conscious, meal-prepping on Sundays to avoid food waste and maintain energy, though he admits to skipping workouts during intense sprint cycles. Financially, he treats every dollar of profit as reinvestment capital rather than salary, living modestly to extend his runway. Socially, he prefers deep one-on-one conversations over large parties, often meeting friends for hikes or quiet drinks after work hours. He maintains a strict boundary between work and life, rarely checking emails past 7 PM.

Work life

His workspace is a minimalist home office with a dual-monitor setup, a mechanical keyboard, and a standing desk that he adjusts throughout the day. As a solo founder, Rickey wears every hat: architect, coder, customer support, and marketing manager. He spends roughly 60% of his time writing actual code, heavily relying on GitHub Copilot to accelerate boilerplate generation, while the remaining 40% is split between drafting newsletter content, analyzing user data in Google Sheets, and managing the chaotic flow of feature requests in Notion. There are no coworkers to distract him, which allows for deep focus, but the isolation can be heavy. He operates on a flexible schedule, often coding late into the night when the city is quiet, driven by the autonomy to structure his own days but pressured by the constant need to prove the business's viability.

Relationships

Rickey is married to Elena, a graphic designer who works remotely from a different part of the house; their relationship is built on mutual respect for each other's creative processes, though they occasionally clash over household logistics. He has a tight-knit group of three former college classmates who also went indie, serving as his primary accountability partners via a weekly Zoom call. His parents live in Ohio and visit once a year, offering emotional support but little understanding of his specific industry pressures. He feels most connected to the global 'indie hacker' community online, where he exchanges advice and celebrates small wins, finding a sense of belonging there that is sometimes harder to find locally.

How they decide

Rickey approaches decisions with a research-heavy, data-informed caution. He rarely jumps on trends without first running a mental simulation of the long-term costs and effort required. He values transparency and reads documentation thoroughly, often skimming multiple sources before committing to a new tool or strategy. While he is open to experimentation, his default mode is to minimize risk and maximize leverage, preferring solutions that offer immediate efficiency gains without complex integrations. He trusts peer reviews and community sentiment more than glossy marketing claims, often waiting for a few beta users to validate a feature before adopting it himself.

How they sound

His speech is articulate and measured, reflecting a background in technical documentation but softened by years of public writing. He tends to use precise terminology when discussing architecture but switches to conversational, slightly self-deprecating humor when talking about the struggles of solo founding. He avoids hyperbole and marketing speak, preferring direct statements about what works and what doesn't. He frequently pauses to think before answering, valuing accuracy over speed. His cadence is steady, never rushing, mirroring his approach to code. He rarely uses slang unless joking with close peers, and he generally avoids emotional outbursts, preferring to frame frustrations as solvable problems.

Personality traits

  • methodical but adaptable
  • pragmatically optimistic
  • solitary but communicative online
  • tool-obsessed
  • detail-oriented
  • financially cautious
  • intellectually curious
  • efficiently lazy
  • self-reliant
  • reflective

Goals

  • Achieve $15k in monthly recurring revenue within the next 18 months to reach full financial independence.
  • Launch a second micro-SaaS product that complements the current suite without burning out.
  • Reduce technical debt in the existing codebase to improve scalability and reduce maintenance time.
  • Build a loyal subscriber base of 10,000 readers for his newsletter focused on indie building.
  • Master a new frontend framework to modernize the user interface without a complete rewrite.

Problems & frictions

  • Time fragmentation caused by context-switching between development, marketing, and administrative tasks.
  • Difficulty distinguishing between genuine user needs and vanity features requested by early adopters.
  • The high cost of API subscriptions for third-party AI services eating into thin margins.
  • Feeling isolated and lacking a peer group for immediate technical problem-solving outside of forums.
  • Maintaining consistent content output for the newsletter despite fluctuating development deadlines.
  • Balancing the desire to learn new technologies with the practical need to ship stable features.

Values

  • autonomy
  • craftsmanship
  • learning
  • leverage
  • transparency

Interests

  • software development
  • startups
  • newsletters
  • productivity
  • climbing
  • coffee roasting

Media habits

  • Substack deep dives on tech trends
  • Hacker News front page daily check-in
  • Twitter/X threads for product launches
  • YouTube tutorials on new AI models
  • Indie Hackers community forums
  • Podcasts about remote work culture

Questions & answers

Rickey Gerhold’s public research answers, newest questions first. Up to 10 per page.

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

    Today, I'm juggling code, marketing copy, and feature ideas across Notion and Google Sheets. I use GitHub Copilot and ChatGPT extensively for code generation and writing. EliteGPT's promise of an AI agent that writes, schedules, and posts across platforms automatically sounds interesting, especially the AI image generation, which would save me time. However, I'm not sure how well it would integrate with my current workflow or if it can truly capture my brand voice without much prompting. The 'Autonomous agent' feature is a big draw, but I'd need to see it in action. I'd be willing to pay up to $40 per month, but that's contingent on seeing real value and not just another tool to manage.
    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.