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

Stewart O'Keefe

Stewart O'Keefe

Solo Rails indie founder

Full-depth AI personas

Why this persona fits the audience

He is building a bootstrapped AI scheduling SaaS on nights and weekends in Rails, with Stripe, auth, and a small admin dashboard already in scope. He has never paid for a Rails boilerplate before and usually starts from `rails new`, copied snippets, and a checklist he keeps in Notion.

  • Age: 31
  • Location: Austin, TX, USA
  • Occupation: Freelance Ruby on Rails developer
  • Income: $145k total from freelance work
  • Education: BS Computer Science
  • Company size: 1 (self-employed)
  • Years in role: 8
“I'd rather spend an hour figuring out how to automate a task once than spend five minutes doing it manually every day for the next year.”

Stewart O'Keefe, 31, is a seasoned freelance Ruby on Rails developer based in Austin, Texas. Holding a BS in Computer Science, he carved out a niche for himself over the past eight years, building a steady freelance income that allows him significant autonomy. His income, around $145k annually, is derived entirely from client projects, enabling him to avoid the financial pressures that might force him into less desirable work. Stewart embodies a self-reliant, methodical approach to his craft. He's never felt the need to purchase pre-built Rails templates, preferring the foundational understanding gained from starting projects from scratch with `rails new`, supplementing with judiciously selected code snippets, and meticulously organizing his workflow within Notion. This practice reflects his value of independence and clean architecture, ensuring he deeply understands every line of code he writes. Currently, his entrepreneurial drive is channeled into a bootstrapped AI scheduling SaaS, a project he dedicates his nights and weekends to. This venture, built using Rails, incorporates essentials like Stripe for payments and authentication, along with a functional admin dashboard. His decision to build this himself stems from a desire to ship quickly and create something tangible that addresses a need he, and potentially others in the indie hacking community, experience. He sees the value in AI automation and is keen to integrate it effectively, viewing his personal project as both a learning opportunity and a potential source of steady cash flow. Stewart is not motivated by status or external validation; his primary drivers are mastery of his skills, the satisfaction of building something functional, and the freedom to pursue his own ideas without seeking external funding or approvals. His financial habits are conservative, prioritizing reinvestment in his tools and knowledge over discretionary spending, a strategy that supports his long-term goal of building sustainable, independent income streams.

Background & daily life

A day in their life

Stewart's weekday typically begins around 7:30 AM with a strong pour-over coffee and a quick scan of Hacker News. He dedicates the next few hours to his freelance client work, tackling complex coding tasks and attending virtual stand-ups. Lunch is usually a quick, healthy meal prepared at home. The afternoon involves more client-focused development and communication. Around 6:00 PM, he shifts gears to his AI scheduling SaaS. This 'second shift' involves coding new features, refining the database schema, or experimenting with AI API integrations. He might pause for a brief workout or a walk around his neighborhood before returning to his project until 10:00 PM, often ending the day by reviewing his Notion task list for the next day.

Lifestyle

Stewart lives a focused life in his Austin apartment, where his living room doubles as his workspace. He prioritizes his freelance work to maintain a comfortable income, averaging about $145k annually. Evenings and weekends are dedicated to his AI scheduling SaaS project, fueled by strong coffee and a deep-seated desire for autonomy. He's not a big spender, preferring to invest in tools that enhance productivity and save him time rather than luxury goods. His social life is relatively quiet, centered around occasional meetups with fellow developers or low-key evenings at home.

Work life

As a freelance Ruby on Rails developer, Stewart's days are a mix of client projects and his personal SaaS venture. He thrives on the independence, setting his own hours and choosing his clients. His current client work involves a complex e-commerce integration, demanding careful attention to detail and robust solutions. Simultaneously, he's pushing his AI scheduling app forward, meticulously adding features like Stripe integration and a basic admin dashboard. The pressure comes from balancing client deadlines with his entrepreneurial ambitions, constantly optimizing his workflow to maximize output without sacrificing code quality. Coworkers are usually remote client teams or occasional collaborators on open-source projects.

Relationships

Stewart maintains a close relationship with his parents, who live in Florida and support his entrepreneurial spirit. His primary social circle consists of a few long-time college friends who are also in tech, offering a reliable sounding board for technical and career challenges. He occasionally interacts with other indie hackers online through forums and Discord servers, but these are largely transactional professional connections.

How they decide

Stewart is a pragmatic decision-maker. He weighs options carefully, often leaning on his extensive experience and analytical skills. When faced with a technical choice, he'll research best practices and evaluate trade-offs, but he's not afraid to make a quick decision if it means unblocking progress. For tool adoption, he prefers open-source or cost-effective solutions that offer clear value and integrate well with his existing stack. He trusts his own judgment and empirical evidence over hype.

How they sound

Speaks with a moderate pace, generally clear and articulate. He uses technical jargon naturally when discussing code but can simplify explanations when needed. He avoids overly casual slang but might use common developer shorthand. He tends to be direct and factual, sometimes a bit dry, but not unfriendly. Prefers to under-promise and over-deliver in his communication.

Personality traits

  • pragmatic
  • self-reliant
  • methodical
  • driven
  • detail-oriented
  • resourceful
  • analytical
  • patient with code, impatient with friction

Goals

  • Achieve sustainable passive income from his SaaS product.
  • Build a reputation as a go-to expert in Rails and AI automation.
  • Develop a tool that genuinely solves a pain point for other indie makers.
  • Achieve greater financial freedom to allow for more project exploration.
  • Maintain a healthy work-life balance without sacrificing ambition.

Problems & frictions

  • Finding focused blocks of time for his SaaS project amidst client demands.
  • The mental overhead of managing multiple client projects and his own product.
  • Occasional imposter syndrome when comparing his bootstrapped approach to well-funded startups.
  • The constant need to stay updated with rapidly evolving AI technologies.
  • The challenge of marketing and sales for a product built by a developer, for developers.

Values

  • shipping quickly
  • independence
  • clean architecture
  • steady cash flow
  • skill mastery

Interests

  • Ruby on Rails
  • AI automation
  • indie hacking
  • Notion systems
  • cryptography basics
  • performance optimization

Media habits

  • Listens to tech podcasts during commutes and workouts
  • Follows specific developers and companies on Twitter/X
  • Reads Hacker News daily
  • Watches YouTube tutorials for specific coding problems
  • Subscribes to niche Rails newsletters

Questions & answers

Stewart O'Keefe’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Lightning Rails (https://lightningrails.com): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    The idea of cutting down on boilerplate is definitely appealing. Building out auth, Stripe, and an admin dashboard from scratch for every side project takes time. The $189 Lifetime + Claudatron option seems like a reasonable one-time cost if it truly saves me weeks of setup, especially with the AI integration. I'd stop considering it if the price went much beyond $250, as the ROI starts to diminish quickly. I'd expect robust documentation and maybe some community support for that price. Ideally, I'd pay $189 one-time for the full package.
    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.