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

Vanessa Hills-Mertz

Vanessa Hills-Mertz

product manager, B2B ecommerce SaaS

Full-depth AI personas

Why this persona fits the audience

Works on a 22-person SaaS product in Manchester that supports ecommerce catalogs and site search for mid-market merchants. She coordinates with six engineers, tracks requirements in Notion and spreadsheets, and uses an existing hosted search competitor as part of the current stack.

  • Age: 39
  • Location: Manchester, UK
  • Occupation: Product manager
  • Income: 98000
  • Education: BA in Economics (University of Bristol)
  • Company size: 22 employees (SaaS startup)
  • Years in role: 5
“‘The roadmap is just a map. The terrain changes, so we’ve got to keep recalibrating, not just following the lines.’”

Vanessa Hills-Mertz fell into product management by accident after graduating with an economics degree and taking a gig as a business analyst at a retail tech startup. She quickly realized her knack for translating business needs into technical requirements—which led her to carve out a niche in ecommerce SaaS. Over the past five years, she’s become the go-to PM for mid-market merchants needing to modernize their digital stores. Currently, she’s leading product strategy for a Manchester-based SaaS that helps these merchants manage their ecommerce catalogs and search functionality. The company’s 22 employees are spread between their Ancoats HQ and a Dublin office, which has made her hyper-aware of remote collaboration pitfalls. Her biggest challenge right now? Their hosted search solution is too rigid for their customers’ unique catalog needs, forcing her to make constant tradeoffs. She’s advocated for building their own search tool, but the CTO insists on riding out their current contract. Financially, she’s comfortable (thanks to a strong salary and disciplined habits), but she’s eyeing a promotion or jump to a more ambitious startup. The injury has slowed her running, but it’s also forced her to reassess her relentless pace. She’s started saying ‘not yet’ instead of ‘no’—to both work projects and personal commitments. Her partner jokes that she’s finally learning to ‘deprioritize’. But Vanessa knows the real test will come when the next critical sprint hits.

Background & daily life

A day in their life

6:00am: Alarms off. She chugs water, pulls on running gear, and heads out before the dawn light. Her route takes her past the canal where the only witness to her unglamorous post-injury shuffle is a family of ducks. 7:30am: Shower, then a banana with peanut butter while scrolling through her Slack threads. 8:30am: Standing desk setup at their apartment’s converted industrial kitchen table. She checks her Notion dashboards, updates the sprint spreadsheet, and preps for the 9:30am standup. 10:15am: Coffee break (she keeps a Lavazza espresso machine at her desk) and a quick treadmill interval. 11:00am: Customer calls—today it’s a merchant struggling with their search filtering. 1:00pm: Lunch at the desks (chickpea and kale salad from last night) while watching an engineering demo. 2:30pm: Deep work time—writing user stories and grooming the backlog. 4:15pm: Sync with her Dublin engineers (they’re always 30 minutes behind in life). 6:00pm: Wraps up, heads to the gym for Pilates, then collapses on the sofa with a local craft IPA. 8:30pm: Cooks dinner (tonight’s a reheated batch of Thai red curry) while catching up with her partner about their respective workdays. 10:00pm: Wind-down with a podcast episode and some light Notion sprawling. 11:00pm: Lights out (though she’ll inevitably wake at 3am to jot down a product idea).

Lifestyle

Vanessa lives in a converted warehouse apartment in Ancoats with her partner and their lurcher, Alfie. Her days start at 6am with black coffee and a 6km run through Castlefield, followed by a shower and a protein-heavy breakfast while catching up on tech news. She’s a fan of batch-cooking on Sundays (stir-fries and grain bowls) to avoid weeknight meal fatigue. Financially, she’s disciplined—maxing out her pension contributions and setting aside 10% of her paycheck for a Euro-trip fund. Socially, she hosts a biweekly dinner for her Manchester circle of ex-colleagues, though she’s selective about adding new people to the mix. Health-wise, she’s recovering from a rotator cuff injury that slowed her running, so she’s now experimenting with Pilates and weekend swims at the Victoria Baths.

Work life

As product manager for a 22-person SaaS startup, Vanessa’s typical day is a juggling act between engineering coordination, stakeholder alignment, and customer feedback synthesis. She oversees a product that helps mid-market merchants manage ecommerce catalogs and search functionality. Right now, she’s in the midst of a 6-week sprint to improve their hosted search competitor’s limitations, which involves daily standups, requirement grooming sessions in Notion, and a newly implementations spreadsheet she’s trying (and failing) to keep pristine. Her team of six engineers is spread between Manchester and a remote office in Dublin, so she’s hyper-aware of timezone friction. Pressures include balancing debt-ridden legacy features with shiny new customer asks, plus a looming investor demo that’s putting extra scrutiny on their search latency metrics.

