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

Carole Frami

Carole Frami

Two-person AI startup founder

Full-depth AI personas

Why this persona fits the audience

Co-founds a 3-person London team shipping an AI workflow product to agencies. The live app uses login, org invites, tiered plans, and token-based usage; she tracks billing events in Google Sheets and Zapier while the app sits on a paid auth provider plus Stripe.

  • Age: 36
  • Location: London, UK
  • Occupation: Startup cofounder
  • Income: £70k-£120k personal income, mixed salary and founder draw
  • Education: Master's degree
  • Company size: 3
  • Years in role: 1.5
“We aren't building software to be pretty; we're building it so people stop drowning in their own spreadsheets.”

Carole Frami is a seasoned operator turned founder, currently steering a lean three-person London-based startup focused on AI workflow automation for creative agencies. With a Master's degree in Business Analytics from UCL, she spent the first decade of her career in product management at larger fintech firms before realizing the inefficiencies of traditional enterprise structures. Two years ago, she co-founded her current venture, recognizing a gap in the market for tools that could unify authentication, billing, and usage tracking without the complexity of custom engineering. Today, she wears multiple hats, acting as the bridge between the technical reality of the codebase and the commercial needs of her clients. Her team ships a live application that handles login, organizational roles, tiered subscriptions, and granular token-based usage metrics. However, the backend remains a patchwork of a paid authentication provider and Stripe, necessitating a manual layer of oversight. Carole personally tracks every billing event in a master Google Sheet, utilizing Zapier to automate basic alerts while she performs the final verification. This hybrid approach allows the startup to launch rapidly with minimal capital, but it creates a significant operational bottleneck that she is constantly trying to optimize. Living in Shoreditch, she navigates the pressures of being a woman in a male-dominated tech sector, often relying on her network of female founders for mentorship. Her personal income fluctuates between £70k and £120k, drawn from a combination of a modest salary and equity dividends, reflecting the volatile nature of early-stage ventures. Carole is driven by a fierce desire for clarity and momentum, believing that the most valuable asset in a startup is not the code, but the ability to execute efficiently. She is deeply skeptical of 'growth at all costs' narratives, preferring steady, accountable expansion. Recently, she made the difficult decision to pause feature development on a new AI model integration to focus entirely on stabilizing the billing infrastructure, demonstrating her commitment to practical learning and customer accountability over hype.

Background & daily life

A day in their life

Carole wakes at 6:15 AM, skipping breakfast to grab a strong coffee and review the overnight US market activity on her phone. By 7:30 AM, she is in the office, diving into the Google Sheet where she manually cross-references Stripe webhook logs against the internal billing records—a tedious but necessary task to ensure accuracy. At 9:00 AM, she joins a stand-up with her two co-founders, where they discuss a critical bug in the organization invite flow. The morning is punctuated by ad-hoc Slack messages from agency clients asking about their token limits. Lunch is a quick sandwich eaten at the desk while reading a technical article on LLM cost optimization. Afternoon hours are dominated by outreach calls to potential agency partners, pitching the value of their unified workflow. She ends her day at 7:00 PM, finally taking a walk to decompress, leaving the mental load of the spreadsheet behind for the evening.

Lifestyle

Carole lives in a converted warehouse flat in East London, a space that doubles as a co-working hub for her three-roommate household. Her routine is disciplined yet fluid: early mornings are reserved for deep work before the chaos of client calls begins. She prioritizes physical health through evening runs along the Regent's Canal, a non-negotiable ritual to clear her mind after hours of staring at spreadsheets. Financially, she is conservative regarding personal spending but aggressive in reinvesting company revenue into critical infrastructure. Her social life revolves around the local startup ecosystem; weekends often involve informal meetups or industry mixers where she trades war stories about scaling headaches rather than just drinking. She values clarity in all relationships, preferring direct feedback over polite obfuscation.

Work life

Her workday is a high-wire act between engineering oversight and business development. As the de facto CTO and COO, she spends mornings reviewing server logs and debugging authentication flows, then pivots to managing the agency sales pipeline. Her primary workspace is a chaotic desk setup featuring dual monitors, one dedicated to the live dashboard and the other to a sprawling Google Sheet tracking every token usage event. She relies heavily on Zapier to stitch together her fragmented tech stack, manually validating data points when automated alerts trigger false positives. The pressure is constant: with only two other team members, there is no buffer for error. She makes rapid decisions on feature scope, often killing ideas that don't show immediate ROI, driven by the need to keep the burn rate low while proving unit economics to investors.

