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

Troy Beahan

Troy Beahan

MSP support engineer

Full-depth AI personas

Why this persona fits the audience

Works in a 6-person managed IT services firm supporting about 40 SMB mailboxes. When a client's Outlook profile is corrupted or a laptop is returned after departure, he is one of the people who receives the OST file, checks whether the mailbox data can be opened or exported, and documents the result for handoff.

  • Age: 34
  • Location: Austin, Texas, US
  • Occupation: MSP support engineer
  • Income: $82k
  • Education: Bachelor's in information systems
  • Company size: Small (6 employees)
  • Years in role: 7
“Every bit of data has its place, and it's my job to make sure we can find it, no matter how tangled things get.”

Troy Beahan found his calling in the intricate world of IT support during his undergraduate studies in Information Systems at a state university. Hailing from a modest background in a smaller Texas town, he developed an early fascination with how computers and networks operated, often taking apart old electronics to see their inner workings. This innate curiosity, coupled with a disciplined approach to learning, propelled him through his degree program. Upon graduation, he joined a local Managed Service Provider (MSP) in Austin, drawn by the opportunity to work with a variety of small businesses and the hands-on problem-solving involved. For the past seven years, he has steadily grown within the firm, currently serving as a key support engineer. His role requires a deep understanding of Windows environments, network infrastructure, and common business applications, with a particular emphasis on email systems like Microsoft Exchange and Outlook. He takes pride in his ability to meticulously document processes and outcomes, a skill honed through countless hours of troubleshooting and client interactions. Recently, he was instrumental in implementing a standardized backup procedure for client PST/OST archives, a decision driven by a particularly challenging data recovery case involving a client's critical financial records. This project reinforced his belief in proactive measures and the importance of robust documentation. He views his work not just as fixing problems, but as building trust with clients by ensuring their digital operations are stable and secure. He's not driven by status or the pursuit of cutting-edge technology for its own sake, but by the satisfaction of solving complex puzzles and providing reliable IT solutions that keep small businesses running smoothly. His income is comfortable for Austin, allowing him to live independently and invest modestly in his personal tech projects and savings, but he remains mindful of budget constraints when evaluating new tools or services for the firm.

Background & daily life

A day in their life

Troy's typical weekday begins around 7:30 AM with a quick breakfast and scanning tech news. He arrives at the office by 8:30 AM, checking the ticketing system for urgent overnight issues. Most of his morning is spent on remote support calls, addressing everything from printer driver problems to network connectivity for small businesses. Around lunchtime, he might grab a sandwich from a local deli. The afternoon often involves a mix of proactive tasks like server patching and dealing with specific client requests, such as extracting data from an OST file for a departing employee. He finishes his workday around 5:30 PM, often spending an hour in his home lab before winding down for the evening, perhaps watching a tech documentary or playing a strategy game.

Lifestyle

Troy lives in a modest two-bedroom apartment in a slightly older but well-maintained part of Austin, prioritizing proximity to his office over trendy amenities. His evenings and weekends are often a blend of hands-on tech work and quiet relaxation. He dedicates time to his home lab, tinkering with network configurations and virtual machines. He cooks most of his meals, aiming for healthy, straightforward dishes to save money and control his diet. Socially, he prefers smaller gatherings with a few close friends, often discussing tech or engaging in low-key activities like board games or catching a local band. He's disciplined with his finances, saving a portion of his income for future investments and tech upgrades.

Work life

Troy's days are a constant juggle of reactive support and proactive maintenance for the firm's SMB clients. He spends significant time remotely accessing user machines, diagnosing network issues, and performing software installations or updates. A recurring task involves recovering data from corrupted Outlook OST files, especially when an employee departs, requiring careful extraction and documentation for HR or legal compliance. He works closely with his four other support engineers and the owner, often collaborating on complex issues or handing off tickets. The pressure comes from client uptime guarantees and the need to resolve issues quickly and accurately, minimizing disruption.

Relationships

Troy is close with his parents, who live a few hours away and whom he visits monthly. He has a small, tight-knit group of college friends who share his interest in technology; they often connect online or meet up for tech talks or gaming. His immediate colleagues at the MSP are his primary professional circle, with whom he shares daily work challenges and occasional lighthearted banter.

How they decide

Troy is a research-oriented decision-maker. He prefers to gather as much information as possible, looking at technical specifications, reading reviews from peers or reputable tech sites, and often testing solutions in his home lab before committing, especially if it involves a purchase or a significant change to a client's setup. He weighs the cost against the perceived benefit and reliability.

How they sound

Troy speaks with a clear, measured cadence. He tends to be articulate and precise when explaining technical concepts, avoiding excessive jargon unless speaking with another IT professional. He uses common, understated slang like 'kinda,' 'stuff,' and 'figure out.' He avoids overly casual language or hyperbole, preferring factual descriptions. His tone is generally calm and reassuring, even when discussing complex problems.

Personality traits

  • methodical
  • detail-oriented
  • patient
  • resourceful
  • calm under pressure
  • analytical
  • conscientious
  • observant
  • dependable

Goals

  • Achieve a senior engineer position within his firm
  • Obtain advanced certifications in cloud infrastructure or cybersecurity
  • Expand his home lab capabilities for more complex testing and learning
  • Develop a personal side project involving home automation
  • Maintain a healthy work-life balance without sacrificing professional growth

Problems & frictions

  • Client environments are often inconsistently configured, leading to unexpected issues
  • Balancing urgent, high-priority tickets with scheduled maintenance tasks
  • Limited budget for advanced diagnostic or recovery tools at the firm
  • Keeping up with the rapid pace of technological change across various platforms
  • Dealing with users who have made significant, undocumented changes to their systems

Values

  • reliability
  • clear documentation
  • client trust
  • efficiency
  • problem-solving

Interests

  • Windows troubleshooting
  • small-business IT
  • home lab networking
  • cybersecurity basics
  • DIY electronics

Media habits

  • Subscribes to tech news aggregators (e.g., Ars Technica, The Verge)
  • Watches YouTube tech repair and DIY channels
  • Listens to tech podcasts during commutes
  • Active on IT professional forums and subreddits
  • Occasional browsing of online tech documentation and vendor blogs

Questions & answers

Troy Beahan’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at WebbyAcad OST File Recovery Software (https://www.techjockey.com/detail/webbyacad-ost-recovery-tool): 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).

    The starting price for this tool is $39, which seems reasonable for occasional use. If it reliably recovers data without issues and supports multiple export formats, I'd consider a one-time purchase of around $75 to $100. For a monthly subscription, I wouldn't pay more than $10, as we don't have a constant need for this, and it's more of a tool for specific client situations. I'd expect it to be straightforward to use and provide clear documentation of the recovered data. The pricing basis is listed as 'per month subscription' in the product blurb, but the $39 is listed as a starting price with 'View plans' and 'Licenses' for Personal, Business, Corporate, and Enterprise. It's a bit unclear if the $39 is a one-time fee or a monthly subscription.
    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.