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

Jimmy Weber-Dach

Jimmy Weber-Dach

Startup CTO who prefers direct build work

Full-depth AI personas

Why this persona fits the audience

Leads engineering for a 4-person startup in Manchester and spends much of the week turning founder ideas into tickets, acceptance criteria, and sprint plans. Usually works straight from docs and issue trackers, with limited time for visual planning.

  • Age: 40
  • Location: Manchester, UK
  • Occupation: CTO
  • Income: £118k + equity
  • Education: Bachelor's degree in software engineering
  • Company size: 4 employees
  • Years in role: 3
“If you can't write the acceptance criteria down clearly enough for a machine to understand, you haven't actually solved the problem yet.”

Jimmy Weber-Dach is a forty-year-old software engineer turned Chief Technology Officer, currently steering the technical direction of a nascent four-person startup based in Manchester. With a Bachelor's degree in Software Engineering from the University of Manchester, Jimmy spent the first decade of his career as a senior backend developer at established fintech firms before transitioning to the volatile world of startups. His current role is a hybrid of architect, product manager, and lead developer, a necessity born from the lean staffing of his organization. Unlike many CTOs who delegate all hands-on work, Jimmy thrives on direct build activities, often found typing away at his keyboard late into the night to ensure the foundational code is robust. He is a man defined by his conscientiousness; his workspace is a model of order, with digital and physical environments meticulously organized to maximize efficiency. His income reflects his dual status as a high-value employee and an early-stage equity holder, providing him with financial security but also tying his personal wealth to the company's survival. Jimmy is deeply skeptical of buzzwords and empty promises, preferring the tangible certainty of well-documented specs and predictable sprint cycles. Recently, he made the difficult decision to reject a popular but complex project management tool in favor of a simpler, text-centric alternative, citing the need to reduce cognitive load for his small team. He views time as his most scarce resource, constantly fighting the urge to optimize his schedule for strategic thinking while being pulled into the weeds of daily operations. Despite the pressures of leading a startup in a competitive market, Jimmy remains grounded, driven by a desire to build something lasting and a commitment to the technical integrity of his craft.

Background & daily life

A day in their life

Jimmy wakes at 6:00 AM for a quick run before heading to his home office to check overnight logs and prioritize the day's tickets. By 8:30 AM, he joins a stand-up with the three other team members, where he translates yesterday's progress into today's deliverables, often reworking vague tickets from the previous night. Mid-morning is dedicated to deep work: writing complex SQL queries, refactoring legacy code, or drafting detailed API documentation for the frontend team. Lunch is a solitary affair, usually eaten at his desk while skimming Hacker News. Afternoons are fragmented by ad-hoc meetings with the founder, where he navigates shifting requirements, followed by code reviews to maintain quality standards. The evening brings a final push to resolve critical bugs or plan the next sprint, often extending until 7:30 PM. He then disconnects to spend quality time with his family, leaving work stress at the door.

Lifestyle

Jimmy lives in a semi-detached house in Chorlton-cum-Hardy, an area popular with young professionals and families. His mornings are strictly regimented; he leaves the house at 7:15 AM to avoid the M56 rush hour, often listening to technical podcasts or reading code documentation on his phone. He is not a gym rat but prioritizes a consistent 30-minute run three times a week to clear his head. Financially, he is comfortable but disciplined, maximizing pension contributions while keeping discretionary spending moderate due to his equity-heavy compensation structure. Socially, he is selective, preferring deep conversations over large gatherings, usually seeing friends once every two weeks for a pint or a meal. He values stability and routine, viewing his home life as the necessary counterbalance to the chaotic nature of early-stage startup development.

Work life

