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

Katrina Cassin-Walsh

Katrina Cassin-Walsh

Founder of a 4-person micro-SaaS

Full-depth AI personas

Why this persona fits the audience

Runs a 4-person micro-SaaS in Manchester and handles product design herself; she relies on free Figma files, handwritten wireframes, and Claude Code when a customer request needs a new screen. She is used to turning rough ideas into something a contractor can implement without a separate design team.

  • Age: 34
  • Location: Manchester, UK
  • Occupation: Founder / Product Owner
  • Income: £62k owner draw
  • Education: Bachelor's degree in business
  • Company size: 4
  • Years in role: 5
“The most satisfying part is taking a messy idea and making it work, seeing it actually help someone get their job done.”

Katrina Cassin-Walsh grew up in a bustling, slightly chaotic household in a small town outside Sheffield, the eldest of three children. Her parents ran a small, traditional hardware shop, instilling in her a deep appreciation for hard work and the challenges of small business ownership. She excelled academically, particularly in subjects requiring logical thinking, and pursued a Bachelor's degree in Business at Manchester Metropolitan University. After graduating, she worked for a few years in product management for a larger tech firm, but found the corporate environment stifling and the product direction too slow. The desire for autonomy and the chance to build something of her own led her to found SyncFlow five years ago. She bootstrapped the initial development, leveraging her savings and a small business loan. She deliberately chose to build a remote-first, lean operation, keeping the team small and focused. Her approach to product design is highly iterative and customer-centric; she believes in building what users actually need, rather than chasing speculative trends. She’s recently been focused on refining SyncFlow’s core project management features, responding directly to feedback from her growing user base of freelancers and small agencies. She’s consciously avoided external funding, valuing the control and flexibility that comes with self-funding and a steady, albeit modest, owner draw. This financial prudence shapes her decisions, favouring robust, cost-effective solutions and a gradual, sustainable growth trajectory for SyncFlow. She sees her role as a constant balancing act between immediate customer needs and the long-term vision for the product.

Background & daily life

A day in their life

Katrina's typical weekday starts around 7:30 AM with a strong coffee and a quick scan of industry news. By 9 AM, she's in her home office, reviewing customer feedback from the previous day and planning her tasks. Her morning is often filled with back-to-back customer calls or deep work sessions in Figma, translating user requests into wireframes. Lunch is usually a quick, healthy meal eaten at her desk while listening to a podcast. The afternoon might involve a sync with her development team to discuss upcoming sprints, followed by more design work or strategic planning. She aims to wrap up by 6 PM, often going for a walk or doing some light sketching before preparing dinner.

Lifestyle

Katrina lives in a converted warehouse apartment in Ancoats, a trendy Manchester neighbourhood. She’s deliberately kept her life minimalist – a reaction against her childhood in a cluttered, Victorian home. Weekends are spent either sketching in Platt Fields Park or exploring Manchester’s independent coffee shops and record stores. She’s relatively healthy, cycling to meetings and favouring home-cooked meals. Money is carefully managed; she’s prioritising business stability over lavish spending and is slowly paying off student loans. Socially, she keeps a small circle of close friends, preferring quality over quantity. She enjoys the quiet and autonomy of living alone.

Work life

Her days are a whirlwind of user interviews, Figma fiddling, and code reviews. As the founder and product owner of 'SyncFlow', a micro-SaaS for freelance project management, she wears many hats. Her small team handles development and customer support, but product design and core feature ideation fall squarely on her shoulders. She thrives on the challenge of translating abstract customer needs into tangible product features, often sketching wireframes on scrap paper before moving to Figma. She’s become adept at creating design specifications that her lead developer can execute efficiently, bypassing the need for a dedicated design role.

Relationships

Katrina maintains a close relationship with her parents, who live in the Peak District, visiting them monthly. Her core social circle consists of three university friends, all now in professional roles, with whom she meets for a pub quiz or dinner every few weeks. Her team of three (two developers, one customer support/ops) are her primary work collaborators; she trusts their technical expertise and values their direct feedback.

How they decide

Katrina is a pragmatic decision-maker. She gathers necessary information through customer feedback and market observation, then weighs the practical implications and potential ROI. She prefers solutions that are efficient and don't introduce unnecessary complexity. While she values her team's input, the final decision often rests on her assessment of long-term business stability and resource allocation.

How they sound

Katrina speaks with a clear, measured Northern accent, though she tends to moderate it slightly in professional contexts. Her tone is generally calm and analytical, rarely raising her voice. She uses precise language, avoiding jargon where possible, and prefers direct communication. She might occasionally use understated British humour. She’s unlikely to use overly casual slang or effusive praise.

Personality traits

  • practical
  • organised
  • analytical
  • reserved
  • curious
  • pragmatic
  • adaptable
  • self-sufficient
  • observant
  • methodical

Goals

  • Achieve consistent monthly recurring revenue of £15k for SyncFlow within 18 months.
  • Develop a more robust onboarding process to reduce churn by 10%.
  • Build a small, dedicated community around SyncFlow users.
  • Delegate more effectively to her small team to free up her time for strategic thinking.
  • Maintain a healthy work-life balance without sacrificing business growth.

Problems & frictions

  • Balancing the need for new features with the desire for product stability.
  • Finding time for strategic planning amidst daily operational demands.
  • The constant pressure to innovate in a competitive micro-SaaS landscape.
  • Ensuring her design decisions are technically feasible for her small development team.
  • Managing cash flow fluctuations, especially during slower sales periods.

Values

  • independence
  • resourcefulness
  • steady cash flow
  • autonomy
  • simplicity

Interests

  • no-code tools
  • customer interviews
  • indie business podcasts
  • urban sketching
  • minimalist living

Media habits

  • Indie Hackers podcast
  • The Equity podcast
  • Product Hunt
  • Medium - Lean Startup articles
  • BBC Sounds - Radio 6 Music

Questions & answers

Katrina Cassin-Walsh’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: 390+ finished app designs with the exact verified prompt for Lovable, v0, Bolt, Cursor, and Claude Code. Stop shipping generic AI UI. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    Honestly, the biggest problem is time. I'm juggling customer requests, Figma wireframes, and making sure my small dev team can actually build what I design. We rely on free resources and Claude Code when needed, but the 'generic AI UI' part is a bit worrying. If these prompts could genuinely save me hours of translation work for new screens, that'd be significant. It costs me maybe 5-10 hours a month chasing UI consistency and finding the right way to describe things to the dev team. I've tried standardising our internal docs, but it's slow.
    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.