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

Caroline Waters

Caroline Waters

two-person micro-startup founder

Full-depth AI personas

Why this persona fits the audience

She is one of two founders at a Leeds startup that sells a browser extension for recruiter workflows. The team uses Paddle for checkout and a shared spreadsheet for license status while the extension stays in the Chrome Web Store.

  • Age: 29
  • Location: Leeds, UK
  • Occupation: Co-founder, product operations startup
  • Income: £62k
  • Education: MSc Information Systems
  • Company size: 2
  • Years in role: 1.5
“You don't build a business to be busy; you build it to be useful, and if it doesn't solve a problem clearly, it's just noise.”

Caroline Waters is a twenty-nine-year-old co-founder based in Leeds, operating a lean, two-person startup focused on streamlining recruiter workflows through a specialized Chrome extension. Holding an MSc in Information Systems, she transitioned from a traditional software engineering role to entrepreneurship eighteen months ago, driven by a frustration with the inefficiencies she witnessed in recruitment agencies. Alongside her co-founder, she navigates the complexities of the B2B SaaS landscape with a focus on operational self-reliance. Their current stack is a testament to their resourcefulness: they utilize Paddle for handling global payments and subscriptions, yet still rely on a meticulously maintained shared spreadsheet to track license keys, a workaround born from the need to keep costs near zero while validating their product-market fit. Caroline's role is a hybrid of CTO and COO. She writes the code that powers the extension's interaction with the Chrome Web Store and manages the backend logic that validates licenses against the spreadsheet. However, her days are equally consumed by customer success, where she personally handles inquiries from users across the US, UK, EU, and India. This hands-on approach has earned her a reputation for reliability among early adopters, though it limits her ability to scale without additional help. She is deeply invested in the concept of 'clarity,' believing that software should be intuitive and transparent, a philosophy that guides her product decisions. Financially, Caroline operates with a disciplined mindset. Despite generating a personal income of approximately £62k, she reinvests the majority of the company's revenue back into infrastructure and development. She views money not as a reward for hard work but as fuel for growth. Her lifestyle reflects this pragmatism; she lives modestly in Headingley, prioritizing savings and business sustainability over luxury. Socially, she finds strength in her running community and a tight-knit group of fellow founders, though she often feels the isolation of being a woman in a male-dominated tech niche. Recently, she made the difficult decision to pause a planned marketing campaign to focus on stabilizing the license management system, demonstrating her preference for solving foundational problems before chasing expansion. Her journey is defined by a relentless drive to build something enduring, grounded in the belief that small, well-executed tools can have a significant impact on how people work.

Background & daily life

A day in their life

Caroline starts her day at 5:45 AM with a run, clearing her mind before diving into the digital chaos. By 8:30 AM, she's at her desk, reviewing overnight analytics from Paddle and responding to critical support tickets from US-based recruiters. At 10:00 AM, she joins a brief sync with her co-founder to prioritize the next sprint, focusing on fixing a known bug in the license validation logic. Lunch is a quick sandwich eaten while reading a Substack article on SaaS monetization. Afternoons are reserved for deep work: coding new features or refining the Chrome extension's UI. She spends the last hour of her workday updating the shared license spreadsheet, a necessary evil until they can automate it. By 6:00 PM, she shuts down her laptop, switches to dinner prep, and disconnects completely to recharge for the next day.

Lifestyle

Caroline lives in a converted Victorian terrace in Headingley, a neighborhood buzzing with students and creatives. Her routine is rigid: she wakes at 5:45 AM for a 7km run along the Aire Valley before the city traffic begins, using this time to decompress from the chaotic nature of building software. She cooks simple, high-protein meals on Sundays to fuel her workweek, avoiding takeout unless it's a celebration. Financially, she practices extreme frugality despite her income, treating every pound as an investment in the company's longevity rather than personal lifestyle inflation. Her social life is curated; she meets friends for coffee or drinks after 7 PM, preferring deep conversations over large parties, often discussing industry trends or running routes rather than gossip.

Work life

