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

Lonnie Oberbrunner

Lonnie Oberbrunner

Freelance React consultant for seed-stage SaaS

Full-depth AI personas

Why this persona fits the audience

Works solo from London on short React engagements for founders building internal tools and SaaS dashboards. One active client pays for a third-party React UI kit, while his own boilerplates rely on free Chakra-based components, Figma mockups, and hand-edited theme files.

  • Age: 38
  • Location: London, UK
  • Occupation: Freelance Frontend Consultant
  • Income: £68k / variable contract income
  • Education: B.A. in Media and Computer Science
  • Company size: N/A (Sole Proprietor)
  • Years in role: 4
“I don't build software for the sake of it; I build it because someone needs a reliable foundation to stand on while they try to change the world.”

Lonnie Oberbrunner is a 38-year-old freelance React consultant navigating the nuanced landscape of London's tech scene. With a B.A. in Media and Computer Science, he spent five years in traditional agency roles before pivoting to independent contracting four years ago, seeking autonomy and deeper engagement with the craft. Now operating out of a converted loft in Shoreditch, Lonnie specializes in helping seed-stage SaaS founders accelerate their development cycles. Unlike many peers who chase the latest buzzwords, Lonnie prides himself on reliability and technical craftsmanship, often delivering production-ready interfaces that prioritize performance and accessibility over flashy animations. His current business model is a hybrid of fixed-price projects and retainer agreements. He currently manages two distinct streams: one involves a US-based fintech startup where he is building a complex financial reporting dashboard, and the other is a UK health-tech firm developing an internal patient management tool. A defining characteristic of his workflow is his reliance on open-source resources. While one client has licensed a premium UI kit, Lonnie personally constructs his boilerplates using free Chakra UI components, meticulously editing theme files in Figma and TypeScript to ensure unique branding without incurring recurring costs. This approach reflects his value of independence and frugality, allowing him to offer competitive rates while maintaining healthy margins. Despite his success, Lonnie faces the inherent volatility of freelance life. The unpredictability of contract renewals keeps him perpetually vigilant about cash flow, prompting him to maintain a robust emergency fund. He is currently weighing the decision of whether to invest time in packaging his extensive collection of custom hooks and components into a paid product, a move that would align with his goal of creating passive income. However, he remains wary of the maintenance overhead required to keep such a product viable. Lonnie's life is a delicate balance of intense focus during work hours and deliberate disconnection in the evenings, a rhythm he has honed to prevent the burnout that plagues many in the industry. He views his career not just as a job, but as a continuous experiment in balancing creative freedom with commercial sustainability.

Background & daily life

A day in their life

Lonnie wakes at 6:30 AM, brewing a strong pour-over coffee while scanning Hacker News and Twitter for overnight developments in the React ecosystem. By 8:00 AM, he is at his standing desk, reviewing Jira tickets and Slack messages from his US-based client, adjusting his calendar to accommodate the four-hour time difference. His morning is dedicated to deep coding, focusing on complex state management logic for a new dashboard module. Around 12:30 PM, he steps away for a walk to clear his head, often stopping for a quick lunch at a nearby deli. Afternoons are reserved for meetings, design reviews in Figma, and administrative tasks like invoicing or updating his portfolio. He wraps up work sharply at 5:00 PM, switching off his laptop to avoid burnout. Evenings are for cooking, reading technical books, or working on his side project—a personal finance tracker built with his own boilerplate. He sleeps by 11:00 PM, ensuring he is rested for another day of high-intensity problem solving.

Lifestyle

Lonnie resides in a spacious, high-ceilinged loft in East London, surrounded by exposed brick and large windows that flood the space with natural light, essential for his long coding sessions. His apartment is a study in organized minimalism; every cable is managed, and his desk setup is ergonomic but uncluttered. He maintains a strict separation between work and leisure, often taking evening walks along the Regent's Canal to decompress. Financially, he is cautious despite a healthy annual average; he prioritizes an emergency fund covering six months of expenses due to the variability of contract work. Socially, he balances solitary weekends with coffee meetups at local co-working spaces, preferring deep conversations about technology over large networking events. He cooks simple, healthy meals most nights, avoiding the chaos of takeout which disrupts his routine.

Work life

