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

Gregg Barrows

Gregg Barrows

Cybersecurity founder

Full-depth AI personas

Why this persona fits the audience

He is the founder of a Seattle cybersecurity startup with exactly three people total: him, one security engineer, and one solutions architect. The company is serving a few design partners and continuously hardening its product.

  • Age: 27
  • Location: Seattle, WA, US
  • Occupation: Founder and CTO
  • Income: USD 115k draw + equity
  • Education: BS Information Security
  • Company size: 3
  • Years in role: 2
“The only acceptable state is secure, and the only acceptable path is rigorous.”

Gregg Barrows, 27, is the quintessential driven founder navigating the volatile landscape of cybersecurity startups. Raised in a middle-class family where hard work and technical aptitude were implicitly valued, he gravitated towards computers early on. His fascination wasn't just with playing games, but with understanding how they worked, and more importantly, how they could be broken and secured. This led him to pursue a BS in Information Security, where he excelled, demonstrating a natural talent for dissecting complex systems and identifying vulnerabilities. Upon graduation, he eschewed lucrative offers from established tech giants, driven by a desire to build something foundational and secure from the ground up. He co-founded his current venture two years ago with a clear vision: to create a cybersecurity solution that prioritized absolute technical rigor and user trust. The company, currently a lean three-person operation in Seattle, is his singular focus. His income of $115k is a draw against future profits, with the vast majority of his personal wealth tied up in equity. He lives frugally, viewing money as a resource to be strategically deployed for product hardening and team growth, not personal indulgence. His personal life is secondary to the mission; social engagements are rare, and hobbies like hiking and gaming are often viewed through the lens of mental discipline or strategic thinking. He recently made the critical decision to pivot their core feature set based on feedback from their initial design partners, a move that required significant refactoring but was essential for achieving true market fit. This involved a deep dive into cryptographic primitives and a complete overhaul of their authentication layer, a task he personally led with meticulous attention to detail, reflecting his unwavering commitment to security and technical excellence.

Background & daily life

A day in their life

Gregg's typical weekday begins around 6:30 AM with coffee and a quick scan of security news feeds and Hacker News. He arrives at the office by 8:00 AM, often before his team. The morning is dedicated to deep work: coding new features, debugging critical issues, or architecting system improvements. He has a brief stand-up meeting with his engineer and architect around 10:00 AM to sync progress and address blockers. Lunch is usually a quick, healthy meal eaten at his desk while reviewing threat intelligence reports. The afternoon involves more coding, code reviews, and sometimes customer calls or technical discussions with design partners. He often stays late, sometimes until 8:00 PM or later, especially if a critical bug needs squashing or a new security vulnerability demands immediate attention. Evenings might include a short gaming session or reading technical papers before winding down.

Lifestyle

Gregg lives a focused, almost monastic existence in Seattle, prioritizing his startup above all else. His one-bedroom apartment is minimalist, with a powerful custom-built PC dominating one corner and stacks of technical books on a shelf. He typically wakes early, fueled by black coffee, and spends most of his day coding or strategizing. Weekends might involve a strenuous hike in the Cascades to clear his head, or late-night gaming sessions with a small, trusted online circle. He's frugal, reinvesting most of his draw back into the company, viewing personal expenses as secondary to building a secure and robust product.

Work life

As Founder and CTO, Gregg's days are a relentless cycle of product development and strategic planning. He works closely with his two-person team – a brilliant security engineer and a sharp solutions architect – in their small, rented office space. The pressure is immense, balancing the need to iterate quickly for their design partners with the absolute necessity of maintaining impeccable security. He spends hours debugging complex code, reviewing security protocols, and architecting new features. Decisions are made collaboratively but ultimately rest on his technical judgment, driven by a deep commitment to technical rigor and the trust placed in them by their early clients.

Relationships

Gregg's social circle is small and tightly knit. His primary relationships are with his co-founders, with whom he shares an intense, collaborative bond built on mutual respect and shared vision. He maintains contact with a few close college friends, mostly online, and occasionally visits his parents back in his home state. His parents are supportive but don't fully grasp the intricacies of his work, though they trust his judgment.

How they decide

Gregg is highly analytical and research-driven, especially concerning technical matters. He values data, evidence, and logical reasoning. For strategic decisions, he consults his co-founders and weighs their input carefully, but ultimately relies on his own deep understanding of the technology and market landscape. He is not impulsive and prefers to thoroughly evaluate options before committing.

How they sound

Gregg speaks with a measured, precise cadence. His tone is generally calm and analytical, rarely raised. He uses technical jargon naturally but can explain complex concepts clearly when necessary, though he sometimes assumes a baseline level of technical understanding. He avoids hyperbole and overly casual slang, preferring direct and accurate language. He might occasionally use a dry, understated wit.

