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

Marshall Kuhn

Marshall Kuhn

Technical lead at a 6-person web agency

Full-depth AI personas

Why this persona fits the audience

Coordinates dependency checks for 20+ client repos, with a split of PHP/Composer and Node projects. Uses spreadsheets, GitHub notifications, and occasional hand reviews to note which packages need updates.

  • Age: 41
  • Location: Manchester, UK
  • Occupation: Technical Lead
  • Income: £78k base
  • Education: BSc Information Systems
  • Company size: 6 employees
  • Years in role: 3
“I've learned the hard way that 'it'll just take a minute' is how technical debt starts. Every refresh, every update—it's all about not leaving problems for future-you to handle.”

Marshall Kuhn, 41, built his career on a foundational principle: technical compromises come back to bite you. After a decade in various UK agencies, he landed at his current 6-person shop where his greatest challenge isn't coding but maintaining the invisible infrastructure surrounding it. His dependency management system—a combination of GitHub alerts, Google Sheets, and occasional brute-force audits—has become legend among junior developers, some of whom whisper (not affectionately) about his '18-column spreadsheet of doom'. Recently, he spent three weekends automating composer update checks, only to discover his solution caused merge conflicts. The experience reinforced his belief that any tool must be deeply understood before being trusted with client work. Professionally, he's respected for his patience with technical debt (a term he abhors—'it's just bad decisions with consequences') and feared for his meticulous code reviews. His greatest professional regret is not learning Docker sooner, though he's currently building a Laravel app to justify the learning curve. At home, his DIY projects follow the same pattern—research until paralysis, execute with obsessive precision, then discover one critical missing tool. His daughters describe him as 'the only person who gets stressed about garden sheds'. Financially stable but perpetually hustling, his biggest worry isn't income but time—there's always one more thing to fix, one more update to apply. His workstation is a shrine to parallel systems: multiple monitors displaying client repos, his dependency tracker, and Laracasts tutorials running in the background. Colleagues often joke he's 'a man who could optimize a Saturday', though they know better than to suggest he take a day off. His philosophy is simple: 'If you're going to do something, do it properly. And if you can't do it properly, don't do it at all.' It's a mentality that serves him well in development but has left his garden office 20% unfinished for 18 months.

Background & daily life

A day in their life

Marshall's weekdays start at 6:15am with coffee and GitHub notifications—he's learned to ignore most 'low priority' alerts but checks each one just to be sure. Breakfast is a rushed affair with his daughters while planning the day's sprint. By 8:30am he's at the office, first task being to update his dependency spreadsheet (a ritualistic process involving three monitors). Mid-morning is spent reviewing a junior developer's pull request for a Laravel upgrade—he finds two undiscovered vulnerabilities and adds them to the spreadsheet. The afternoon involves a tense standup about a client project behind schedule, where he pushes for dependency updates to be prioritized (met with some eye-rolling). After work, he picks up his daughters, then spends 45 minutes debating with his wife about whether to hire a roofer for that tree issue or 'just do it himself'. Dinner is quiet, then he returns to his laptop to prototype a script that might automate some of his dependency checks. By 10:30pm, he's still up updating his home project Trello board, feeling guilty about the unfinished garden office.

Lifestyle

Marshall lives in a semi-detached house he's slowly renovating in Salford, where he balances the chaos of teenage daughters with his love for control in professional spaces. His mornings start with strong black coffee and a quick scan of GitHub alerts before the family breakfast routine. Weekends alternate between football coaching responsibilities and building a garden office—currently on hold due to a debate between cedar or oak cladding. Financially conservative, he's focused on paying off the mortgage while his wife handles the family budget. Health-wise, he walks everywhere in Manchester but skips the gym, preferring to call his DIY endeavors 'workout enough'. Social life revolves around the local football club, the occasional pub quiz with agency colleagues, and occasional weekend trips to the Peak District.

Work life

As lead at a small digital agency, Marshall's days are split between client projects and maintaining the agency's technical infrastructure. His biggest time sink is dependency management across 20+ repos, where he juggles GitHub notifications, a meticulously maintained spreadsheet, and manual PHP/Composer audits. He's recently pushed for better documentation standards after a client panic about an outdated jQuery package. His team of 4 developers respect his technical knowledge but sometimes chaff at his insistence on manual review vs. automated tools. He's considering Laravel-specific services to streamline workflows but hesitates at the cost. Late nights are common when patching client vulnerabilities, and he's felt the tension between 'good enough' and 'perfect' security practices. His days often end with a 15-minute standup with his wife to sync on family logistics.

Relationships

Marshall's marriage is stable though slightly strained by his perfectionist tendencies in home projects. His wife, a physiotherapist, is his voice of reason when he overcomplicates things. His two daughters (14 and 16) are his greatest pride and frustration—he loves coaching them but despairs at their phones' constant notifications. Professionally, he trusts his agency's senior developer but has tension with the creative director over 'unrealistic deadlines'. He's loosely connected with Manchester's PHP meetup group but rarely attends, preferring to learn through forums. His local football network is his main social circle, where he's known as the 'bloke who actually knows the offside rule'.

How they decide

Marshall is a cautious, research-heavy decision maker who prefers data over hype. He'll prototype solutions himself before committing to external tools, often building temporary scripts to test concepts. In professional settings, he leans on peer validation but trusts his own technical judgment above all. Financially, he obsessively compares costs but hates feeling 'ripped off'—once a tool feels like an obligation, he'll find alternatives. Personal decisions are made with a mix of long-term planning (career, finances) and emotional investment (DIY projects, football).

How they sound

Marshall speaks in measured, practical terms with a slight Northern English cadence. He avoids jargon in client conversations but uses technical shorthand with colleagues ('That composer.lock needs a proper audit'). His sentences often include qualifiers ('Might be better to...', 'We could consider...') and he habitually prefaces opinions with 'From experience...'. He's quick to deflect credit ('That was really the dev's work') and equally quick to gently correct misinformation ('Actually, that package update is critical for...'). He's not one for motivational speech—prefers the blunt ('We need to fix this before it becomes a proper problem'). When frustrated, his sarcasm becomes more acid ('Of course the client will notice the security warning *after* launch').

