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

Brittany O'Reilly

Brittany O'Reilly

Freelance full-stack developer

Full-depth AI personas

Why this persona fits the audience

Splits the week between client projects and a solo SaaS for bookkeeping agencies; she maintains a reusable starter repo, swaps APIs for different jobs, and often prototypes auth, billing, and admin screens before a client handoff.

  • Age: 36
  • Location: London, UK
  • Occupation: Freelance full-stack developer
  • Income: £88k variable freelance income
  • Education: Master's degree in software engineering
  • Company size: Solo operator (1 person)
  • Years in role: 9
“I build systems that outlast the current trend because I've seen too many startups fail simply because their foundation was built on sand.”

Brittany O'Reilly is a thirty-six-year-old freelance full-stack developer based in London, operating at the intersection of high-level engineering and pragmatic entrepreneurship. With a Master's degree in Software Engineering and nearly a decade of experience, she has evolved from a corporate employee to a solo founder navigating the volatile freelance market. Her career is defined by a dual focus: delivering reliable, high-quality solutions for external clients while simultaneously building her own portfolio product—a SaaS tailored for bookkeeping agencies. This split requires a unique mental agility, as she must constantly switch contexts between solving specific client pain points and architecting scalable, reusable infrastructure for her own venture. Brittany is the architect of her own 'starter repo,' a meticulously maintained repository that abstracts away the mundane complexities of authentication, billing, and admin interfaces. This tool allows her to prototype applications rapidly, swapping out API providers like Stripe or Braintree depending on the geographic needs of the client. However, this reliance on automation does not diminish her commitment to craftsmanship; she believes deeply in writing clean, maintainable code, even when deadlines loom. Her income fluctuates around £88,000 annually, a figure that reflects her ability to command premium rates for her expertise while maintaining the flexibility to decline low-value projects. Living alone in a Shoreditch loft, Brittany has structured her life to maximize autonomy. She is disciplined about her time, using running as a buffer against the mental fatigue of screen-based work. Her professional relationships are selective, favoring quality connections over quantity. She is currently facing the classic scaling dilemma: how to grow her SaaS revenue without compromising the quality of her client work or her personal well-being. As she navigates the next phase of her career, her decisions are driven by a desire for sustainable growth rather than explosive, risky expansion.

Background & daily life

A day in their life

Brittany wakes at 6:00 AM, skipping breakfast to lace up her trainers for a brisk run along the canal. By 7:30 AM, she is back in her home office, brewing strong coffee and reviewing the day's priorities on Notion. From 9:00 AM to 12:00 PM, she engages in deep work on her SaaS, focusing on swapping out a Stripe integration for a localized European provider. At noon, she steps away for a walk to clear her head, often listening to a tech podcast. Afternoon sessions involve video calls with a client in New York, followed by code reviews and writing unit tests for the admin dashboard she built yesterday. She avoids late meetings to protect her evening routine. Around 5:30 PM, she logs off, checking her automated financial dashboards to ensure invoices are processed. Evenings are reserved for cooking a fresh meal, reading fiction, or scrolling through GitHub issues, never touching code unless a critical bug arises.

Lifestyle

Brittany lives in a high-ceilinged, light-filled loft in Shoreditch, surrounded by exposed brick and minimal furniture designed to reduce visual noise. Her mornings begin with a 5km run along the Regent's Canal, a non-negotiable ritual that grounds her before the digital chaos begins. She is financially prudent, automating savings immediately upon invoice payment and avoiding lifestyle inflation despite her solid earnings. Socially, she prefers one-on-one coffee chats or small dinner gatherings over loud networking events, valuing deep conversation over broad connection. Her evenings are often spent tinkering with personal code or reading technical papers, though she makes a conscious effort to disconnect by 9 PM to preserve mental space for her partner and hobbies.

Work life

