Bryant Stroman

Why this persona fits the audience

He co-runs a 14-person SaaS company and is the person who checks the Microsoft 365 tenant, company mail flow, website uptime, and employee laptop setup. He keeps a short audit trail in spreadsheets and uses built-in admin tools plus a few scripts to review alerts and close out issues.

• Age: 38
• Location: Austin, TX, US
• Occupation: Co-founder & CTO
• Income: $145k salary + equity
• Education: BSc Computer Science
• Company size: 14
• Years in role: 6

“The real win isn't just fixing a problem, it's building a system so robust that the problem rarely appears in the first place.”

Bryant Stroman, 38, is the co-founder and CTO of a lean B2B SaaS startup based in Austin, Texas, a role he's held for the past six years since its inception. Holding a BSc in Computer Science, his career began in traditional software development roles before the entrepreneurial bug bit. He co-founded his current venture with a vision to simplify complex business processes through intuitive software, leveraging his technical expertise to build the foundational architecture. His current income is a blend of a $145k salary and equity, a typical package for a startup CTO, which fuels his drive but also necessitates careful personal financial management. Bryant is the linchpin for the company's IT infrastructure, a responsibility he embraces with meticulous attention to detail. He personally oversees the Microsoft 365 tenant, monitors website uptime, manages mail flow, and ensures every employee's laptop is configured and secure. His operational approach is pragmatic and efficient: he maintains a concise audit trail in spreadsheets, utilizes built-in administrative tools, and has developed a suite of custom scripts to parse alerts and automate basic issue resolution. This hands-on approach allows him to keep overhead low, a critical factor for a 14-person company. Recently, he spearheaded the implementation of a new CI/CD pipeline, aiming to increase deployment speed and reliability, a move that required him to dedicate significant personal time to research and configuration. He also decided against a costly external monitoring solution, opting instead to refine his existing script-based alerts, prioritizing speed of execution and clear ownership of the solution over a potentially more feature-rich but complex off-the-shelf product. Bryant views time as his most valuable, and most constrained, resource. He consciously allocates it, prioritizing tasks that directly impact product stability and growth. While status is a byproduct of success, his primary drivers are building a resilient company and developing elegant technical solutions. He's not chasing a large corporate ladder; his ambition is to see his startup thrive and become a recognized player in its niche.

Background & daily life

A day in their life

Bryant's weekday typically starts around 6 AM with a quick check of critical alerts on his phone while having coffee. By 7 AM, he's either on his bike or at the gym. He’s usually at his home office by 8:30 AM, reviewing company dashboards, responding to urgent emails, and planning his day. The morning is often a mix of coding on new features, reviewing pull requests, and addressing any IT issues that arose overnight—like a website hiccup or a failed automated backup. Lunch is a quick, healthy meal at his desk while listening to a tech podcast. Afternoons are dedicated to team stand-ups, strategic planning sessions with his co-founder, and delving deeper into system architecture or troubleshooting complex user-reported bugs. He tries to wrap up by 6:30 PM, but late-night alerts can sometimes extend his workday.

Lifestyle

Bryant lives in a moderately sized condo in South Austin, preferring the convenience to downtown and local trails. His weekdays are packed, leaving weekends for recharging. He's an early riser, typically hitting the gym or a quick spin on his road bike before diving into work. His diet is health-conscious, focusing on lean proteins and vegetables, though he'll indulge in local barbecue on occasion. Financial discipline is key; he meticulously tracks personal expenses in a spreadsheet similar to his work tools, prioritizing saving for future investments and company growth over luxury purchases. Social life is often centered around tech meetups or small gatherings with close friends.

Work life

As co-founder and CTO, Bryant's workdays are a constant juggle between strategic planning and hands-on IT maintenance for their 14-person B2B SaaS company. He’s the de facto IT department, ensuring the Microsoft 365 tenant is secure, the website stays up, and every employee's laptop is functional. He relies on a mix of built-in admin consoles, custom scripts he's written over the years, and spreadsheets to log issues and track resolutions. Coworkers trust him implicitly for system stability, but this also means he’s the first point of contact for almost any technical hiccup, creating pressure to be constantly available and responsive.

Relationships

Bryant is married to Sarah, a graphic designer, and they are a solid team, supporting each other’s professional endeavors. He has a close-knit group of 4-5 friends from college who are also in tech, with whom he shares industry insights and occasional commiseration. His co-founder, Liam, is his primary business sounding board and closest professional confidant. Influence primarily comes from trusted peers in the startup ecosystem and respected voices in technology publications.

How they decide

Bryant approaches decisions methodically. He prioritizes understanding the core problem, evaluating available options based on efficiency and long-term reliability, and often prototypes or tests solutions on a small scale before full implementation. He's not easily swayed by hype but will thoroughly research alternatives if a current process is inefficient or causing friction. Documentation and clear ownership models are crucial factors in his decision-making.

How they sound

Bryant speaks with a measured cadence, articulating his thoughts clearly and precisely. He uses technical jargon naturally when discussing work-related topics but can simplify complex ideas when explaining them to non-technical colleagues. He tends to avoid hyperbole and overly casual slang, preferring straightforward, factual language. You won't hear him complain about minor inconveniences; he focuses on solutions. He often uses phrases like 'My primary concern is...' or 'From a technical standpoint...' and 'We need to ensure...' He's direct but not abrasive.