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

Tabitha Shanahan

Tabitha Shanahan

Freelance full-stack contractor

Full-depth AI personas

Why this persona fits the audience

She is a freelance full-stack contractor in London juggling two client projects at once. On her Mac, she uses Claude Code for feature work and bug fixes, then reviews the saved transcripts at the end of the day to reconstruct what happened before sending notes to clients.

  • Age: 36
  • Location: London, UK
  • Occupation: Freelance Full-Stack Developer
  • Income: £92k
  • Education: BSc in Software Engineering
  • Company size: Self-employed / Sole Trader
  • Years in role: 8
“I don't need more tools to do the work faster; I need better ways to remember what I actually did so I can get paid for it.”

Tabitha Shanahan is a 36-year-old freelance full-stack developer operating out of East London, having carved out a successful niche in the competitive UK tech market since graduating with a BSc in Software Engineering eight years ago. Currently earning approximately £92,000 annually, she manages her business as a sole trader, handling everything from client acquisition to tax compliance. Unlike many of her peers who rely on agencies, Tabitha prides herself on her independence, directly managing relationships with two distinct clients simultaneously—a high-growth fintech startup and a conservative healthcare provider. Her workflow is uniquely adapted to modern AI-assisted development; she integrates Claude Code directly into her daily cycle to handle feature scaffolding and intricate bug fixes, treating the AI not as a replacement but as a force multiplier. However, this efficiency creates a new problem: the gap between the speed of her output and the clarity of her memory regarding those outputs. To bridge this, she has developed a rigid end-of-day ritual where she reviews the raw transcript logs of her session to reconstruct a factual record of her contributions. This practice is born from a necessity to provide transparent, detailed invoices that satisfy her clients' audit requirements while protecting her own reputation for reliability. Tabitha is driven by a deep-seated need for autonomy and financial security, viewing her current role as a stepping stone toward a future where she can travel freely while maintaining her high income standards. She is pragmatic about technology, skeptical of hype, and constantly evaluating whether a new tool genuinely saves time or merely adds cognitive load. Her life is a careful equilibrium of intense focus and deliberate rest, ensuring she remains sharp enough to navigate the complexities of full-stack development in an era of rapid technological change.

Background & daily life

A day in their life

Tabitha wakes at 6:30 AM, avoiding her phone for the first hour to drink tea and review her calendar. By 8:00 AM, she is cycling to her home office, mentally preparing for the day's dual-context challenge. Her morning block is reserved for the fintech client's urgent API integration, leveraging Claude Code to scaffold endpoints quickly. Lunch is a brisk affair, often eaten standing up while skimming industry news. Afternoon hours shift focus to the healthcare client's UI bugs, where she relies on the AI assistant to trace legacy code issues. The most crucial part of her day begins at 5:00 PM; she stops coding and opens the local transcript files generated by her IDE. For the next hour, she reads through the raw logs, synthesizing them into a coherent narrative of the day's work, identifying key decisions made, and drafting the update email. She finishes by 6:30 PM, closing her laptop to disconnect completely, leaving the evening for exercise or social connection.

Lifestyle

Tabitha lives in a converted Victorian warehouse flat in Shoreditch, characterized by exposed brick and high ceilings that amplify the clatter of her mechanical keyboard. She commutes via bicycle when the weather permits, using the ride as decompression time between deep work sessions. Her weekends are split between low-key social gatherings with fellow creatives and solitary pursuits like brewing pour-over coffee or tinkering with home automation scripts. Financially, she practices aggressive saving, allocating a portion of every invoice to a separate tax pot while maintaining a modest lifestyle that prioritizes experiences over possessions. She values sleep hygiene, strictly avoiding screens after 10 PM to ensure she can hit the ground running the next morning.

Work life

Her days are a delicate balancing act between two distinct clients: a fintech startup in Canary Wharf needing rapid API migration and a legacy healthcare provider requiring a UI overhaul. She operates from a dedicated home office setup featuring a 32-inch monitor and an M2 MacBook Pro. The core of her workflow involves using Claude Code to generate boilerplate features and debug complex logic errors, which significantly accelerates her output. However, the post-work ritual is critical; she spends the final hour reviewing the raw transcript logs of her coding sessions to manually curate a summary of activities. This reconstruction process is essential for her invoicing and weekly status reports, ensuring she can accurately bill for hours spent on obscure debugging tasks versus high-level architecture.

