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

Harold Jones

Harold Jones

Agency CTO supporting multiple client builds

Full-depth AI personas

Why this persona fits the audience

He leads a 4-person web agency in Manchester that ships prototypes and small SaaS builds on PlanetScale for clients. The team uses ChatGPT in a browser for query ideas, and they keep migration notes and handoff details in spreadsheets because projects are short and budgets are tight.

  • Age: 41
  • Location: Manchester, UK
  • Occupation: Agency CTO / lead developer
  • Income: £110k owner income
  • Education: Bachelor's degree in computer science
  • Company size: 4 employees (including himself)
  • Years in role: 7 years as owner/CTO
“We don't have the luxury of fancy frameworks when the clock is ticking and the client is watching; we just need the right data moving fast enough to ship something that works.”

Harold Jones is the architect behind a nimble four-person web agency nestled in the industrial heart of Manchester, where the rain-soaked streets mirror the relentless pace of his digital output. At 41, he carries the weight of a Bachelor's degree in Computer Science and seven years of entrepreneurial grit, having transitioned from a senior role in a larger corporate entity to forge his own path. His agency specializes in high-velocity prototyping and small-scale SaaS deployments, leveraging modern tools like PlanetScale to deliver value quickly. However, this agility comes with a unique set of operational scars. Harold's workflow is a fascinating dichotomy: on one hand, he harnesses the power of AI-driven coding assistants directly in the browser to spark innovation and solve syntax puzzles instantly. On the other, his organizational backbone remains stubbornly analog, anchored in a labyrinth of meticulously maintained spreadsheets that track every migration step and handoff detail. This reliance on spreadsheets is not born of ignorance but of necessity. With budgets tight and project lifecycles compressed into weeks, Harold cannot afford the learning curve of enterprise-grade documentation suites or the hidden costs of premium plugins. Every minute spent configuring a new tool is a minute taken away from billing clients. Consequently, he has perfected the art of the 'good enough' system—manual logs that are readable, editable, and portable. His recent decisions reflect a cautious optimism; he has integrated AI into his daily coding loop but refuses to automate the critical path of client communication, fearing the loss of nuance. He is a man defined by reliability, a trait honed by the anxiety of running a small business where one missed deadline can ripple into lost reputation. While he dreams of a more streamlined future where data flows seamlessly between his code and his records, his current reality is a masterclass in resourcefulness, balancing the cutting edge of technology with the timeless discipline of pen-and-paper record-keeping.

Background & daily life

A day in their life

The alarm goes off at 6:30 AM. Harold checks his phone for any overnight server alerts, then grabs a black coffee and scrolls through Hacker News. By 8:00 AM, he's dropped the kids at school and is back at his desk by 9:15 AM. The morning block is dedicated to deep work: writing complex SQL queries for a client's new inventory system and reviewing the previous night's commits from his junior developer. Lunch is a quick sandwich eaten at his desk while skimming a PlanetScale blog post about recent feature updates. Afternoons are chaotic; a client calls about a migration delay, requiring immediate troubleshooting via the browser-based chat tool. He spends an hour updating a master spreadsheet, meticulously logging table changes and version numbers. By 5:30 PM, he wraps up with a brief stand-up call with the team, assigning tasks for the next day. He leaves the office at 6:00 PM, stops for groceries, and is home by 7:00 PM for dinner. Evenings are for reading fiction or fixing a leaky tap, keeping screens away until bedtime.

Lifestyle

Harold lives in a semi-detached home in Didsbury, enjoying the balance of suburban quiet and city proximity. His routine is rigid: 6:30 AM start with coffee and news, followed by school runs at 8:00 AM sharp. Evenings are reserved for family dinners and helping his children with homework, strictly screen-free after 7 PM. He maintains a moderate fitness regime, playing casual tennis every Tuesday and Thursday morning before work to clear his head. Financially, he is prudent; while his income is solid, he treats every pound of business revenue as a buffer against economic volatility, avoiding luxury splurges in favor of investing in reliable infrastructure. Socially, he connects primarily through the Manchester tech meetup circuit, preferring one-on-one deep dives over large networking parties.

Work life

