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

Rick Gutkowski

Rick Gutkowski

early-stage solo founder who has never paid for a boilerplate

Full-depth AI personas

Why this persona fits the audience

He is a Denver-based solo founder building a niche CRM for small service businesses, and so far every prototype has been assembled from open-source templates, manual Stripe links, and ad hoc scripts without paying for a commercial SaaS starter.

  • Age: 34
  • Location: Denver, CO, USA
  • Occupation: solo founder and solutions developer
  • Income: $118k
  • Education: Self-taught with a bootcamp certificate
  • Company size: 1 (himself)
  • Years in role: 3
““If you can’t build it yourself with what’s already free, you probably don’t understand it well enough yet.””

Rick Gutkowski, 34, is a Denver-based solo founder and solutions developer who embodies the spirit of lean, self-sufficient entrepreneurship. His journey into tech wasn't a traditional one; after a stint in a field unrelated to software, he discovered a passion for problem-solving through code, culminating in a certificate from a coding bootcamp. This experience solidified his belief in continuous learning and self-reliance. He founded his current venture, a niche CRM tailored for small service businesses, driven by a personal frustration with existing solutions that were either too complex, too expensive, or didn't fit his specific vision. Rick's defining characteristic is his unwavering commitment to frugality and resourcefulness. He has never paid for a commercial SaaS boilerplate or starter kit. Instead, he meticulously assembles his product's foundation from open-source templates, custom-written scripts, and manual integrations like Stripe payment links. This approach, while time-consuming, aligns perfectly with his value of independence and his desire to maintain absolute control over his technology stack and burn rate. His income of $118k, likely a mix of previous savings, freelance work, and early, non-dilutive revenue, is carefully managed, with a significant portion being reinvested or held as a buffer. He views time spent learning and building as an investment, not a cost. Rick’s recent decisions have centered on iterating on his core CRM features based on feedback from a handful of early adopters, while simultaneously exploring ways to automate user onboarding and support processes using serverless functions and open-source tools. He’s currently wrestling with optimizing database performance as his user base slowly grows, a challenge he’s tackling by diving deep into PostgreSQL indexing strategies rather than immediately considering a paid database service.

Background & daily life

A day in their life

Rick's day typically begins around 6:00 AM with a 5-mile run, listening to a tech podcast. He's back home by 7:00 AM, makes coffee, and reviews overnight system logs and any urgent messages. From 7:30 AM to noon, he dives deep into coding, tackling bugs, implementing new features, or refining existing scripts for his CRM. Lunch is a quick, home-prepared meal eaten at his desk around 12:30 PM. The afternoon, from 1:00 PM to 5:00 PM, is dedicated to less intensive tasks: responding to user feedback, researching new open-source libraries, updating documentation, or planning the next development sprint. He might spend an hour between 5:00 PM and 6:00 PM reviewing SaaS newsletters or Hacker News. Evenings are for dinner, a bit of relaxation (perhaps reading a tech blog or watching a documentary), and then often another hour or two of work before winding down around 10:00 PM.

Lifestyle

Rick lives a focused, almost spartan existence in a modest Denver apartment, prioritizing his startup above most else. His income allows for comfort but not extravagance; he meticulously tracks expenses, viewing every dollar saved as a dollar that can be reinvested or used to extend runway. His routine is regimented: early morning runs to clear his head, followed by long hours coding and strategizing. Social life is minimal, often revolving around online communities or occasional meetups with fellow tech enthusiasts. He cooks most meals at home, finding satisfaction in self-sufficiency and avoiding unnecessary costs.

Work life

As a solo founder and developer, Rick's work life is all-consuming. He's the architect, coder, marketer, and support team for his niche CRM. His current focus is on refining the core functionality, which he's built entirely using open-source components and custom scripts. He spends his days wrestling with integration challenges, optimizing database queries, and manually setting up payment links for early testers. The pressure is immense, stemming from his own high standards and the need to prove his concept's viability without external funding. Coworkers are non-existent; his only collaborators are the open-source communities he taps into.

Relationships

Rick maintains a small circle of close friends, mostly met during his bootcamp or through online tech communities. They offer a sounding board for ideas and a dose of camaraderie. His family lives out of state and he communicates with them sporadically, prioritizing his work. He doesn't have a mentor but follows several prominent indie hackers and developers online whose journeys he respects.

How they decide

Rick is highly analytical and research-driven. He meticulously weighs pros and cons, often creating spreadsheets or flowcharts to visualize options. He prioritizes long-term value and efficiency over immediate convenience, and is deeply skeptical of anything that seems like a shortcut or over-hyped solution. He trusts data and demonstrable results, preferring to test things himself before committing.

How they sound

Speaks clearly and deliberately, with a measured pace. Tends to be precise and avoids hyperbole or overly casual slang. Uses technical terms naturally but can explain complex concepts in simpler terms when necessary. His tone is generally calm and rational, even when discussing challenges. He often pauses to formulate his thoughts, ensuring accuracy.

Personality traits

  • resourceful
  • analytical
  • driven
  • detail-oriented
  • pragmatic
  • independent
  • patient
  • methodical
  • skeptical of hype

Goals

  • Achieve product-market fit for his CRM
  • Build a sustainable, profitable business without external investment
  • Continuously improve his technical skills
  • Automate as much of his business operations as possible
  • Maintain financial independence and control over his venture

Problems & frictions

  • Balancing feature development with essential business tasks
  • The inherent limitations and maintenance overhead of custom-built solutions
  • Finding time for marketing and customer acquisition amidst development
  • The mental toll of solo entrepreneurship and constant problem-solving
  • Scaling infrastructure reliably without incurring significant costs
  • The difficulty of predicting user needs accurately

Values

  • frugality
  • learning
  • independence
  • usefulness
  • efficiency

Interests

  • open source
  • SaaS newsletters
  • automation
  • running
  • indie hacking
  • developer tools

Media habits

  • Reads Hacker News daily
  • Subscribes to several SaaS and indie hacking newsletters
  • Listens to tech podcasts during runs
  • Watches YouTube tutorials on coding and business
  • Follows niche developers on Twitter/X

Questions & answers

Rick Gutkowski’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://zerodrag.cloud/ (ZeroDrag) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core idea of skipping the boilerplate is appealing. It claims to save 35+ hours, which is a significant chunk of time I could spend on my CRM's unique features. What's unclear is the extent of customization possible without it feeling like I'm fighting the boilerplate itself. The "dogfooded in production" claim is good, but I'd need to see the codebase to be sure. The "Pro" features like AI integrations and Sentry sound useful, but I'd need to understand their necessity for my current stage. I'd sign up if I could see a clear path to tailoring it to my specific needs and if the "zero lock-in" promise holds up under scrutiny, especially regarding switching providers. The 50% off launch offer is tempting, but I'd need to evaluate the Starter price first.
    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.