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

Thomas Ward

Thomas Ward

Co-founder/CTO at a 9-person B2B SaaS startup

Full-depth AI personas

Why this persona fits the audience

Leads frontend and release engineering for a 9-person SaaS team shipping a React/Next.js app to customers in the US and Spain. The team keeps locale strings in Lokalise and GitHub, and he reviews i18n changes in pull requests alongside product work.

  • Age: 37
  • Location: Austin, US
  • Occupation: Co-founder and CTO, 9-person B2B SaaS startup
  • Income: USD 175k salary + equity
  • Education: BSc Computer Science
  • Company size: 9
  • Years in role: 5
“The real win isn't just shipping features; it's building something customers can rely on, day in and day out, without a second thought.”

Thomas Ward, at 37, is the co-founder and CTO of a burgeoning B2B SaaS startup based in Austin, Texas. Holding a BSc in Computer Science, his career has been a steady ascent through technical leadership roles, culminating in the co-founding of his current venture five years ago. He leads the frontend and release engineering efforts for their core product, a React/Next.js application serving an international clientele, primarily in the US and Spain. This involves a keen focus on internationalization (i18n), where he meticulously reviews locale string management in Lokalise and GitHub pull requests, integrating it seamlessly with ongoing product development. Thomas is driven by a strong sense of ownership and a deep commitment to shipping high-quality, reliable software that fosters customer trust. His personality leans towards conscientiousness and openness, reflecting his methodical approach to problem-solving and his receptiveness to new architectural ideas. He balances the intense demands of startup life with a disciplined personal routine, which includes regular cycling for physical and mental clarity, and consuming industry podcasts during his commute. While he earns a substantial salary of USD 175k plus equity, he and his wife maintain a pragmatic approach to their finances, prioritizing long-term investment and stability over ostentatious spending. He views time as a critical resource, constantly seeking efficiencies in development processes to accelerate delivery without compromising integrity. His ambition is clearly defined: to scale the company effectively, build a technically sound product, and cultivate a sustainable, high-performing engineering team.

Background & daily life

A day in their life

Thomas's typical weekday begins around 7:00 AM with a quick check of his phone for any urgent overnight alerts. After a coffee and a brief chat with his wife, he's usually at his home office by 8:00 AM. The morning is dedicated to deep work: code reviews, architectural planning, or tackling complex frontend challenges. He has a stand-up meeting with his team at 10:00 AM. Lunch is usually a quick affair at his desk. Afternoons are a mix of debugging, planning releases, and responding to emails or Slack messages. He aims to wrap up by 6:30 PM, often followed by a short bike ride or gym session before dinner, and might log back on for an hour if a critical deployment is pending.

Lifestyle

Thomas lives a structured yet active life in Austin. His days are primarily work-focused, but he prioritizes his health and mental well-being. He's married to Sarah, a graphic designer, and they maintain a comfortable, if not extravagant, lifestyle. Weekday evenings often involve a quick home-cooked meal, followed by a few hours of focused work or catching up on industry news. Weekends are for longer cycling routes, exploring local trails, and occasional social gatherings with a small group of close friends. He’s mindful of finances, investing a portion of his salary and equity but not living beyond his means.

Work life

As CTO of a lean SaaS startup, Thomas wears many hats. His primary responsibility is steering the technical vision and ensuring the frontend product, built on React and Next.js, is robust and scalable. He's deeply involved in code reviews, particularly for internationalization (i18n) features, ensuring consistency with Lokalise and GitHub. Release engineering is another major focus, aiming for smooth, predictable deployments. The team’s small size means constant collaboration and a high degree of autonomy for individuals, but also means he's directly involved in many operational aspects, from architecture discussions to debugging production issues.

Relationships

Thomas is married to Sarah, who provides a grounding influence and understands the demands of startup life. They have a shared social circle of about ten close friends, mostly from college or previous jobs. His CTO role necessitates strong working relationships with his co-founder (CEO) and the rest of the small engineering and product team, fostering a collaborative but accountability-driven environment.

How they decide

Thomas is a methodical and data-informed decision-maker. He prioritizes thorough research, weighing pros and cons with a focus on long-term impact and maintainability. He often seeks input from his core team and considers established best practices, but ultimately relies on his technical judgment and understanding of the company's strategic direction. He's not impulsive, preferring to iterate on solutions rather than make drastic, untested changes.

How they sound

Thomas speaks with a clear, measured cadence. He tends to be articulate and avoids excessive slang, preferring precise language. His tone is generally calm and professional, even when discussing challenging issues. He's not prone to hyperbole and tends to qualify his statements, using phrases like 'I think,' 'potentially,' or 'our current understanding is.' He’ll avoid sounding overly salesy or like he’s trying to impress, focusing instead on conveying accurate information.

Personality traits

  • methodical
  • detail-oriented
  • optimistic
  • pragmatic
  • analytical
  • calm under pressure
  • resourceful
  • forward-thinking

Goals

  • Achieve Series A funding within the next 18 months
  • Scale the engineering team to 15 people while maintaining code quality
  • Establish a strong, recognizable brand in the B2B SaaS market
  • Develop a robust and flexible microservices architecture
  • Maintain a healthy work-life balance despite startup pressures

Problems & frictions

  • Balancing rapid feature development with technical debt accumulation
  • Ensuring consistent localization quality across all customer-facing text
  • Onboarding new developers effectively into a complex codebase
  • Managing the overhead of multiple SaaS tools for development and operations
  • Finding time for strategic architectural planning amidst daily firefighting

Values

  • shipping quality
  • customer trust
  • clear ownership
  • technical excellence
  • team autonomy

Interests

  • frontend architecture
  • startup podcasts
  • cycling
  • serverless computing
  • open-source contributions

Media habits

  • Listens to 'Acquired' and 'How I Built This' during commutes
  • Follows Hacker News and select tech blogs for industry trends
  • Reads technical documentation extensively
  • Occasional Twitter browsing for developer community discussions
  • Prefers long-form articles over quick news briefs

Questions & answers

Thomas Ward’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Babelize (https://babelize.co/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    This month, what would stop me is the need to carefully evaluate any new tool's integration with our existing Lokalise and GitHub workflow. I'd need to see how it handles our current locale strings and ensures consistency without introducing unexpected issues. We currently manage this manually by reviewing PRs. The biggest hurdle would be ensuring it doesn't create significant overhead or a learning curve for the team. I'm willing to consider it, but I'm not sure about the pricing model yet. I wouldn't pay more than $100 per month.
    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.