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

Tom Ondricka

Tom Ondricka

Technical lead at a small web agency

Full-depth AI personas

Why this persona fits the audience

Leads a 5-person agency team in Manchester that uses Claude Code and Cursor to maintain multiple client codebases. Keeps client setup steps, deployment quirks, and standard fixes in Google Sheets and a docs folder because work shifts between sites and repositories weekly.

  • Age: 33
  • Location: Manchester, UK
  • Occupation: Technical lead
  • Income: GBP 68k
  • Education: BSc in Software Engineering
  • Company size: 5 people
  • Years in role: 4 years
“It's all about building things that last, not just for the client, but for us too – so we don't have to reinvent the wheel every other week.”

Tom Ondricka, 33, is a dedicated Technical Lead at PixelCraft Solutions, a small web agency nestled in the heart of Manchester. His journey into software engineering began with a BSc from a local university, where he developed a strong foundation in core principles. Four years ago, he joined PixelCraft, quickly rising to lead their five-person development team. His role is defined by the constant flux of client work; the agency specializes in maintaining and developing for a diverse range of businesses, from local SMEs to burgeoning tech startups. This necessitates a deep dive into multiple codebases, often on a weekly rotation. Tom's approach to managing this complexity is rooted in his conscientiousness and a strong sense of dependability. He meticulously documents every client's unique setup, deployment quirks, and standard fixes in a combination of Google Sheets and a shared Notion folder. This system, while functional, is a testament to his practical nature and his commitment to ensuring his team can navigate the shifting landscape of client projects efficiently. He relies heavily on AI coding assistants like Claude Code and Cursor, integrating them into his daily workflow to accelerate development and reduce repetitive tasks. His income of GBP 68k reflects his experience and the critical nature of his role in ensuring client satisfaction and project delivery. Tom is not driven by status or rapid career advancement; his focus is on building robust, maintainable systems and fostering a stable, collaborative environment for his team. He recently decided to invest more time in refining the agency's internal documentation processes, recognizing that the current system, while effective, is becoming increasingly unwieldy as the client roster grows. This decision stems from a desire for greater predictability and a reduction in the 'firefighting' that often consumes their workdays. His personal life is grounded in routine and shared experiences, balancing his professional dedication with his interests in football and woodworking, which serve as vital outlets for creativity and stress relief.

Background & daily life

A day in their life

Tom's typical weekday starts around 7:00 AM with a quick check of urgent emails and Slack messages before making coffee and having breakfast with Sarah. He cycles to the office by 8:45 AM. The morning is usually dedicated to focused coding, tackling complex bugs or new feature development for the agency's primary SaaS client, often using Claude Code for boilerplate or complex logic. After a quick team stand-up at 10:00 AM, he spends time reviewing pull requests, assisting junior developers, and updating the agency's internal documentation spreadsheets with any new deployment quirks discovered. Lunch is a quick sandwich at his desk while scanning tech news. The afternoon involves client calls, planning upcoming sprints, and troubleshooting issues for the bakery chain's website, where he meticulously follows the steps documented in their Google Sheet. He usually leaves the office around 6:00 PM, cycles home, and unwinds by cooking dinner or spending an hour in his workshop.

Lifestyle

Tom lives in a rented terraced house in Chorlton, Manchester, with his partner, Sarah, a primary school teacher. Their evenings are often spent cooking together, watching documentaries, or Tom tinkering in his small, well-organised shed at the bottom of the garden, working on intricate woodworking projects like custom shelving or small furniture pieces. Weekends are a mix of attending Manchester United matches (season ticket holder), cycling along the canal towpaths, or catching up with friends. He's financially responsible, prioritising saving for a house deposit over frequent holidays, and generally avoids impulse purchases.

Work life

Tom's days are a constant juggle of client demands and team support. He leads a small team of four developers at 'PixelCraft Solutions', a Manchester-based agency. Their work is highly varied, jumping between maintaining legacy systems for a local bakery chain, developing new features for a SaaS startup, and troubleshooting deployment issues for an e-commerce client. He relies heavily on Claude Code and Cursor for coding assistance and uses a meticulously organised Google Sheet and a shared Notion folder to track client-specific setup procedures, deployment quirks, and common bug fixes, as the team frequently context-switches between different projects and repositories.

Relationships

Tom is in a stable, long-term relationship with Sarah, who provides a grounding influence. His core social circle consists of a few close friends from university, with whom he shares a passion for football. Within the agency, he has a good working relationship with his team, built on mutual respect and shared challenges, though he tends to keep his personal life separate.

How they decide

Tom is a cautious and research-oriented decision-maker. He weighs practical benefits against potential downsides, often seeking out peer reviews or technical documentation before committing to a new tool or approach. He values reliability and proven solutions over novelty, preferring incremental improvements to radical changes, especially when client projects are involved.

How they sound

Tom speaks with a clear, measured Mancunian accent, avoiding overly technical jargon when speaking to non-technical colleagues. His tone is generally calm and pragmatic, rarely raising his voice. He tends to use phrases like 'right then,' 'let's have a look,' and 'the sensible approach would be...' He's not one for hyperbole or effusive praise, preferring understated acknowledgements of good work. He avoids slang that feels forced or overly trendy.

Personality traits

  • methodical
  • detail-oriented
  • loyal
  • reserved
  • analytical
  • self-motivated
  • pragmatic
  • patient

Goals

  • Achieve greater stability and predictability in client project workflows.
  • Mentor his team to become more autonomous and skilled.
  • Save enough for a deposit to buy a house with Sarah.
  • Complete a challenging woodworking project, perhaps a custom dining table.
  • Maintain a healthy work-life balance without sacrificing project quality.

Problems & frictions

  • The constant context-switching between disparate client projects leads to mental fatigue and occasional errors.
  • Onboarding new developers or bringing existing team members up to speed on a new client's specific setup is time-consuming and error-prone.
  • Keeping track of unique deployment scripts and troubleshooting steps for each client's environment is a manual, repetitive task.
  • Balancing the need for speed with the agency's commitment to quality code.
  • The pressure to deliver on tight deadlines for multiple clients simultaneously.

Values

  • dependability
  • practicality
  • teamwork
  • efficiency
  • problem-solving

Interests

  • agency life
  • football
  • woodworking
  • reading
  • cycling
  • local history

Media habits

  • TechCrunch
  • BBC News
  • The Guardian
  • football podcasts
  • YouTube tutorials
  • Reddit (r/webdev, r/programming)

Questions & answers

Tom Ondricka’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Mengram (https://mengram.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).

    This Mengram tool sounds interesting, particularly the idea of a shared memory for AI tools like Claude Code and Cursor. My main concern right now is the constant context-switching between client projects, which does lead to fatigue and occasional errors. Today, I manage this by meticulously updating our Google Sheets and Notion docs with client-specific details. While Mengram promises to solve the 'relearning' problem, I'm hesitant to introduce another tool without understanding how it integrates and if it adds more complexity. I'd need to see a clear demonstration of how it simplifies my current documentation process rather than just adding to it. The pricing isn't entirely clear for agency use cases, but if it significantly reduced the time spent documenting and troubleshooting, I might consider paying around $10 per month per developer, but I'd need to test it thoroughly first.
    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.