Bennie Hills

Why this persona fits the audience

He manages launches for a 9-person SaaS startup and keeps shared links in Slack, action items in Linear, and notes in Apple Notes; the team also pays for Notion and Google Workspace.

• Age: 29
• Location: London, UK
• Occupation: product manager
• Income: £78k
• Education: MSc in computer science
• Company size: 9 people (Seed stage)
• Years in role: 3 years

“I don't need another dashboard; I need a system that actually tells me what's broken before the client does.”

Bennie Hills is a twenty-nine-year-old Product Manager based in London, operating at the nerve center of a lean, nine-person SaaS startup. With an MSc in Computer Science from Imperial College London, he possesses the rare ability to bridge the gap between technical feasibility and market reality. His professional journey began in backend development, but a natural aptitude for orchestrating cross-functional teams led him to pivot into product management three years ago. Currently, he navigates the precarious waters of a seed-stage company, where resources are tight and the margin for error is non-existent. His working style is characterized by a relentless pursuit of speed and accountability; he believes that ambiguity is the enemy of progress. To manage this, he has constructed a fragmented but functional digital ecosystem: Slack for real-time communication, Linear for task tracking, and Apple Notes for capturing ephemeral insights. Despite the company paying for enterprise-grade tools like Notion and Google Workspace, Bennie's personal reliance on these disparate systems highlights a persistent pain point: the lack of seamless integration. He recently made the decision to overhaul the team's internal reporting structure, manually consolidating data from five different sources to create a unified view for investors—a move that saved the team forty hours of work but underscored the inefficiencies of their current stack. Outside of work, Bennie is a devotee of efficient living, viewing his apartment and routine as extensions of his professional philosophy. He is financially stable, earning £78,000 annually, yet he remains skeptical of spending money on tools that promise more than they deliver. His relationships are curated for depth over breadth, and he finds solace in the rhythm of cycling and the structured chaos of launching new features. Bennie is driven by a desire to build products that truly serve users, even if it means rejecting the latest industry trends in favor of proven, reliable methods.

Background & daily life

A day in their life

Bennie wakes up at 6:30 AM, brewing a strong pour-over coffee while checking global markets and overnight Slack messages. By 7:45 AM, he's cycling through the quiet streets of Shoreditch, listening to a podcast on growth strategies. At 8:45 AM, he arrives at the office, immediately diving into the morning stand-up where he clarifies priorities for the engineering squad. The bulk of his morning is spent in Linear, unblocking developers and updating ticket statuses. Lunch is a quick sandwich eaten at his desk while reviewing analytics dashboards. Afternoon meetings are packed with sales syncs and design reviews, interspersed with frantic Slack responses. Around 4 PM, he retreats to his notes app to draft a launch plan, struggling to merge data from different sources. He leaves the office by 6:30 PM, exhausted but satisfied with the day's progress, heading home to cook dinner and disconnect from work notifications until the next morning.

Lifestyle

Bennie lives in a slightly cramped but stylishly renovated Victorian terrace in Shoreditch, sharing the upper floor with two fellow creatives. His apartment is a sanctuary of minimalism, dominated by a standing desk and a single mechanical keyboard, reflecting his desire for a frictionless environment. He cycles to work religiously, using the commute to decompress or mentally prepare for the day's sprint. On weekends, he balances his analytical mind with physical exertion, often joining local group runs or exploring obscure coffee shops in Dalston. Financially, he lives comfortably but cautiously; despite his salary, he avoids unnecessary subscriptions, preferring to invest in hardware that lasts rather than recurring services he hasn't fully vetted. He values social connections deeply but curates them tightly, preferring deep conversations with close friends over large, noisy gatherings.

Work life

At his nine-person startup, Bennie acts as the operational glue between engineering, design, and sales. His day is a constant negotiation between immediate fires and long-term strategy. He spends hours in Slack managing urgent requests, then switches to Linear to triage bugs and feature requests, ensuring nothing slips through the cracks. While the company pays for Notion and Google Workspace, Bennie relies heavily on his personal Apple Notes for rapid capture of fleeting ideas, which he later synthesizes into formal documentation. The pressure is palpable; with a seed round burning cash, every launch must be perfect. He frequently finds himself manually compiling data from spreadsheets because the existing tools don't talk to each other seamlessly, leading to late nights where he tries to automate workflows that should have been solved months ago.

Relationships

Bennie maintains a tight-knit circle of three university friends who are also in tech, meeting for Sunday brunches to discuss career trajectories. He has a supportive relationship with his parents in Manchester, though their interest in his specific job duties is limited to general questions about success. Professionally, he is mentored by a former CTO who now works remotely in Berlin, providing him with high-level strategic advice via monthly video calls. He is not heavily involved in broader community groups, preferring to engage in online forums where technical depth is expected, finding more value there than in local networking events which he views as superficial.

How they decide

Bennie operates on a 'verify before investing' model. He rarely commits to a new process or tool without a clear understanding of its integration capabilities and long-term cost-benefit ratio. His decisions are heavily influenced by peer validation within the tech community; if a solution is endorsed by trusted engineers or product leaders, he moves faster. However, he remains cautious of hype cycles, often running small-scale pilots or manual workarounds to test efficacy before committing resources. He prefers data-driven justifications over emotional appeals, requiring concrete evidence of efficiency gains before altering his established routines.

How they sound

His speech is crisp, direct, and punctuated with industry-specific jargon like 'synergy,' 'blockers,' and 'velocity.' He speaks quickly when discussing workflows but slows down when explaining complex constraints. He rarely uses filler words, preferring to get straight to the point. In casual settings, he adopts a dry, self-deprecating humor about the chaos of startup life. He avoids vague adjectives, always seeking specificity. He is comfortable with silence in conversation, using it to let others finish their thoughts, but will interrupt politely if a discussion veers off-track or lacks direction.