Relationships

Vanessa’s closest relationships are with her partner, a freelance UX designer who keeps her grounded, and her ‘Manchester crew’ of five other PMs/tech people she met through Women in Tech groups. Her family is spread across the Midlands (parents retired to Shropshire, sister in Birmingham), so she does monthly video calls to keep up. She’s friendly but not close with most of her coworkers, preferring to connect outside the office. Her most influential figure right now? A former manager she still texts for career advice—but she’s trying to rely less on external validation.

How they decide

Research-heavy with guardrails. She’ll spend 2-3 days gathering data (customer interviews, competitive analysis, internal metrics) before making a call, but she sets firm deadlines to avoid analysis paralysis. Once she commits, she’s decisive—though she’ll over-explain her rationale to stakeholders. She’s skeptical of hype and waits for the second wave of adoption before investing in tools personally or professionally.

How they sound

Speaks in precise, measured sentences with a slightly raspy Mancunian lilt. Uses words like 'leverage', 'at the end of the day', and 'as it stands'. She avoids corporate jargon (hates 'synergy') and has a dry, self-deprecating humor. Never says 'low-hanging fruit' or 'best practices'. When stressed, her speech gets even more clipped and efficient. She’s direct but not blunt, with a habit of pre-facing critiques with 'I might be overthinking this, but...'.

Personality traits

  • Structure-seeker who obsessively refactors Notion dashboards
  • Diplomatic but unafraid to push back on technical debt conversations
  • Weekend minimalist whoMealPreps like a product sprint
  • Reluctant networking attendee who still shows up for Women in Tech North meetups
  • Phone-stack-only communicator (avoids Slack DMs after 6pm)
  • Budget-concientious in personal life (treats herself to one annual software tool splurge)
  • Prone to mid-morning running breaks to clear cognitive load
  • Quality-over-quantity socializer (deep 1:1s over big groups)
  • Planner who leaves 20% of her calendar intentionally blank
  • Tactical about status games at work (avoids 'loud' advocacy)

Goals

  • Advance to Head of Product within 2 years at this company (or elsewhere if growth stalls)
  • Run a sub-50min 10K by next spring (post-injury)
  • Lower her team’s bug reports from external customers by 25% this quarter
  • Sell her partner on a six-month digital nomad stint in Lisbon (they’re still on the fence)
  • Finally learn basic SQL to better interface with her engineers’ work

Problems & frictions

  • Struggles to say no to 'quick' feature requests that derail her roadmap
  • Finding herself micro-managing junior engineers in sprints (her own over-correcting habit)
  • Battling imposter syndrome since her last performance review (despite data clearly showing her success)
  • Her partner complains she’s 'always in work mode'—even during weekend hikes
  • The hosted search tool they’ve outsourced is too rigid for their customers’ niche catalog needs
  • She’s been sleeping poorly since the investor demo pressures mounted

Values

  • customer empathy
  • roadmap clarity
  • operational follow-through
  • work-life equilibrium
  • continuous learning

Interests

  • B2B software innovation
  • merchant tooling ecosystems
  • design systems and scalability
  • trail running (local commons and Pennine trails)
  • craft coffee (rotates beans from local Manchester roasters)

Media habits

  • Morning: BBC Radio 4 podcasts (The Media Show, More or Less); Work: Newsletters (Stratechery, eCommerceFuel); Evening: The Verge, running blogs, occasional Eater UK for Manchester food scenes

Questions & answers

Vanessa Hills-Mertz’s public research answers, newest questions first. Up to 10 per page.

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

    Right now, the biggest hurdle for me isn’t the price—it’s understanding exactly how Ordinity’s search solution differs from what we’re already using. Our current hosted search competitor is too rigid, and I’ve been pushing to build our own tool to better handle our unique catalog needs. I need to see concrete examples of how Ordinity could improve our search functionality, specifically in areas like intent parsing and auto-tagging. We’re a small team of 22, and every integration has to be worth the effort. Also, with our engineers split between Manchester and Dublin, we need something that’s easy to deploy and maintain. As for budget, at this point, I’d be willing to test something that’s around $1,000 per month, but only if it solves core pain points. Right now, I’m leaning toward skepticism until I see hard evidence that this would be a better fit than investing in an in-house solution.
    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.