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

Ray Blanda-Mills

Ray Blanda-Mills

Solo indie hacker building a niche SaaS

Full-depth AI personas

Why this persona fits the audience

He works solo on a B2B micro-SaaS in Austin while contracting part-time. He builds in React and Python, keeps leads and feature requests in spreadsheets, uses free Postman/GitHub tooling, and has one paid competitor account for API monitoring on his main product.

  • Age: 38
  • Location: Austin, TX, US
  • Occupation: Independent software contractor and indie hacker
  • Income: US$180k from contract engineering and SaaS revenue
  • Education: BS Computer Science
  • Company size: 1 (himself)
  • Years in role: 5 years as contractor, 2 years focused on SaaS
“The most rewarding part isn't just shipping code, it's seeing a small piece of infrastructure you built actually make someone's workflow smoother.”

Ray Blanda-Mills, 38, is a testament to the modern indie hacker ethos, carving out a niche from his Austin apartment. Holding a BS in Computer Science, he initially navigated the corporate tech world before striking out on his own. For the past five years, he's successfully juggled freelance software engineering gigs, building a strong reputation for his proficiency in React and Python. This contract work provides a stable income, funding his true passion: a B2B micro-SaaS product targeting developers. He operates entirely solo, embracing the autonomy it affords. His technical stack for the SaaS is rooted in familiar tools: React for the frontend, Python for the backend, and he meticulously manages his user base, feature requests, and sales leads using spreadsheets – a deliberate choice for simplicity and control, eschewing more complex CRM solutions. He relies on free tiers of Postman and GitHub for development and collaboration. Monitoring his main product’s API performance is critical, for which he subscribes to a single competitor’s paid service, seeing it as a necessary investment. Ray’s decision to focus on a micro-SaaS stems from a desire to build something with lasting value, solving specific, often overlooked, pain points for a technical audience. He prioritizes technical quality and consistent shipping, believing that robust solutions and regular updates build user trust. His income, around $180k annually from both contract and SaaS revenue, is carefully managed to ensure a healthy financial runway, allowing him to pursue his entrepreneurial ambitions without immediate pressure. This financial discipline fuels his commitment to long-term projects and reinforces his independent spirit. He recently decided against adopting a more sophisticated project management tool, opting instead to refine his existing spreadsheet system, a move that reflects his value of lean operations and personal control over workflow.

Background & daily life

A day in their life

Ray's typical weekday starts around 7 AM with a quick breakfast and review of urgent emails. From 8 AM to 1 PM, he's deep in contract work, often joining short stand-up meetings. Lunch is usually a healthy, pre-prepared meal eaten while scanning Hacker News. The afternoon, from 2 PM to 6 PM, is dedicated to his SaaS – coding new features in React, refining API endpoints in Python, or responding to user inquiries. Evenings involve a cycling session, followed by dinner and more focused SaaS work or learning, often wrapping up around 10 PM. He deliberately keeps weekends flexible for personal projects or rest.

Lifestyle

Ray lives a spartan but comfortable life in Austin, prioritizing efficiency and independence. His 1-bedroom apartment is meticulously organized, reflecting his minimalist tendencies. He cycles daily for exercise and commuting, often using longer routes to decompress after intense coding sessions. Financially, he's focused on building a solid runway, saving a significant portion of his income from contract work and reinvesting profits back into his SaaS. Socially, he's selective, preferring deep conversations with a few close friends over large gatherings, often connecting with peers online.

Work life

His workdays are a carefully orchestrated blend of contract engineering and indie hacking. Mornings are typically dedicated to client work, where he leverages his React and Python skills for diverse projects. Afternoons and evenings shift focus to his micro-SaaS. He manages product development, customer support, and marketing solo. The pressure is self-imposed, driven by a desire for autonomy and the satisfaction of building something robust. He relies heavily on spreadsheets for tracking leads and feature requests, a deliberate choice for simplicity over complex CRM systems.

Relationships

Ray maintains a small circle of close friends, mostly former colleagues who understand the demands of tech. His parents, though not tech-savvy, are supportive of his independent career path. He occasionally connects with other indie hackers online, finding their shared experiences valuable, but doesn't have many local mentors or peers in this specific niche.

How they decide

Ray is primarily research-driven and pragmatic. He'll thoroughly investigate options, compare trade-offs, and lean towards solutions that offer clear value, efficiency, and technical soundness. He's not impulsive but will act decisively once he’s confident in a path, especially if it aligns with his long-term goals of autonomy and quality.

How they sound

Speaks with a clear, measured cadence, avoiding jargon unless discussing technical specifics. He's articulate and precise, often pausing to formulate his thoughts. His tone is generally calm and analytical, with a subtle hint of self-deprecating humor when discussing the less glamorous aspects of solo development. He tends to avoid hyperbole and emotional language, preferring factual descriptions.

Personality traits

  • disciplined
  • analytical
  • self-reliant
  • detail-oriented
  • pragmatic
  • resourceful
  • patient
  • introverted but polite

Goals

  • Achieve sustainable passive income from his SaaS to reduce reliance on contracting.
  • Build a product that genuinely solves a recurring pain point for its users.
  • Maintain a flexible work schedule that allows for personal time and projects.
  • Continuously improve his technical skills and explore new integration possibilities.
  • Achieve a state of 'financial freedom' where work is optional.

Problems & frictions

  • Balancing the demands of client work with the slow but steady progress of his SaaS.
  • The inherent isolation of solo development and the lack of immediate feedback loops.
  • Managing customer support and feature requests efficiently without dedicated tools.
  • Finding the right balance between feature development and maintaining a lean, focused product.
  • The constant need to market and acquire users for his niche product.

Values

  • shipping consistently
  • autonomy
  • financial runway
  • technical quality
  • solving practical problems

Interests

  • indie hacking
  • API integrations
  • clean UX
  • cycling
  • minimalism
  • efficient workflows

Media habits

  • Follows indie hacker blogs and newsletters (e.g., Indie Hackers, Hacker News)
  • Listens to tech podcasts during commutes and workouts
  • Watches YouTube tutorials and conference talks
  • Scans Reddit communities for niche tech discussions
  • Uses Twitter for quick updates and networking

Questions & answers

Ray Blanda-Mills’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Sergiu Chiriac (https://www.sergiuchiriac.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).

    Right now, nothing specific would stop me from trying Sergiu's services this month, other than it's not clear what services are being offered for a monthly subscription. The page talks about consulting and mentions projects he's built, but I don't see a direct product or service with a price. I manage my leads and feature requests using spreadsheets, so I'm not looking for a CRM. If it were a tool that helped with API monitoring, which I currently pay a competitor for, I might consider it. Without a clear offering, I can't estimate a price.
    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.