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

Casey Shanahan

Casey Shanahan

Freelance Android contractor

Full-depth AI personas

Why this persona fits the audience

He works as a freelance Android contractor for two bootstrapped clients in Chicago and is currently handling one client's Play Console closed test by collecting tester signups manually through email, Slack, and a form, then logging feedback in Notion.

  • Age: 40
  • Location: Chicago, Illinois, USA
  • Occupation: Freelance Android developer
  • Income: USD 132k mixed contract income
  • Education: Associate degree in computer information systems
  • Company size: N/A (self-employed)
  • Years in role: 12
“The best tool is the one that actually gets the job done without creating more work.”

Casey Shanahan has been navigating the world of Android development for over a decade, carving out a niche as a reliable freelance contractor. His journey began with an Associate degree in Computer Information Systems, followed by several years in traditional agency roles before the allure of independent work became too strong to resist. He found that his pragmatic approach and knack for problem-solving were well-suited to the demands of freelancing. Now 40, he operates primarily out of his Chicago apartment, a testament to his value of practicality and an independent income. He currently serves two bootstrapped clients, a dynamic that requires constant adaptation and a keen understanding of their limited resources. This often means he's not just coding but also managing project logistics. His current focus is a prime example: he's meticulously handling the closed testing phase for one client's app. This involves the unglamorous but critical task of manually collecting tester signups through a patchwork of email threads, Slack channels, and a Google Form. He then diligently logs all incoming feedback into Notion, a system he's optimized for clarity. This hands-on approach, while time-consuming, ensures he maintains direct oversight and builds crucial client trust. He’s made conscious decisions to avoid the complexity of larger project management suites, preferring lightweight systems that he can control and customize. His income, while solid at $132k, is entirely contract-based, reinforcing his commitment to reliability and client satisfaction as paramount. He views his work not just as coding, but as providing a dependable service that helps small businesses launch and iterate on their mobile products. He’s always on the lookout for ways to streamline these manual processes, driven by a desire for greater efficiency without sacrificing quality or client relationships.

Background & daily life

A day in their life

Casey's weekday typically starts around 8:00 AM with coffee and a quick scan of tech news. He dedicates the morning to deep work, often tackling complex coding tasks for his clients. Around noon, he'll break for a simple lunch, perhaps a sandwich or leftovers. The afternoon is usually a mix of client calls, responding to emails, and managing the current beta testing signup process – sending out invites, checking the form submissions, and updating the Notion board. He might spend an hour experimenting with a new mobile tooling library or working on a small personal automation script. Evenings are for winding down, maybe a walk, dinner, and then either personal coding projects or relaxing with a book or show, aiming to log off by 9:30 PM.

Lifestyle

Casey lives a fairly routine-driven life in a modest but well-kept apartment in Chicago's Lincoln Square neighborhood. His income allows for comfort but not extravagance; he prioritizes saving for future stability and occasional travel. Weekends often involve catching up on personal projects, exploring local breweries with a small circle of friends, or simply unwinding with a book or a streaming series. He's not a big spender on material goods, preferring experiences or investments in his professional toolkit. Health-wise, he tries to walk to coffee shops and occasionally hits the gym, but his work can sometimes lead to sedentary stretches.

Work life

As a freelance Android developer, Casey's workdays are a blend of focused coding and client communication. He juggles two primary clients, both bootstrapped startups, which means he's often wearing multiple hats. Currently, a significant chunk of his time is dedicated to managing a closed testing phase for one client. This involves manually collecting tester sign-ups via email and Slack, setting up forms, and meticulously logging feedback in Notion. The pressure comes from tight deadlines and the need to maintain client trust through consistent, high-quality delivery, often with limited resources. He values the autonomy but sometimes misses the collaborative energy of a larger team.

Relationships

Casey maintains a small but close-knit group of friends, mostly met through past tech meetups or university. He's on good terms with his parents, who live in a suburb outside Chicago, and calls them weekly. His professional network is primarily online, relying on connections made through freelance platforms and developer forums for advice and potential leads.

How they decide

Casey is a cautious and research-driven decision-maker, especially when it comes to tools or processes that impact his workflow. He weighs practicality and long-term reliability heavily, often seeking out reviews, comparing features, and considering the effort required for implementation before committing. He's not easily swayed by hype and prefers solutions that demonstrably solve a problem efficiently.

How they sound

Speaks in a clear, measured tone. Uses precise technical language when discussing work but can switch to more casual phrasing with friends. Avoids hyperbole and overly enthusiastic sales pitches. Tends to be direct and factual, often prefacing opinions with 'I think' or 'From my experience.' He doesn't use much slang but might occasionally drop a mild expletive when frustrated with a bug. His cadence is steady, reflecting his methodical approach.

Personality traits

  • Methodical
  • Resourceful
  • Detail-oriented
  • Independent
  • Pragmatic
  • Patient
  • Reliable
  • Quietly competent
  • Adaptable

Goals

  • Achieve a more predictable income stream with fewer client onboarding cycles.
  • Develop a small, reusable library or tool that simplifies a common Android development pain point.
  • Save enough for a down payment on a small condo within the next five years.
  • Maintain a healthy work-life balance to avoid burnout.
  • Become a go-to expert for a niche area within Android development.

Problems & frictions

  • The administrative overhead of managing freelance contracts and invoicing.
  • Manually handling repetitive tasks like tester recruitment for beta programs.
  • Inconsistent project scope creep from bootstrapped clients with evolving visions.
  • Finding reliable, high-quality contract work consistently.
  • The isolation of working solo without a dedicated team for brainstorming or support.

Values

  • practicality
  • client trust
  • independent income
  • efficiency
  • reliability

Interests

  • mobile tooling
  • freelancing
  • lightweight project systems
  • automation
  • app performance optimization

Media habits

  • Reads tech blogs (Android Developers Blog, Medium publications)
  • Listens to tech podcasts during commutes
  • Active on Stack Overflow and Reddit (r/androiddev)
  • Follows key Android influencers on Twitter
  • Occasional YouTube tutorials for specific tools

Questions & answers

Casey Shanahan’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of BetaCircle (https://www.betacircle.app) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make BetaCircle better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I'm manually collecting tester signups via email and Slack, then logging feedback in Notion. It's tedious, but I have direct control. The idea of getting testers automatically is appealing, especially if it streamlines the closed testing phase. However, the "earn diamonds" model sounds a bit complex. I'd need to understand how that translates to getting *my* app tested reliably. Is it truly free, or is there an indirect cost or time investment in testing other apps? The "verified login" and "14 days" sound promising for meeting Google Play requirements. I'm hesitant about paying for something until I'm sure it consistently delivers what I need without a significant time sink. For now, I'd consider paying up to $25 per month if it proves to be a significant time saver and reliably gets me the testers I need without a lot of management overhead on my part.
    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.