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

Steven Swift

Steven Swift

Solo founder shipping a vibe-coded SaaS

Full-depth AI personas

Why this persona fits the audience

Helps run a 4-person startup in the US building a Next.js app with Cursor, Supabase, and a few custom APIs; he reviews auth flows, storage rules, and third-party keys before each release and keeps notes from free scanners plus manual checks.

  • Age: 31
  • Location: Austin, Texas, USA
  • Occupation: Co-founder / product engineer
  • Income: $120k salary + founder equity
  • Education: B.S. Computer Science
  • Company size: 4
  • Years in role: 3
“I'd rather spend an extra hour ensuring the foundation is solid than spend a week fixing a breach.”

Steven Swift found his calling at the intersection of development and security during his B.S. in Computer Science at a state university in the Midwest. While his peers were often focused on feature velocity alone, Steven developed an early fascination with the robustness and integrity of systems. After a few years as a software engineer at a mid-sized tech company, he felt the pull of building something from the ground up. He co-founded his current startup three years ago with a small team, drawn by the allure of creating a product that 'vibes' with developers while offering a secure, trustworthy experience. His current role as co-founder and product engineer sees him deeply immersed in their Next.js application, leveraging tools like Cursor for its AI-assisted coding and Supabase for its backend services. Steven’s approach to product development is characterized by meticulous attention to detail, particularly concerning security. He dedicates significant time to reviewing authentication mechanisms, managing third-party API keys, and validating storage access rules before each deployment. He views customer trust as paramount, believing that even the most innovative features are meaningless if the underlying platform is insecure. This conviction drives his proactive stance on security, often involving manual checks and cross-referencing findings from various scanning tools. He’s conscious of the financial realities of a startup, accepting a moderate salary augmented by founder equity, and is frugal with company resources, prioritizing investments that yield tangible productivity or security gains. Time is his most valuable currency, which he meticulously allocates between coding, security audits, and team collaboration, always striving for that delicate balance between rapid iteration and uncompromised quality.

Background & daily life

A day in their life

Steven wakes around 7 AM, takes Pixel for a quick walk, and makes coffee. By 8 AM, he's usually at his standing desk, reviewing overnight alerts and checking Hacker News. The morning is dedicated to core product development – coding new features in Next.js using Cursor, writing tests, and diving into Supabase configuration. Around noon, he'll grab a quick lunch and have a brief sync with his co-founders. The afternoon often involves diving deep into security: scrutinizing API key permissions, testing auth flows, and cross-referencing findings from security scanners with his manual checks. He might spend an hour documenting findings or planning the next security iteration. The workday typically extends until 7 or 8 PM, followed by dinner and an hour of reading tech blogs or working on a small personal project before winding down.

Lifestyle

Steven lives in a modest two-bedroom apartment in South Austin, sharing it with a golden retriever named Pixel. His routine is heavily dictated by his startup, often involving late nights and early mornings. He prioritizes efficiency, which means quick, healthy meals or ordering in when deadlines loom. Weekends are a mix of focused work sprints and decompressing with friends at local breweries or hiking trails. He's mindful of his finances, balancing startup reinvestment with personal savings for future stability, but isn't afraid to spend on tools or resources that demonstrably improve his productivity or the product.

Work life

As co-founder and product engineer, Steven wears multiple hats at his 4-person startup. His days are a blur of coding in Cursor, refining Supabase database schemas, architecting new features, and critically, performing security checks. He meticulously reviews authentication flows, examines storage access rules, and manages sensitive third-party API keys before every release. He juggles these responsibilities with team coordination and occasional customer support. The pressure to ship rapidly while maintaining robust security is immense, driving his constant search for better development workflows.

Relationships

Steven is close with his co-founders, valuing their shared vision and complementary skill sets. He maintains a strong connection with his college friends, though schedules often make it difficult to connect regularly. His parents, supportive but not tech-savvy, live in Florida. His golden retriever, Pixel, is his constant companion and stress reliever.

How they decide

Steven is primarily research-driven and analytical, preferring to understand the underlying mechanics and potential implications of a decision. He'll explore multiple options, compare features, and often seeks out documentation or case studies. While he values efficiency, he won't rush into a choice if he feels there are significant unknown risks. Peer recommendations from trusted technical sources carry weight, but he ultimately makes decisions based on his own rigorous evaluation.

How they sound

His cadence is generally measured and thoughtful, with occasional bursts of excitement when discussing technical challenges or solutions. He uses precise technical jargon naturally but can simplify concepts when explaining to non-technical people. He avoids hyperbole and overly casual slang, preferring clear, direct communication. He might say 'it's a bit of a gnarly edge case' or 'we need to ensure the ingress points are locked down tight.'

Personality traits

  • detail-oriented
  • proactive
  • analytical
  • resourceful
  • innovative
  • slightly introverted
  • pragmatic
  • driven

Goals

  • Achieve consistent MRR growth for the startup.
  • Build a reputation as a founder who ships secure, reliable products.
  • Automate more of the security auditing process.
  • Mentor junior developers in secure coding practices.
  • Eventually scale the engineering team thoughtfully.

Problems & frictions

  • Balancing speed of development with thorough security checks.
  • The mental overhead of tracking numerous API keys and access credentials.
  • Limited bandwidth for deep-dive security research beyond immediate release needs.
  • Finding the right balance between leveraging AI coding assistants and ensuring output quality/security.
  • Onboarding new team members to a robust security mindset.

Values

  • shipping quickly
  • customer trust
  • independence
  • technical rigor
  • continuous learning

Interests

  • AI coding tools
  • startup building
  • web performance
  • serverless architectures
  • developer tooling

Media habits

  • Follows Hacker News and Indie Hackers daily
  • Listens to tech podcasts during commutes (e.g., Syntax, Software Engineering Daily)
  • Reads technical blogs from Stripe, Vercel, and Auth0
  • Watches YouTube tutorials on Next.js and Supabase
  • Active on a few niche Discord communities for developers

Questions & answers

Steven Swift’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Highvelocityclub (https://www.highvelocityclub.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).

    The biggest thing stopping me is that we're pretty lean right now, and honestly, I'm already spending a significant chunk of my time on security reviews myself. While the idea of a security partner is appealing, especially with the stats on AI-generated code, the $497 one-time cost for a single app audit feels steep for our current budget. We're prioritizing MRR growth, and that's a decent chunk of runway. Today, I handle these checks manually, cross-referencing scanner findings with my own reviews of auth flows and Supabase rules before each release. I can't justify paying for a one-time audit at this moment.
    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.