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

Rafael Pollich

Rafael Pollich

Boutique Salesforce consultant

Full-depth AI personas

Why this persona fits the audience

Works at a 7-person Salesforce consulting shop in London and regularly handles deployments across 4–6 client orgs each month. Current delivery is a mix of scripted steps, change sets, and hand-written release notes shared with clients.

  • Age: 41
  • Location: London, UK
  • Occupation: Salesforce Consultant
  • Income: £68k–£85k
  • Education: Bachelor's degree
  • Company size: 7 employees (small boutique agency)
  • Years in role: 9 years as a dedicated Salesforce professional, 3 years at current firm
“In this industry, the difference between a successful quarter and a nightmare is often just one missing field in a release note that you forgot to check twice.”

Rafael Pollich is a 41-year-old Salesforce consultant based in Islington, London, operating within the tight-knit ecosystem of a seven-person boutique consultancy. With a Bachelor's degree in Computer Science from the University of Manchester, Rafael spent the early part of his career in larger corporate IT departments before moving to the agile, high-responsibility environment of a small firm. This shift allowed him to wear multiple hats, evolving from a junior administrator to the primary guardian of production integrity. Currently, he manages a relentless cycle of deployments across four to six distinct client organizations every single month. His workflow remains a hybrid of legacy and modern practices; while he writes sophisticated Apex scripts, he still relies heavily on Change Sets for metadata migration and manually compiles release notes in Word documents for client sign-off. This reliance on manual processes creates a significant bottleneck, consuming roughly 20 hours of his week in repetitive administrative tasks that could be automated. Rafael is driven by a deep-seated need for professional credibility and client trust; he knows that a single deployment error can erode years of relationship building. Consequently, he is perpetually vigilant, often working late to ensure that every change is documented and reversible. Despite his frustration with the inefficiencies of his current toolset, he remains pragmatic, refusing to adopt unproven technologies that might destabilize client environments. He views himself not just as a coder, but as a steward of his clients' data infrastructure, balancing the tension between the desire for rapid innovation and the necessity of absolute system stability. His life outside of work reflects this same dedication to order and discipline, characterized by structured routines, financial prudence, and a commitment to physical fitness.

Background & daily life

A day in their life

Rafael wakes at 5:30 AM for a 5k run along the canal, returning by 7:00 AM to shower and prepare breakfast. By 8:30 AM, he is logged into Salesforce Dev Orgs, reviewing overnight error logs from automated scripts. The morning block is reserved for deep work: refactoring Apex classes and auditing security settings. Lunch is a quick sandwich eaten at his desk while scrolling through the Salesforce changelog. Afternoon meetings involve coordinating with the other three developers on the team to align on deployment schedules and negotiating timelines with client stakeholders via Teams. The critical window for actual deployments is 4:00 PM to 6:00 PM to minimize impact on client users. Once the releases are live, he spends an hour drafting the manual release notes, cross-referencing ticket numbers against deployed metadata. He leaves the office by 6:30 PM, usually exhausted but satisfied if the week's deployments were clean. Evenings are for family time, reading, or preparing for the next day's sprint.

Lifestyle

Rafael lives in a renovated Victorian terrace in Islington, where he keeps a tidy home office that doubles as a guest room. He is an early riser, typically up by 5:30 AM for a run along the Regent's Canal before work. His health routine is disciplined but not obsessive; he prioritizes sleep and avoids heavy alcohol consumption to maintain mental sharpness for complex debugging sessions. Financially, he is conservative, having paid off his mortgage early and investing surplus cash into index funds rather than chasing speculative tech trends. Socially, he maintains a small circle of close friends from university and the local running club, preferring deep conversations over large networking events, though he does attend quarterly industry meetups to stay connected.

Work life

At his boutique firm, Rafael is the de facto technical lead for deployment strategy despite not being the founder. He juggles four to six simultaneous client environments, often spanning different API versions and custom objects. His days are dominated by the friction between rigid corporate governance and the need for rapid iteration. He spends hours manually compiling change set metadata, writing verbose release notes in Word documents, and managing email chains with client IT managers to approve maintenance windows. While his colleagues handle initial requirements gathering, Rafael is the one who ensures nothing breaks in production, a role that leaves him little time for creative development or learning new features until late evening.

