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

Morris Robel

Morris Robel

Automation consultant at a small agency

Full-depth AI personas

Why this persona fits the audience

Works as the technical half of a 3-person automation consultancy in Bristol, building browser-based workflows for clients and maintaining internal demos in Chrome and Edge. Uses Cline in VS Code, Playwright, and a paid browser automation platform to validate flows, capture pages, and hand reproducible steps to clients.

  • Age: 28
  • Location: Bristol, UK
  • Occupation: Automation Consultant
  • Income: GBP 62k
  • Education: BSc Computer Science
  • Company size: 3-person consultancy (micro-business)
  • Years in role: 4 years in current role
“If you can't reproduce it in a clean environment, it doesn't exist as a solution, only as a temporary fix.”

Morris Robel is a 28-year-old Automation Consultant residing in Bristol, UK, operating as the technical linchpin of a micro-agency alongside two partners. With a BSc in Computer Science from a UK university, he entered the workforce during the early rise of browser-based automation, quickly realizing that the gap between human intent and machine execution was best bridged by robust, scriptable interfaces. Over the past four years, he has carved out a niche in building bespoke browser workflows, specializing in the intersection of traditional Selenium/Playwright practices and the emerging wave of AI-driven agents. His daily reality involves a relentless pursuit of technical rigor; he spends hours validating flows across Chrome and Edge environments, ensuring that the reproducibility of his work meets the high standards required by enterprise clients. He relies heavily on Cline within VS Code and maintains a portfolio of internal demos that serve as both quality assurance benchmarks and sales tools. Despite his young age, Morris carries the weight of a small business owner's responsibility, balancing the creative freedom of coding with the commercial necessity of delivering reliable results. He is financially stable but conservative, viewing money as a tool for securing autonomy rather than status. Recently, he made the strategic decision to pivot some of his agency's focus toward AI agent orchestration, recognizing the market shift but remaining skeptical of unproven platforms. His life is a study in balance: a disciplined routine that supports deep technical work, a social circle that grounds him in reality, and a career defined by the quiet satisfaction of systems that just work.

Background & daily life

A day in their life

Morris wakes up at 6:30 AM, brewing strong coffee while checking GitHub notifications and scanning industry newsletters. By 8:00 AM, he's settled at his standing desk, tackling the most complex debugging tasks of the week while his brain is fresh. Lunch is a quick meal prep box eaten while reading documentation, followed by a 15-minute walk to clear his head. Afternoon hours shift to collaboration: a stand-up with his co-founders, a client demo where he walks them through a newly validated workflow, and responding to Slack threads. He often extends his workday until 7:00 PM to finish a critical Playwright test suite before the browser update cycle hits. Evenings are reserved for winding down—perhaps a run or cooking dinner—before returning to a personal coding project late at night if inspiration strikes, though he tries to limit this to avoid burnout. He ends the day by tidying his digital workspace, ensuring no loose threads remain.

Lifestyle

Morris lives in a slightly drafty but character-filled terrace house in Easton, Bristol, sharing rent with two colleagues from the design industry. His apartment is a hub of low-light productivity: multiple monitors, a custom mechanical keyboard, and shelves lined with tech books. He prioritizes health through occasional evening runs along the Avon Gorge and strict sleep hygiene, avoiding screens an hour before bed. Financially, he is cautious; while his income is solid for a junior-mid level, he saves aggressively for a potential property deposit in five years. Socially, he maintains a tight-knit circle of friends, mostly other developers or creatives, preferring quiet pub evenings or board game nights over loud clubs. He spends weekends tinkering with personal projects rather than traveling extensively, often converting free time into coding experiments.

Work life

As the technical backbone of a three-person Bristol consultancy, Morris splits his day between client delivery and internal R&D. Mornings are dedicated to deep work: debugging complex browser flows in Cline within VS Code and refining Playwright scripts for client-specific scenarios. Afternoons involve client calls where he translates technical constraints into plain English, ensuring they understand the fragility of automated workflows. He manages a shared repository of internal demos that must run flawlessly across Chrome and Edge, requiring constant validation against browser updates. The pressure comes from the need to be both a generalist and a specialist; one minute he's writing JavaScript logic, the next he's explaining why a captcha blocked their lead gen flow. There is little room for error, as the agency's reputation hinges on the reliability of the automations he builds.

