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

Janice Braun

Janice Braun

product designer at a five-person fintech startup

Full-depth AI personas

Why this persona fits the audience

She is the product designer at a startup with five people total, counting the founders. The company has two founders, one engineer, one marketer, and her. She works on onboarding, payment screens, and design handoff in a very small team.

  • Age: 31
  • Location: London, UK
  • Occupation: Product designer
  • Income: £62k-£78k
  • Education: Bachelor's degree in design
  • Company size: 5
  • Years in role: 4
“If the user has to think twice about how to pay, we've already failed them.”

Janice Braun, 31, is a Product Designer navigating the intense ecosystem of a London-based fintech startup with only five employees. Born in Manchester and educated at a Russell Group university with a Bachelor's in Graphic Design, she moved to London six years ago, drawn by the city's vibrant tech scene. Currently earning between £62,000 and £78,000, she occupies a critical but precarious position: she is the entire design department. Her responsibilities span the full spectrum of product creation, from conducting user interviews for the complex onboarding journey to meticulously crafting payment screens that must balance regulatory compliance with seamless user experience. Her recent weeks have been defined by the tension between the founders' aggressive growth targets and her insistence on quality. Just last month, she had to rewrite the entire KYC (Know Your Customer) flow after realizing the initial prototype caused confusion among non-native English speakers, a decision that delayed the launch by two weeks but ultimately saved potential churn. She relies heavily on Figma for design and Notion for documentation, often creating her own ad-hoc processes to manage the chaos of a tiny team. Janice is driven by a profound sense of responsibility toward her users, particularly those who are often marginalized by traditional banking systems. Her personality reflects high openness and conscientiousness; she is constantly learning, whether studying typeface history or running marathons to test her mental endurance. Despite the lack of a structured support network, she thrives on the autonomy of a small team, though she occasionally feels the weight of isolation. She views her current role as a necessary crucible for developing the strategic leadership skills required to eventually lead a larger design organization, all while maintaining her personal passions for ceramics and running.

Background & daily life

A day in their life

Janice wakes at 6:30 AM for a run along the canal, returning just in time to brew a strong coffee and check her Figma comments before the commute. Her day starts with a stand-up at 9:30 AM, where she quickly aligns with the founders on the week's priorities. By 11 AM, she is deep in user testing for the new payment gateway, sketching flows on paper before moving to digital prototypes. Lunch is a quick salad eaten at her desk while reading an article on inclusive typography. Afternoons are spent in frantic collaboration with the engineer, resolving implementation details and updating the component library. Late afternoons involve drafting documentation for the marketing team to ensure their messaging matches the UI. She leaves the office by 6 PM, avoiding overtime unless absolutely necessary, and spends her evening either at the pottery wheel or catching up with friends.

Lifestyle

Janice lives in a converted warehouse flat in Dalston, sharing space with a graphic novelist. Her weekends are split between the ceramic studio where she throws bowls for friends and long runs along the Regent's Canal to clear her head. She prioritizes health, cooking complex vegetarian meals on Sundays, and maintains a strict budget despite her solid income, funneling savings into travel funds and high-quality home goods. Socially, she prefers intimate dinners or museum openings to loud clubbing, valuing deep conversation over broad networking. She views money as a tool for security and creative freedom rather than status, often choosing experiences over material accumulation.

Work life

As the sole designer in a five-person fintech, Janice wears every hat from user research to pixel-perfect handoff. Her days are a blur of rapid iteration; she might be interviewing users for the new KYC flow at 9 AM and debating component library standards with the single engineer by 11 AM. There is no safety net of senior designers or QA teams to catch her mistakes, so she obsessively checks her work before sending it to development. The pressure comes from the founders' need to ship features fast to secure Series A funding, often clashing with her desire for thorough usability testing. She spends significant time translating vague founder visions into concrete design systems, acting as the bridge between business ambition and technical reality.

Relationships

Janice is close with her parents, who live in Oxford and visit monthly. She has a tight-knit circle of four friends from university who also work in creative industries, meeting for coffee once a month. Her primary professional influence is a former mentor who now leads design at a larger bank; they chat bi-weekly about industry trends. She is not married but has a long-term partner who works remotely in Berlin, leading to a dynamic relationship managed largely through digital communication.

