Glen Little-Gerlach

Why this persona fits the audience

Runs delivery for a 6-person web agency in London. He asks contractors to use coding agents for boilerplate and refactors, then reviews diffs himself, with run notes and model costs tracked in Sheets and GitHub issues; most tooling is free or built from scripts.

• Age: 42
• Location: London, UK
• Occupation: Technical Director, digital agency
• Income: £96k
• Education: BEng Software Engineering
• Company size: 6
• Years in role: 5

“The real trick isn't just making the code work, it's making it work reliably, efficiently, and in a way that doesn't create more problems than it solves down the line.”

Glen Little-Gerlach, 42, has carved out a niche as the Technical Director for a compact, six-person web agency based in the bustling heart of London. His journey into this role began with a BEng in Software Engineering, followed by several years honing his craft at various digital consultancies. He found his current position five years ago, drawn to the agency's focus on agile delivery and client-centric solutions. Glen is married to Sarah, a primary school teacher, and they share a comfortable life in East London, prioritizing saving and sensible financial planning over ostentatious spending. His income of £96k reflects his experience and the demands of his role, but he remains deeply committed to lean operations, a value instilled from his early career. He’s a pragmatist, always seeking the most efficient path to a high-quality outcome. This pragmatism is evident in his approach to AI development tools. Rather than adopting every new shiny object, Glen meticulously evaluates their utility. He’s currently integrating coding agents for tasks like boilerplate generation and code refactoring, but with a crucial caveat: he personally reviews all the diffs. This hands-on approach ensures quality control and allows him to track model costs and performance metrics diligently, primarily using Google Sheets and GitHub issues. Most of the tooling he employs is either free or built from custom scripts, a testament to his resourcefulness and commitment to cost-effectiveness. His decision to use contractors for initial AI-assisted development, followed by his own rigorous review, is a direct response to the need for predictable client delivery within budget constraints. He sees AI as a powerful assistant, but one that requires experienced human oversight to truly leverage its potential without introducing unforeseen risks. His cycling hobby isn't just for fitness; it's a mental reset, a way to clear his head and approach complex technical challenges with renewed focus. He views time and money as finite resources, to be managed with precision and foresight, ensuring that every investment, whether in technology or personal development, yields tangible returns.

Background & daily life

A day in their life

Glen's day typically starts around 7:00 AM with a quick scan of overnight emails and industry news while making coffee. He cycles to the office, arriving by 8:30 AM. The morning is usually a blur of stand-ups, client calls, and code reviews, often focusing on the output of coding agents used by contractors for initial drafts. Lunch is a quick affair, often eaten at his desk while reviewing project documentation or planning the afternoon's tasks. Afternoons involve more in-depth technical problem-solving, mentoring junior developers, and managing project timelines. He leaves the office around 6:00 PM, cycles home, and spends the evening with his wife, often discussing work challenges or planning weekend activities. He might spend an hour before bed reading tech articles or planning his next day's priorities.

Lifestyle

Glen lives in a modest but well-maintained flat in East London with his wife, Sarah, a primary school teacher. They've been married for ten years and are comfortable financially, though they're careful with spending, preferring to save for future travel or home improvements rather than impulsive purchases. His weekdays are structured around work, with evenings often spent catching up on industry news or tinkering with personal projects. Weekends are a mix of long cycling routes through the countryside surrounding London, visiting local pubs, and occasional social gatherings with a small circle of close friends. He prioritizes health, cycling to work most days and cooking most meals at home.

Work life

As Technical Director for a small web agency, Glen is the primary technical lead and delivery manager. He juggles client demands, team management, and staying abreast of rapidly evolving technologies. His team of five developers, plus a rotating cast of contractors, relies on him for technical direction and problem-solving. He's deeply involved in code reviews, particularly for AI-generated code, ensuring quality and adherence to project standards. The pressure is constant to deliver high-quality work on time and within budget, often requiring creative solutions to resource constraints. He spends a significant portion of his day in meetings, reviewing code, and managing project workflows.

Relationships

Glen is married to Sarah, who provides a grounding influence and a different perspective on life. His professional network consists of a few trusted former colleagues and agency owners he occasionally exchanges insights with. Within the agency, he has a collaborative but professional relationship with his team, respecting their expertise while guiding their work.

How they decide

Glen is a cautious and research-driven decision-maker. He prefers to gather data, understand the underlying mechanics, and assess potential risks before committing to a new tool or process. He values evidence and practical application over hype, often testing solutions with small, contained projects before wider adoption. Peer recommendations carry some weight, but only if backed by demonstrable results.

How they sound

Glen speaks with a clear, measured cadence, typical of a London professional. He avoids overly casual slang but isn't stiffly formal. His tone is generally calm and analytical, even when discussing challenges. He tends to use precise language, especially when discussing technical matters, and is comfortable with jargon within a professional context. He's not prone to hyperbole and prefers to state facts and observations directly. He might occasionally use understated British humour.