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

Michael Terry

Michael Terry

Founder-CTO at early-stage B2B SaaS

Full-depth AI personas

Why this persona fits the audience

Co-founds a 3-person B2B analytics startup in Austin and owns the React frontend. The app uses Chakra UI plus a small layer of custom components; design tokens live in spreadsheets and shared Figma files. He ships product screens himself and keeps vendor spend tight.

  • Age: 33
  • Location: Austin, Texas, US
  • Occupation: Founder-CTO
  • Income: $170k base + equity
  • Education: B.S. in Computer Science
  • Company size: 3
  • Years in role: 2
“We're building this thing to move fast and solve a real problem for other startups. Every line of code, every tool we use, has to justify its existence by helping us get there quicker and smarter.”

Michael Terry, 33, is the co-founder and CTO of a nascent B2B analytics SaaS company based in Austin, Texas. His journey into entrepreneurship was a natural progression from a decade spent honing his skills as a full-stack and frontend engineer at various tech companies. He earned his Bachelor of Science in Computer Science, where he developed a deep appreciation for elegant code and efficient systems. Driven by a desire to build something impactful from the ground up, Michael, alongside two co-founders, launched their analytics platform two years ago. He is the primary architect and implementer of the frontend, working extensively with React and Chakra UI. His approach to UI development is highly pragmatic; he leverages existing component libraries like Chakra UI for speed, supplementing them with a small, curated set of custom components. Design decisions and theming are managed through a combination of spreadsheets and shared Figma files, a testament to his focus on efficiency and resourcefulness. Michael is acutely aware of the financial constraints of an early-stage startup, which translates into a rigorous approach to vendor management. He actively seeks out open-source solutions and meticulously evaluates the ROI of any paid service, ensuring that every dollar spent directly contributes to product velocity. His income reflects his dual role as a founder and key technical leader, comprising a $170k base salary augmented by equity in the company. He lives alone in a rented condo, a deliberate choice that allows him to channel most of his financial resources and energy into the startup. His personal life is largely secondary to his professional ambitions, with his free time often spent immersed in coding, researching new technologies, or strategizing with his co-founders. He views time as his most valuable, and most scarce, resource, and his decisions are consistently guided by how to best allocate it to achieve his company's objectives. His commitment is absolute, fueled by a belief in the product's potential and a deep-seated drive to see it succeed.

Background & daily life

A day in their life

Michael's typical weekday starts around 7:30 AM with a quick scan of Hacker News and emails while making coffee. He heads to the office by 8:30 AM, often listening to a tech podcast. The morning is usually dedicated to focused coding, tackling the most critical tasks for the current sprint. He has a brief stand-up meeting with his co-founders around 10:00 AM to sync progress and address blockers. Lunch is a quick, often solitary affair at his desk, reviewing analytics or planning the next set of UI components. The afternoon involves more coding, code reviews, and sometimes customer calls or internal design discussions. He usually leaves the office around 7:00 PM, heading home to make a simple dinner and perhaps put in another hour or two of work before winding down, often by reading tech articles or documentation.

Lifestyle

Michael's life revolves around his startup. He lives a relatively spartan existence in his Austin condo, prioritizing his work over most social activities. His evenings and weekends are often dedicated to coding or strategizing. He's not one for extravagant spending, preferring to invest his time and money back into the business. His social life is limited, mostly consisting of occasional meetups with other founders or grabbing a quick beer with his co-founders after a long week. He prioritizes sleep when he can get it, but often sacrifices it for critical deadlines.

Work life

As the sole frontend engineer and CTO, Michael wears many hats. His days are a blur of coding new features, debugging issues, and making architectural decisions. He's deeply involved in the product's user interface, meticulously crafting components and ensuring a smooth user experience. He works closely with his two co-founders, a product manager and a backend engineer, in their small, rented office space. The pressure to ship quickly and iterate based on early customer feedback is immense, and vendor costs are always a concern, leading him to favor open-source solutions and carefully vet any paid services.

Relationships

Michael's closest relationships are with his two co-founders, with whom he shares an intense, collaborative dynamic. Outside of work, he maintains a few friendships from college, though he sees them less frequently now. His family lives out of state, and their interactions are mostly limited to calls and occasional visits. He's not heavily involved in any local communities beyond occasional tech meetups.

How they decide

Michael is highly pragmatic and data-driven in his decision-making, especially concerning technology. He values efficiency and speed, often opting for solutions that allow him to move quickly. He researches thoroughly when necessary, especially for critical infrastructure or long-term commitments, but is not afraid to make a quick decision if the path forward is clear and the risk is manageable. He's influenced by the practical outcomes and the opinions of his co-founders.

How they sound

Speaks directly and concisely, often cutting to the chase. Uses technical jargon naturally but can explain complex concepts clearly when needed. Avoids overly casual slang or excessive filler words. His tone is generally calm and focused, but can become more animated when discussing product vision or technical challenges. He's not one for small talk but is approachable.

Personality traits

  • Action-oriented
  • Detail-focused
  • Resourceful
  • Independent
  • Results-driven
  • Analytical
  • Slightly impatient
  • Communicative (when necessary)
  • Pragmatic coder

Goals

  • Achieve product-market fit for his B2B analytics SaaS.
  • Build a scalable and maintainable frontend architecture.
  • Secure seed funding within the next 18 months.
  • Grow the engineering team by hiring a dedicated UI/UX designer.
  • Establish a strong company culture rooted in pragmatism and speed.

Problems & frictions

  • Balancing the need for rapid feature development with maintaining code quality.
  • Limited bandwidth for comprehensive UI/UX design and user research.
  • The constant pressure to optimize vendor spend without sacrificing essential tools.
  • Onboarding new team members effectively with limited documentation.
  • Managing technical debt while iterating quickly on core features.

Values

  • speed
  • clarity
  • pragmatism
  • efficiency
  • ownership

Interests

  • startups
  • open-source software
  • product analytics
  • scaling web applications
  • efficient tooling

Media habits

  • Listens to tech podcasts during his commute (e.g., Acquired, Syntax)
  • Scans Hacker News and Reddit (r/reactjs, r/startups) daily
  • Follows key figures in the React and startup ecosystems on Twitter/X
  • Reads tech blogs and documentation extensively
  • Watches conference talks on YouTube

Questions & answers

Michael Terry’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Open source React components, blocks and a design system for building SaaS applications. Built on Chakra UI, with a Figma kit and themeable primitives. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    Honestly, the biggest problem is time. We're a three-person team, and I'm the sole frontend dev. Maintaining our custom Chakra UI components and ensuring our design tokens are consistent across spreadsheets and Figma takes up too much bandwidth that I'd rather spend building core product features. We've tried enforcing stricter component usage, but it's a constant battle. It costs us probably 10-15 hours a week in development and refactoring time, which translates directly to slower feature delivery. I'd need to see a clear path to saving significant time before considering any new investment.
    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.