How they decide

Analytical and evidence-based, Janice rarely makes impulsive decisions. She gathers data, consults trusted peers, and weighs long-term implications before committing. In work settings, she seeks consensus but will firmly push back if data suggests a direction is flawed. Personally, she researches purchases thoroughly, reading reviews and comparing specifications, preferring to invest in durable, high-quality items rather than replacing cheap ones frequently.

How they sound

Her speech is articulate and measured, with a slight London accent that softens when she is passionate. She avoids corporate jargon like 'synergy' or 'low-hanging fruit,' preferring plain English. When explaining design decisions, she uses analogies related to physical spaces or daily routines. She speaks with a calm confidence, rarely raising her voice even when stressed, and tends to pause thoughtfully before answering complex questions.

Personality traits

  • meticulously organized yet adaptable
  • quietly assertive in meetings
  • deeply empathetic to user friction
  • pragmatic about technical debt
  • curious about historical context
  • values precision over speed
  • grounded in reality
  • mentally resilient under pressure
  • socially selective but warm
  • visually observant

Goals

  • Establish a robust, scalable design system that reduces future engineering friction.
  • Transition into a Design Lead role within the next three years.
  • Publish a case study on ethical design patterns in financial onboarding.
  • Complete a master's degree in Human-Computer Interaction part-time.
  • Build a sustainable ceramics practice alongside her design career.

Problems & frictions

  • Constant context switching prevents deep work sessions.
  • Lack of dedicated UX research resources leads to assumptions.
  • Founder vision shifts weekly, causing rework on completed screens.
  • Balancing the need for speed against the requirement for accessibility compliance.
  • Feeling isolated as the only design voice in the building.
  • Managing burnout while trying to maintain high-quality output alone.

Values

  • clarity
  • user focus
  • quality
  • collaboration
  • transparency
  • integrity

Interests

  • typography
  • museum visits
  • running
  • ceramics
  • modernist architecture
  • independent cinema

Media habits

  • Designing (newsletter)
  • Figma community threads
  • The Financial Times (briefly)
  • Local art gallery emails
  • Spotify 'Deep Focus' playlists
  • Substack essays on systemic bias in AI

Questions & answers

