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

Kelly Lebsack

Kelly Lebsack

Technical product manager building on weekends

Full-depth AI personas

Why this persona fits the audience

She works as a technical product manager at a 3-person startup in Chicago and is building a small Rails AI summarization app on weekends. She handles authentication flows, Stripe setup, and a simple admin area herself while the rest of the team reviews the roadmap.

  • Age: 29
  • Location: Chicago, IL, USA
  • Occupation: Technical product manager
  • Income: $112k
  • Education: BS Information Systems
  • Company size: 3
  • Years in role: 4
“'I think the hardest part about building something useful isn't the code—it's making it so simple that people actually want to use it.'”

Kelly Lebsack grew up in a blue-collar Milwaukee neighborhood, one of the few kids who consistently scored in the top percentile on STEM aptitude tests. While her classmates dreamed of college, Kelly actually did the homework to get into Marquette University, where she graduated with a degree in Information Systems. A summer internship at a Chicago fintech startup kept her in the city post-graduation, where she quickly transitioned from QA tester to product manager through sheer persistence and technical curiosity. At 25, she joined a pre-seed startup as their first dedicated product hire, where she's currently the technical product manager for a SaaS tool that helps small law firms manage client intake. The company's tiny size means she's involved in everything from drafting user stories to occasionally debugging production issues. Her technical background makes her uniquely positioned to bridge gaps, but it also creates friction as she resists becoming the 'accidental engineer.' On weekends, she's building a side project that matters: an AI-powered summarization tool for long-form content that she hopes will solve her own pain point of information overload. The app uses Rails and Claude API, and she's handling everything from the authentication flow to the Stripe integration on her own. She's iterating in the open, sharing her progress on Indie Hackers, where her transparent approach has earned her both supporters and unsolicited advice. Financially, she's comfortable but does everything to avoid lifestyle creep—her biggest indulgence is a yearly solo trip to a tech conference in Europe. Status-wise, she's content with her current role but is eyeing director-level positions in a year. She views her side project as both a creative outlet and potential exit strategy if her startup doesn't scale as planned. Her biggest constraint isn't technical skill but time management, as she's constantly balancing work responsibilities, her side project, and her growing interest in technical product leadership. She's particularly proud of having built a maintainable codebase in her spare time, which she sees as proof that she can 'build and ship useful things without sacrificing her life to it.'

Background & daily life

A day in their life

Kelly's alarm goes off at 5:50 AM. She forces herself out of bed, makes a cold brew, and starts reviewing Jira tickets while eating yogurt at her tiny kitchen counter. The commute is a 20-minute bike ride to Wicker Park, where she showers at the office before the team's 8:30 standup. The morning is spent reviewing customer feedback, while the afternoon involves a deep dive with the engineer on their API architecture—where she's tempted to grab the keyboard but restrains herself. At 6:00 PM, she orders Thai takeout and brings it back to her apartment, where she sets up her second workstation to tackle her Rails app. By 11:00 PM, she's wrestling with Stripe webhook failures, muttering to herself about inconsistent documentation. She finally calls it a night when she sees the time, promising herself she'll start automating more tests tomorrow.

Lifestyle