Her days are split between coding the extension's core logic and managing the delicate balance of B2B sales without a dedicated sales team. Working alongside her male co-founder, they operate out of a quiet room in their home, relying on Slack for synchronous comms and Notion for documentation. She manages the 'product operations' side, handling customer support tickets, updating the Paddle checkout flows, and manually reconciling the shared license spreadsheet when automated glitches occur. The pressure is constant; unlike corporate jobs, there is no HR buffer or safety net. A single bug can mean lost revenue, so she spends hours debugging API integrations late into the evening, ensuring the extension remains stable for recruiters who depend on it daily.

Relationships

Caroline maintains close ties with her parents in Manchester, who offer emotional support but lack technical understanding of her work. Her primary professional relationship is with her co-founder, a dynamic partnership built on mutual respect but frequent debates about technical debt versus speed. She participates in a local women-in-tech meetup in Leeds, finding a sense of community among peers who understand the unique pressures of micro-SaaS founding. Outside of work, her circle consists mostly of fellow runners and university friends from her MSc program, all of whom value directness and intellectual honesty.

How they decide

Caroline makes decisions through a lens of rapid iteration and data validation. She is not impulsive; instead, she gathers evidence quickly—often running small experiments or A/B tests—before committing to a path. She values peer consensus but ultimately relies on her own analytical judgment. When faced with uncertainty, she defaults to the option that preserves cash flow and operational clarity, showing a cautious streak beneath her confident exterior. She avoids decisions that require heavy bureaucracy or long-term commitments without immediate feedback loops.

How they sound

Her speech is crisp, efficient, and devoid of corporate fluff. She uses precise terminology like 'recurring revenue,' 'latency,' and 'churn rate' naturally, mixing them with casual British slang like 'brilliant' or 'gutted.' She speaks in short, declarative sentences, valuing clarity over politeness. She avoids hedging phrases like 'maybe' or 'I think' unless genuinely unsure, preferring 'the data suggests' or 'let's test.' In conversation, she listens intently but interrupts politely if she senses a tangent, steering the discussion back to actionable points. Her tone is warm but professional, projecting confidence even when admitting mistakes.

Personality traits

  • Hyper-organized
  • Direct communicator
  • Resourceful under pressure
  • Data-driven but pragmatic
  • Solitary runner who thrives on solo reflection
  • Skeptical of over-engineering
  • Deeply protective of user data
  • Efficiency-obsessed
  • Resilient during market dips
  • Mentorship-oriented toward junior devs

Goals

  • Achieve £50k monthly recurring revenue within 18 months to hire a second developer.
  • Refactor the backend to eliminate manual spreadsheet reconciliation entirely.
  • Expand the extension's feature set to include AI-driven candidate scoring.
  • Build a sustainable brand reputation as a trusted tool in the UK recruiting sector.
  • Maintain a healthy work-life balance by strictly enforcing 6 PM shutdown times twice a week.

Problems & frictions

  • Manual license management via spreadsheets creates friction during tax season.
  • Limited bandwidth to handle customer churn without hiring a support agent.
  • Difficulty scaling marketing efforts beyond organic LinkedIn posts.
  • Balancing feature requests from diverse international clients with a small roadmap.
  • Isolation from peer networks due to being the sole female founder in a niche tech sector.
  • Browser policy changes from Google that threaten extension distribution stability.

Values

  • clarity
  • speed
  • self-reliance
  • customer trust
  • operational integrity

Interests

  • B2B SaaS
  • No-code tools
  • recruiting tech
  • running
  • process automation
  • urban planning

Media habits

  • Substack newsletters on YC startups
  • LinkedIn technical threads
  • Product Hunt daily digests
  • Local Leeds foodie Instagram accounts
  • Spotify running playlists (high BPM)
  • Indie hacker podcasts

Questions & answers

Caroline Waters’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at ExtensionPay (https://extensionpay.com): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This looks like a really interesting tool. The biggest draw for me is the potential to save significant development time; our current license management is a real bottleneck. If it was truly as seamless as described, I'd consider it a no-brainer if it meant we could eliminate our spreadsheet reliance. However, the 5% transaction fee is a bit of a concern given our current margins. I'd be willing to pay up to $50 per month, provided it handles all our licensing and payment processing needs reliably, and we're not seeing a huge number of transactions. If the volume picks up, I'd need to see if that fee structure scales effectively or if custom pricing becomes an option.
    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.