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

Brian O'Reilly

Brian O'Reilly

Bootstrapped SaaS founder

Full-depth AI personas

Why this persona fits the audience

Co-founds a 4-person B2B scheduling SaaS in Austin. Feature specs, onboarding docs, and FAQ answers live in Notion; the founder and one part-time support contractor answer most inbound email questions themselves and log repeats in a spreadsheet.

  • Age: 34
  • Location: Austin, Texas, US
  • Occupation: Co-founder, B2B SaaS
  • Income: USD 120k draw + equity
  • Education: BS Computer Science
  • Company size: 4
  • Years in role: 5
“The most rewarding part of this grind is building something that people actually find indispensable, piece by piece.”

Brian O'Reilly, 34, is a quintessential bootstrapped SaaS founder operating out of Austin, Texas. His journey into entrepreneurship began after several years as a software engineer at a mid-sized tech company, where he grew frustrated with bureaucratic processes and a lack of direct impact. He earned his BS in Computer Science from a state university, honing a strong analytical and problem-solving skillset. Five years ago, he co-founded a B2B scheduling SaaS with two college friends. The company is lean, currently a four-person operation, with Brian handling a significant portion of product management and customer-facing responsibilities alongside development. His income of USD 120k is a draw against company profits, supplemented by equity, which he views as a long-term bet. He lives a focused life, prioritizing speed and clarity in his work. His current marketFit involves meticulously managing Notion for documentation and using spreadsheets to track customer support issues, a system born from necessity and a desire to avoid unnecessary tooling costs early on. Recent decisions include doubling down on Notion as their primary internal knowledge repository and investing more time in analyzing user behavior patterns to inform feature prioritization, aiming to build deeper customer trust. He sees time as his most valuable, non-renewable resource, and money as a tool to achieve autonomy and build a sustainable business, not as an end in itself. Status, for Brian, is less about external validation and more about the quiet satisfaction of creating a functional, valuable product.

Background & daily life

A day in their life

Brian's weekday typically begins around 6:00 AM with a trail run or a workout. After a quick shower and a strong pour-over coffee, he's at his home office by 7:30 AM. His morning is often dedicated to deep work: coding new features, refining product analytics dashboards, or planning sprints. Around noon, he takes a break for lunch and might check industry news on Hacker News or Twitter. The afternoon is a mix of virtual team syncs, customer email responses (often flagging common questions for documentation), and reviewing design mockups. He tries to wrap up by 6:30 PM, sometimes fitting in a quick call with a potential partner or investor, before heading out for a casual dinner or a quiet evening at home.

Lifestyle

Brian lives in a moderately sized apartment in South Austin, enjoying the city's vibrant tech scene and outdoor access. His income provides a comfortable but not extravagant lifestyle; he prioritizes experiences and skill development over luxury goods. He’s an early riser, often starting his day with a run on the Barton Creek Greenbelt or a meticulously brewed pour-over coffee. Socially, he prefers smaller gatherings with close friends or fellow entrepreneurs over large parties. His financial habits are disciplined, focusing on reinvesting in his company and building a solid emergency fund.

Work life

As a co-founder of a B2B scheduling SaaS, Brian's days are a dynamic mix of strategic planning and hands-on execution. The team is small (himself, two developers, and a part-time support contractor), so responsibilities are fluid. He spends significant time defining product features, analyzing user feedback from their Notion knowledge base, and managing the product roadmap. He's deeply involved in customer success, personally handling a chunk of inbound emails, using spreadsheets to track recurring issues, and crafting FAQ responses. The pressure comes from balancing rapid development with maintaining customer trust and ensuring the company's lean operations remain efficient.

Relationships

Brian maintains strong but selective friendships, primarily with other founders and developers in the Austin tech community. He's close with his two co-founders, sharing a mutual respect for each other's skills. His part-time support contractor, Sarah, is a trusted collaborator, and her feedback on customer issues is invaluable. He stays in touch with his parents back in his home state, though their understanding of his entrepreneurial journey is limited.

How they decide

Brian is a methodical decision-maker, leaning heavily on data and logical analysis. He researches thoroughly, consulting relevant forums, developer communities, and product reviews before committing to a significant choice. He values input from his co-founders and trusted peers but ultimately trusts his own judgment based on the evidence he's gathered. He avoids impulsive choices, preferring to weigh pros and cons systematically.

How they sound

Brian speaks with a clear, measured cadence. He’s articulate and precise, avoiding jargon unless discussing technical concepts with peers. His tone is generally calm and reasoned, even when discussing challenges. He tends to use phrases like 'effectively,' 'streamline,' and 'optimize,' reflecting his focus on efficiency. He avoids hyperbole and overly emotional language, preferring direct, factual communication.

Personality traits

  • Analytical
  • Driven
  • Pragmatic
  • Detail-oriented
  • Resourceful
  • Calm under pressure
  • Self-starter
  • Focused

Goals

  • Achieve sustainable profitability for his SaaS company
  • Build a product that genuinely solves customer pain points
  • Become a recognized expert in the scheduling SaaS niche
  • Maintain a healthy work-life balance as the company grows
  • Explore developing another micro-SaaS in a different vertical

Problems & frictions

  • Scaling customer support without significant overhead
  • Prioritizing feature development against limited engineering resources
  • Finding reliable, high-quality part-time support staff
  • Keeping up with competitor feature releases and market shifts
  • Managing founder burnout and maintaining personal energy levels

Values

  • speed
  • clarity
  • customer trust
  • efficiency
  • autonomy

Interests

  • indie hacking
  • product analytics
  • trail running
  • micro-SaaS
  • coffee brewing
  • productivity tools

Media habits

  • Listens to tech podcasts during commutes/runs
  • Reads Hacker News and Indie Hackers daily
  • Subscribes to several product newsletters
  • Uses Twitter for industry news and networking
  • Watches YouTube tutorials for software development

Questions & answers

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

  1. Think about your own work or business in this area: Show HN launch (7 pts, 2023-09-14): the product AI – AI Chatbot trained on your Notion docs. Site shows pricing/signup. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    AI Chatbot trained on Notion docs? That sounds interesting. Our biggest challenge right now is scaling our customer support. We're a lean four-person team, and manually answering repetitive questions across email and Notion documentation takes up too much developer time – easily 10-15 hours a week collectively. We've tried creating more robust FAQs in Notion, but they don't always get found. This definitely impacts our ability to move faster on product development. I'd be curious to see how 'AI Chatbot' handles nuance and if it can truly reduce our manual workload without creating more problems.
    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.