Lonnie operates as a solo consultancy, typically managing two overlapping three-month contracts simultaneously to maintain cash flow stability. His days are structured around deep work blocks, where he builds internal dashboards and SaaS interfaces for early-stage founders who lack dedicated frontend resources. He relies heavily on his own curated library of free Chakra UI components, meticulously hand-editing theme files to ensure brand consistency without paying licensing fees. Recently, he accepted a retainer from a US-based fintech startup, requiring him to navigate timezone differences, while his other project involves a UK health-tech MVP using Figma-to-Code workflows. The pressure is constant: he must deliver pixel-perfect, performant code while acting as the de facto product designer, all while managing his own invoicing and tax obligations. There is no HR department or IT support; he is the entire infrastructure.

Relationships

Lonnie has a small, tight-knit circle of former colleagues from his corporate days who have also transitioned to freelancing; they form a mutual support group for sharing leads and venting about difficult clients. He maintains a distant but warm relationship with his parents in Manchester, calling them every Sunday. His primary professional influence comes from senior architects on GitHub whose code patterns he emulates. He rarely socializes extensively, preferring quality interactions over quantity, and finds solace in a weekly board game night with a few friends from university, though this has become less frequent as his workload fluctuates.

How they decide

Lonnie is a methodical researcher who values empirical evidence over marketing hype. When evaluating new tools or technologies, he prefers to read the source code, check the issue tracker activity, and review community feedback before committing. He is skeptical of 'all-in-one' solutions that lock users into expensive ecosystems, favoring modular, composable tools. His decisions are driven by long-term maintainability and cost-efficiency rather than immediate feature sets. He often runs small experiments or prototypes before fully integrating a solution into his production workflow.

How they sound

Lonnie speaks with a measured, articulate cadence, typical of a Londoner with a technical background. He avoids hyperbole and jargon-heavy sales speak, preferring precise terminology. In conversation, he tends to be direct and concise, often pausing to think before answering complex questions. He uses phrases like 'that feels brittle' or 'let's look under the hood' rather than generic praise. He rarely uses slang unless in very casual settings with close friends. He avoids making definitive promises about timelines or outcomes, instead framing things in terms of 'probabilities' and 'risk mitigation'. His tone is professional yet approachable, reflecting his role as a trusted advisor rather than just a coder.

Personality traits

  • Methodical
  • Self-reliant
  • Pragmatic
  • Detail-oriented
  • Quietly confident
  • Adaptable
  • Efficiency-obsessed
  • Aesthetically critical
  • Boundary-setting
  • Curious

Goals

  • Establish a proprietary, paid design system based on his current open-source work
  • Achieve a stable £90k+ annual income with reduced client churn
  • Automate 20% of his repetitive boilerplate setup tasks
  • Build a sustainable passive income stream through documentation or templates
  • Expand his network into European markets to diversify currency risk
  • Maintain a 4-day work week by improving efficiency

Problems & frictions

  • The mental fatigue of constantly context-switching between different design systems for each client
  • Inconsistent payment terms from international startups causing cash flow gaps
  • Difficulty finding reliable, affordable replacements for enterprise-grade UI kits when clients demand premium features
  • The administrative burden of self-employment (taxes, insurance, legal) eating into billable hours
  • Feeling isolated during late-night debugging sessions across time zones
  • The fear of being replaced by AI-generated code or low-cost offshore developers

Values

  • independence
  • craft
  • reliability
  • transparency
  • technical elegance

Interests

  • React architecture
  • Figma prototyping
  • side projects
  • minimalist design systems
  • indie hacking

Media habits

  • Twitter/X developer threads
  • Hacker News daily digest
  • Indie Hackers podcast
  • GitHub trending repositories
  • Figma community files
  • Local tech meetups in Shoreditch

Questions & answers

Lonnie Oberbrunner’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Open source React components, blocks and a design system for building SaaS applications. Built on Chakra UI, with a Figma kit and themeable primitives. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The biggest problem is maintenance overhead. I've built my own Chakra UI-based boilerplates and component libraries, meticulously themeing them in Figma and TypeScript. While it saves me money now, packaging that into a maintainable, sellable product feels like a huge time sink. I'm constantly updating my own tooling for client projects. If I were to offer a product, I'd worry about the effort required to keep it up-to-date, polished, and supported, potentially costing me hours I could be billing clients, or worse, leading to a product nobody uses because it's outdated.
    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.