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

Irvin Feil

Irvin Feil

Startup product manager

Full-depth AI personas

Why this persona fits the audience

Works at a 7-person SaaS startup in London and regularly assembles screenshots, PRDs, CSV exports, release notes, and slide decks on a Mac while moving files between Notion, Figma, Google Drive, Slack, and Keynote for sprint reviews and customer demos.

  • Age: 37
  • Location: London, UK
  • Occupation: Product manager
  • Income: £78,000
  • Education: MSc in Management
  • Company size: 7 employees
  • Years in role: 4
“Efficiency isn't about doing more things faster; it's about removing the steps that don't actually move the needle.”

Irvin Feil is a 37-year-old Product Manager navigating the turbulent waters of a seven-person SaaS startup in East London. With an MSc in Management from a top-tier UK university, he entered the tech sector after a brief stint in traditional consulting, realizing he preferred building products over advising on them. Four years into his current role, he has evolved from a junior coordinator to the operational backbone of the company, effectively serving as the bridge between the founders' vision and the engineers' execution. His daily reality is a relentless cycle of context switching: drafting Product Requirement Documents (PRDs) late at night, analyzing CSV exports to track user churn, and frantically assembling slide decks from scattered screenshots and Figma prototypes just hours before a critical customer demo. Irvin is acutely aware of the inefficiencies inherent in his workflow. He spends a disproportionate amount of time managing file versions across Notion, Google Drive, and local Mac folders, often losing sleep over the fear of presenting outdated information. Despite his high conscientiousness, the chaotic nature of a micro-startup leaves little room for the systematic organization he craves. He earns £78,000, a salary that reflects his seniority relative to the team size but offers limited buffer against the financial instability common in early-stage ventures. He is pragmatic about money, investing heavily in his retirement and avoiding luxury goods, yet he is willing to spend on tools that promise to reclaim his most valuable asset: time. Recently, he made the difficult decision to push back on a feature request from a key investor because the engineering team lacked the bandwidth, a move that tested his political capital but reinforced his commitment to team sustainability. Irvin is defined by a quiet determination to build something meaningful without sacrificing his health or sanity, constantly seeking ways to streamline the chaos of modern product management.

Background & daily life

A day in their life

Irvin wakes up at 5:45 AM, not because he loves the early hours, but because it guarantees quiet time before the noise of London begins. After a quick stretch and a run along the river, he returns home for a coffee and a scan of the overnight GitHub activity and Slack messages. By 8:45 AM, he is commuting to his office in Shoreditch, listening to an episode of a productivity podcast while reviewing the day's agenda. The morning block is reserved for deep work: writing a new PRD for a feature currently stuck in limbo. Lunch is a sandwich eaten at his desk while watching a recorded customer demo to gather feedback for the team. Afternoon meetings are a gauntlet of sprint planning, engineering syncs, and a frantic assembly of a slide deck for a potential client demo scheduled for the following week. The commute home is spent mentally decompressing, switching off completely until he starts cooking dinner. Evenings are reserved for family time or light reading, though a lingering notification occasionally pulls him back into the digital fray.

Lifestyle

Irvin lives in a compact, well-organized flat in Shoreditch, where every surface is either a workspace or a clear zone. He runs five mornings a week along the Thames Path to maintain his mental clarity, often listening to deep-dive tech podcasts while training for a half-marathon. Financially, he is cautious; he maximizes pension contributions and avoids impulse buys unless they solve a specific workflow bottleneck. His social life revolves around work colleagues and fellow runners rather than large parties. He enjoys cooking simple, high-protein meals on Sundays and values weekends that offer genuine disconnection from screens, though the line between work and home is frequently blurred by the nature of his role in a small startup.

Work life

