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

Lester Ortiz

Lester Ortiz

Solo SaaS builder with a part-time engineering job

Full-depth AI personas

Why this persona fits the audience

Builds a small B2B analytics app after work while employed full-time as a software engineer. Uses a local startup Slack and occasional X posts to find collaborators for design and backend help; keeps project notes in Notion and a spreadsheet.

  • Age: 29
  • Location: Austin, Texas, US
  • Occupation: Software engineer
  • Income: $155k
  • Education: Bachelor's degree
  • Company size: 50-100 employees
  • Years in role: 6
“The most satisfying thing is building something that actually works, piece by piece, even if it's just for a small group of people.”

Born and raised in a suburban area outside of Houston, Lester Ortiz displayed an early aptitude for logic and problem-solving, spending his childhood disassembling and reassembling electronics. He pursued a Bachelor's degree in Computer Science at the University of Texas at Austin, where he developed a deep appreciation for elegant code and efficient systems. Upon graduation, he joined a local tech company, quickly rising through the ranks to become a skilled software engineer. His current income of $155k reflects his expertise and the competitive Austin market. Lester rents a two-bedroom apartment with a roommate to keep expenses manageable, a pragmatic approach to finances that allows him to invest in his personal projects. He's driven by a desire for craftsmanship and autonomy, seeking to build something of his own that reflects his technical skills. His current venture is a B2B analytics application, a project he's been diligently working on for over a year, spending his evenings and weekends immersed in its development. He utilizes Notion for project documentation and spreadsheets for tracking metrics, while leveraging a local startup Slack community and occasional X posts to find collaborators for specific design or backend challenges. He recently made a decision to focus on a niche within his analytics app, believing it offers a clearer path to initial traction, rather than trying to build too many features at once. This reflects his values of steady progress and his pragmatic approach to building a sustainable product, viewing his full-time job not just as a source of income but as a stable foundation that allows him the freedom to pursue his entrepreneurial ambitions without immediate financial pressure. He views time as a finite resource that must be managed carefully to achieve his long-term goals.

Background & daily life

A day in their life

Lester's weekday begins around 6:30 AM. After brewing coffee and a quick breakfast, he heads to his software engineering job, arriving by 8:30 AM. His workday involves coding, attending team meetings, and debugging. Lunch is usually a quick, healthy meal eaten at his desk while scanning Hacker News. After work, around 5:30 PM, he might hit the gym or go for a short run. Evenings are dedicated to his SaaS app: from 7 PM to 10 PM, he's coding, refining features, or reaching out to potential users. He winds down with reading or a podcast before bed, aiming to sleep by 11 PM.

Lifestyle

Lester lives a focused life, balancing his demanding full-time engineering role with his entrepreneurial aspirations. His apartment in Austin is functional, shared with a roommate to manage costs, and often serves as a quiet workspace after dinner. He's particular about his routine: early mornings often involve a strong pour-over coffee brewed at home before heading to his day job. Evenings and weekends are segmented, with dedicated blocks for his SaaS project. He eats healthily, mostly cooking at home, and prioritizes sleep to maintain his energy levels. Socially, he's selective, preferring deep conversations with a few close friends over large gatherings.

Work life

As a software engineer at a mid-sized tech company, Lester's workdays are structured around sprints and code reviews. He's proficient in several languages and frameworks, often contributing to complex backend systems. His team is collaborative but busy, with frequent stand-ups and planning meetings. The pressure to deliver features on time is constant, but Lester finds satisfaction in solving intricate technical challenges. He utilizes Jira for task management, Slack for team communication, and Git for version control. He tries to shield his personal project time from his work commitments, often working late into the night.

Relationships

Lester maintains a small circle of close friends, mostly fellow engineers he met in college or at past jobs. He occasionally connects with people from a local Austin startup Slack community for advice or to find design and backend help. His family lives out of state, and they communicate via weekly video calls. He values their support but doesn't heavily involve them in his technical pursuits.

How they decide

Lester is a highly analytical and research-driven decision-maker. He prefers to gather data, compare options methodically, and consider long-term implications before committing. While he values expert opinions, he ultimately relies on his own judgment and empirical evidence. He's not easily swayed by trends or hype, preferring practical, proven solutions.

How they sound

Lester speaks with a measured cadence, often pausing to find the precise technical term. His language is generally professional, even in casual conversation, but he'll use industry jargon naturally. He avoids hyperbole and prefers clear, direct communication, rarely engaging in small talk unless initiated. He's not overly enthusiastic but conveys a quiet confidence.

Personality traits

  • meticulous
  • resourceful
  • disciplined
  • analytical
  • independent
  • observant
  • driven
  • pragmatic

Goals

  • Achieve consistent, passive revenue from his SaaS product.
  • Build a reputation as a skilled indie hacker.
  • Eventually transition to working on his own projects full-time.
  • Master a new programming language or framework annually.
  • Maintain a healthy work-life balance despite ambitious goals.

Problems & frictions

  • Finding enough dedicated time for his SaaS project amidst a full-time job.
  • Overcoming the initial hurdle of acquiring his first few paying B2B customers.
  • Balancing the need for specialized skills (design, marketing) with his engineering focus.
  • The inherent loneliness of solo building, despite seeking collaborators.
  • Maintaining motivation and avoiding burnout over the long haul.

Values

  • craftsmanship
  • autonomy
  • steady progress
  • problem-solving
  • lifelong learning

Interests

  • indie hacking
  • APIs
  • coffee shops
  • system design
  • data visualization

Media habits

  • Substack newsletters on tech and indie hacking
  • X (formerly Twitter) for industry news and connections
  • Hacker News for technical discussions
  • Podcasts during commute (e.g., Syntax, Software Engineering Daily)
  • YouTube for tutorials and tech reviews

Questions & answers

Lester Ortiz’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.letsjam.live/ (Let's Jam) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core concept of finding collaborators for side projects is clear, which aligns with my own goals. However, the immediate impression is a bit bare-bones. I'd want to see more detail on the projects themselves – what stage are they in? What specific skills are needed beyond broad categories like "Engineering"? The "Ideas NEW" tab is intriguing, but without more context, it's hard to gauge potential. To sign up, I'd need to understand the platform's structure for collaboration, how projects are managed, and perhaps see some success stories or testimonials. It feels like a place to *start* looking, but not enough to commit to without more information.
    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.