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

Bobby Johnson

Bobby Johnson

Bootstrapped solo founder

Full-depth AI personas

Why this persona fits the audience

Runs a one-person B2B invoicing SaaS from Austin and is building sign-up, password reset, and invite-based access for the first customer portal; he currently keeps beta users in a spreadsheet and uses a hand-rolled auth flow in a Next.js app.

  • Age: 33
  • Location: Austin, TX, US
  • Occupation: Founder and solo developer
  • Income: USD 110k plus equity
  • Education: BSc Computer Science
  • Company size: 1
  • Years in role: 4
“I'd rather build a solid foundation myself than rely on something I can't fully control or understand, even if it takes a bit longer.”

Bobby Johnson, 33, is a bootstrapped solo founder operating from his Austin, TX apartment, where he runs a one-person B2B invoicing SaaS. Armed with a BSc in Computer Science from a state university, he founded his company four years ago with a vision for simplifying small business finances. He lives a life defined by independence and a relentless pursuit of efficiency, reflected in his cycling hobby and preference for straightforward, pragmatic solutions. His income of $110k plus equity allows for a comfortable lifestyle, though he's highly focused on reinvesting profits back into the business and maintaining lean operations. Recently, he's been grappling with the technical debt of his hand-rolled authentication system. He's currently in the thick of building out critical user portal features—sign-up, password reset, and invite-based access—for his first major client. This move signifies a shift from his initial beta phase, where he managed users via spreadsheets and a less robust, custom auth flow in his Next.js app. This project demands significant attention, pulling him away from more immediate feature requests, but he recognizes its foundational importance for scalability and security. Bobby values speed and simplicity but is increasingly understanding the necessity of robust infrastructure as his user base grows, albeit slowly. His decision to tackle the auth system now, rather than later, is a testament to his conscientiousness and a pragmatic acknowledgment of its growing importance.

Background & daily life

A day in their life

Bobby's weekday typically starts around 7 AM with a quick walk with Byte, followed by coffee and scanning Hacker News. He'll hit the gym or go for a bike ride for an hour or two before settling into his home office around 10 AM. Mornings are dedicated to coding, currently focused on the user portal's authentication flow. Lunch is usually a simple, quick meal. Afternoons involve responding to emails, working on marketing materials, or tackling customer support queries. He tries to wrap up work by 6 PM, but often finds himself back at his desk for an hour or two in the evening if a bug pops up or inspiration strikes for a new feature. He unwinds by watching a documentary or reading tech articles.

Lifestyle

Bobby lives in a modest two-bedroom rental on the east side of Austin, sharing it with a rescue dog named 'Byte'. He cycles to his co-working space or the coffee shop where he often works, prioritizing health and avoiding the stress of Austin traffic. His income covers his living expenses comfortably, with a decent chunk going into savings for future business scaling or unexpected life events. He's not extravagant, preferring to invest in quality tools and experiences over material possessions. Social life is often centered around meetups with other indie hackers or casual rides with a small group of cycling buddies.

Work life

As a solo founder, Bobby wears every hat: developer, marketer, support, and finance. His current focus is on building out the core features for his B2B invoicing SaaS, specifically the user portal functionalities. The pressure is on to deliver a polished experience for his first paying customer, a local accounting firm. He's currently deep in the weeds of implementing a secure sign-up, password reset, and invite system within his Next.js application, a task he's been putting off in favor of more immediate feature development. He relies heavily on open-source libraries and a few essential SaaS tools for project management and communication.

Relationships

Bobby's closest relationships are with his fellow indie hackers and a few long-term friends from college who understand his entrepreneurial drive. He occasionally connects with his parents back in Ohio, who are proud but don't fully grasp the intricacies of his work. Online communities on Hacker News and Twitter are significant sources of camaraderie and technical advice.

How they decide

Bobby is a pragmatic decision-maker. He researches thoroughly, weighing pros and cons, but prioritizes solutions that are simple to implement and maintain, especially given his solo status. He's not afraid to build things himself if it saves money or offers more control, but will opt for well-vetted, straightforward tools when the trade-off is clear and beneficial.

How they sound

Speaks in a clear, measured tone. Uses precise technical jargon when discussing development but simplifies when explaining business concepts. Avoids overly casual slang but might use occasional tech-specific idioms. Tends to be direct and avoids excessive politeness or fluff. Can sound a bit dry but is earnest.

Personality traits

  • resourceful
  • pragmatic
  • detail-oriented
  • independent
  • driven
  • analytical
  • slightly introverted
  • skeptical of hype

Goals

  • Achieve consistent monthly recurring revenue (MRR) for his SaaS.
  • Build a scalable and secure authentication system.
  • Automate more of his business operations.
  • Maintain his independence and avoid external funding for as long as possible.
  • Eventually hire a part-time developer or support person.

Problems & frictions

  • Balancing feature development with essential but less exciting infrastructure work (like auth).
  • Managing customer expectations as a one-person operation.
  • The constant pressure to acquire new customers while retaining existing ones.
  • Technical debt accumulating from hand-rolled solutions.
  • Finding time for marketing and sales amidst development.

Values

  • independence
  • speed
  • simplicity
  • autonomy
  • practicality

Interests

  • indie hacking
  • cycling
  • small business software
  • open-source
  • productivity tools

Media habits

  • Hacker News
  • Indie Hackers podcast
  • Twitter (following tech/founder accounts)
  • specific tech blogs (e.g., dev.to, CSS-Tricks)
  • YouTube tutorials

Questions & answers

Bobby Johnson’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Hanko (https://www.hanko.io/) 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, the main thing that would stop me from trying Hanko is the fact that I'm knee-deep in building out the user portal's sign-up, password reset, and invite flow for my first paying customer. It's a critical feature, and I can't really divert resources from that right now. Currently, I'm handling user access via a spreadsheet and a custom-built auth system within my Next.js app. It's not ideal, but it works for the current beta users. I'd be willing to pay around $50 per month, but that's based on scaling up my MRR 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.