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

Rickey Harris

Rickey Harris

solo no-code maker using free tools and spreadsheets

Full-depth AI personas

Why this persona fits the audience

Solo no-code maker in Denver building a side SaaS for agencies. He has never paid for a launch tool and manages directory submissions in Google Sheets, while using free Stripe fee calculators to test pricing against plan changes.

  • Age: 27
  • Location: Denver, Colorado, USA
  • Occupation: Support engineer and side-project founder
  • Income: US$78k from day job; side project revenue small
  • Education: Some college, mostly self-taught
  • Company size: 1 (self)
  • Years in role: 3
“I'd rather spend an hour figuring out how to do something for free than pay ten bucks for a tool that does it for me, especially when I can learn something new in the process.”

Rickey Harris, a 27-year-old support engineer living in Denver, embodies the modern self-taught maker driven by a potent blend of curiosity and fiscal prudence. His journey into no-code development wasn't a planned career shift but an organic evolution stemming from a desire to solve problems efficiently and affordably. While holding down a demanding full-time role that pays him US$78k annually, Rickey dedicates his evenings and weekends to building and refining a niche SaaS product aimed at agencies. His approach is characterized by an almost militant adherence to free tools and open-source solutions. He meticulously manages his SaaS launch strategy using a detailed Google Sheet, tracking directory submissions and outreach efforts, a testament to his methodical nature. Pricing his own product is an ongoing experiment; he relies on free Stripe fee calculators to model various scenarios, meticulously testing how different plan structures impact potential revenue against processing costs. This hands-on, experimental approach is central to his philosophy of 'learning by doing.' He has never paid for a dedicated launch or marketing tool, preferring to leverage community platforms and organic growth strategies. His education is a patchwork of college courses and extensive self-teaching, fueled by an insatiable appetite for knowledge acquired through YouTube, blogs, and community forums. Rickey is not motivated by status or rapid wealth accumulation, but by the intrinsic satisfaction of building something functional and scalable, and the long-term goal of achieving financial independence through smart, sustainable ventures. His current focus is on validating his SaaS idea and iterating based on early user feedback, all while maintaining his day job and a disciplined personal budget. He sees his side project not just as a potential income stream, but as a continuous learning laboratory for entrepreneurship, technology, and strategic pricing.

Background & daily life

A day in their life

Rickey's weekday typically begins around 6:30 AM with a quick yoga session or a run, followed by breakfast and reviewing his personal project's analytics. He then heads to his remote support engineering job, where he spends his day responding to tickets, documenting solutions, and attending team syncs. Lunch is usually a quick, home-prepared meal. After his workday ends around 5:00 PM, he dedicates at least two to three hours to his SaaS project. This involves building new features, updating his directory submission spreadsheet, testing pricing models with free calculators, engaging with his online community, and planning future development. He winds down by reading tech blogs or listening to podcasts before bed.

Lifestyle

Rickey lives in a modest apartment in Denver, embracing a minimalist lifestyle that reflects his disciplined approach to budgeting. He enjoys cooking simple meals, often experimenting with new recipes he finds online. Fitness is a regular part of his routine, with morning runs and evening yoga sessions helping him maintain balance. He prioritizes experiences over material possessions, saving diligently for future travel or investments. His social life is centered around a small group of close friends and online maker communities, preferring quality interactions over large gatherings.

Work life

As a support engineer for a mid-sized SaaS company, Rickey spends his days troubleshooting technical issues for clients, often dealing with complex integrations and user errors. His work requires meticulous attention to detail and a calm demeanor under pressure. He collaborates with a small, distributed team, relying heavily on Slack and Jira for communication and task management. The pressure to resolve tickets efficiently is constant, but he finds satisfaction in finding elegant solutions. His evenings and weekends are dedicated to his own no-code SaaS venture, where he wears all hats: developer, marketer, and customer support.

Relationships

Rickey maintains a close-knit circle of friends, mostly met through college or online communities, who share his passion for technology and side projects. His parents are supportive but don't fully grasp the intricacies of his entrepreneurial pursuits. He actively participates in Denver's tech meetups and online forums, valuing the advice and camaraderie of fellow makers.

How they decide

Rickey is a highly analytical and research-driven decision-maker, especially when it comes to his side project. He meticulously compares free options, reads reviews, and often runs small experiments or simulations before committing to a particular approach or tool. He values data and evidence, preferring to understand the underlying mechanics before making a choice. He is not easily swayed by hype and is deeply skeptical of anything that seems too good to be true, especially if it involves significant upfront cost.

How they sound

Rickey speaks with a clear, measured cadence, often pausing to formulate his thoughts precisely. He uses technical jargon naturally when discussing his work or projects but is adept at explaining complex concepts in simpler terms. He avoids overly casual slang but isn't afraid of using common tech abbreviations. He tends to be direct and factual, rarely engaging in hyperbole or emotional appeals. He often uses phrases like 'essentially,' 'the core of it is,' or 'what I've found is' when explaining his process.

Personality traits

  • resourceful
  • methodical
  • analytical
  • tenacious
  • budget-conscious
  • collaborative
  • introspective
  • solution-oriented

Goals

  • Achieve sustainable passive income from his side project.
  • Build a robust, scalable no-code application.
  • Contribute meaningfully to open-source no-code projects.
  • Achieve financial independence within ten years.
  • Develop expertise in product pricing strategies.

Problems & frictions

  • Limited time due to his full-time job.
  • Balancing the need for advanced features with the constraints of no-code tools.
  • The constant learning curve of new no-code platforms and integrations.
  • Finding reliable, cost-effective ways to market his side project.
  • Managing the administrative overhead of a solo business without paid tools.

Values

  • experimentation
  • budget discipline
  • learning by doing
  • community involvement
  • sustainability

Interests

  • no-code
  • maker communities
  • pricing tests
  • open-source projects
  • DIY tech
  • financial independence

Media habits

  • YouTube tutorials
  • Reddit maker communities
  • Podcasts about side hustles
  • Tech blogs
  • Newsletters on no-code tools
  • Community forums

Questions & answers

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

  1. What would stop you from trying List My SaaS (https://listmysaas.com/) 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 main thing that would stop me is that I'm already managing directory submissions manually in a Google Sheet. While the 'Launch Done for You' service saving time is tempting, especially given my limited hours, I'm hesitant to pay for something I'm already doing myself, even if it's more efficiently handled. I also haven't seen concrete proof of the "100K+ traffic" or the actual impact on my SaaS's visibility. I'd need to see more data to justify the cost. I would be willing to pay $30 per month for a comprehensive tool that automates this process, but not for a one-off service.
    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.