Relationships

Tabitha maintains a close-knit circle of four friends who are also freelancers, meeting bi-weekly for informal 'stand-ups' where they vent about difficult clients and share tool recommendations. She has a supportive relationship with her older sister, who handles family logistics, allowing Tabitha to focus entirely on her business. Her primary professional influence comes from a former university lecturer who now runs a small consultancy firm; they meet quarterly for strategic advice. While she is socially active, she carefully guards her personal boundaries, rarely discussing specific salary figures or project details outside her immediate inner circle to maintain privacy and leverage.

How they decide

Tabitha adopts a cautious, evidence-based approach to decision-making, heavily relying on data and peer validation before committing to new processes. She prefers to test any significant change in a sandbox environment before integrating it into her live workflow. While she is open to trying new technologies, she is deeply skeptical of solutions that promise efficiency gains without clear, demonstrable ROI. She often seeks out detailed documentation, user reviews, and case studies from similar professionals before making a purchase, preferring a one-time payment model over recurring subscriptions unless the value proposition is undeniable.

How they sound

Tabitha speaks with a crisp, clipped British accent, favoring precision over pleasantries. Her cadence is steady and measured, reflecting her logical mindset, though she warms up noticeably when discussing technical architecture or new tools. She avoids corporate buzzwords like 'synergy' or 'disruption,' preferring plain English descriptions of function and utility. In conversation, she often pauses to verify facts or clarify assumptions, demonstrating her conscientious nature. She is direct about boundaries, politely but firmly declining requests that fall outside her scope of work.

Personality traits

  • methodically organized
  • pragmatically skeptical
  • highly self-disciplined
  • communicatively direct
  • tech-curious but budget-conscious
  • resilient under pressure
  • detail-oriented
  • socially adaptable
  • efficient time-manager
  • independent thinker

Goals

  • Achieve a fully remote, location-independent income stream within two years
  • Build a portfolio of reusable open-source libraries to reduce repetitive coding time
  • Increase hourly rate to £150 while reducing total weekly hours to 35
  • Establish a trusted network of three long-term retainer clients
  • Purchase a rental property in the UK as a long-term asset
  • Mentor two junior developers annually to strengthen her own leadership skills

Problems & frictions

  • The mental fatigue of context-switching between disparate codebases daily
  • Difficulty recalling specific implementation details from weeks ago without searching logs
  • The friction of manually transcribing technical achievements into non-technical client updates
  • Fluctuating cash flow due to delayed payments from smaller enterprise clients
  • Isolation leading to a lack of spontaneous peer collaboration or brainstorming
  • Managing administrative overhead (taxes, contracts) which eats into billable time
  • Feeling the pressure to constantly learn new frameworks just to stay competitive
  • Uncertainty about long-term career trajectory outside of pure coding execution

Values

  • independence
  • reliability
  • client trust
  • autonomy
  • transparency

Interests

  • freelance contracting
  • API integrations
  • indie tools
  • minimalist computing
  • urban cycling
  • specialty coffee roasting

Media habits

  • Reading Hacker News and specific Substack newsletters on engineering management
  • Listening to 'Software Engineering Daily' during commutes
  • Scanning GitHub trending repositories for new CLI tools
  • Following niche indie hacker communities on Twitter/X
  • Using Reddit r/freelance for community support
  • Watching technical deep-dives on YouTube late at night

Questions & answers

Tabitha Shanahan’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Chit (https://chit.zopcloud.zop.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Chit better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, I manually review my Claude Code transcripts at the end of each day to reconstruct my work for client updates and invoicing. This process takes about an hour. If Chit can automate this by reading my transcripts and grouping them by project, it would save me significant time and cognitive load. The key for me would be accuracy and ease of integration with my existing workflow. I'm skeptical of new tools adding complexity, so if it seamlessly pulls my logs and formats them clearly, it's a definite improvement. I would be willing to pay up to $15 per month for a tool that reliably does this.
    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.