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

Donald Hansen

Donald Hansen

Revenue operations manager

Full-depth AI personas

Why this persona fits the audience

Manages revenue reporting for a 2-person revops function at a London B2B software firm, using PostgreSQL and Google Sheets to pull pipeline and churn data; writes or edits SQL for weekly board decks and cross-checks results against CRM exports.

  • Age: 38
  • Location: London, UK
  • Occupation: Revenue Operations Manager
  • Income: £74,000/year
  • Education: BSc in Business & Economics
  • Company size: Small B2B SaaS firm (approx. 45 employees)
  • Years in role: 4
“If the numbers don't add up to the penny, the whole story falls apart, no matter how good the narrative sounds.”

Donald Hansen, 38, is a quintessential anchor in the chaotic ecosystem of a growing London B2B startup. Born in Surrey and educated with a BSc in Business & Economics, he found his stride not in pure finance or pure engineering, but in the intersection where business strategy meets database architecture. For the past four years, he has served as the Revenue Operations Manager at a mid-sized software firm, effectively acting as the de facto Chief Data Officer despite having a team of only two. His role is defined by a relentless pursuit of reliability; he views data not just as metrics, but as the moral compass of the organization. His technical toolkit is a testament to his pragmatism. While many peers rush toward expensive, all-in-one platforms, Donald prefers the transparency of PostgreSQL combined with the ubiquity of Google Sheets. He writes his own SQL, often spending hours crafting complex joins to pull pipeline velocity and churn data that standard CRM exports simply cannot capture. This hands-on approach stems from a deep-seated skepticism of black-box tools and a belief that if you can't explain the query logic, you shouldn't trust the result. Recently, Donald made the difficult decision to reject a proposed enterprise BI license, arguing that the customization costs outweighed the benefits for their current stage. Instead, he invested time in building a semi-automated validation script that runs every night, flagging anomalies before they reach the board. This decision, while time-consuming, has cemented his reputation as the person who ensures nothing slips through the cracks. He is driven by the twin desires of pace and accountability, often working late to ensure the Friday board deck is flawless. To his colleagues, he is the calmest person in the room during a crisis, provided the data is accurate. To himself, he is constantly balancing the need for speed with the imperative of perfection, a tension that defines his professional identity.

Background & daily life

A day in their life

Donald wakes at 6:15 AM in Clapham, immediately checking his phone for overnight US market updates and any critical alerts from the database monitoring systems. After a quick run and a shower, he commutes via train, using the hour to listen to finance podcasts while mentally rehearsing the day's query priorities. Upon arriving at the office around 9:00 AM, he bypasses email to dive straight into the PostgreSQL terminal, resolving a data inconsistency flagged by the sales director regarding Q3 churn rates. By 11:30 AM, he is in a sync with the product team, translating their vague feature requests into precise SQL filters for the upcoming cohort analysis. Lunch is a solitary affair at his desk, eating a pre-prepared meal while reviewing a new Python script to automate a recurring manual check. The afternoon is spent refining the visualizations for the Friday board deck, meticulously cross-referencing three different data sources to ensure absolute alignment. He leaves the office by 6:00 PM sharp, ensuring he makes it home for dinner, knowing that the mental load of being the final gatekeeper of financial data requires a clear head for the next morning.

Lifestyle

Donald resides in a modern, slightly compact apartment in Clapham with his partner, prioritizing convenience over space due to long commute times. His weekends are a structured mix of watching local cricket matches on TV and preparing meals for the week ahead, reflecting his need for control and efficiency. He is financially disciplined, contributing heavily to a pension fund and avoiding impulse purchases, viewing money as a tool for security rather than status. Socially, he maintains a small, tight-knit circle of university friends and work colleagues, preferring deep one-on-one conversations over large networking events. He stays physically active through running along the Thames, using the time to decompress from the mental load of daily data reconciliation.

Work life

At his London-based B2B software firm, Donald operates as the sole architect of truth for the revenue engine alongside one junior analyst. His days are dominated by the tension between the speed of sales cycles and the slowness of manual data verification. He spends hours writing and debugging SQL queries directly against their PostgreSQL database, often rewriting complex logic that the Sales team's native CRM tools cannot handle. The pressure peaks during the weekly board meeting preparation, where a single decimal error could undermine the company's valuation narrative. He relies heavily on a hybrid workflow: raw data extraction via SQL, transformation in Google Sheets for visualization, and rigorous cross-checking against Salesforce exports to ensure the 'single source of truth' remains intact.

