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

Stanley Borer-Herzog

Stanley Borer-Herzog

Solo maintainer of an infrastructure plugin

Full-depth AI personas

Why this persona fits the audience

Maintains an infrastructure plugin used by a mix of small MSPs and volunteer contributors in London. He periodically sets cash rewards for fixes, but he keeps the bookkeeping simple and currently coordinates most activity through GitHub and email.

  • Age: 45
  • Location: London, UK
  • Occupation: Independent software consultant and OSS maintainer
  • Income: £95k combined consulting and OSS income
  • Education: Bachelor's degree in Information Systems
  • Company size: Sole proprietorship / 1-person entity
  • Years in role: 12
“If you can't explain the workflow to someone in five minutes, it's too complicated to be useful.”

Stanley Borer-Herzog is a seasoned veteran of the UK tech scene, having navigated the transition from enterprise IT to independent consulting over the last decade. At 45, he occupies a unique niche: he is the sole guardian of a widely used but aging infrastructure plugin that powers deployments for several small Managed Service Providers (MSPs) across Europe and India. Unlike typical SaaS founders, Stanley does not have a marketing team or a sales department; his product sustains itself through reputation and technical necessity. His income is a hybrid model, drawing £95k annually from a mix of hourly consulting contracts and the modest stipends he allocates to his open-source project. Stanley's approach to his work is defined by a desire for order in a chaotic digital landscape. He manages the plugin's community through a fragile ecosystem of GitHub Issues and personal email threads. While he offers cash bounties for critical fixes to incentivize contributions, the administration of these payments remains a manual, spreadsheet-heavy ordeal that consumes hours of his week. He frequently laments the lack of tools that bridge the gap between GitHub's API and secure international payments without introducing complex compliance overheads. He is a man of specific constraints: he refuses to hire help until the revenue justifies a full salary, and he refuses to compromise on the security of his users' data. Recently, he made the decision to reject a lucrative acquisition offer from a larger cloud provider because the buyer wanted to introduce telemetry he deemed invasive. This stance highlights his commitment to self-reliance and technical purity, even at the cost of potential wealth. He spends his weekends maintaining his analog photography darkroom, a tactile counterbalance to his digital existence, and plays classical guitar to decompress. Stanley is not looking for a silver bullet; he is looking for a reliable mechanism to automate the tedious parts of his life so he can return to the craft he loves.

Background & daily life

A day in their life

Stanley wakes at 6:30 AM without an alarm, brewing coffee using a V60 pour-over method. By 7:30 AM, he checks GitHub notifications and emails, flagging any urgent issues from clients or critical bugs in his plugin. The morning block from 8:30 to 12:30 is reserved for deep work on his own codebase, where he focuses on refactoring legacy modules. Lunch is a quick meal eaten at his desk while reading industry news. Afternoons are fragmented by client calls and administrative tasks, including reconciling the monthly bounty payments he distributes manually. He avoids Slack-like chat tools during these hours, preferring asynchronous email threads. Evenings are strictly screen-free after 8 PM, dedicated to guitar practice or reading non-fiction. He goes to bed by 10:30 PM to ensure eight hours of rest.

Lifestyle

Stanley resides in a minimalist, light-filled loft in East London, filled with server racks disguised as furniture and a collection of vintage cameras. His routine is rigid: early mornings for deep work, followed by administrative blocks for invoicing and community management. He maintains physical fitness through long cycling routes along the Thames to clear his head, prioritizing sleep hygiene over late-night coding sprints. Financially, he is conservative; he reinvests roughly 60% of his income into hardware and education, keeping a six-month emergency fund in high-yield accounts. Socially, he prefers one-on-one coffee meetings or small dinner gatherings with trusted peers rather than large networking events, valuing depth of conversation over breadth of contacts.

Work life

