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

Karen Towne

Karen Towne

freelance full-stack developer

Full-depth AI personas

Why this persona fits the audience

Takes on 2-4 SaaS MVP contracts a quarter in London; she is assembling a new productized-service project from free starter templates, a shared spreadsheet backlog, and manual setup for auth and payments.

  • Age: 34
  • Location: London, UK
  • Occupation: Freelance full-stack developer
  • Income: GBP 88k
  • Education: MSc Human-Computer Interaction
  • Company size: Sole trader (1 person)
  • Years in role: 6
“I don't want to just build software; I want to build the engine that lets me build anything else faster.”

Karen Towne is a thirty-four-year-old freelance full-stack developer based in East London, operating as a sole proprietor with an annual income hovering around £88,000. With an MSc in Human-Computer Interaction, she possesses a unique blend of technical prowess and user-centric philosophy, allowing her to navigate the complex landscape of modern SaaS development. For the past six years, Karen has carved out a niche in delivering rapid MVPs for startups, typically taking on two to four contracts per quarter. Her current workflow is a testament to her resourcefulness and her desire for independence: she is actively assembling a new productized service by cobbled-together free starter templates, meticulously maintaining a shared spreadsheet backlog, and manually handling the tedious but critical setup of authentication and payment processing. Despite her success, Karen is acutely aware of the inefficiencies in her current approach. The repetitive nature of setting up auth and payments from scratch consumes valuable hours that could be spent on actual product innovation or rest. She is driven by a deep-seated value for craft and reliability, striving to create clean, maintainable codebases that stand the test of time. Her lifestyle reflects this discipline; she balances her intense work schedule with a rigorous running routine and a passion for specialty coffee, finding solace in the predictability of physical training amidst the chaos of freelance life. Karen's recent decisions have centered on trying to bridge the gap between her client work and her personal ambitions. She is currently weighing the pros and cons of various tools to streamline her workflow, not out of desperation, but out of a strategic need to scale her impact without scaling her hours. While she is skeptical of 'magic bullet' solutions that promise too much, she remains open to tools that genuinely solve specific bottlenecks, particularly those related to infrastructure setup. Her relationship with money is pragmatic; she views income as fuel for freedom rather than a status symbol, reinvesting profits into better hardware and learning resources. As she moves forward, Karen is focused on reducing the friction in her development process, aiming to reclaim her time and focus on the creative aspects of software that truly excite her.

Background & daily life

A day in their life

Karen wakes at 5:45 AM, brewing coffee and checking the weather for her run. By 7:00 AM, she's lacing up her trainers for a brisk jog along the canal, listening to a podcast on indie business models. Back home by 8:15 AM, she showers and settles at her desk. From 9:00 AM to 12:00 PM, she focuses on deep work, usually tackling a tricky backend integration for a client's MVP. Lunch is a quick salad eaten while reviewing a shared spreadsheet backlog for her own product. Afternoons are reserved for meetings, emails, and lighter tasks like updating documentation or tweaking UI components. Around 5:00 PM, she shifts gears to her personal project, manually wiring up a payment webhook. She finishes work by 6:30 PM, disconnecting completely to cook dinner and perhaps read a book or call her parents, avoiding screens until bedtime to ensure quality sleep.

Lifestyle

Karen lives in a converted warehouse flat in Hackney, surrounded by exposed brick and the constant hum of the Overground. Her mornings are ritualistic: a V60 pour-over using beans from a local specialist roaster, followed by a 10km run along the Regent's Canal before her workday begins. She values fitness as much as code, often using running to clear mental fog after complex debugging sessions. Financially, she practices strict budgeting despite a healthy income, keeping personal expenses low to maximize savings for tax obligations and future sabbaticals. Socially, she maintains a tight circle of fellow creatives and runners, preferring deep one-on-one conversations over large networking events, finding genuine connection in shared interests rather than superficial industry mingling.

Work life

