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

Guy Hettinger

Guy Hettinger

Product marketing manager

Full-depth AI personas

Why this persona fits the audience

Owns customer-facing FAQs and onboarding docs for a UK fintech with 2 support agents and a designer. Uses Intercom Articles, Figma, and a release spreadsheet to keep help pages aligned with weekly product changes and compliance updates.

  • Age: 41
  • Location: London, UK
  • Occupation: Product Marketing Manager
  • Income: £86k/year
  • Education: Master's degree in marketing
  • Company size: Series B startup (approx. 65 employees)
  • Years in role: 3
“In this industry, trust isn't just a brand value; it's the only currency that matters, and if your documentation doesn't match reality, you've already lost it.”

Guy Hettinger is a seasoned Product Marketing Manager based in London, operating at the intersection of fintech innovation and strict regulatory compliance. At 41, he brings nearly two decades of experience to his current role at a Series B startup, where he serves as the primary custodian of all customer-facing documentation. His career trajectory reflects a steady climb from general marketing roles into specialized product communication, driven by a fascination with how technology impacts user behavior and legal obligations. He holds a Master's degree in Marketing from a prestigious London university, a foundation that supports his meticulous approach to content strategy. Currently, Guy navigates a high-pressure environment where product teams iterate weekly, yet the documentation must remain legally watertight. He personally manages the entire lifecycle of help articles using Intercom Articles, coordinating closely with a lean design team via Figma and maintaining a granular release spreadsheet that maps every code change to a knowledge base update. This manual orchestration is his greatest challenge; while effective, it consumes hours that could be spent on strategic initiatives. His recent decisions have focused on tightening the feedback loop between support agents and product managers to catch discrepancies earlier, though the sheer volume of updates often keeps him in a reactive state. Outside of work, Guy is a man of discipline. He trains rigorously for marathons, treating his physical fitness with the same systematic planning he applies to his job. He lives in a vibrant part of London, surrounded by the city's tech pulse, but finds solace in quiet routines and historical sites. His income of £86k provides a comfortable life, allowing him to invest wisely and plan for a secure future, though he remains acutely aware of the volatility inherent in the startup world. To his colleagues, he is the reliable anchor—the person who ensures that when the product changes, the truth follows immediately. He values precision above all, believing that in the financial sector, clarity is the ultimate form of respect for the customer.

Background & daily life

A day in their life

Guy starts his day with a 45-minute run along the canal, listening to a true-crime podcast to clear his mind. By 7:30 AM, he is showered and commuting into Shoreditch, checking the overnight email from the US-based engineering team regarding their latest API changes. At 9:00 AM, he joins the stand-up meeting, where he immediately flags a potential compliance risk in the new 'Instant Transfer' feature being released today. His morning is spent rewriting three help articles in Intercom, cross-referencing the Figma designs to ensure screenshots match the new UI. He takes a quick lunch break walking to a nearby park, then attends a sprint review where he pushes back on a vague description provided by a developer. Afternoon hours are dedicated to the master release spreadsheet, meticulously tagging every change with its corresponding regulatory clause. He finishes work by 6:30 PM, heading to the gym for weightlifting before picking up takeaway dinner and catching up on football highlights. He ends the evening reading a book on behavioral economics before bed, ready to repeat the cycle tomorrow.

Lifestyle

Guy resides in a modern, slightly noisy flat in Shoreditch, balancing the energy of London's tech hub with a need for quiet focus at home. His routine is rigid: he wakes at 5:30 AM for a run along the Regent's Canal before the city fully stirs. He is health-conscious, adhering to a strict diet and training schedule for local marathons. Financially, he is prudent but not frugal; he maximizes his pension contributions and invests in index funds, viewing money as a tool for security rather than status. Socially, he maintains a tight circle of childhood friends and colleagues, preferring deep conversations over large parties. His weekends are split between football matches at the Emirates or watching Premier League games with a small group, and tackling DIY projects around his flat.

Work life