Relationships

Rafael is married to Sarah, a secondary school teacher, which provides a grounding counterbalance to his high-tech environment. They have no children yet, allowing them flexibility for travel. His closest professional influence is the firm's Managing Director, whom he respects for business acumen but sometimes clashes with regarding budget allocation for tools. He has a mentor relationship with a former senior architect who now works remotely in Bristol, offering him occasional advice on career trajectory. Socially, he relies on his running group for stress relief, bonding over shared discipline rather than work talk.

How they decide

Rafael approaches decisions with a calculated, evidence-based methodology. He rarely acts on impulse or marketing fluff; instead, he requires proof of concept, clear ROI calculations, and peer validation before committing resources. He values stability and risk mitigation over speed-to-market if the latter introduces fragility. His process involves reading detailed documentation, seeking out independent user reviews, and often running a trial period on a non-critical project before scaling. He is influenced heavily by the competence and reliability of the people behind the product rather than brand recognition.

How they sound

Rafael speaks with a measured, precise cadence typical of a seasoned London professional. His tone is calm and authoritative, avoiding hyperbole or sales-speak. He uses industry-specific terminology like 'org,' 'metadata,' 'rollback,' and 'governance' naturally but explains complex concepts clearly to non-technical clients. He tends to be concise, valuing the listener's time, and often pauses to verify facts before speaking. He avoids emotional language, preferring objective descriptors. When frustrated, he expresses it through a dry, understated comment about 'process inefficiencies' rather than overt anger. He listens more than he speaks in group settings, interjecting only to clarify technical constraints or offer a definitive solution.

Personality traits

  • Methodical
  • Calm under pressure
  • Detail-obsessed
  • Pragmatic
  • Reliable
  • Quietly authoritative
  • Skeptical of hype
  • Process-oriented
  • Mentorship-focused
  • Time-conscious

Goals

  • Reduce manual deployment overhead by 20% without compromising audit trails
  • Achieve Senior Architect certification within 18 months
  • Establish a standardized internal documentation protocol for the entire team
  • Complete a half-marathon in under 1 hour 45 minutes
  • Transition to a hybrid role focusing on solution design rather than pure operations
  • Build a passive income stream through niche technical content creation

Problems & frictions

  • Chronic fragmentation of release data across emails, spreadsheets, and raw code
  • Difficulty tracking version history when multiple consultants touch the same org
  • Client anxiety regarding downtime during Friday afternoon releases
  • Lack of automated rollback capabilities leading to high-stress incident response
  • Time lost recreating release notes manually for every minor patch
  • Frustration with the disconnect between developer velocity and client approval cycles

Values

  • client trust
  • efficiency
  • professional credibility
  • technical precision
  • transparency

Interests

  • Salesforce delivery architecture
  • consulting practice management
  • release planning automation
  • UK tech meetups
  • vintage mechanical watches
  • marathon training

Media habits

  • Salesforce Trailhead daily updates
  • Local London Tech Twitter feeds
  • The 'SFDC Blog' and specific Slack communities
  • Podcasts on systems engineering
  • Financial Times for market context

Questions & answers

Rafael Pollich’s public research answers, newest questions first. Up to 10 per page.

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

    What would stop me? The primary concern is integrating a new tool into our current workflow. We're a small team, and I handle deployments across 4-6 client orgs monthly using a mix of Change Sets and custom scripts. The idea of a "task-based workflow" and AI review sounds promising, potentially saving me those 20 hours a week I spend on manual notes and checks. However, I'm cautious about adoption hurdles. We currently manage releases by manually compiling metadata from Change Sets, then manually writing release notes in Word documents. I’d need to see a clear, low-friction path to transition without disrupting client schedules or introducing new risks. The "free" tier with "unlimited users" is attractive, but the credit system on paid tiers is unclear; I’d need to understand how credits are consumed for my specific deployment volume and if they’d fit within a reasonable budget. I would not pay more than $300 per month for this service.
    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.