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

Floyd Miller

Floyd Miller

Claims automation business analyst at an MGA

Full-depth AI personas

Why this persona fits the audience

Sits between product and claims ops for a 3-person automation squad at a Texas MGA. He maps claims handoffs, writes requirements for intake and task-routing changes, and tests exports from the claims platform before rollout.

  • Age: 29
  • Location: Austin, Texas, USA
  • Occupation: Claims automation business analyst
  • Income: US$96k/year
  • Education: Bachelor's degree in computer science
  • Company size: Mid-sized MGA (approx. 150 employees)
  • Years in role: 4
“Every process, no matter how messy, can be broken down, understood, and ultimately, optimized.”

Floyd Miller's journey into claims automation began not with an immediate passion for insurance, but with a fascination for how systems work. Growing up in suburban Texas, he was the kid who took apart the family VCR and rebuilt it, driven by an insatiable curiosity about underlying mechanics. This led him to pursue a Bachelor's in Computer Science at the University of Texas at Austin. After graduation, he gravitated towards roles where he could apply his analytical skills to real-world problems, eventually landing at a Texas-based MGA. His current role as a Claims Automation Business Analyst is a perfect fit, allowing him to blend his technical acumen with a pragmatic approach to improving operational efficiency. He sits at a critical junction, translating the needs of claims operations into functional requirements for a small, dedicated automation squad, and then meticulously testing the outputs. His daily work involves dissecting claims handoffs, writing detailed user stories for intake and task-routing enhancements, and rigorously validating data exports from the core claims platform before any changes go live. This constant cycle of analysis, design, and testing fuels his drive for systems thinking and speed. He recently championed a small but impactful change that automated the initial triage of low-complexity claims, significantly reducing manual assignment time. Outside of work, Floyd's pragmatism extends to his personal life; he diligently saves a portion of his $96k income, viewing it as a tool for future freedom and opportunities, whether that's investing in new tech for his coding side projects or funding his passion for fishing. He's not driven by status, but by a quiet satisfaction in building and improving things, whether it's a more efficient claims workflow or a personal app for tracking fishing conditions.

Background & daily life

A day in their life

Floyd's typical weekday starts around 7:30 AM with a quick check of industry news and personal emails over coffee. By 8:30 AM, he's logged into the company's VPN, diving into his claims platform dashboards. The morning is usually dedicated to mapping a new claims intake process or writing user stories for the development team. Lunch is a brief, often solo affair at his desk while reviewing code snippets for a side project. The afternoon involves collaborating with claims adjusters to refine requirements or testing recent automation updates. Around 5:30 PM, he logs off, often heading to the gym or starting his coding side project, and then cooks dinner. He might catch an F1 race replay or read technical documentation before bed.

Lifestyle

Floyd lives a structured but dynamic life in Austin. His weekdays revolve around optimizing work processes, punctuated by coding sessions after dinner. Weekends often involve early morning fishing trips to nearby lakes or catching up on the latest Formula 1 races, often with friends at a local sports bar or his apartment. He enjoys exploring Austin's growing craft brewery scene, viewing it as another form of process experimentation. Financially, he's pragmatic, saving diligently for future investments and mindful of his income, but not afraid to spend on tech gadgets or weekend getaways.

Work life

Floyd's role as a Claims Automation Business Analyst is central to his professional identity. He thrives on dissecting complex claims workflows and translating them into actionable automation requirements. His daily grind involves deep dives into the existing claims platform, mapping intricate handoffs, and meticulously documenting user stories for the 3-person automation squad. He collaborates closely with both the product development team and claims operations, acting as a crucial bridge. The pressure is on to deliver tangible improvements in efficiency and reduce manual touchpoints, making his testing of platform exports and new intake processes a critical step before any rollout.

Relationships

Floyd maintains a close-knit circle of friends, many met through college or shared hobbies like fishing and F1. His parents, who live in a smaller town outside of Houston, are proud of his career but don't fully grasp the technical details. His automation squad colleagues are his primary work influence; they challenge his assumptions and collaborate on solutions.

How they decide

Floyd is a research-heavy and pragmatic decision-maker. He meticulously gathers data, analyzes options from multiple angles, and often builds small prototypes or proofs-of-concept to validate his choices before committing. He values efficiency and long-term viability, preferring solutions that offer scalable benefits over quick fixes. While he listens to his colleagues' input, the final decision is usually based on his own thorough investigation and logical assessment of the system's impact.

How they sound

Speaks clearly and concisely, with a measured cadence. Uses precise, technical language when discussing work but can switch to more casual, enthusiastic tones when talking about his hobbies. Avoids hyperbole and focuses on facts and logical explanations. Occasionally uses mild tech jargon, but generally tries to be understood by a broader audience. His tone is generally calm and confident, reflecting his problem-solving approach.

Personality traits

  • analytical
  • detail-oriented
  • methodical
  • proactive
  • resourceful
  • curious
  • calm under pressure
  • results-focused

Goals

  • Become a senior analyst specializing in AI-driven claims optimization
  • Develop a personal app that streamlines local fishing trip planning
  • Achieve financial independence through smart investing
  • Contribute to open-source projects related to data processing
  • Master advanced data visualization techniques

Problems & frictions

  • Navigating legacy system limitations that hinder full automation potential
  • Balancing the need for rapid implementation with thorough testing and validation
  • Communicating technical intricacies of automation to non-technical stakeholders in claims operations
  • Keeping up with the rapid pace of AI advancements and identifying relevant applications
  • Data silos and inconsistencies across different claims modules

Values

  • systems thinking
  • pragmatism
  • speed
  • efficiency
  • data-driven decisions

Interests

  • coding side projects
  • fishing
  • Formula 1
  • craft breweries
  • data visualization

Media habits

  • Follows tech news sites (e.g., TechCrunch, The Verge)
  • Listens to podcasts on AI, automation, and F1 during commute
  • Uses Reddit for coding forums and hobby discussions
  • Watches YouTube tutorials for coding and data analysis
  • Reads industry blogs related to insurance technology

Questions & answers

Floyd Miller’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Modernize customer journeys, reduce expenses, and increase capacity through AI-driven insights and process automation. 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 hurdle we face is integrating AI insights with our existing, somewhat legacy, claims platform. We're talking about modernizing customer journeys and reducing expenses, but our current system has limitations that make full automation tough. We've tried mapping out new workflows and writing detailed requirements, but the underlying tech just doesn't always support the level of AI integration we're aiming for. It's a constant battle between what's technically feasible and what the business needs. I haven't quantified the exact cost in time or lost customers, but it definitely slows down our ability to implement impactful changes.
    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.