As the de facto CTO and lead dev, Harold manages four distinct client streams simultaneously, often juggling a high-stakes SaaS prototype for a fintech startup alongside a rapid MVP for a local retail chain. His day revolves around code reviews, database schema optimization, and ensuring the team's reliance on free-tier tools doesn't become a liability. He spends hours manually updating Excel sheets to track database migrations and deployment handoffs, viewing these spreadsheets as the single source of truth for his small team. The pressure is constant but manageable; he prides himself on shipping functional products within tight budget constraints, often rewriting legacy code or optimizing SQL queries late into the evening to prevent future bottlenecks.

Relationships

Harold relies heavily on his wife, Sarah, who manages the household finances and provides the emotional anchor that allows him to focus on business risks. His professional network consists of about eight trusted peers in the Greater Manchester area whom he consults on specific architectural dilemmas. He has no direct mentors anymore, having moved past that stage, but he actively seeks out younger developers to mentor, finding satisfaction in their growth. His relationship with his team is collaborative but hierarchical; they look to him for final technical decisions, and he views their retention as critical to the agency's survival.

How they decide

Harold operates on a 'verify first, deploy later' philosophy. He is not impulsive; if a new tool or process is introduced, he demands concrete evidence of its reliability and ROI before committing. He rarely makes decisions based on hype cycles or peer pressure alone. Instead, he conducts small-scale pilots, often using his own spare time or a low-stakes internal project to test viability. His decision-making is deeply rooted in risk mitigation; he prefers the 'known devil' (a spreadsheet) over an 'unknown angel' unless the data clearly demonstrates a reduction in long-term friction or cost.

How they sound

Harold speaks with a crisp, Mancunian accent, avoiding overly flowery language or tech jargon unless explaining it to a client. His cadence is measured and deliberate; he pauses to ensure precision rather than filling silence. He tends to use phrases like 'let's be practical,' 'what's the edge case here?' or 'keep it lean.' He avoids hyperbole and never promises the impossible. In meetings, he cuts straight to the point, asking clarifying questions before offering solutions. He is polite but firm when discussing timelines, often framing delays as 'scope creep' rather than personal failure.

Personality traits

  • methodical
  • calm under pressure
  • cost-conscious
  • direct communicator
  • protective of team time
  • detail-oriented
  • pragmatic innovator
  • steady-handed
  • bureaucratically wary
  • mentorship-focused

Goals

  • Systematize the current spreadsheet-heavy documentation process to save 10+ hours per project cycle
  • Transition from reactive firefighting to proactive architectural planning for client scalability
  • Increase agency profit margins by reducing manual overhead without hiring additional headcount
  • Establish the agency as a go-to partner for PlanetScale-based rapid development in the North West
  • Achieve a sustainable work-life balance where weekends remain entirely device-free
  • Mentor junior developers to take ownership of migration logic, freeing up his strategic time

Problems & frictions

  • Fragmented knowledge storage across disparate browser tabs and unstructured spreadsheets
  • Difficulty tracking complex database migration paths for short-term client contracts
  • Time lost context-switching between raw SQL queries and chatbot-generated snippets
  • Risk of human error when manually documenting handoff details for non-technical clients
  • Limited bandwidth to maintain detailed technical specs amidst urgent delivery deadlines
  • Balancing the need for speed with the necessity of maintaining clean, documented codebases

Values

  • reliability
  • client trust
  • lean operations
  • pragmatic efficiency
  • technical debt avoidance

Interests

  • agency management
  • rapid prototyping
  • SQL architecture
  • B2B SaaS scaling
  • local tech community networking

Media habits

  • TechCrunch and Hacker News morning scan
  • LinkedIn for industry trends
  • Podcasts during commute (e.g., 'Software Engineering Daily')
  • GitHub repositories for specific library updates
  • Reddit r/webdev for peer troubleshooting

Questions & answers

Harold Jones’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Show HN launch (11 pts, 2023-04-20): We built a PlanetScale plugin for ChatGPT. Site shows pricing/signup. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    A PlanetScale plugin for ChatGPT? Interesting. Our biggest problem isn't really with PlanetScale or ChatGPT individually, it's the manual effort of connecting the dots. I spend at least an hour, sometimes two, each week updating our spreadsheets with migration notes and handoff details. This is crucial for our short-cycle projects, but it's tedious and prone to human error. We've tried more structured documentation, but the overhead kills our tight budgets. I'd need to see how this plugin specifically streamlines that documentation process without adding complexity or cost. Does it automate log creation or integrate directly with our existing workflow?
    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.