Personality traits

  • Pragmatic problem-solver who distrusts over-engineered solutions
  • Quietly competitive (keeps dependency spreadsheet as the 'most accurate' reference)
  • Takes pride in personal system-building (hand-crafted Composer update workflows)
  • Moderate skeptic of SaaS tools (prefers to understand the internals before using)
  • Gets irritated when developers 'forget' to check package vulnerabilities
  • Deeply loyal to Manchester City FC (still bitter about 2012 Agüero goal)
  • Prefers to be the 'over-prepared' one in professional settings
  • Dislikes meetings that don't have clear action items
  • Enjoys the tactile satisfaction of physical work (DIY projects)
  • Socially adaptable but introverted by nature (thrives in small team settings)

Goals

  • Complete the garden office before winter (currently 60% done)
  • Reduce average package update time from 48 to 24 hours for client projects
  • Coach his daughters' team to league finals (currently 3rd in division)
  • Teach himself Docker in the new year (has been 'meaning to' for 18 months)
  • Pay off the mortgage 5 years early (current trajectory: 7 years early)
  • Find a better system for tracking agency-wide tech debt

Problems & frictions

  • Client repositories often have outdated packages with no clear ownership
  • Junior developers sometimes skip dependency checks when deadlines loom
  • His current spreadsheet system works but breaks when teams add new repos
  • Daughters' football schedule keeps conflicting with his preferred work hours
  • Neighbor's tree shed limbs on his roof during storms (should've cut it himself)
  • Wants to improve team documentation but hates writing it himself

Values

  • client accountability
  • practical problem-solving
  • cost discipline
  • reliability
  • self-sufficiency

Interests

  • Laravel development
  • local football (manages his daughters' U-16 team)
  • DIY home renovations
  • British real ale
  • minimalist productivity tools

Media habits

  • Listens to developer podcasts (Laravel News, Syntax) during commutes
  • Reads Hacker News and PHP The Right Way blog
  • Watches Football League highlights on YouTube
  • Subscribes to Home Improvement magazines
  • Uses GitHub daily but avoids Twitter

Questions & answers

Marshall Kuhn’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying NPM Scan (https://npmscan.io/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    As someone who juggles multiple client repos, I’m all too familiar with the dependency management nightmare. Right now, I rely on GitHub notifications, a rather overwhelming spreadsheet, and manual checks to keep track of outdated or vulnerable packages. The idea of a tool that centralizes this information is incredibly appealing, but there are a few hesitations. Firstly, I would need to ensure that NPMscan integrates seamlessly with my existing workflow without adding complexity. Additionally, I need to be confident that it covers all the dependency types we use, especially Composer and npm, and provides actionable insights. I also worry about access control and data privacy since we handle sensitive client information. If NPMscan can address these concerns and provide a clear, actionable format for our current stack, it could save me a great deal of time and stress. Given our budget constraints and the importance of this task, I’d be willing to spend up to $29 per month for a reliable solution that covers all our projects, as this aligns with the Agency pricing tier on their page. However, I’d need to verify that it’s more efficient than my current setup before committing.
    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.