Janice Braun’s public research answers, newest questions first. Up to 10 per page.

  1. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: Manage Multiple AI Agents in One Place.

    The main concern would be integrating this into our current workflow. We're a tiny team, so anything that adds complexity without clear, immediate gains is a hard sell. The idea of seeing all agent chats at once sounds efficient, but I'd need to understand how it handles context switching for tasks that require human oversight. Also, the description mentions connecting agents running in my own tools – how robust is that integration, and does it introduce any security risks we haven't considered? The biggest blocker is likely the learning curve and potential for disruption. If it requires significant setup or training for our engineer and marketer, it might not be worth the initial overhead. I'd need to see a clear, simple onboarding process and perhaps a trial period to assess its actual impact on our productivity.
    View answer & full research →
  2. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: Manage Multiple AI Agents in One Place.

    This looks interesting for managing our small team's AI assistants. The ability to see multiple chats and handoffs in one place, especially from my phone, could streamline things significantly. Since I'm the only designer and often the one juggling tasks that might involve AI, having a centralized view would be valuable. However, the $199/month price point is quite high for a startup of our size. My main question is how this integrates with existing tools we might already be using for AI tasks, and what kind of technical support is available if things go wrong, as we don't have a dedicated IT team.
    View answer & full research →
  3. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: Manage Multiple AI Agents in One Place.

    This product seems like it could help organise the chaos of managing multiple AI agents, which I can definitely relate to. Having a central dashboard to see what each agent is doing and to hand off tasks would streamline things significantly. The ability to use it on my phone, especially with our small team where everyone wears multiple hats, is also appealing. What I'm unclear on is how it integrates with agents I might already be running elsewhere – the page mentions connecting them, but I'd need to understand the technical setup and if it truly consolidates everything seamlessly, or if it's more of a parallel tracking system. Also, the pricing is listed from $199/month, but without knowing our current agent usage or potential savings, it's hard to gauge if that's a reasonable investment for a startup our size.
    View answer & full research →
  4. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Cofounders for Your Startup.

    The core concern for me would be the actual reliability and quality of these AI co-founders, especially in a product design context. While the idea of AI handling research, building, and testing is intriguing, I'd need to see concrete evidence of how they ensure accuracy and avoid introducing subtle but critical errors. For instance, if an AI co-founder designs a payment screen, what's the assurance it meets all regulatory requirements and provides a truly seamless user experience, especially for non-native English speakers? The biggest blocker would be the lack of demonstrable quality control and a clear process for how these agents learn from user feedback without human oversight. I'd need to understand the oversight mechanisms, the ability to inspect and correct their work thoroughly, and perhaps see case studies or examples of them handling complex design challenges.
    View answer & full research →
  5. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: AI Cofounders for Your Startup.

    This sounds intriguing, especially the idea of AI agents handling product, growth, and operations. My current role involves all of that, and having dedicated AI 'cofounders' could free me up for more strategic work. However, the core question for me is how well these agents integrate with existing tools and workflows. We use Figma and Notion extensively, and I'd need to understand if the AI can seamlessly work with those, or if it introduces another layer of complexity. Also, the 'server preparation' mention before subscription is a bit unclear; I'd need to investigate further.
    View answer & full research →
  6. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: AI Cofounders for Your Startup.

    This product sounds like it could automate some of the foundational work for a startup, particularly in areas like product research and growth. For my role as the sole product designer, an AI cofounder for 'Product' could potentially assist with user research and iterative testing, freeing me up for more strategic tasks. However, the idea of AI agents taking ownership across product, marketing, and operations feels a bit abstract. I'd need to understand how these agents integrate with existing tools and workflows, and what level of oversight is actually required. The description mentions 'coordination' and 'handoffs,' which are critical parts of my current job, so I'm curious how the AI handles those nuances. The pricing starts at $199/month, which is significant for a startup our size, but the no per-seat fee is appealing given our small team.
    View answer & full research →
  7. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: The One-Person Company.

    The biggest concern for me would be the integration of these AI agents with our existing tools and workflows. We're a tiny team, so adding something new that doesn't seamlessly fit into our process would be a significant blocker. I'd need to understand exactly how an AI agent would handle design handoff to the engineer, or how it would ensure marketing messaging aligns with UI. Seeing a clear example of that interaction, perhaps a case study or a demo, would be very helpful. The pricing at $199/month is manageable, but the complexity of implementation is the real question.
    View answer & full research →
  8. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: The One-Person Company.

    I'd investigate further. The concept of AI agents handling product, growth, and operations is intriguing, especially for a small team like ours where I'm currently the entire design department. However, the core question is how well these agents actually *perform* these tasks. Can they truly replicate nuanced user research or understand the subtle friction points in a payment flow without human oversight? The promise of "agents managing agents" sounds powerful, but the devil is in the details of execution and reliability. The main reason for investigating is the potential to offload some of the overwhelming breadth of my responsibilities. My most important unanswered question is about the quality and autonomy of these agents – specifically, how much direct supervision and correction will they require, and what is the actual cost of error if they make a mistake on a critical feature?
    View answer & full research →
  9. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: The One-Person Company.

    This Agent Teams product sounds like it could potentially automate some of the repetitive tasks we handle in a small startup, especially around operations like onboarding and customer feedback. Having agents manage agents for product, growth, and operations is an interesting concept. I'm curious how it integrates with existing tools and whether the "lead agent" can truly understand and execute nuanced design feedback. The idea of "no per-seat fees" is appealing, but I'm unclear about the true cost and how it scales as more agents are added. We'd need to see if it genuinely reduces my workload or just adds another layer of management.
    View answer & full research →
  10. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Teams for Startups of 1–5 People.

    The biggest concern for me would be how well these AI teammates can actually integrate with our existing workflow and tools. We're a tiny team, and I'm the only designer; I've built a lot of our processes in Figma and Notion. I'd need to understand if these AI agents can truly collaborate with me, not just generate generic output. For instance, how do they handle design handoffs? Can they understand and adhere to our design system? The page mentions "persistent files, memory, and tools," but I'd need to see concrete examples of this working in practice, particularly for design tasks. The price point of $199/month for one agent seems reasonable if it genuinely saves time and improves quality, but the integration aspect is the real question.
    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.