As the sole guardian of documentation for a fast-moving fintech, Guy's day is a constant negotiation between speed and accuracy. He manages a tiny team of two support agents and collaborates daily with a designer and four engineers. His workflow relies heavily on Intercom Articles for publishing, Figma for visual guides, and a master Google Sheet that tracks every feature release against compliance requirements. The pressure is high because a single outdated FAQ can lead to regulatory breaches or a surge in support tickets. He spends his mornings syncing with engineering on what shipped last night and his afternoons drafting and refining content. He is often the bottleneck, ensuring that every change meets the strict standards of the UK Financial Conduct Authority before it goes live.

Relationships

Guy is married to Sarah, an architect who appreciates his structured nature. They have no children yet, which allows them flexibility for travel and weekend trips. His closest confidants are his parents, who live in Manchester, and a college roommate now working in software development in Berlin. At work, he relies heavily on his relationship with the Head of Product, though they occasionally clash on timelines. He is a regular fixture at the local pub near his office, where he has built a reputation as the person who knows the latest industry regulations.

How they decide

Guy is a deliberate, research-heavy decision-maker who values data and peer validation over hype. He rarely makes impulsive purchases, preferring to test tools through free trials and consult internal stakeholders before committing budget. He analyzes the long-term maintenance costs and integration capabilities of any new system, prioritizing reliability and precision over flashy features. Once he verifies a solution fits his specific workflow constraints, he moves quickly to implementation.

How they sound

Guy speaks with a crisp, Received Pronunciation accent that softens slightly when relaxed with friends. His cadence is measured and precise, avoiding filler words like 'um' or 'like'. He favors professional terminology but explains complex concepts with simple analogies. In meetings, he asks clarifying questions early to avoid ambiguity later. He avoids hyperbole, emotional outbursts, or slang unless joking with close peers. He tends to use phrases like 'let's align on that,' 'the compliance angle is tricky,' and 'we need to verify the source.' He is polite but direct, never sugar-coating a critical error.

Personality traits

  • methodical
  • calm under pressure
  • detail-obsessed
  • diplomatic
  • proactive
  • structured
  • reliable
  • pragmatic
  • curious about systems
  • disciplined

Goals

  • Reduce the time-to-market for new help articles by 30% without sacrificing accuracy.
  • Achieve a 'zero-defect' audit score for all customer-facing documentation next fiscal year.
  • Mentor junior marketers on the intersection of product strategy and regulatory compliance.
  • Complete a full marathon within the next 12 months.
  • Build a more automated internal feedback loop between product teams and support.
  • Secure a senior leadership role focused on customer experience strategy.

Problems & frictions

  • The manual process of updating documentation lags behind rapid product iteration cycles.
  • Maintaining consistency across text and visuals when resources are stretched thin.
  • The fear of missing a subtle compliance nuance in a complex financial update.
  • Difficulty quantifying the ROI of documentation improvements to senior stakeholders.
  • Fragmented communication channels causing version control issues between teams.
  • The mental fatigue of constantly switching context between creative writing and technical logic.

Values

  • precision
  • trust
  • cross-functional coordination
  • regulatory adherence
  • efficiency

Interests

  • fintech regulation
  • product analytics
  • football
  • marathon running
  • historical architecture

Media habits

  • Financial Times (daily print)
  • The Telegraph (Sunday)
  • Twitter/X for tech news
  • Spotify podcasts during commute
  • LinkedIn industry groups
  • BBC Radio 4 Newsnight

Questions & answers

Guy Hettinger’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of DocCharm (https://doccharm.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make DocCharm better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I manage all customer-facing documentation using Intercom Articles, Figma for designs, and a detailed spreadsheet to track product changes against compliance updates. DocCharm's promise of automatically drafting updates based on product changes sounds incredibly appealing, given the hours I spend manually keeping our help pages current with our weekly releases. The key for me would be the accuracy of these drafts – if they truly capture the nuance of fintech compliance and product changes without extensive editing, that would be a significant improvement. My main concern is ensuring it integrates seamlessly without requiring a substantial engineering effort, as I only have limited support from that team. The ability for it to flag stale articles proactively is also a strong point. Given my current workload, anything that saves me time here is valuable, but I'm cautious about adding complexity or cost without clear ROI. I'd be willing to pay up to $150 per month, assuming the 'Starter' plan's article limits are sufficient for our needs.
    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.