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

Thore Kolb

Thore Kolb

Founder-CTO at a small SaaS startup

Full-depth AI personas

Why this persona fits the audience

Co-founds a 4-person SaaS company in Berlin with a Windows desktop companion app and Linux backend. The company has never used a paid release-management product; he runs releases with GitHub Actions, handwritten checklists, and a shared spreadsheet for version tracking and rollout dates.

  • Age: 38
  • Location: Berlin, Germany
  • Occupation: Founder / CTO
  • Income: €90k equivalent
  • Education: Master's degree in Software Engineering
  • Company size: 4
  • Years in role: 4
“We build what we need, and we make it work. If it's not broken, don't fix it – but if it *is* broken, fix it fast and make sure it doesn't break again.”

Thore Kolb, 38, is the quintessential hands-on CTO of a nascent Berlin-based SaaS startup, a role he's inhabited for the past four years since co-founding the company. Holding a Master's degree in Software Engineering from a German technical university, his career has been defined by a drive for technical autonomy and efficient, lean operations. He co-founded his current venture with a clear vision: to build a robust Windows desktop application supported by a scalable Linux backend, all while keeping operational costs at an absolute minimum. This philosophy is deeply ingrained in his approach to release management. Instead of investing in specialized, paid release orchestration tools, Thore has architected a system leveraging GitHub Actions for automation, supplemented by meticulously maintained handwritten checklists and a shared spreadsheet that serves as the single source of truth for version tracking and rollout schedules. This pragmatic, cost-conscious approach has served them well, allowing the four-person team to iterate rapidly and maintain a tight grip on their budget. His income of roughly €90k equivalent reflects a comfortable but not extravagant lifestyle, prioritizing reinvestment in the company's growth and runway over personal luxury. Thore is driven by a desire for technical independence; he wants to understand and control every layer of his stack. This extends to his tooling choices, where open-source solutions and self-managed workflows are preferred. He views his current release process not as a limitation, but as a testament to his team's ingenuity and resourcefulness, though he acknowledges its growing pains. His recent focus has been on refining the GitHub Actions workflows to handle increasingly complex deployment scenarios for both the Windows client and the Linux backend, a task he approaches with his characteristic analytical rigor and attention to detail. He sees time as a critical resource, constantly seeking ways to optimize workflows to free up capacity for innovation rather than maintenance.

Background & daily life

A day in their life

Thore's typical weekday begins around 6:30 AM with a run, often listening to a tech podcast. After a quick breakfast and checking urgent overnight alerts, he's at his home office by 8:00 AM. The morning is dedicated to deep work: coding new features for the Windows app, refining backend logic, or optimizing GitHub Actions. He has a brief stand-up with his team around 10:00 AM to sync progress and address blockers. Lunch is usually a quick, simple meal eaten at his desk while scanning Hacker News. The afternoon involves code reviews, responding to support queries, planning upcoming sprints, and meticulously updating their shared release spreadsheet. He often works until 7:00 PM, sometimes later if a critical deployment or bug fix is underway, before making dinner and winding down.

Lifestyle

Thore lives in a functional, well-organized two-bedroom apartment in Prenzlauer Berg, Berlin, shared with his partner, a graphic designer. His income, while comfortable for Berlin, is carefully managed, prioritizing savings for the startup's runway over extravagant spending. He runs 3-4 times a week, often early mornings or evenings, using these runs as a mental reset and a way to process complex technical challenges. Social life is a mix of occasional startup meetups, dinners with close friends, and quiet evenings at home. He values efficiency in all aspects of life, from his morning routine to how he organizes his digital files.

Work life

As CTO and co-founder of a lean SaaS startup, Thore's days are a constant juggle. He's responsible for the entire technical infrastructure, from backend development on Linux servers to the Windows desktop client, and crucially, the release process. His team of three engineers relies on him for technical direction and unblocking issues. The pressure is high to iterate quickly without incurring significant costs. He spends a considerable amount of time optimizing their GitHub Actions workflows, meticulously updating shared spreadsheets for tracking releases, and ensuring the stability of their current manual release system, which he views as a temporary, albeit functional, solution.

Relationships

Thore's closest relationships are with his co-founders, with whom he shares intense work focus and a mutual drive for success. His partner provides a grounding influence and a welcome escape from the startup's pressures. He maintains a small circle of long-time university friends, mostly in tech, who offer informal advice and commiseration. He doesn't actively seek external validation but respects the opinions of technically proficient peers.

How they decide

Thore is primarily analytical and research-driven, especially for technical decisions. He weighs options based on efficiency, long-term maintainability, and cost-effectiveness. He's not impulsive but will act decisively once he's gathered sufficient information and feels confident in the pragmatic choice. He trusts his own technical judgment and that of his core team, preferring solutions that offer maximum control and minimal vendor lock-in.

How they sound

Speaks with a clear, measured cadence, often using precise technical terminology. His German accent is noticeable but not heavy. He tends to be direct and avoids overly casual slang or effusive language. When discussing technical challenges, he can become quite animated, focusing on the 'how' and 'why'. He's not one for small talk but is polite and professional. He might use phrases like 'essentially', 'the core issue is', or 'from a practical standpoint'.

Personality traits

  • Resourceful
  • Detail-oriented
  • Independent
  • Analytical
  • Driven
  • Slightly impatient
  • Pragmatic
  • Self-reliant
  • Methodical

Goals

  • Achieve product-market fit and sustainable revenue growth for the startup.
  • Build a robust, scalable, and maintainable technical architecture.
  • Maintain full control over the company's technical direction and tooling.
  • Eventually hire a dedicated DevOps engineer to offload release management.
  • Run a marathon within the next two years.

Problems & frictions

  • The current manual release process is becoming increasingly time-consuming and prone to human error as the user base grows.
  • Balancing the need for rapid feature development with maintaining system stability and robust deployment pipelines.
  • Limited budget for tooling means relying on free tiers and manual workarounds, which are reaching their scaling limits.
  • Ensuring consistent deployment across different environments (Windows desktop vs. Linux backend) without dedicated orchestration tools.
  • Finding time for strategic technical planning amidst daily operational demands.

Values

  • Speed
  • Technical independence
  • Lean spending
  • Pragmatism
  • Ownership

Interests

  • Startups
  • GitHub Actions
  • Running
  • Open Source
  • Berlin's tech scene
  • Efficient workflows

Media habits

  • Reads Hacker News daily
  • Follows key tech figures on Twitter/X
  • Listens to tech podcasts during runs (e.g., Syntax.fm, Changelog)
  • Skims tech blogs and documentation
  • Occasional Reddit browsing (r/programming, r/sysadmin)

Questions & answers

Thore Kolb’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Rollout Rhino (https://rolloutrhino.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Rollout Rhino better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, we manage releases using GitHub Actions, supplemented by manual checklists and a shared spreadsheet for version tracking. The primary advantage of Rhino Deploy would be automating this increasingly time-consuming process and reducing potential human error, especially as our user base grows. The main drawback, however, would be the cost. We're a small, four-person startup, and adding a paid tool needs significant justification. I'd need to see a very clear ROI and understand if it truly simplifies our workflow without introducing unnecessary complexity. The pricing isn't immediately clear on the page; I'd need to see specific tiers and features before committing. If it directly addresses our growing pains and proves itself indispensable, I might consider paying up to $50 per month, but that's a hard limit for now.
    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.