Kelly rents a top-floor apartment in Logan Square with a dedicated work corner where her 15-inch MacBook Pro gets prime real estate. She keeps weekends sacrosanct for building her Rails app, fueling herself with cold brew from a hand-dripper and granola bars stashed in her coding setup. When not working, she cycles to the 606 Trail for training rides (she's training for her third century ride) or meets a small group of friends at a local brewery for card games. She tracks her spending meticulously in YNAB, having learned to live well on her salary without lifestyle inflation. Health-wise, she struggles to get enough sleep but compensates with a protein-heavy diet and intermittent fasting to maintain energy. Socially, she's part of a loose Chicago tech scene but prefers in-depth 1:1 connections over big networking events.

Work life

At her startup, Kelly is the glue between their engineering lead and non-technical founder, often fielding requests that fall between product and technical domains. Her typical day involves syncs with the engineering team (where she'll occasionally write quick Ruby scripts to answer questions), updating their Notion roadmap, and handling mundane but critical tasks like coordinating with Stripe support. Her technical background means she frequently contributes to their Rails codebase, but she's deliberate about not overstepping into full engineering work. The company's tiny size means she wears many hats—she just set up their first Intercom for customer support. The biggest work tension comes from resource constraints, where her weekend app-building skills would be invaluable if she could justify spending work hours on it.

Relationships

Kelly's closest confidant is her older sister, a nurse practitioner in Milwaukee, who serves as her emotional anchor. She speaks to her every Sunday evening—a ritual that anchors her week. Back in Chicago, her social circle consists primarily of ex-actuaries turned indie hackers and a few riders from her cycling club. She's cautiously dating a data scientist at a fintech company, though their different sleep schedules have created some friction. At work, she and the engineering lead share a productive, if occasionally tense, relationship built on mutual respect but different priorities. She finds herself frequently advising newer members of the Rails community in online forums, though she's hesitant about calling herself an 'expert.'

How they decide

Kelly researches thoroughly but trusts her instincts once she's gathered enough data. She'll collect multiple opinions but ultimately makes decisions quickly to avoid analysis paralysis. She values transparency in collaboration but dislikes drawn-out consensus-building processes. When it comes to technical decisions, she favors well-documented solutions over cutting-edge experiments unless the risk has clear upside. In personal matters, she tends to lean on her sister's pragmatic advice.

How they sound

Kelly speaks at a measured pace, choosing her words carefully but frequently inserting self-deprecating humor to keep conversations light. She avoids jargon when possible, preferring to explain technical concepts in simple terms even with other developers. She has a habit of starting sentences with 'So here's the thing' and ends them with drawn-out 'okays' to signal she's done speaking. She's particularly averse to corporate buzzwords, especially when they're used to obscure reality. When excited about a technical solution, her voice picks up speed and she'll use enthusiastic hand gestures even in Zoom calls.

Personality traits

  • Highly self-driven but selects collaborations carefully
  • Prefers deep work over small talk
  • Balances pragmatism with idealism in tech choices
  • Optimizes routines to maximize creative time
  • Dislikes ambiguity in specifications
  • Tends to over-plan personal projects before committing
  • Uses humor to defuse work tension
  • Shifts between hands-on coding and strategic thinking efficiently
  • Tolerates short-term chaos for long-term gains
  • Seeks out mentorship from senior engineers

Goals

  • Launch her summarization app to 100 paid users in the next 3 months
  • Move into a leadership role at her current company by year-end
  • Complete an advanced Ruby on Rails certification
  • Save enough to join a friends' trip to Portugal next summer
  • Build a personal brand as a thought leader in technical product management
  • Learn to ride a fixed-gear bike without training wheels

Problems & frictions

  • Feels stretched between her startup's needs and personal project time
  • Struggles to say no to additional responsibilities at work
  • Her Rails app's authentication flow keeps breaking during Stripe upgrades
  • Finding the right balance between technical implementation and product strategy
  • Needs to improve her public speaking skills to gain recognition
  • Her weekend coding sessions often run into late nights, disrupting her workout routine

Values

  • ownership
  • clarity
  • learning
  • useful products
  • autonomy

Interests

  • product management
  • Rails
  • AI summarization
  • side projects
  • coffee brewing
  • urban cycling

Media habits

  • Indie Hackers forums
  • Ruby on Rails blog
  • Hacker News
  • The Verge (tech news)
  • Spotify (independent artists)
  • Instagram (minimalist decor)

Questions & answers

Kelly Lebsack’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Lightning Rails (https://lightningrails.com): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    As someone building a Rails app on weekends, this seems tempting. The $189 lifetime license for both Lightning Rails and Claudatron feels steep, though—especially since I'm already comfortable setting up auth, Stripe, and admin systems manually. I'd consider it for $99, but only if the AI integrations genuinely save me 10+ hours. The 'ship in hours' claim feels optimistic, but Claudatron could replace some of my Indie Hackers troubleshooting. That said, I'm still skeptical about paying upfront for lifetime access when my side project might not scale.
    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.