His days are a constant context-switching exercise across a fragmented ecosystem of apps. As one of only three non-engineering staff at his seven-person SaaS startup, Irvin wears multiple hats: he writes the PRDs, manages the backlog, analyzes CSV export data for feature adoption, and builds the slide decks for investor updates. The pressure comes from the need to align a tiny, overworked engineering team with vague market demands without burning them out. He spends hours dragging screenshots between Figma and Notion, then exporting raw data to Google Sheets before formatting it into Keynote for Friday's demo. The lack of administrative support means he is also the de facto project manager, ensuring that nothing falls through the cracks despite the chaotic environment.

Relationships

He is married to Sarah, a digital marketer who understands the grind of the startup world but often has to be the 'adult' in the room when work bleeds into dinner time. His closest confidants are two former university classmates who now run agencies in Berlin and New York; they provide a sounding board for strategic ideas. Professionally, he relies heavily on his CTO, with whom he shares a relationship built on mutual respect but frequent debates about technical debt versus feature velocity. He maintains a loose network of other PMs in London's tech scene, mostly met through running clubs and meetups.

How they decide

Irvin is a methodical researcher who prefers peer validation over flashy marketing claims. He rarely adopts a new tool immediately upon release; instead, he waits for community consensus, reads detailed case studies, and often requests a trial period to test integration with his existing stack. He is willing to pay for software if it demonstrably saves time or reduces cognitive load, but he is deeply skeptical of features that add complexity without solving a core friction point. His decisions are driven by practical utility and long-term ROI rather than trends.

How they sound

Irvin speaks with a measured, precise cadence, typical of someone who has spent years translating complex product requirements into plain English. He avoids hyperbole and corporate jargon, preferring direct statements. In meetings, he uses phrases like 'let's ground this in data' or 'what's the actual friction here?' He rarely raises his voice, even when stressed, but his tone can become sharp if he feels time is being wasted on irrelevant discussions. He tends to pause before answering complex questions, thinking aloud to structure his thoughts. He avoids saying 'I don't know' without immediately following up with 'but I will find out,' reflecting his accountability-focused mindset.

Personality traits

  • methodical
  • verbally precise
  • chronically time-poor
  • frustrated by ambiguity
  • pragmatically optimistic
  • data-driven but human-centric
  • ritualistic about morning routines
  • protective of team focus
  • technologically curious but skeptical of hype
  • reliable under pressure

Goals

  • Lead the successful launch of the company's new enterprise tier within six months
  • Achieve a sustainable work-life balance where evenings remain screen-free
  • Build a personal brand as a thoughtful voice in the European SaaS space
  • Save enough capital to eventually co-found a second venture focused on developer tools
  • Complete a sub-1:45 half-marathon next autumn
  • Streamline internal documentation to reduce meeting times by 20%

Problems & frictions

  • Fragmented file storage makes retrieving old design assets for client demos painfully slow
  • Difficulty maintaining version control across disparate tools like Notion and Google Drive
  • Time lost manually assembling presentation materials instead of strategizing
  • Ambiguity in stakeholder expectations regarding sprint priorities
  • Burnout risk from constantly context-switching between deep work and administrative tasks
  • Lack of dedicated resources for data visualization beyond basic spreadsheet exports

Values

  • efficiency
  • accountability
  • team alignment
  • practicality
  • transparency

Interests

  • SaaS tools
  • roadmapping
  • running
  • tech podcasts
  • cycling infrastructure
  • indie hacking

Media habits

  • The Product Hunt Daily newsletter
  • Reply All (podcast)
  • Stratechery blog
  • LinkedIn industry groups
  • Hacker News front page
  • Local running club WhatsApp group

Questions & answers

Irvin Feil’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Dockside (https://hachipoo.com/dockside-app) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    My current workflow involves a lot of moving files between Notion, Google Drive, and Slack, often just grabbing screenshots directly into Keynote or Figma. While Dockside seems like it could help streamline some of that, especially with quick access to downloads and screenshots, I'd need to see how well it integrates with my existing tools. The lifetime license for $5.99 is very appealing, especially given the subscription fatigue I'm experiencing with other tools. The main hesitation would be ensuring it doesn't add another layer of complexity or become another app I have to manage and organize. I'd want to test its actual impact on my daily context switching during the trial.
    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.