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

Raymond Lucas

Raymond Lucas

Agency owner on a mixed filter stack

Full-depth AI personas

Why this persona fits the audience

He runs a 7-person digital agency in Lyon and manages client mail on cPanel and Ubuntu servers. A competitor filter is already installed on part of the fleet; the rest is handled with default server tools, manual allowlists, and periodic log review. He keeps MX records stable because some customers share hosting with outside DNS providers.

  • Age: 41
  • Location: Lyon, France
  • Occupation: Founder, digital agency and hosting services
  • Income: €63k equivalent, owner draw
  • Education: Master's degree in information systems
  • Company size: 7
  • Years in role: 9
“I've learned that 'works on my machine' is just a polite way of saying 'you'll spend three weeks debugging this.'”

Raymond Lucas founded his digital agency nine years ago after a decade as a systems administrator in corporate Lyon. The transition from wage slave to small business owner was initially freeing, though he quickly discovered that his writing skills needed 'serious patches' to handle client communication. His agency's 'patchwork stack' approach to technology reflects his philosophy: use what works until it doesn't, then find the simplest replacement. The current email filtering system is a case study in this - half his clients use a mid-tier commercial solution, the other half rely on his evening log reviews and manual blocklists. This inconsistency galls him, but client resistance to DNS changes keeps his hands tied. Raymond's technical decisions are made in the context of a strict triple constraint: client trust cannot be compromised, system reliability must be absolute, and solutions must ultimately save time (or appear to). His 7-person team operates with minimal process documentation - a situation he knows is unsustainable but hasn't found time to rectify. The upcoming maternity leave of his lead technician is forcing him to finally formalize some procedures, though he worries about 'losing the magic' of their ad-hoc problem solving. Despite these pressures, Raymond maintains a reputation among his small business clients for being the rare technician who explains things clearly without condescension. His personal philosophy of 'minimal viable status' keeps him from chasing industry trends, though he religiously follows developments in open-source email security. When not managing servers, he can be found at local cycling clubs or the Institut Lumière, where he occasionally volunteers to help restore vintage projectors. His apartment wall still displays the 2017 calendar marking '365 days without major outages' - a milestone he's determined to achieve again this year.

Background & daily life

A day in their life

Raymond's alarm goes off at 6:15am, though he's already been awake for 45 minutes reviewing overnight server logs. After a quick café au lait and a slice of baguette, he rides to the office, stopping to adjust the chain on his bike with tools he keeps in his messenger bag. The morning is a blur of client emails - one architect can't access invoices, a winery's newsletter is being marked as spam. By 11am, he's in the server closet, running another round of manual blacklist updates. Lunch is usually a takeaway salad eaten while watching a tech conference talk. Afternoons are spent working on the migration of a particularly stubborn client to the paid spam filter, though he keeps getting interrupted by 'urgent' requests like resetting a client's password. He leaves the office by 6:30pm, but checks his phone every 20 minutes during his evening walk through Parc de la Tête d'Or.

Lifestyle

Raymond lives in a modernized 19th-century apartment near Lyon's Croix-Rousse district, where he bikes to work daily along the Rhône. His home is spare but intentionally curated - an IKEA bookshelf holds physical backups of critical client data next to film books and vintage cycling magazines. He cooks simple meals (lentil soups, ratatouille) with ingredients from his balcony garden, though wine purchases remain a weak point. Health checkups are always scheduled but rarely attended, as he jokingly claims 'the server room is my cardio.' Weekends are divided between 80-mile cycling routes and the Institut Lumière, where he watches restored French New Wave films. His social circle is small but loyal - mainly former classmates from Lyon 1 University and a handful of agency clients who've become friends.

Work life

Raymond's agency handles mostly small business clients: local restaurants, architects, and wine merchants who need basic websites and email management. His 7-person team works from a shared workspace where 'Q3 client emails' is the standing joke over morning Nespresso. The cPanel servers hum in a rented data closet three blocks away - a compromise between cost and control. His mornings are spent resolving client panics (usually 'my emails disappeared!'), while afternoons are for the Sisyphean task of maintaining a patchwork spam solution. He's installed a mid-range competitor on half the server fleet, but the other half still uses manual blacklists and daily log reviews. The inefficiency gnaws at him, but client pushback about mixing DNS providers keeps him from switching.