As the de facto product manager and architect for a four-person team, Jimmy's role is a constant balancing act between high-level strategy and granular execution. His primary friction point is translating the founder's visionary but often vague concepts into actionable engineering tasks. He rarely engages in whiteboard sessions; instead, he relies heavily on text-based specifications in Jira or Linear, meticulously crafting acceptance criteria to prevent scope creep. His days are dominated by ticket grooming, code reviews, and debugging production issues that arise unexpectedly. While he has the authority to make architectural decisions, his time is consumed by the operational necessity of ensuring the small team delivers predictable sprints. He spends his evenings reviewing logs and planning the next day's critical path, often working late to ensure the foundation laid today doesn't crumble tomorrow.

Relationships

Jimmy is married to Sarah, a primary school teacher, whose organizational skills complement his logical approach. Their six-year-old son is his primary motivation for seeking stability. He maintains a tight-knit circle of former university mates, mostly engineers, who serve as a sounding board for professional challenges rather than social distractions. He is influenced more by peer validation within the local Manchester tech community than by industry influencers, valuing practical success stories over theoretical frameworks. His relationship with his founders is built on trust but occasionally strained by the communication gap between vision and implementation.

How they decide

Jimmy operates with a cautious, evidence-based decision-making style. He is not swayed by marketing fluff or aggressive sales tactics; instead, he requires concrete data, clear documentation, and proof of reliability before committing resources. When evaluating new tools or processes, he conducts a thorough cost-benefit analysis, weighing the long-term maintenance burden against immediate gains. He tends to rely on peer recommendations and technical reviews, often testing solutions in a sandbox environment before full adoption. His decisions are deliberate and calculated, prioritizing predictability and risk mitigation over speed or novelty.

How they sound

His speech is precise, direct, and devoid of corporate jargon unless necessary. He speaks with a measured cadence, often pausing to formulate exact thoughts rather than filling silence. He avoids hyperbole, preferring 'this will take three days' over 'we can probably get it done soon.' In casual conversation, he might slip into technical analogies but generally keeps them grounded. He rarely uses slang, maintaining a professional tone even in informal settings, and tends to cut off rambling explanations with a polite but firm request for brevity.

Personality traits

  • Methodical
  • Direct
  • Analogous thinker
  • Time-poor
  • Detail-obsessed
  • Skeptical of hype
  • Structured
  • Low-maintenance
  • Pragmatic
  • Protective of team focus

Goals

  • Stabilize the core infrastructure to support rapid scaling without technical debt accumulation
  • Achieve a sustainable work-life balance that allows for presence at family events
  • Lead the company through its Series A funding round with clean financials
  • Mentor junior developers to reduce reliance on his own direct coding output
  • Implement a robust automated testing suite to minimize manual QA overhead

Problems & frictions

  • Founder requests often lack the specificity required for immediate engineering execution
  • Difficulty finding time for strategic architecture work amidst daily firefighting
  • Managing expectations regarding delivery timelines when requirements shift mid-sprint
  • Limited budget for enterprise-grade developer tools compared to larger competitors
  • Risk of burnout due to wearing too many hats in a small team environment

Values

  • technical rigor
  • predictability
  • accountability
  • efficiency
  • pragmatism

Interests

  • agile delivery
  • issue tracking
  • cloud architecture
  • developer tools
  • UK football

Media habits

  • Hacker News daily digest
  • Local tech meetups in Manchester
  • Twitter/X for infrastructure news
  • Podcasts on systems design
  • GitHub trending repositories

Questions & answers

Jimmy Weber-Dach’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of Flowmaps (https://flowmaps.app/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Flowmaps 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 use Jira for ticket management and documentation. It's text-centric and fits our workflow, avoiding the cognitive load of more complex tools. Flowmaps seems to offer a visual way to plan, which could be beneficial if it truly simplifies translating founder ideas into actionable tasks. However, I'm skeptical of visual tools that add complexity rather than clarity. The ability to directly integrate with AI builders is interesting, but I'd need to see if it genuinely streamlines our process or just adds another layer. The "Pro" tier at $19/month might be acceptable for unlimited ventures, but I'd need to evaluate the actual time savings and reduction in rework.
    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.