Why this persona fits the audience
Runs a 3-person content studio that publishes restaurant price-and-calorie pages for UK and US chains. The team splits research across browser tabs, shared sheets, and a competitor's menu-data export that they already keep in the workflow.
- Age: 38
- Location: Manchester, UK
- Occupation: Owner, content studio
- Income: £62k
- Education: B.Sc. in marketing
- Company size: 3 employees (including himself)
- Years in role: 5
“If I'm spending more time hunting for the right number than actually publishing it, I've built a broken system.”
Paul Rath is the architect of a niche digital content studio based in Manchester, specializing in the granular world of fast-food nutrition and pricing data. At 38, he sits at the intersection of marketing strategy and technical execution, leveraging his B.Sc. in marketing to build a business that thrives on specificity. Five years ago, frustrated by the lack of accurate, consolidated data for transatlantic fast-food comparisons, he launched his studio with a single laptop and a relentless drive for reliability. Today, his small team of three manages a sprawling ecosystem of web pages serving millions of users seeking calorie counts and price points for chains ranging from Sheetz to Tesco. Paul's professional identity is defined by his meticulous nature and his resistance to 'black box' solutions. He has built a robust, albeit fragile, workflow relying on a patchwork of browser tabs, shared Google Sheets, and a proprietary competitor data export that serves as his golden source of truth. While others might chase the next big AI trend, Paul is deeply invested in optimizing the mundane: perfecting the regex patterns that scrape menu items and refining the CMS templates that display them. His income of £62k reflects the profitability of his lean model, allowing him to reinvest in automation tools that keep his overhead low. Despite his success, Paul is constantly battling the friction of scale. The sheer volume of menu updates across dozens of global chains creates a bottleneck that manual verification cannot sustain indefinitely. He recently turned down a potential acquisition offer because the acquirer wanted to centralize his data processes, threatening the independence he cherishes. Instead, he is quietly developing internal scripts to handle the heavy lifting, viewing his current setup as a temporary necessity rather than a permanent state. For Paul, the goal isn't just to exist in the market, but to be the most reliable source of truth in a sea of outdated information, even if it means working harder than anyone else to keep the numbers right.
Background & daily life
A day in their life
Paul wakes at 6:30 AM, immediately checks the server status for the main US client sites, and grabs a strong black coffee. By 7:30 AM, he is at his desk, reviewing overnight traffic reports and scanning for any sudden price drops reported by users. He holds a brief 15-minute stand-up with his team at 9:00 AM to assign tasks, focusing on verifying the new breakfast menu items for a major chain. Lunch is usually a quick sandwich eaten while reading a technical blog post about API integrations. Afternoon hours are dedicated to deep work: writing custom Python scripts to parse HTML tables and cleaning up messy data exports. He spends the last hour of the day QA-ing the next day's content, ensuring all calorie counts align with official PDFs. At 6:00 PM, he shuts down the computer, takes a short walk to clear his head, and heads home for dinner with his wife, leaving work thoughts behind until the next morning.
Lifestyle
Paul lives in a quiet, leafy part of Chorlton where he can walk to his favorite gastropub, The Old Churchyard, for a pint after work. He maintains a strict separation between work and home, rarely checking email after 7 PM unless a client site is down. His weekends are split between DIY projects around the house—recently repainted the kitchen cabinets—and hiking in the Peak District with his partner. He is financially prudent, having paid off his student loans aggressively, and prefers investing in tools that save time rather than buying luxury goods. He enjoys the ritual of Sunday roast dinners but often finds himself mentally drafting content briefs while chopping vegetables. Socially, he keeps a tight circle of friends who understand the demands of running a small business, preferring one-on-one coffee catch-ups over large group gatherings.
Work life
Paul runs a lean operation from a converted garage office in his garden, managing a three-person team: two junior researchers and one freelance editor. Their core product is hyper-specific landing pages detailing prices and calories for major fast-food chains like McDonald's and Burger King in both the UK and US markets. The daily grind involves a chaotic dance of twenty open browser tabs, multiple Google Sheets, and a legacy CSV export from a competitor that serves as their baseline. Paul spends his mornings auditing data accuracy, ensuring the calorie counts match the latest nutritional guidelines, and his afternoons debugging CMS plugins or refining automation scripts. The pressure is constant; a single error in a price point can lead to angry customer comments and SEO penalties. He prides himself on maintaining a streamlined workflow despite the manual nature of much of the research, often staying late to ensure the morning publish goes live without hitches.
Relationships
Paul is married to Sarah, a primary school teacher who provides a grounding counterbalance to his tech-focused stress. They have no children yet, allowing them flexibility to travel occasionally. His closest confidants are two former university mates who also run digital agencies in Leeds and Bristol; they meet quarterly to swap notes on client management and tax strategies. He has a mentorship relationship with an older SEO specialist he met at a conference five years ago, who advises him on algorithm updates. Professionally, he relies heavily on his two researchers, treating them as partners rather than subordinates, fostering a culture of mutual respect and autonomy.
How they decide
Paul operates with a cautious, evidence-based approach. He rarely commits to new software without a thorough trial period and a clear demonstration of ROI against his existing spreadsheet-heavy workflow. He values peer recommendations from trusted industry circles over marketing hype. When evaluating solutions, he prioritizes data security and integration capabilities over flashy UI features. He is willing to pay for efficiency if the tool eliminates a recurring manual task, but he will not invest in a platform that requires a steep learning curve or disrupts his established processes without a compelling reason.
How they sound
Paul speaks with a measured, Midland English cadence, avoiding slang but using precise terminology. He tends to be direct and concise, valuing clarity over pleasantries. In professional settings, he uses phrases like 'the data doesn't stack up' or 'we need to automate this loop.' He avoids hyperbolic language like 'revolutionary' or 'game-changing,' preferring grounded descriptions of functionality. He often pauses to think before answering complex questions, indicating a careful consideration of facts. His tone is generally calm and professional, though he can become slightly sharp if he detects inefficiency or lack of attention to detail in a process.
Personality traits
- Meticulous about data accuracy
- Skeptical of 'magic button' solutions
- Quietly confident in technical ability
- Time-obsessed
- Prefers asynchronous communication
- Protective of proprietary workflows
- Dislikes unnecessary meetings
- Methodical problem solver
- Independent thinker
- Pragmatic optimist
Goals
- Achieve 100% uptime and zero data discrepancies across all published pages for the next fiscal year
- Reduce the average time spent on manual menu data entry by 40% through better scripting
- Expand the studio's portfolio to include European market chains without increasing headcount
- Build a passive income stream through affiliate partnerships with healthy eating apps
- Maintain a healthy work-life balance to prevent burnout
- Establish the studio as the definitive authority on US-UK fast food pricing transparency
Problems & frictions
- Fragmented data sources requiring constant cross-referencing across disjointed spreadsheets
- The high cognitive load of manually verifying hundreds of menu changes weekly
- Difficulty scaling operations without hiring more staff, which erodes profit margins
- Inconsistent data formatting from different chain websites causing CMS integration issues
- The tedious nature of updating historical archives when prices change retroactively
- Limited budget for enterprise-grade data scraping tools that fit their specific niche
Values
- reliability
- efficiency
- independence
- data integrity
- pragmatism
Interests
- CMS publishing
- automation
- pub food
- local brewing
- spreadsheet architecture
- SEO trends
Media habits
- Skimms industry newsletters (Search Engine Journal, Marketing Week) on commute
- Watches technical YouTube deep-dives on Python scripting while cooking dinner
- Listens to true-crime podcasts during gym sessions
- Reads local Manchester news sites before bed
- Active on LinkedIn but mostly lurks
- Uses Reddit r/sysadmin and r/marketing for troubleshooting