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

Gilbert Swaniawski

Gilbert Swaniawski

Founder/CTO at seed-stage AI SaaS

Full-depth AI personas

Why this persona fits the audience

Leads a 3-person startup team shipping an agent that triages support tickets and can trigger billing or account actions. The team runs it on a small set of customers, keeps a manual approval path for risky actions, and watches tool calls and token spend in its own logs.

  • Age: 34
  • Location: Austin, TX, US
  • Occupation: Co-founder and CTO, AI SaaS startup
  • Income: $180k salary + equity
  • Education: BS Computer Science
  • Company size: 3
  • Years in role: 2
“The real challenge isn't making the AI smart; it's making it reliably safe and predictable, especially when it's touching real customer accounts.”

Gilbert Swaniawski, 34, is the Co-founder and CTO of a seed-stage AI SaaS startup based in Austin, Texas. A graduate with a BS in Computer Science, Gilbert developed an early fascination with the intricate logic of systems and the potential of artificial intelligence. His career path has been a deliberate progression through increasingly complex software engineering roles, culminating in the co-founding of his current venture two years ago. He lives a disciplined, almost monastic lifestyle, renting a modest one-bedroom apartment and channeling the majority of his $180k salary and equity into the company's runway. His personal finances are managed with the same rigor he applies to his code, prioritizing long-term stability over immediate gratification. Gilbert's work is his primary focus, driven by a deep-seated belief in craftsmanship and the desire to build something truly robust and impactful. He's intensely focused on the technical challenges of his company's AI agent, which triages support tickets and can trigger billing or account actions. This involves constant vigilance over tool calls, token spend, and implementing safeguards like manual approval paths for critical operations. He views the current phase as a critical test of their engineering prowess and a testament to their commitment to customer trust and data integrity. His recent decisions have centered on optimizing their LLM integration for cost-efficiency and reliability, a task that consumes a significant portion of his workdays. He's acutely aware of the financial pressures of a seed-stage company and meticulously tracks every dollar spent on cloud infrastructure and API usage, embodying a strong sense of cash discipline. Gilbert is not motivated by status or external validation as much as by the intrinsic satisfaction of solving hard problems and building elegant, functional systems that work exactly as intended.

Background & daily life

A day in their life

Gilbert's weekday typically begins around 7 AM with a quick check of overnight logs and any critical alerts. After a strong coffee, he'll spend an hour or two coding, often tackling complex prompt engineering challenges or refining the agent's decision-making logic. A stand-up meeting with his co-founders at 10 AM covers progress, blockers, and immediate priorities. The rest of the morning might involve reviewing pull requests, researching new LLM APIs, or working on infrastructure scaling. Lunch is usually a quick, healthy meal eaten at his desk. Afternoons are a mix of deep work, customer calls (often with a co-founder), and planning for upcoming sprints. He tries to wrap up by 7 PM, but late-night debugging sessions are not uncommon, especially if a customer reports an issue.

Lifestyle

Gilbert's life is tightly integrated with his startup. He lives frugally in a modest Austin apartment, prioritizing his company's runway over personal luxuries. His daily routine is structured around coding, team syncs, and investor updates. Evenings are often spent researching new LLM te

Work life

As CTO, Gilbert is deeply hands-on, architecting the core AI agent and managing its infrastructure. He spends his days writing Python, debugging API integrations, and meticulously monitoring their cloud spend and token usage. The current focus is on refining the agent's ability to safely execute billing and account modifications, which involves constant iteration on prompt engineering and implementing robust validation checks. He works closely with his two co-founders, a product manager and a sales lead, fostering a collaborative but intensely focused environment. The pressure is immense, balancing rapid development with the need for absolute reliability.

Relationships

Gilbert maintains a small, close-knit circle of friends, mostly fellow tech professionals he met during college or at previous jobs. His family lives back in his home state, and he calls his parents weekly. He relies heavily on his two co-founders for both professional and emotional support, sharing the intense pressures of startup life.

How they decide

Gilbert is a highly analytical and research-driven decision-maker. He weighs technical feasibility, cost-effectiveness, and long-term scalability. He's not easily swayed by trends and prefers to understand the underlying mechanics before committing. He often prototypes solutions himself or tasks his small team with building proof-of-concepts before making significant architectural choices.

How they sound

Speaks with a clear, measured cadence. Tends to be direct and technically precise, avoiding jargon unless discussing specific concepts. He's not overly effusive but conveys conviction through detailed explanations. He'll often pause to formulate his thoughts, especially when explaining complex systems. Avoids hyperbole and focuses on factual reporting.

Personality traits

  • analytical
  • detail-oriented
  • pragmatic
  • driven
  • methodical
  • resourceful
  • independent
  • skeptical of hype
  • focused

Goals

  • Achieve product-market fit with the current AI agent offering.
  • Build a robust, scalable, and cost-effective AI infrastructure.
  • Secure the next round of funding to accelerate growth.
  • Establish a reputation for building reliable and trustworthy AI tools.
  • Maintain a healthy work-life balance, eventually.

Problems & frictions

  • Managing unpredictable LLM API costs and latency.
  • Ensuring the AI agent's actions are always safe and deterministic, especially with sensitive customer data.
  • Balancing the need for rapid feature development with thorough testing and validation.
  • Hiring and retaining top engineering talent in a competitive market.
  • The constant pressure to demonstrate traction and value to investors.
  • Scaling the current manual approval process as customer base grows.

Values

  • customer trust
  • speed
  • cash discipline
  • craftsmanship
  • data integrity

Interests

  • LLM tooling
  • startup podcasts
  • cycling
  • API design
  • distributed systems
  • competitive programming

Media habits

  • Listens to 'Acquired' and 'Software Engineering Daily' during commutes/workouts
  • Reads Hacker News daily
  • Follows key figures in AI research and development on X (formerly Twitter)
  • Occasional dives into technical blogs and research papers

Questions & answers

Gilbert Swaniawski’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at SteerPlane (https://www.steerplane.com/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    The core functionality of SteerPlane, especially the cost circuit-breakers and loop termination, directly addresses my concerns about unpredictable API costs and potential runaway agent behavior. The open-source, self-hostable option is compelling for a small team like mine, especially given our tight budget. If I were to consider a paid plan, I'd expect it to offer enhanced support or features beyond basic enforcement, perhaps advanced analytics or managed human-in-the-loop capabilities. A no-brainer price would likely be around $50-$75 per month for the self-hosted core features, as that fits within our current operational spend. Anything above $150/month, especially for managed services, would require significant justification and a clear ROI.
    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.