Relationships

Donald's primary influence comes from his direct line manager, a former VP of Sales who values speed over process, creating a constant friction point. He is married to Sarah, an accountant who provides a grounding perspective on his financial anxieties and offers sharp critique on his logic. He has no children yet, which keeps his evenings relatively open for skill-building. His professional network is niche, consisting mostly of other RevOps practitioners on LinkedIn whom he follows for specific technical tricks rather than general industry news. He trusts few people with sensitive financial data, preferring to validate information personally before sharing it upward.

How they decide

Donald approaches decisions with a methodical, evidence-first mentality. He rarely acts on intuition alone, preferring to gather sufficient data points to construct a logical argument before committing to a course of action. He is cautious about adopting new workflows, especially those involving external vendors, requiring extensive testing in a sandbox environment before any full-scale implementation. Peer recommendations carry weight only if backed by tangible case studies or technical specifications. He is not impulsive; instead, he is a slow burner who conducts thorough due diligence, weighing the long-term maintenance costs against immediate gains.

How they sound

Donald speaks with a measured, clipped cadence typical of London professionals who value precision. He avoids hyperbole and emotional language, preferring terms like 'discrepancy,' 'variance,' and 'source of truth.' He rarely uses slang, though he might drop a brief cricket metaphor if the context fits. He tends to speak in complete, grammatically strict sentences, often pausing to choose the exact right word to avoid ambiguity. In conversation, he asks clarifying questions repeatedly until the scope of a request is undeniable. He avoids saying 'I think' or 'maybe' when discussing numbers, substituting them with 'the data indicates' or 'according to the schema.'

Personality traits

  • meticulously organized
  • data-skeptical
  • quietly authoritative
  • time-conscious
  • pragmatic problem-solver
  • loyal but demanding of accuracy
  • efficient communicator
  • risk-averse regarding financial data
  • methodical
  • grounded

Goals

  • Reduce the weekly board deck preparation time by 40% without sacrificing data integrity
  • Achieve a CRO certification within the next 18 months
  • Build a fully automated, self-healing dashboard system that requires zero manual intervention
  • Secure a promotion to Head of Revenue Operations as the company scales
  • Maintain a work-life balance that allows for consistent weekend cricket attendance
  • Eliminate all 'shadow Excel' files used by sales managers that contradict official reports

Problems & frictions

  • Frequent data discrepancies between the CRM export and the live PostgreSQL database that require hours of forensic investigation
  • Lack of dedicated engineering resources to build custom dashboards, forcing reliance on brittle spreadsheet hacks
  • The cognitive fatigue of constantly switching contexts between high-level strategy and low-level query syntax
  • Difficulty explaining complex data lineage issues to non-technical sales leadership who demand immediate answers
  • Limited budget approval for enterprise-grade BI tools, necessitating a patchwork of free or low-cost solutions
  • The risk of burnout during quarter-end close when manual validation processes peak in intensity

Values

  • reliability
  • pace
  • accountability
  • practicality

Interests

  • Excel shortcuts
  • sales ops
  • cricket
  • finance podcasts

Media habits

  • The Daily (podcast)
  • Financial Times newsletter
  • Cricket England live streams
  • LinkedIn technical threads
  • Local news apps

Questions & answers

Donald Hansen’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://mygeniesql.live (SQLGenie) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The "Free SQL Query Generator" sounds intriguing, especially the "Text to SQL" part. I'm always looking for ways to speed up data extraction, and the promise of turning plain English into runnable queries for PostgreSQL is appealing. What's unclear is how well it handles complex joins or our specific schema without a direct integration. I'd also want to understand the validation process – how robust is it compared to my own manual checks? If it can genuinely generate accurate, optimized queries for our PostgreSQL database without needing a lengthy setup or exposing our schema unnecessarily, I'd consider using it regularly. Signing up would depend on seeing concrete examples that match our data complexity.
    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.