Her work reality is a perpetual juggling act between client delivery and building her own asset. Currently, she is managing three concurrent contracts, each requiring distinct tech stacks, while simultaneously piecing together her own SaaS offering. This involves stitching together free GitHub templates, manually configuring authentication services like Clerk or Auth0, and wiring up Stripe payment flows without a unified framework. She spends her days switching contexts rapidly, often feeling the friction of rebuilding the same boilerplate components repeatedly. Her office is a dual-monitor setup in a quiet corner of her home, where she relies heavily on Notion for backlog management and spreadsheets for tracking non-code deliverables. The pressure stems from the need to maintain high reliability for clients while ensuring her own product development doesn't stall due to administrative overhead.

Relationships

Karen shares a flat with two other freelancers who understand the irregular hours and the mental load of self-employment. She has a supportive but busy partner who works in digital marketing, often bonding over weekend hikes or Sunday meal prep. Her professional network is largely virtual, maintained through Discord communities and Twitter interactions, though she values face-to-face meetups with her local running club more highly. She rarely seeks mentorship formally, preferring to learn by doing, but she keeps an informal peer group of five other female founders who share resources and vent about client scope creep.

How they decide

Karen is a methodical researcher who prefers data-driven decisions over hype. She typically gathers information from multiple independent sources—technical forums, peer recommendations, and hands-on testing of free alternatives—before committing to any tool or strategy. She is cautious about vendor lock-in and prioritizes flexibility and cost-efficiency, often willing to invest significant time in custom solutions if it ensures long-term control. However, she is not impulsive; she weighs the opportunity cost of time against monetary savings carefully, often opting for the solution that offers the cleanest integration with her existing ecosystem rather than the cheapest or most feature-rich option.

How they sound

Karen speaks with a clipped, efficient cadence, favoring precise terminology over fluff. She tends to use British English idioms sparingly, mostly in casual settings, but switches to standard professional English during client calls. She avoids hyperbole, rarely saying 'amazing' or 'revolutionary,' preferring terms like 'robust,' 'scalable,' or 'efficient.' In conversation, she often pauses to clarify definitions, especially regarding technical constraints or project scopes. She is direct about boundaries, stating clearly what is out of scope without apologizing. Her tone is generally calm and composed, even when discussing tight deadlines, reflecting her low neuroticism score.

Personality traits

  • methodical
  • pragmatic
  • self-reliant
  • curious about edge cases
  • time-conscious
  • diplomatically direct
  • systematic
  • resilient under pressure
  • aesthetic-driven
  • boundary-setting

Goals

  • Reduce repetitive setup time for new projects by 50% within six months
  • Launch a self-sustaining micro-SaaS that generates passive income within a year
  • Achieve a consistent 4-day workweek by Q4
  • Build a robust design system library reusable across all freelance contracts
  • Save enough capital to take a three-month sabbatical for travel
  • Establish a reputation as a 'go-to' expert for rapid MVP scaling

Problems & frictions

  • Context-switching fatigue when managing multiple disparate tech stacks
  • Time lost manually configuring authentication and payment gateways from scratch
  • Difficulty estimating project timelines when starting from bare-bones templates
  • Lack of a centralized documentation source for her own recurring workflows
  • Balancing client billing cycles with long-term product development goals
  • Isolation leading to occasional decision paralysis on architectural choices

Values

  • independence
  • craft
  • clear scope
  • reliability
  • efficiency
  • autonomy

Interests

  • design systems
  • running
  • indie web apps
  • specialty coffee
  • minimalist architecture
  • urban cycling

Media habits

  • Indie hacker newsletters (e.g., Indie Hackers, TLDR)
  • GitHub trending repositories
  • Local running group chats
  • Specialty coffee roaster blogs
  • Twitter/X tech threads
  • Notion community templates

Questions & answers

Karen Towne’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Fast Forward Dev (https://fast-forward-dev.com/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    This looks interesting for offloading the boilerplate of auth and payments, which is exactly what I spend time on now. The fact that it's a single repository with the frontend and API sharing types is appealing. My main hesitation is the 'agent' setup – I'm a bit skeptical of relying too heavily on AI to configure critical infrastructure. I prefer to have explicit control and understanding. Today, I manage auth and payments by manually integrating libraries like Clerk and Stripe, then writing custom webhook handlers, all documented in Notion. I'd need to see how the agent setup truly works and if it's easily auditable before committing. If it proves robust and transparent, I might consider paying up to $49 per month, but that's contingent on seeing it in action.
    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.