Why this persona fits the audience
Oversees a 4-person web agency in Manchester and keeps 3 client repos moving on a Mac Studio and MacBook Air. He starts Claude Code or Gemini sessions for small fixes, checks the latest notes at the end of the day, and uses a shared spreadsheet to see what each agent touched.
- Age: 44
- Location: Manchester, UK
- Occupation: Technical Director, Digital Agency
- Income: £78k
- Education: HND Information Technology
- Company size: 5 people (including himself)
- Years in role: 6
“I don't care how fast you write the code if I can't prove exactly what it did when the lights go out.”
Josh Hammes is a 44-year-old Technical Director based in Manchester, UK, who has spent nearly two decades navigating the shifting tides of web development. Holding an HND in Information Technology, he transitioned from a solo freelancer to leading a boutique agency, now employing four staff members. His career is defined by a relentless pursuit of operational stability; he built his reputation on delivering complex web applications on time and under budget, a feat he achieved by obsessively refining his internal workflows. In recent years, Josh has been the first in his small team to integrate AI coding assistants like Claude Code and Gemini into daily operations, driven by the need to scale output without scaling headcount proportionally. His workspace is a testament to his pragmatism: a sleek Mac Studio paired with a MacBook Air, serving as the nerve center for three active client repositories. Unlike many peers who adopt new tools impulsively, Josh treats technology as a utility to be stress-tested. He currently relies on a shared Google Spreadsheet to track which AI agents have touched which files, a makeshift solution born of necessity that he knows is fragile. He finds himself spending more time reconciling these logs than writing code, a friction point that gnaws at his sense of efficiency. Financially, Josh earns £78k, a comfortable salary that allows him to live securely in Didsbury but also makes him sensitive to wasteful spending. He views money as a resource for stability, not status. Professionally, he is driven by accountability; he cannot delegate the final responsibility for code quality, even when the code was generated by an algorithm. His recent decisions have focused on creating repeatable processes for AI interactions, trying to turn the chaotic potential of generative tools into a predictable manufacturing line. Despite his age and experience, he remains technically agile, constantly learning new frameworks, though he admits to feeling the fatigue of constant context switching. For Josh, the ideal future isn't about flashy new tech, but about a system where the machine does the heavy lifting, and the human remains the unshakeable guardian of quality.
Background & daily life
A day in their life
Josh wakes at 6:15 AM, brews coffee, and checks emails before the kids stir. By 7:45 AM, he's dropped the children at school and is commuting to his office. At 9:00 AM, he fires up the Mac Studio, reviewing the overnight log files from the AI agents working on Client A's React migration. He spends an hour verifying the changes in the terminal, then joins a 15-minute stand-up with his two juniors and a designer. Lunch is a quick sandwich eaten while reading a thread on GitHub issues. Afternoon blocks are dedicated to writing internal automation scripts or responding to Slack messages from clients. At 4:30 PM, he does a final sweep of the shared spreadsheet, ensuring every agent action is logged. He leaves at 5:30 PM sharp, takes the train home, and spends an hour helping his son with math homework before dinner. Evenings are screen-free unless there's a critical server alert.
Lifestyle
Josh lives in a semi-detached Victorian house in Didsbury, a leafy suburb where he values quiet over noise. His routine is rigid: early mornings with coffee before the kids wake, evening walks along the River Irwell to decompress, and weekends reserved for family or fixing things around the house. He is financially comfortable but not extravagant; money is allocated to savings and home improvements rather than luxury cars. Health-wise, he manages mild back pain from long hours at his desk by swimming twice a week. Socially, he maintains a tight circle of three close friends from university and relies heavily on his partner for emotional grounding, preferring deep one-on-one conversations over large gatherings.
Work life
As Technical Director of a four-person agency, Josh wears every hat except sales. His day is a constant juggle between architecting solutions for clients and debugging his own team's output. He runs a dual-machine setup: a powerful Mac Studio as the command center and a MacBook Air for client meetings. The pressure is high; with only three active client repositories, any bottleneck affects everyone. He spends his mornings reviewing code pulled by AI agents and his afternoons managing expectations. He trusts his team implicitly but micromanages the *process* of how they work, ensuring every commit has a traceable reason. The stress isn't about the work itself, but the lack of visibility into where time is actually being spent versus where it appears to be going.
Relationships
Josh is deeply embedded in the Manchester tech scene through informal meetups but remains somewhat introverted outside of work. His primary influence comes from his partner, Sarah, who grounds him in reality, and a former mentor who still challenges his technical assumptions. He has a strong bond with his children, often involving them in simple coding projects to teach logic. While he respects local peers, he rarely seeks validation from them, preferring to trust his own data and results. He values loyalty above all in personal connections, having known his closest friends for over two decades.
How they decide
Josh is a cautious, evidence-based decision-maker who dislikes impulse buys. He approaches new tools by creating a controlled test environment, running them against existing workflows for at least two weeks, and measuring concrete outputs before committing. He is influenced more by peer reviews and open-source community feedback than marketing copy. If a tool lacks transparency in its pricing or data handling, he will walk away immediately. He prefers incremental adoption—trying one feature at a time—rather than overhauling his entire stack at once.
How they sound
Josh speaks with a flat, direct Mancunian cadence, avoiding fluff or corporate jargon. He uses precise technical terms like 'idempotent', 'merge conflict', and 'latency' naturally. He tends to pause briefly before answering complex questions, thinking through the logic aloud. He avoids hyperbole ('game-changing', 'revolutionary') and prefers qualifiers like 'potentially useful' or 'needs testing'. He doesn't use slang frequently but might drop a dry British idiom like 'bit of a faff' when describing inefficiencies. His tone is professional yet approachable, never condescending but firm on boundaries regarding scope creep.
Personality traits
- Methodical
- Direct
- Systematic
- Guarded but fair
- Time-obsessed
- Pragmatic optimist
- Detail-oriented
- Steady under pressure
- Skeptical of hype
- Process-driven
Goals
- Standardize the handover process between junior devs and AI tools to reduce onboarding time by 30%
- Build a proprietary internal dashboard that tracks all automated tasks without manual logging
- Increase agency profit margins by automating 20% of repetitive maintenance tasks
- Achieve a consistent 45-hour work week to reclaim weekend evenings
- Mentor the two junior developers into senior roles within the next two years
Problems & frictions
- Fragmented visibility across multiple terminal windows and chat logs makes auditing agent work difficult
- Inconsistent documentation when AI agents generate code leads to knowledge gaps for human team members
- Difficulty quantifying the ROI of time saved by AI vs. the time spent setting up prompts
- Reliance on a static Google Sheet that becomes outdated immediately after updates are made
- Balancing the speed of AI generation with the need for rigorous code quality assurance
- Keeping up with rapidly changing CLI tools while maintaining stable legacy systems for clients
Values
- delivery
- accountability
- repeatable processes
- pragmatic efficiency
- transparency
Interests
- agency operations
- web app maintenance
- automation scripts
- low-code architectures
- local football (Man Utd)
Media habits
- Skims Twitter/X for dev tool leaks
- Subscribes to 'The Changelog' podcast
- Reads Hacker News during lunch
- Follows niche Substack newsletters on SaaS ops
- Uses LinkedIn sparingly for industry news
- Watches tech YouTube tutorials on weekends