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

Boyd Beatty

Boyd Beatty

Shopify agency front-end developer

Full-depth AI personas

Why this persona fits the audience

Builds Shopify and headless storefronts for retail clients in a 7-person agency, translating Figma comps into reusable React and Liquid components and keeping a shared library of UI symbols for common ecommerce states.

  • Age: 38
  • Location: Manchester, UK
  • Occupation: Front-end developer
  • Income: GBP 72k
  • Education: BSc in Computer Science
  • Company size: 7 employees (Agency)
  • Years in role: 14
“A system that works today but breaks tomorrow is just a ticking time bomb we haven't noticed yet.”

Boyd Beatty is a seasoned front-end architect based in Manchester, operating at the intersection of e-commerce logistics and digital aesthetics. With a BSc in Computer Science and nearly fifteen years of industry experience, he has evolved from a novice coder into the primary guardian of code quality for a seven-person boutique agency. His current role demands a dual focus: delivering bespoke, headless storefronts for international retail clients while simultaneously curating a robust, shared library of React and Liquid components. This responsibility places him in a unique position where he must translate abstract Figma designs into performant, accessible, and maintainable code that scales across multiple brands. Boyd's career trajectory reflects a shift from pure development to architectural stewardship. In his early twenties, he was driven by the novelty of new frameworks, but his thirties have been defined by a pragmatic obsession with reliability. He is the person who notices when an icon set is inconsistent across three different client sites and immediately initiates a refactor to prevent future fragmentation. His workspace is a testament to this orderliness; every file is named logically, and his version control commits are descriptive and concise. He views technical debt not as a necessary evil, but as a moral failing of the process, constantly advocating for refactoring sessions despite the pressure of client deadlines. Outside of code, Boyd is a man of quiet intensity. He channels his competitive nature into running and football, finding solace in the predictable rhythms of sport after the chaotic nature of web development. Financially, he is secure but not ostentatious, preferring to invest in high-quality equipment and savings rather than luxury goods. He is currently navigating the complexities of balancing a demanding career with personal life, often sacrificing weekend leisure for critical production fixes. Despite the stress, he remains a cornerstone of his team, respected for his ability to de-escalate conflicts and provide clear, logical solutions to ambiguous problems.

Background & daily life

A day in their life

Boyd wakes at 6:30 AM, making coffee and checking the news briefly before heading out. He takes the tram to the city centre, arriving at the agency by 9:00 AM. The morning starts with a stand-up meeting where he clarifies blockers for the team, followed by deep work blocks dedicated to writing clean React hooks and reviewing pull requests. Lunch is often a quick sandwich eaten at his desk while reading documentation on the latest Shopify updates. Afternoons are reserved for client calls and collaborative coding sessions, often involving whiteboard sketches of component hierarchies. By 6:00 PM, he logs off to avoid burnout, spending his evening on fitness or family time. Weekends are strictly for rest, football, and personal projects, ensuring he returns Monday ready for another sprint.

Lifestyle

Boyd lives in a modernised Victorian terrace in Chorlton, a neighbourhood known for its village feel and coffee culture. His evenings are split between cooking elaborate meals—usually something requiring precision like risotto—and tinkering with his mechanical keyboard setup at the kitchen table. He is an avid follower of Manchester City, attending matches when work permits but mostly watching from home with a pint of local ale. Financially, he is cautious; he maximises pension contributions and avoids debt, preferring to buy high-quality tools that last rather than replace them annually. Socially, he maintains a tight circle of three close friends from university and regular weekly football viewing parties, preferring deep conversation over loud clubbing scenes.

Work life

At the agency, Boyd is the gatekeeper of code quality, responsible for bridging the gap between design files and functional commerce logic. His days are dominated by debugging complex Liquid logic in Shopify themes and refactoring React components for headless implementations using Hydrogen. He spends significant time maintaining their internal Design System, ensuring that icons and UI states remain consistent across all client projects. The pressure comes from tight launch deadlines and the need to keep the shared component library bug-free for six other developers. He rarely works alone; pair programming sessions are standard practice to ensure knowledge transfer and maintain code integrity.

Relationships

Boyd is married to Sarah, a graphic designer who understands the friction of creative workflows better than anyone. They share responsibilities for their household and the care of their cat. His closest confidants are two former university classmates who now work in fintech and product management in London; they meet monthly for dinner. Professionally, he looks up to the agency's CTO for architectural guidance but acts as a mentor to the junior developers joining the team. He is not politically active but stays informed through local community newsletters and trusted news outlets.

How they decide

Boyd operates on a 'measure twice, cut once' philosophy. He rarely makes impulsive decisions regarding tools or infrastructure. When evaluating new software, he relies heavily on peer reviews, documentation quality, and long-term maintenance viability rather than flashy marketing. He prefers to run small-scale proofs of concept before committing any part of the team to a new workflow. His choices are driven by data, logical consistency, and the potential impact on the team's long-term efficiency.

How they sound

His speech is measured, articulate, and devoid of unnecessary filler words. He uses precise technical terminology when discussing code but switches to plain English when explaining concepts to non-technical stakeholders. He tends to speak in complete sentences, often prefacing opinions with 'From a maintenance perspective...' or 'In my experience...'. He avoids hyperbole and rarely raises his voice, even during stressful sprints. Slang is minimal, mostly limited to industry-standard acronyms. He values clarity above wit in professional settings.

Personality traits

  • Meticulously organized
  • Pragmatic problem solver
  • Quietly confident
  • Process-oriented
  • Team-first collaborator
  • Patient under pressure
  • Detail-obsessed
  • Conservative risk-taker
  • Direct communicator
  • Systematic thinker

Goals

  • Achieve Principal Developer status within the next two years
  • Reduce technical debt in the agency's legacy Liquid codebase by 40%
  • Launch a personal open-source utility library for React/Shopify integration
  • Complete a marathon in under four hours
  • Secure a senior leadership role managing the frontend architecture team
  • Save enough capital to purchase a property in Greater Manchester

Problems & frictions

  • Fragmented icon sets across different client designs requiring manual cleanup
  • Time-consuming handover process between designers and developers due to missing asset metadata
  • Difficulty scaling the internal component library without bloating bundle sizes
  • Client requests for custom animations that break existing responsive breakpoints
  • Keeping up with rapid changes in the Shopify Headless ecosystem while maintaining stability
  • Balancing the need for perfect code with aggressive client launch timelines

Values

  • reliability
  • maintainability
  • teamwork
  • craftsmanship
  • efficiency

Interests

  • React
  • Liquid templates
  • football
  • design systems
  • mechanical keyboards
  • local craft beer

Media habits

  • Shopify Community forums
  • Reactiflux Discord
  • The Guardian tech section
  • Manchester Evening News
  • Twitter/X for dev trends
  • Spotify 'Deep Focus' playlists

Questions & answers

Boyd Beatty’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of ElastoUI (https://elastoui.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make ElastoUI 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).

    Currently, we're managing our UI icons by building them custom or sourcing free sets from various places, which can lead to inconsistencies. The biggest issue is maintaining a shared library across our projects. ElastoUI offers a centralized solution, which would be a definite improvement. However, without seeing the actual range and style of icons beyond the generic examples, it's hard to judge the quality. The "Free Ecommerce UI Icons Library" aspect is appealing, but it's unclear if there's a paid tier or what limits apply. If the free offering is comprehensive and high-quality, I wouldn't pay anything. If there were premium features or a more extensive set, I'd consider up to $15 per month, but that's contingent on a very robust offering.
    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.