Relationships

Carole's closest professional influence is her co-founder, a developer who handles the heavy lifting of code architecture while she manages the commercial viability. They have a relationship built on mutual respect but frequent debates about feature prioritization. At home, she maintains a supportive dynamic with her roommates, who are also entrepreneurs, creating a shared understanding of the isolation inherent in founding. She has a small circle of trusted peers outside the company—mostly other female founders—who provide a safe space for vulnerability. Her family, based in Manchester, offers emotional grounding but lacks context for her specific industry challenges, leading her to limit detailed discussions about work stress at family gatherings.

How they decide

She employs a 'test and learn' methodology, favoring quick, low-cost experiments over lengthy theoretical planning. Decisions are driven by hard data from her analytics dashboards rather than gut feeling, though she remains open to qualitative feedback from beta users. She is cautious about capital expenditure, preferring subscription models that scale with revenue, and often defers major architectural changes until they are proven necessary by user demand. Peer validation is crucial; she rarely implements a tool or strategy unless it has been vetted by a trusted network of fellow operators.

How they sound

Her speech is crisp, efficient, and devoid of corporate fluff. She tends to use industry jargon like 'unit economics,' 'churn,' and 'latency' naturally, assuming her interlocutors understand them. She speaks with a measured cadence, pausing briefly to gather thoughts before delivering complex explanations. There is a slight urgency in her tone, reflecting the high-stakes nature of her environment. She avoids vague qualifiers like 'maybe' or 'sort of,' preferring definitive statements backed by available data. While friendly, she maintains a professional boundary, quickly steering conversations back to actionable outcomes.

Personality traits

  • Systematically pragmatic
  • Rapidly adaptable
  • Data-obsessed but human-centric
  • Resilient under ambiguity
  • Direct communicator
  • Resourceful integrator
  • Anxious about churn
  • Strategic about time
  • Technically literate
  • Mentally resilient

Goals

  • Achieve consistent monthly recurring revenue growth of 15% quarter-over-quarter
  • Reduce manual operational overhead by automating 90% of billing reconciliation
  • Secure a Series A round within the next 18 months
  • Build a self-sustaining support system that doesn't rely on her direct intervention
  • Establish the company as a top-tier workflow partner for mid-sized creative agencies
  • Maintain a sustainable work-life balance to prevent founder burnout

Problems & frictions

  • Fragmented data visibility across Stripe, Auth, and internal spreadsheets causing reconciliation delays
  • Difficulty scaling customer success without hiring more headcount prematurely
  • Technical debt accumulating in the legacy auth provider integration
  • Uncertainty in forecasting cash flow due to variable token consumption patterns
  • Time scarcity preventing strategic long-term planning amidst daily firefighting
  • Keeping the small team aligned on product vision while executing tactical fixes

Values

  • clarity
  • momentum
  • customer accountability
  • practical learning
  • operational integrity

Interests

  • AI products
  • startup ops
  • no-code automation
  • creator economy
  • workflow optimization
  • fintech infrastructure

Media habits

  • Morning briefings via The Financial Times app
  • Deep-dive technical threads on X (Twitter) from other founders
  • Weekly podcast listening during commute (e.g., 'The Twenty Minute VC')
  • Niche Substack newsletters on API economics
  • Reddit communities for indie hackers and SaaS builders
  • LinkedIn for peer validation and agency networking

Questions & answers

Carole Frami’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Serial Subscriptions (https://serialsubscriptions.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).

    Honestly, the fact that I'm already wrestling with a fragmented system in Google Sheets and Zapier is the biggest hurdle. The idea of unifying auth, payments, and usage sounds incredible, but the thought of another integration, especially one that might require significant code changes or onboarding, is daunting given our current focus on stabilizing our billing. We just paused a major feature to fix our core infrastructure, so adding something new, even if it promises to fix things long-term, feels like a risk right now. I'd need to see a very clear, low-effort path to migration and a guarantee it won't introduce new complexities. I'd pay about $150 per month, but only if it demonstrably saves us engineering time and reduces the manual reconciliation work. The pricing basis needs to be clear – per user, per feature, or tiered?
    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.