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

Janet Klocko

Janet Klocko

Product designer at a 5-person B2B SaaS startup

Full-depth AI personas

Why this persona fits the audience

She is currently the product designer at a seed-stage B2B SaaS startup that has exactly five people total: two founders and three non-founder team members. Her day-to-day work covers interface design, user flows, and handoff with the engineer and founder team on a small shared product roadmap.

  • Age: 29
  • Location: Austin, TX, USA
  • Occupation: Product designer
  • Income: USD 118k base salary with small equity
  • Education: Bachelor's degree in graphic design
  • Company size: 5
  • Years in role: 3
“ 'Every pixel has to earn its place; if it doesn't serve the user or the business, it's just noise.' ”

Janet Klocko grew up in a suburban environment, the daughter of an accountant and a librarian, fostering an early appreciation for order and information. Her passion for design ignited during high school art classes, leading her to pursue a Bachelor's in Graphic Design at a state university. Post-graduation, she worked for a couple of years at a small branding agency, honing her visual design skills but craving more direct impact. She transitioned into UX/UI design, finding her niche in the fast-paced world of tech. Three years ago, she joined her current startup, drawn by the founders' compelling vision and the opportunity to shape a product from its nascent stages. She finds satisfaction in the tangible progress and the deep ownership her role affords, even if it means navigating inherent startup volatility. Her income, while good, is carefully managed, with a significant portion earmarked for savings and long-term investments, a habit born from observing the financial ups and downs of early-stage companies. Janet's relationship with time is one of constant negotiation; she strives for efficiency but understands that impactful design often requires patient iteration. She sees her equity stake as a long-term bet, motivating her to pour her energy into the company's success, viewing her role not just as a job, but as a significant investment in her future and the product's journey.

Background & daily life

A day in their life

Janet's typical weekday starts around 8:00 AM with a strong pour-over coffee and reviewing her task list. She might spend an hour in a focused design session, sketching out wireframes for a new feature on her tablet or refining UI components in Figma. Mid-morning often involves a quick sync with the engineer to discuss implementation details or a brief product roadmap alignment meeting with the founders. Lunch is usually a quick affair, perhaps a salad at her desk or a brisk walk. The afternoon is dedicated to detailed UI design, creating prototypes, and preparing assets for handoff, interspersed with Slack messages and occasional unscheduled problem-solving. She aims to wrap up by 6:00 PM, though late nights happen when deadlines loom.

Lifestyle

Janet lives in a moderately sized one-bedroom apartment in a walkable Austin neighborhood, close to a popular cycling path. Her weekdays are structured around work, often starting with a strong pour-over coffee at home before heading to the co-working space they utilize. Weekends are a mix of catching up on personal design projects, exploring new coffee spots with friends, and longer urban cycling routes. She's diligent with her finances, aiming to save a significant portion of her salary, understanding the volatility of startup equity. Socially, she prefers smaller, deeper connections over large gatherings.

Work life

As the sole product designer in a five-person B2B SaaS startup, Janet wears many hats. Her days are a blur of wireframing new features, meticulously crafting UI elements, and mapping out user flows for their core product. She works closely with the two founders, one of whom is heavily involved in product strategy, and the single engineer who brings her designs to life. Handoffs are frequent and require clear documentation and ongoing communication to ensure the engineer has everything they need. The pressure to iterate quickly on a lean roadmap means prioritizing ruthlessly and making design decisions that balance user needs with immediate business goals.

Relationships

Janet maintains close ties with her parents, who live in a different state, and a small circle of college friends who are also in tech. Her primary professional relationships are with her two co-founders and the engineer; these interactions are frequent, direct, and collaborative, fostering a sense of shared mission. She occasionally seeks advice from a former mentor from a previous internship.

How they decide

Janet tends to be a methodical researcher, but within the startup context, she prioritizes fast iteration. She'll gather necessary data and user feedback quickly, weigh the pros and cons, and make a confident decision, often leaning on her own experience and intuition when time is short. She values practical, data-informed choices that move the product forward.

How they sound

Speaks clearly and with purpose, avoiding excessive jargon unless explaining technical design concepts. Her cadence is steady, reflecting her conscientious nature. She uses phrases like 'what if we tried,' 'my initial thought is,' and 'let's make sure it's crystal clear.' She tends to be optimistic but grounded, rarely complaining explicitly about challenges, instead focusing on solutions.

Personality traits

  • detail-oriented
  • proactive
  • methodical
  • collaborative
  • resourceful
  • analytical
  • independent
  • adaptable

Goals

  • Grow into a design leadership role within a scaling tech company
  • Build a portfolio of impactful products that solve real user problems
  • Achieve financial independence through smart investing and equity growth
  • Maintain a healthy work-life balance despite startup demands
  • Contribute to the open-source design community in some capacity