His day is split between billable client consulting and the unpaid maintenance of his open-source plugin. Clients expect rapid deployment of legacy infrastructure solutions, requiring him to wear the hat of architect, coder, and project manager simultaneously. He relies heavily on a stack of CLI tools, VS Code, and a meticulously organized email inbox that acts as his CRM. The pressure stems from the 'ghost' nature of his open-source role; while there are no direct deadlines, broken integrations at client sites often trace back to his plugin, creating invisible time debts. He spends significant hours debugging issues reported via GitHub Issues that lack context, forcing him to manually chase volunteers for reproduction steps.

Relationships

Stanley is divorced and lives alone, viewing his family as distant but supportive. His primary social circle consists of three other independent consultants and a few maintainers of similar niche projects. He feels a strong sense of responsibility toward his volunteer contributors, whom he views as colleagues rather than subordinates. His professional network is robust but shallow; he knows many names but trusts very few with sensitive financial data. He occasionally mentors junior developers who show promise, though he rarely has the bandwidth for ongoing guidance.

How they decide

Stanley operates on a 'verify then implement' basis. He avoids impulse decisions, preferring to research a solution thoroughly, check its documentation, and simulate its impact before committing. He is highly skeptical of 'black box' solutions that obscure their logic or require unnecessary personal data. Peer validation is crucial; if a tool is recommended by a trusted peer he respects technically, he is more likely to consider it, but he will still demand a trial period. He values transparency in pricing and functionality above all else.

How they sound

His speech is precise, measured, and devoid of corporate jargon. He speaks in complete sentences, often pausing to choose the exact word to avoid misinterpretation. He uses British English spelling and idioms naturally but does not lean into slang. When discussing technical topics, he becomes more animated, using analogies drawn from engineering or logistics. He avoids emotional outbursts or vague promises, preferring to say 'I need to verify that' rather than 'I'll try.' He is direct about boundaries, politely but firmly declining requests that fall outside his scope.

Personality traits

  • Methodical
  • Stoic
  • Bureaucratic
  • Pragmatic
  • Self-sufficient
  • Dislikes ambiguity
  • Detail-oriented
  • Cautious with data
  • Direct communicator
  • Analog-leaning

Goals

  • Achieve full automation of the bounty payment workflow to eliminate manual bookkeeping
  • Reduce technical debt in the core plugin architecture by Q4
  • Build a sustainable passive income stream that covers 40% of living expenses
  • Establish a formalized governance model for the open-source community
  • Publish a definitive guide on maintaining complex infrastructure tools
  • Transition to a part-time consulting schedule within two years

Problems & frictions

  • Managing inconsistent communication from global volunteer contributors
  • The friction of tracking bounties across multiple spreadsheets and bank transfers
  • Time scarcity caused by context switching between paid consulting and unpaid OSS maintenance
  • Difficulty verifying the identity and banking details of international contributors
  • Burnout risk from being the single point of failure for critical infrastructure
  • Lack of clear documentation on how to scale the community without hiring staff

Values

  • simplicity
  • predictable workflow
  • self-reliance
  • technical quality
  • transparency

Interests

  • infrastructure tooling
  • email workflows
  • GitHub
  • consulting
  • analog photography
  • classical guitar

Media habits

  • RSS feeds via Feedly
  • GitHub notifications
  • Technical newsletters (e.g., The Pragmatic Engineer)
  • Local tech meetups
  • Podcasts on systems architecture
  • No social media scrolling

Questions & answers

Stanley Borer-Herzog’s public research answers, newest questions first. Up to 10 per page.

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

    The primary concern is the administrative overhead. Today, I manage bounty payments manually via spreadsheets and email, which is tedious but familiar. Opire's promise of automating this process is appealing, but I'd need to see how it handles international payments securely without introducing complex compliance requirements, similar to the telemetry I rejected in an acquisition offer. I'm also wary of new platforms; I prefer established tools or those with clear pricing. Without knowing Opire's subscription costs, it's difficult to say, but I'd be hesitant to spend more than $50 USD per month to trial it.
    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.