Roman Marvin

Why this persona fits the audience

He is the product marketing manager at a London fintech with a 7-person marketing team, responsible for conversion copy on campaigns, demo pages, and onboarding pages. He already uses Hotjar and GA4 to compare page performance across launches.

• Age: 31
• Location: London, UK
• Occupation: Product marketing manager
• Income: £72k
• Education: Master's degree
• Company size: 50-200 employees (Series B startup)
• Years in role: 3

“If I can't measure why someone left, I haven't done my job yet, no matter how good the design looks.”

Roman Marvin, 31, is a Product Marketing Manager at a mid-sized fintech startup in East London, navigating the turbulent waters between user acquisition and retention. Born in Manchester and raised in a household that valued academic rigor, he pursued a Master's in Digital Economics before pivoting into marketing after realizing his passion lay in the behavioral intersection of code and human psychology. Currently earning £72,000, he represents the new breed of marketer who codes queries in SQL and interprets heatmaps with the same fluency as a copywriter. His career trajectory has been defined by a relentless pursuit of precision; he moved from a large agency where he felt disconnected from the final product to a smaller, high-growth startup where every conversion dollar counts. Roman is currently managing a seven-person marketing team, a significant step up from his previous individual contributor roles, forcing him to delegate while maintaining strict quality control over their output. He recently led a complete overhaul of the company's onboarding flow, a project that required him to mediate between designers who wanted aesthetic purity and engineers concerned about technical debt. Despite the pressures, he maintains a disciplined routine, cycling to work daily and treating his personal finances with the same strategic foresight he applies to his campaigns. He is skeptical of 'magic bullet' solutions, having seen too many tools promise easy wins only to deliver noisy data. Instead, he trusts in the slow accumulation of granular insights, believing that the difference between a successful product and a failed one often lies in the subtle nuances of the words on a button or the placement of a single input field. His life is a continuous loop of hypothesis, test, analyze, and iterate, driven by a belief that efficiency is the highest form of empathy in the digital age.

Background & daily life

A day in their life

Roman wakes at 6:15 AM, skipping breakfast to maximize cycling time. By 7:45 AM, he's at his desk, immediately checking overnight server logs and GA4 anomalies from the previous night's traffic surge. His first meeting is a 30-minute stand-up with the product team to align on the sprint's conversion goals. At 10:30 AM, he spends an hour diving into Hotjar recordings, watching users struggle with a specific form field on the pricing page, taking notes on hesitation points. Lunch is a quick sandwich eaten while reading a thread on LinkedIn about AI-generated copy. The afternoon is dominated by drafting three variations of a landing page headline, followed by a contentious review with engineering leads who argue the proposed layout changes require a refactor. He ends his day at 6:30 PM, reviewing the day's A/B test results and sending a concise summary email to the CEO before heading to the gym. The evening is reserved for cooking and unwinding, ensuring he returns to the data the next morning with fresh eyes.

Lifestyle

Roman lives in a converted warehouse loft in Shoreditch, balancing modern minimalism with functional clutter—whiteboards covered in funnels dominate his home office. He cycles to work regardless of rain, using the commute to decompress before diving into data. His weekends are split between intense gym sessions at a local CrossFit box and quiet evenings cooking elaborate meals, as he treats food prep like another form of process optimization. Financially, he is cautious; he maxes out his pension contributions early and avoids flashy spending, preferring to invest in high-quality gear that lasts rather than trendy gadgets. Socially, he maintains a tight circle of four or five close friends, mostly from university or previous tech roles, prioritizing deep conversations over large networking events.

Work life

His day revolves around the friction between engineering velocity and user retention. Roman sits in the middle of a cross-functional triangle: Product, Engineering, and Sales. Mornings are spent debugging why a specific onboarding step has a 40% drop-off rate by triangulating GA4 event data with Hotjar session replays. Afternoons are dedicated to writing and A/B testing copy variants for the new demo page launch, often clashing with engineers who view content changes as low-priority distractions. He manages a small team of three content specialists and one designer, requiring him to constantly translate user behavioral insights into actionable briefs. The pressure is constant; every percentage point in conversion directly impacts the company's runway, making his role feel less about 'branding' and more about survival engineering.

Relationships

Roman is married to Sarah, a graphic designer who provides a creative counterbalance to his analytical mindset; they make decisions together on major purchases but respect each other's domain expertise. His closest friend group consists of three former colleagues from a previous agency job, meeting monthly for dinner to discuss industry shifts rather than just venting. He is loosely connected to a mastermind group of CMOs in London, attending quarterly meetups where they trade anonymized benchmarks. While he values peer validation, he rarely seeks advice from family regarding career strategy, viewing his professional life as a distinct sphere where his parents' traditional views on stability sometimes clash with the volatility of tech startups.

How they decide

Roman operates on a 'verify before committing' model. He is neither impulsive nor paralyzed by analysis; instead, he requires a logical chain of evidence connecting a proposed change to a measurable outcome. He leans heavily on quantitative data (GA4, Hotjar) to validate qualitative hypotheses, but remains wary of tools that promise answers without transparency. He prefers peer-reviewed case studies over vendor sales pitches and will typically run a small-scale internal pilot before adopting a new workflow. Once a solution demonstrates efficiency gains in a controlled environment, he adopts it rapidly, valuing speed once the risk is mitigated.

How they sound

Roman speaks in a clipped, efficient cadence typical of London tech professionals. He avoids flowery adjectives, preferring precise verbs and nouns. In meetings, he interrupts politely to ask for data sources ('Can we pull the cohort size for that?') rather than arguing opinions. He rarely uses corporate jargon like 'synergy' or 'paradigm shift,' replacing them with 'handshake,' 'pipeline,' or 'friction.' When explaining complex concepts, he defaults to analogies involving plumbing or mechanics. He tends to pause briefly before answering, mentally calculating the statistical significance of his own statement before speaking. His tone is generally neutral and professional, though he can become animated when discussing a particularly elegant solution to a user problem.