Problems & frictions

  • Limited resources and time to explore every design possibility thoroughly
  • Balancing the founders' vision with user feedback and technical constraints
  • Scope creep on features due to the rapid pace of startup development
  • Lack of dedicated QA or user research resources
  • Feeling the pressure of sole design ownership and responsibility
  • Navigating the inherent instability and uncertainty of a seed-stage company

Values

  • craft and clarity
  • ownership
  • fast iteration
  • practical teamwork

Interests

  • interface design
  • startup culture
  • coffee shops
  • urban cycling

Media habits

  • Follows design blogs and tech news sites (e.g., UX Collective, TechCrunch)
  • Listens to podcasts on design, startups, and productivity during commutes
  • Active on LinkedIn for professional networking and industry insights
  • Occasional browsing of Dribbble and Behance for inspiration

Questions & answers

Janet Klocko’s public research answers, newest questions first. Up to 10 per page.

  1. 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 product, Agent Teams, sounds like it could potentially automate some of the more operational or repetitive tasks in product development, like initial market research or tracking customer feedback. It promises to delegate tasks to specialized 'agents' coordinated by a lead agent, which might free me up to focus on higher-level strategy and design. However, it feels unclear how much hands-on involvement is needed from my end to guide these agents effectively, especially for nuanced product decisions. The idea of agents handling research and testing is intriguing, but I'd need to understand the quality and depth of their output, and how it integrates with my Figma workflows for handoff. The 'lead agent' coordinating specialists sounds like a potential layer of management, but it's not clear if this would truly support or complicate my current direct collaboration with our engineer and founders.
    View answer & full research →
  2. 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.

    My biggest concern would be the integration and reliability of these AI teammates. We're a small team, and I'm the sole designer. If these AI agents aren't seamlessly integrated into our workflow or if they make errors, it could actually slow us down or create more work for me. I'd need to see clear evidence of how they handle complex tasks, maintain context across different functions, and what kind of oversight and error correction mechanisms are in place. Specifically, how does the 'Chat Wall' work for coordinating tasks between human and AI teammates? The $199/month base price is manageable, but the real question is the return on investment and whether it truly augments our tiny team without introducing significant overhead.
    View answer & full research →
  3. 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 Teams for Startups of 1–5 People.

    I'd investigate further. The concept of AI teammates for product, growth, and operations is really compelling for a small team like ours, especially the idea of working in parallel and sharing context. The pricing starting at $199/month seems reasonable, especially with no per-seat fees. However, my main question is about how these agents handle creative tasks, specifically in product design. Can they generate novel UI concepts or just iterate on existing ones? Also, how do their outputs integrate with our current Figma workflow?
    View answer & full research →
  4. 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 Teams for Startups of 1–5 People.

    This product, Agent Teams, seems like it could offer AI teammates for product, growth, and operations for our small five-person startup. It could potentially help offload some of the product research, build, and testing tasks, fitting into my day-to-day by working in parallel with me and the engineer. What feels unclear is how seamless the handoffs would truly be between these AI agents and our human team, and how much context sharing is possible without creating noise. I'd also want to understand the level of control we have over the AI's decision-making versus just task execution.
    View answer & full research →
  5. 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: One Founder, a Company of Agents.

    My biggest concern would be the integration and actual effectiveness of these AI agents within our existing, lean workflow. As the sole product designer, I'm used to having direct control and understanding exactly how features are built and function. My initial thought is, can these agents truly replicate the nuanced problem-solving and iterative design process we're currently doing with our engineer? It's hard to imagine handing off our product roadmap or user flows to an AI without a significant amount of setup and oversight. To resolve this, I'd need to see very clear examples of how complex tasks are managed and a robust system for inspecting and correcting agent work, perhaps even a trial period to test it with our specific product.
    View answer & full research →
  6. 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: One Founder, a Company of Agents.

    I would investigate further. The concept of an AI team handling product, growth, and operations is fascinating, especially given my role where I'm juggling so many responsibilities. My main reason for pausing is the lack of clarity on how deeply these agents integrate with existing tools and workflows. The most important unanswered question for me is how much control I, or my engineer, would actually have over the agents' decisions and outputs. We're a tiny team, so efficiency is key, but we also need to maintain quality and direction.
    View answer & full research →
  7. 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: One Founder, a Company of Agents.

    This looks interesting for a solo founder or a very lean team. The idea of AI agents handling product research, growth marketing, and operations sounds like it could significantly reduce bandwidth for tasks that currently take up a lot of my time. It seems like it would fit into my work by offloading some of the more repetitive or research-heavy aspects of product development and growth strategy. What feels unclear is how well these agents would integrate with our existing engineer and how much oversight would truly be needed. I'd want to understand the level of control and customization available.
    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.