Relationships

Morris has a supportive but busy family in Somerset who visit occasionally, though they don't fully grasp the nuances of his work. His primary professional influence comes from his co-founders, a marketing strategist and a sales lead, creating a balanced dynamic where he provides the 'how'. He has a close friend group of four, all working in tech or creative fields, with whom he shares frustrations about industry trends. In the broader community, he engages lightly on developer forums but rarely seeks mentorship, preferring to learn by doing. His relationship with his roommates is cordial and practical, centered around shared bills and household chores.

How they decide

Morris employs a research-heavy, evidence-based decision-making style. He rarely adopts new tools based on marketing claims alone; instead, he demands proof of concept, often running local sandbox tests or reviewing source code repositories. He values peer reviews and community feedback over executive endorsements. When evaluating options, he weighs technical debt implications heavily, preferring a slightly slower implementation if it ensures long-term stability. He is cautious with financial commitments, preferring modular subscriptions over large upfront licenses until he has verified the utility in a live environment.

How they sound

His speech is precise, measured, and devoid of unnecessary filler words. He tends to use technical terminology correctly but explains it simply when speaking to non-technical audiences. He avoids hyperbolic language like 'game-changing' or 'revolutionary,' preferring terms like 'significant improvement' or 'efficiency gain.' He pauses frequently to think, valuing accuracy over speed. There is a slight British understatement in his tone, even when discussing successes. He rarely uses slang unless among close peers, and he actively avoids jargon that obscures meaning. His cadence is steady, reflecting a mind that processes information sequentially.

Personality traits

  • Methodical about edge cases
  • Quietly confident in code
  • Prone to deep-focus sprints
  • Skeptical of hype cycles
  • Highly organized digital files
  • Prefers written over verbal communication
  • Values clean architecture over quick hacks
  • Empathetic to client confusion
  • Resilient under deadline pressure
  • Curious about AI capabilities beyond the buzzwords

Goals

  • Achieve senior-level autonomy by leading a major enterprise automation project independently
  • Build a library of reusable MCP server components to reduce repetitive setup time
  • Transition from hourly billing to value-based pricing models
  • Establish a thought leadership presence in the niche of browser-based agent orchestration
  • Save enough capital to fund a side-project that solves a specific pain point in local business workflows

Problems & frictions

  • Maintaining consistency across different browser versions causes unexpected script failures
  • Client expectations often outpace the current stability of AI-driven automation
  • Time spent documenting reproducible steps detracts from actual development time
  • Balancing the need for rapid prototyping with the requirement for long-term code robustness
  • Limited bandwidth to stay updated on every emerging AI agent framework without burning out
  • Difficulty quantifying the ROI of internal tooling improvements for non-technical stakeholders

Values

  • technical rigor
  • autonomy
  • client trust
  • reproducibility
  • pragmatic efficiency

Interests

  • workflow automation
  • AI agents
  • JavaScript
  • developer tools
  • mechanical keyboards
  • indie game development

Media habits

  • Follows specific subreddits on r/automation and r/webdev
  • Subscribed to newsletters like 'The Automation Weekly' and 'TLDR'
  • Listens to tech podcasts during commutes (e.g., Syntax, Changelog)
  • Active on GitHub following maintainers of open-source scraping libraries
  • Uses Twitter/X primarily for real-time tool updates and breaking dev news
  • Reads documentation before watching tutorials

Questions & answers

Morris Robel’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: AI devtools in the browser you're already signed into. the product is an AI browser automation extension and MCP server for Chrome, Edge, Firefox,… 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 single biggest problem I foresee is the potential for another layer of complexity and maintenance. We already juggle browser updates and platform compatibility. Adding an AI browser automation extension that needs its own MCP server sounds like more work to integrate and keep stable across Chrome and Edge, especially for clients who might not have the technical understanding to troubleshoot it. It could cost us significant time in debugging and potentially lead to customer frustration if it's not rock-solid, impacting our reputation for reliability. We've tried various browser extensions before, but they often lack the deep integration or control we need.
    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.