Relationships

Raymond's family lives in Saint-Étienne, where he visits monthly, often bringing his mother obscure French postcards. His closest friends are fellow sysadmins he met at the 2016 Lyon Open Source Summit - they share a private Slack channel for 'venting about clients' and occasionally organize 'no-tech' hiking weekends in the Beaujolais. His colleagues describe him as 'a human YAGNI' (You Aren't Gonna Need It), though they respect his ability to foresee system failures others ignore. He's romantically single, though his dating app profile mentions 'bike mechanics > gym selfies' which sometimes backfires.

How they decide

Cautious but not inflexible - he'll test new tools in a sandbox for weeks before client deployment, but once convinced, implements changes decisively. Prefers peer review over vendor claims, and has been burned enough times to distrust 'revolutionary' promises. Will pay for solutions that demonstrably save time, though he'll begrudge the cost for years afterward.

How they sound

Speaks with measured cadence, often pausing to consider phrasing. Uses precise technical terms but avoids jargon when explaining to clients. Prefers short, declarative sentences over rhetorical questions. Has a habit of saying 'in an ideal world' before admitting compromises. Avoids business buzzwords and calls himself 'the permanent intern' when teaching new hires. His humor is dry, often self-deprecating, and delivered with a half-smile that makes it hard to tell if he's joking.

Personality traits

  • Fastidious about system architecture but flexible in implementation
  • Prefers functional elegance over flashy solutions
  • Skeptical of vendor claims but open to evidence
  • Patient with clients' learning curves but impatient with inconsistency
  • Consciously avoids over-engineering for small problems
  • Takes pride in being the longest-tenured sysadmin of his client base
  • Mildly paranoid about data integrity after a 2017 backup failure
  • Has a dry humor that clients sometimes misread as brusqueness
  • Will meticulously document a process before delegating it
  • Prefer his mornings quiet and chaotic workdays predictable

Goals

  • To finally document all agency processes before he retires (whenever that is)
  • To ride the Route des Grandes Alpes next summer without stopping for coffee
  • To reduce his 3:1 work-life ratio below 2:1 by 2025
  • To automate another tedious task quarterly
  • To host a clientless weekend without checking logs

Problems & frictions

  • The inconsistent spam filtering leaves clients complaining about phishing scams
  • His lead technician's upcoming maternity leave terrifies him
  • Finding time to update his servers' SSL certificates before browser warnings scare clients
  • Balancing his perfectionist tendencies with agency profitability
  • The café downstairs' WiFi occasionally leaks into his server monitoring stats

Values

  • client trust
  • efficiency
  • clean systems
  • measured risk
  • autonomy
  • reliability

Interests

  • cycling
  • French cinema
  • open-source software
  • urban gardening
  • tech podcasts
  • local wine

Media habits

  • RSS feeds for tech blogs
  • Twitch for cycling livestreams
  • French arthouse films on MUBI
  • Medium long-form articles
  • French public radio (France Inter)

Questions & answers

Raymond Lucas’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying bashemail (https://bashpilot.com/bashemail/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    I'd be hesitant to try BashEmail this month, primarily because integrating a new system with my existing patchwork setup could disrupt my clients' stability—not to mention the resistance I'd face from those tied to their DNS providers. Right now, half my fleet already uses a competitor, and the other half relies on manual log reviews. Adding another layer might complicate things further. That said, if I did pursue it, the key selling point for me would be the promise of no MX or DNS changes, which aligns with my clients' needs. The $23 per month for the Standard plan seems steep, but it might be justifiable if it saves time and reduces manual log reviews. My maximum acceptable price would be around $15 per month, as anything higher would strain my budget given that I manage multiple servers. I'd need to see a cost-benefit analysis before committing.
    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.