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

Terrence Stehr

Terrence Stehr

Indie SaaS founder

Full-depth AI personas

Why this persona fits the audience

Co-founds a 2-person B2B SaaS in Austin and regularly captures onboarding screens, changelog pages, and support examples from live URLs for the product site and internal docs. Uses a mix of a small custom script, browser screenshots, and copy-pasted image links in Notion and Linear.

  • Age: 34
  • Location: Austin, Texas, USA
  • Occupation: Co-founder / product lead
  • Income: $140k-$180k personal income; startup-equity heavy
  • Education: B.S. Computer Science
  • Company size: 2
  • Years in role: 4
“The goal isn't just to build something; it's to build something that *works* reliably, something that makes a user's life tangibly easier, and to do it with maximum efficiency.”

Terrence Stehr, 34, is a quintessential indie SaaS founder operating out of Austin, Texas. His journey into entrepreneurship began after a successful stint as a software engineer at a mid-sized tech firm, where he grew increasingly frustrated with the slow pace of development and the bureaucratic hurdles that stifled innovation. Armed with a B.S. in Computer Science from a state university, he craved the autonomy and direct impact that only building something from the ground up could offer. Four years ago, he co-founded a two-person B2B SaaS company with his former colleague, Maya, focusing on developer tools. They bootstrapped aggressively, pouring personal savings and future equity into the venture. Terrence's current role as product lead involves a hands-on approach; he's intimately involved in every stage of the product lifecycle, from ideation to customer support. He champions a philosophy of lean development, emphasizing speed and clarity in both their product and their internal processes. A significant portion of his workday is dedicated to meticulously capturing visual elements—onboarding screens, changelog updates, support ticket examples—from live URLs. He employs a hybrid system: a small custom script automates some of the data gathering, supplemented by manual browser screenshots and copy-pasted image links, all meticulously organized within Notion and Linear. This process is crucial for maintaining up-to-date product documentation and marketing materials, reflecting his deep sense of ownership over the user experience. His personal income hovers between $140k-$180k, but the majority of his net worth is tied up in the startup's equity, a constant reminder of the high stakes. He lives frugally, seeing personal expenditure as secondary to the company’s growth, yet he’s not immune to the pressures of the industry, often feeling the scarcity of time and resources acutely. His recent focus has been on refining the initial user journey, believing that a seamless onboarding experience is paramount to reducing churn and building a loyal customer base.

Background & daily life

A day in their life

Terrence's typical weekday begins around 7:00 AM with a strong cup of coffee and a quick scan of Hacker News and his company's key metrics dashboard. From 8:00 AM to noon, he's deep in product development, often pairing with Maya or tackling complex coding challenges. Lunch is usually a quick, healthy meal prepared the night before, eaten at his desk while reviewing customer support tickets or user feedback. The afternoon is dedicated to product strategy, customer interviews, and refining the documentation pipeline – this is where he'll run his custom script to capture and organize website elements. He aims to wrap up by 7:00 PM, though late-night coding sessions aren't uncommon if a critical bug arises or inspiration strikes. He finishes the day by winding down with a short read or a brief walk.

Lifestyle

Terrence lives a focused, almost spartan lifestyle in Austin, prioritizing his startup's growth above most else. His 1-bedroom apartment is minimalist, clean, and functional, reflecting his appreciation for efficiency. Weekends often involve a mix of deep work sessions, catching up on industry news, and the occasional social gathering with fellow entrepreneurs or tech friends, though he's not one for large, loud parties. He cooks simple, healthy meals at home most nights and runs a few times a week to clear his head. Financial decisions are pragmatic; he prioritizes reinvesting in the business over personal luxuries, aware of his equity's long-term potential.

Work life

As co-founder and product lead, Terrence's days are a whirlwind of strategy, user feedback, and execution. He works closely with his technical co-founder, Maya, on feature development and bug fixes. His current focus is streamlining the onboarding process for their B2B SaaS, which involves meticulously documenting every step. He spends significant time analyzing product analytics to identify user drop-off points and manually capturing screenshots and snippets from live customer interactions for internal knowledge bases and public-facing documentation. The pressure to iterate quickly and show consistent user growth is ever-present, especially with limited resources.

Relationships

Terrence's closest professional relationship is with his co-founder, Maya, with whom he shares a strong rapport built on mutual respect and shared vision. His social circle is primarily composed of other founders and developers he's met through Austin's tech scene and online communities. His parents, who live in a different state, are supportive but don't fully grasp the intricacies of his startup journey. He values candid feedback from his small network of trusted peers.

How they decide

Terrence is a methodical decision-maker, heavily reliant on data and logical reasoning. He'll research options, weigh pros and cons, and often consults with his co-founder or a few trusted peers. He values speed but not at the expense of making a fundamentally flawed choice; he prefers a well-informed, moderately fast decision over a rushed one. He's not easily swayed by hype but will adopt new tools or methodologies if a clear benefit is demonstrated through evidence or practical application.

How they sound

Terrence speaks with a clear, measured cadence, often using precise technical language when discussing his work but capable of explaining concepts plainly. He avoids overly casual slang or jargon in professional contexts but might use terms like 'MVP' or 'iterate' naturally. He's direct and avoids hyperbole, preferring to stick to facts and logical explanations. When excited about a product feature or technical solution, his speech becomes more animated, but he remains grounded.

Personality traits

  • Analytical
  • Detail-oriented
  • Proactive
  • Resourceful
  • Slightly introverted
  • Driven
  • Practical
  • Self-disciplined

Goals

  • Achieve a sustainable MRR of $50k within 18 months.
  • Build a product that solves a genuine pain point for developers and businesses.
  • Attract a small, seed-stage investment round to scale the team.
  • Develop a robust automation pipeline for documentation and marketing assets.
  • Maintain a healthy work-life balance that prevents burnout.

Problems & frictions

  • Limited time for comprehensive user research due to development demands.
  • Balancing feature development with essential documentation and marketing tasks.
  • The inherent risk and financial uncertainty of bootstrapping a startup.
  • Maintaining consistent code quality and testing with a small team.
  • Staying on top of emerging technologies and competitor moves in a fast-paced market.

Values

  • speed
  • clarity
  • ownership
  • efficiency
  • autonomy

Interests

  • indie software
  • product analytics
  • automation
  • developer tools
  • lean startup methodologies

Media habits

  • Reads Hacker News daily
  • Listens to podcasts during commutes (e.g., Lex Fridman, Lenny's Podcast)
  • Follows tech influencers on Twitter/X
  • Skims tech newsletters (e.g., TLDR, Exponential View)
  • Watches YouTube tutorials for specific technical problems

Questions & answers

Terrence Stehr’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Maker launch on TinyLaunch: Screenshot any website with one API call. Free to start.. the product is a screenshot API for developers. One HTTP request turns a URL, HTML or Markdown… 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.

    The biggest problem for me right now is the manual effort involved in capturing and organizing screenshots for our product docs. I spend hours each week pulling these visuals from live URLs – using a mix of custom scripts, browser screenshots, and copy-pasting image links into Notion and Linear. It's time-consuming and prone to inconsistencies. If this API can truly automate capturing any website with one call, it would save me significant engineering and product time, which is currently my most scarce resource. I'm not sure about the accuracy or the ease of integrating it, though. Does it handle dynamic content well?
    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.