Her workday is a deliberate oscillation between two distinct modes: billable client work and equity-building side projects. Mornings are reserved for deep coding sprints on her proprietary SaaS for bookkeeping agencies, where she refactors her 'starter repo' to ensure it remains agnostic to specific API providers. Afternoons shift to client calls, Slack threads, and delivering bespoke features for external contracts. She operates as a one-woman army, handling everything from architecture diagrams to deployment pipelines. The pressure isn't just technical; it's the constant juggling act of maintaining high-quality output while managing the administrative burden of running a business. She relies heavily on headless CMS setups and component libraries to speed up delivery without sacrificing the clean code she demands of herself.

Relationships

Brittany is single and lives independently, which grants her total autonomy but sometimes leaves her feeling professionally isolated. Her closest support network consists of a tight-knit group of three other freelancer friends in London with whom she meets bi-weekly for 'co-working' sessions at a local cafe. She has a supportive family in Manchester who visit occasionally but don't fully grasp the nuances of her gig-economy lifestyle. She actively participates in the UK indie hacker Discord communities, where she finds both technical validation and occasional collaboration opportunities. Her primary influence comes from the open-source maintainers whose code she relies on daily.

How they decide

Brittany is a research-heavy, risk-averse decision-maker who prioritizes long-term stability over short-term gains. She rarely adopts a new tool or technology until she has read the documentation thoroughly, checked the GitHub activity history, and verified its integration capabilities against her existing ecosystem. She values data and case studies over marketing hype, often creating a small proof-of-concept before committing to a purchase. While she is open to experimentation, her default stance is skepticism; she assumes that if something is too good to be true, it likely lacks the robustness required for production environments. Peer recommendations from trusted technical circles weigh heavier than advertising spend.

How they sound

Direct, articulate, and precise. Brittany speaks with a measured cadence, avoiding filler words like 'um' or 'like'. She uses industry terminology naturally but explains complex concepts clearly when speaking to non-technical stakeholders. She tends to be slightly formal in written communication, favoring complete sentences over slang, though she loosens up in casual voice notes with close colleagues. She avoids emotional language in professional contexts, preferring objective descriptions of problems and solutions. When frustrated, she doesn't complain; she analyzes the root cause and documents the fix.

Personality traits

  • methodically organized
  • pragmatically skeptical
  • solitary but connected
  • process-oriented
  • efficiently verbose
  • resilient under pressure
  • curious about edge cases
  • protective of personal time
  • detail-obsessed
  • self-reliant

Goals

  • Achieve a fully passive income stream from her SaaS that covers 50% of living expenses within two years
  • Reduce weekly billable hours to 25 to allow for more strategic architectural thinking
  • Establish a standardized, documented design system that can be licensed or sold as a micro-product
  • Maintain consistent physical fitness and avoid burnout through strict boundary setting
  • Mentor two junior developers remotely per year to give back to the community

Problems & frictions

  • Time fragmentation caused by context switching between generic client requests and specialized SaaS development
  • The recurring overhead of re-implementing authentication and billing flows for every new project, even when using templates
  • Difficulty finding high-quality, niche clients who understand the value of long-term maintainability over quick fixes
  • Isolation in decision-making regarding technical stack choices without immediate peer review
  • Managing tax complexity and cash flow variability across multiple currencies and jurisdictions
  • Balancing the desire for perfect code craftsmanship with the commercial necessity of rapid delivery

Values

  • autonomy
  • craftsmanship
  • reliability
  • flexibility

Interests

  • React
  • design systems
  • running
  • small-business software

Media habits

  • The Changelog podcast
  • Hacker News morning digest
  • Local running group WhatsApp
  • GitHub trending repositories
  • Twitter/X tech circles
  • Substack newsletters on indie hacking

Questions & answers

Brittany O'Reilly’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.launchfa.st/ (LaunchFast) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on LaunchFast, I'm immediately drawn to the promise of skipping weeks of setup for auth, payments, and infra. My own starter repo is pretty robust, but the idea of having that boilerplate already wired with swappable providers like Stripe or Lemon Squeezy, and databases like Postgres or MongoDB, is appealing. What's unclear is the depth of customization available for the UI components and how seamless the actual provider swapping is in practice, especially for complex client requirements. I'd sign up if I saw clear examples of integration with less common European payment providers, given my client base, and a robust demo that lets me poke around the codebase.
    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.