Kevin Stehr

Why this persona fits the audience

He bills a small roster of UK clients for website builds and maintenance, usually 4–6 invoices a month. He currently issues invoices from Xero and keeps project notes in GitHub and a task board; client confidentiality is part of his day-to-day work.

• Age: 41
• Location: Manchester, UK
• Occupation: independent web developer
• Income: GBP 78k
• Education: BSc in computer science
• Company size: Sole trader (1 person)
• Years in role: 12 years as an independent contractor

“Efficiency isn't about doing things faster; it's about ensuring you're not wasting effort on things that don't matter.”

Kevin Stehr, 41, is a seasoned independent web developer operating out of Manchester, UK. With a BSc in Computer Science and over a decade of experience, he transitioned from corporate employment to freelancing twelve years ago, seeking autonomy and better work-life balance. Today, he operates as a sole trader, billing a steady roster of four to six UK clients for bespoke website builds and ongoing maintenance. His income hovers around £78,000 annually, allowing him to live comfortably while reinvesting significantly into his own infrastructure and savings. Unlike many in his field, Kevin places a premium on privacy and precision, often refusing projects that require compromising client data security. His workflow is a testament to his high conscientiousness; he utilizes Xero for financial administration and GitHub for version control and project tracking, maintaining a rigid separation between personal and professional data. He is deeply involved in the open-source community, contributing to various networking and development libraries, viewing this as both a professional obligation and a personal hobby. Recently, Kevin made the decision to migrate his entire home infrastructure to a self-hosted Proxmox cluster, eliminating reliance on public cloud storage for sensitive backups. This move reflects his broader philosophy: total control over one's digital environment is non-negotiable. Despite his solitary nature, he remains engaged with a small circle of trusted peers, valuing their technical insights over social validation. He is currently focused on optimizing his automated invoicing workflows to reclaim hours lost to administrative drudgery, aiming to redirect that time toward higher-level architectural consulting.

Background & daily life

A day in their life

Kevin wakes at 05:30, brews a single-origin pour-over, and cycles 15 miles to clear his head. By 07:45, he is seated at his desk, reviewing overnight logs and checking emails, though he avoids replying until 09:00. From 09:30 to 12:30, he engages in deep coding work on a client's React application, focusing strictly on performance optimization. A quick lunch break involves walking outside, away from screens. The afternoon is split between code reviews, updating documentation in GitHub, and administrative tasks like generating invoices in Xero. He blocks out 16:00 to 17:00 for client calls, keeping them tight and agenda-driven. After wrapping up, he spends an hour configuring his home lab or reading technical articles before shutting down his machines completely to ensure a digital sunset.

Lifestyle

Kevin resides in a sun-drenched, slightly cluttered flat in Didsbury where he has personally wired the entire home network with Cat6a cabling and managed a Proxmox server for local backups. His mornings begin at 05:30 with a 15-mile ride through the local canals before breakfast, a ritual that grounds him before the screen-heavy workday. He maintains a frugal but high-quality lifestyle, investing heavily in ergonomic office gear and mechanical keyboards rather than luxury goods. Financially, he lives well below his means, aggressively reinvesting profits into tax-efficient ISAs and a dedicated emergency fund. Socially, he is selective, preferring one-on-one coffee meetups or small group cycling clubs over large parties, valuing deep conversation over small talk.

Work life

His workspace is a dual-monitor setup with a custom Linux distribution running on a bare-metal build, reflecting his preference for control. As a sole trader, Kevin manages a rotating roster of four to six UK-based clients, handling everything from frontend architecture to server maintenance. He relies heavily on Xero for invoicing, which he finds functional but occasionally rigid, and uses GitHub Issues alongside a Trello board to track project milestones. The pressure is self-imposed; there is no boss, only deadlines and the constant need to upskill to remain competitive. He structures his days in strict ninety-minute sprints to maintain flow, minimizing context switching between coding, administrative tasks, and client communication.

Relationships

Kevin is divorced and lives independently, maintaining close ties with two siblings in the North West who share his interest in technology. His primary support network consists of three former university colleagues who now run agencies; they meet monthly for lunch to discuss industry trends rather than complain. He is influenced more by anonymous online contributors and documented case studies than by influencers or traditional media figures. While not widely known locally, he is a respected figure in Manchester's smaller developer circles, often the go-to person for advice on security hardening.

How they decide

Decisions are made methodically after a period of silent research. He rarely acts on impulse or peer pressure, preferring to validate claims against technical documentation or community consensus. When evaluating new tools, he prioritizes long-term stability and data sovereignty over feature bloat. He will test a solution in a sandbox environment before committing any resources, trusting logic and evidence over marketing narratives.

How they sound

Kevin speaks with a calm, measured Mancunian cadence, avoiding slang unless in casual company with close friends. His sentences are precise, often structured logically with clear cause-and-effect reasoning. He tends to avoid absolutes like 'always' or 'never' unless referring to technical facts. In conversation, he listens more than he speaks, pausing to consider the nuance of a question before answering. He rarely uses hyperbole and prefers understated descriptions of complex problems. When discussing technology, he shifts into a more rapid, technical lexicon, dropping colloquialisms entirely.