Personality traits

  • Analytical
  • Meticulous
  • Reserved
  • Driven
  • Principled
  • Detail-oriented
  • Pragmatic
  • Focused

Goals

  • Achieve product-market fit for their core offering
  • Build a company culture that prioritizes security and ethical practices
  • Become a recognized leader in a niche cybersecurity sector
  • Maintain personal technical proficiency and stay ahead of emerging threats
  • Secure Series A funding within 18 months

Problems & frictions

  • Balancing rapid development with stringent security requirements
  • Recruiting top-tier security talent in a competitive market
  • Managing cash flow and runway effectively
  • The constant pressure of staying ahead of sophisticated adversaries
  • Ensuring the scalability of their current architecture
  • Finding time for strategic thinking amidst daily operational demands

Values

  • security
  • discipline
  • technical rigor
  • trust
  • innovation

Interests

  • ethical hacking
  • gaming
  • hiking
  • hardware
  • competitive programming
  • cryptography

Media habits

  • Follows security researchers on Twitter/X
  • Reads Hacker News daily
  • Listens to tech podcasts during commutes
  • Watches DEF CON talks on YouTube
  • Subscribes to security newsletters

Questions & answers

Gregg Barrows’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 appears to be an AI-driven team to handle product development, growth, and operations, led by an AI "lead agent" that I would direct. For my startup, it could potentially offload some of the tasks my two team members and I are currently managing. Specifically, the "Product" agent could assist with research and testing, which aligns with our need to harden the product. However, the claim that agents manage agents feels a bit abstract. I'm unclear on the level of control I'd truly have over the AI's decision-making, especially concerning security protocols, which is paramount for us. The pricing structure starts at $199/month, which is reasonable given the "no per-seat fees," but the actual efficacy and security implications of these AI agents are the main unknowns.
    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 primary concern would be around security and data privacy. We're building a cybersecurity product, so trusting a third-party AI with sensitive company context and operations is a significant hurdle. How is the data isolated? What are the access controls and audit trails like? The biggest blocker is the potential for data leakage or unauthorized access. I would need to see clear, verifiable security assurances, perhaps SOC 2 compliance or detailed penetration test reports, before even considering this.
    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 would investigate further. The concept of AI teammates for product, growth, and operations is intriguing, especially for a small team like ours. My main reason for further investigation is to understand the actual security implications and data handling practices. As CTO, security is paramount, and I need to know how these agents integrate and what attack vectors they might introduce. My most important unanswered question is about the level of control and transparency we have over the AI's actions and data access, particularly concerning our proprietary information and design partner data.
    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.

    The idea of AI teammates for product, growth, and operations is intriguing. For a company of our size, offloading some of the more repetitive or research-intensive tasks in those areas could free up critical time for my engineer and architect, and myself, to focus on core product hardening. I'm particularly interested in how these agents would handle context and maintain security, especially given our focus on cybersecurity. The page mentions "persistent files, memory, and tools" for each agent, which raises questions about data isolation and access control. The "From $199/month" pricing is noted, but the exact capabilities included at that tier aren't entirely clear without more detail on what "1 running agent" entails.
    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.

    The primary concern would be data security and control. Entrusting core product functions to an external AI team raises significant questions about data residency, access controls, and the integrity of our cryptographic primitives. We'd need absolute assurance that our sensitive data, intellectual property, and customer information are managed with the same rigor we apply internally. The biggest blocker is the lack of transparency regarding the underlying security architecture and the specific tools or models these agents utilize. To resolve this, we'd require detailed documentation on their security protocols, data handling policies, and assurances regarding compliance with industry standards relevant to cybersecurity. Without that, the risk is simply too high.
    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.

    Investigate further. The concept of an AI team handling product, growth, and operations is intriguing, especially with no per-seat fees. My primary concern would be the actual security and integrity of the agents themselves. How do they handle sensitive data, and what are the potential attack vectors if an agent is compromised? Without understanding the security architecture and auditing capabilities, I can't make a purchasing decision.
    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.

    The idea of an AI team handling product, growth, and operations is intriguing, especially for a lean startup like ours. It could potentially automate tasks that currently consume significant time, like initial product research or market analysis, freeing up my engineer and architect for more critical security work. However, the concept of handing over core functions, even to AI, raises immediate security and data privacy concerns. How is the data isolated? What are the protocols for information sharing between these agents and our internal systems? The lack of clarity on the security architecture and the robustness of their "persistent files, memory, browser, and tools" makes me hesitant. I need to understand the security posture before considering such a tool.
    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.