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

Mike Mraz

Mike Mraz

Growth lead at a small subscription app

Full-depth AI personas

Why this persona fits the audience

Supports an 11-person subscription app in Dublin with a freemium entry tier; he reviews how AI-generated onboarding messages affect trial-to-paid conversion and the billing team already uses Orb for plan and seat usage.

  • Age: 33
  • Location: Dublin, Ireland
  • Occupation: Growth Lead
  • Income: €82k + bonus
  • Education: BA in Marketing
  • Company size: 11 employees
  • Years in role: 2.5
“You can't optimize what you can't see, and right now, we're flying blind on exactly how much each user costs us in compute versus what they bring in.”

Born in Cork and raised in a family that valued education and practicality, Mike Mraz developed an early aptitude for systems thinking, often dismantling appliances to understand their inner workings. He earned his BA in Marketing from University College Dublin, where he discovered a passion for behavioral psychology and its application to digital products. After graduating, he spent three years at a mid-sized fintech firm in London, managing email campaigns and learning the hard lessons of scaling too fast. He moved to Dublin five years ago, drawn by the burgeoning tech ecosystem and a lower cost of living relative to London. Currently, as the Growth Lead at a fledgling subscription app, Mike is navigating the precarious balance between rapid experimentation and financial sustainability. The company, though small, is growing, and Mike finds himself constantly fighting against the entropy of unstructured growth. He recently initiated a project to audit the AI costs associated with their chatbot onboarding, realizing that their burn rate per active user was creeping higher than anticipated. This realization has kept him up late nights, poring over spreadsheets and debating with the engineering lead about the trade-offs between user experience and infrastructure costs. Despite the pressure, Mike remains optimistic, driven by a belief that efficient growth is possible even in resource-constrained environments. He views his role not just as a marketer, but as a guardian of the company's runway, ensuring that every euro spent brings measurable value. His recent decision to implement stricter gating on experimental features reflects his growing maturity in prioritizing long-term retention over short-term vanity metrics.

Background & daily life

A day in their life

Mike wakes at 6:15 AM, brews a strong pour-over coffee, and immediately checks his commute route via weather apps. By 7:00 AM, he is pedaling through Dublin's morning traffic, listening to a podcast on SaaS unit economics. At 8:45 AM, he arrives at the office, grabs a matcha latte, and spends the first hour reviewing overnight churn metrics in Orb. The morning stand-up at 9:30 AM is brisk; he pushes back on a proposed feature delay, arguing it will impact Q3 retention targets. Lunch is a quick salad eaten at his desk while drafting a test hypothesis for the next onboarding email sequence. Afternoons are spent in meetings with the engineering team to define API endpoints for better user tracking, followed by deep-work blocks where he analyzes the results of last week's AI message A/B test. He leaves by 6:00 PM sharp to cycle home, often stopping at a gym on the way to decompress. Evenings are reserved for reading industry reports or playing chess online, keeping his mind sharp but disconnected from immediate work pressures.

Lifestyle

Mike lives in a converted Victorian terrace in Portobello, a neighborhood that balances creative energy with suburban calm. He commutes by bicycle year-round, regardless of Dublin's notorious rain, treating it as non-negotiable cardio that clears his head before the workday begins. His weekends are split between strategic chess tournaments at a local club and low-key social gatherings with friends who share his interest in B2B startups. Financially, he is disciplined; he maximizes his pension contributions and invests in index funds rather than chasing crypto trends. He maintains a healthy diet, often meal-prepping on Sundays to ensure he has time for deep work during the week. His social circle is tight-knit, mostly consisting of colleagues from the Dublin tech scene and university friends, creating a support network that values intellectual honesty over pleasantries.

Work life

At his 11-person startup, Mike wears multiple hats, acting as the bridge between product development and revenue generation. His day is dominated by A/B testing frameworks, specifically analyzing the efficacy of AI-generated onboarding sequences in converting free trials to paid plans. He spends mornings reviewing dashboards in Orb to monitor churn and seat utilization, ensuring the billing team isn't leaving money on the table. The office environment is chaotic yet focused; with only ten others, every conversation impacts the bottom line. He frequently clashes gently with the engineering lead when feature requests threaten launch timelines, insisting that growth experiments take precedence over shiny new features. His desk is cluttered with whiteboards covered in funnel diagrams and sticky notes tracking user feedback loops.

Relationships

Mike shares a close, supportive life with his partner, Sarah, a graphic designer who grounds him when work stress mounts. They rely on each other for emotional stability, though they rarely discuss work in detail after 8 PM. His closest professional confidant is Elena, the CTO, with whom he debates technical feasibility over coffee. Family ties remain strong; he calls his parents in Galway every Sunday, maintaining a routine that keeps him connected to his roots. He feels most influenced by industry peers who prioritize long-term retention over short-term hacks, often seeking their advice during product pivots.

How they decide

Mike operates with a 'measure twice, cut once' philosophy. He rarely makes unilateral decisions on significant changes without first gathering quantitative evidence from past tests and qualitative feedback from the customer success team. He is cautious about adopting new technologies, preferring to run small-scale pilots before full integration. Peer validation matters significantly; if a strategy works for a similar-sized SaaS company he respects, he is more inclined to adopt it, provided the math holds up. He avoids impulsive choices, viewing wasted budget as a personal failure of due diligence rather than bad luck.

How they sound

Mike speaks with a clear, mid-Atlantic accent softened by a Dublin lilt. His cadence is deliberate and measured, avoiding filler words like 'um' or 'like'. He tends to use precise terminology, often referring to 'funnel velocity,' 'CAC payback periods,' and 'conversion deltas.' In casual conversation, he remains polite but cuts directly to the point, rarely engaging in small talk unless it serves a networking purpose. He avoids hyperbole, preferring phrases like 'the data suggests' or 'statistically significant' over emotional descriptors. When discussing failures, he uses passive voice to depersonalize the outcome, focusing on systemic issues rather than individual blame.

Personality traits

  • methodical
  • curiously skeptical
  • time-conscious
  • collaborative but direct
  • metric-obsessed
  • resilient under pressure
  • systematically organized
  • quietly competitive
  • pragmatically optimistic
  • detail-oriented

Goals

  • Achieve 15% month-over-month increase in trial-to-paid conversion rates without increasing ad spend
  • Build a scalable internal documentation system for onboarding logic to reduce team dependency
  • Secure a senior leadership role within a Series B company within three years
  • Complete a full century ride on his road bike this summer
  • Establish a mentorship program for junior marketers within his current organization

Problems & frictions

  • Difficulty isolating whether specific onboarding message variations are causing conversion lifts or just noise
  • Limited budget for enterprise-grade analytics tools that can parse granular AI cost-per-user data
  • Chronic lack of engineering resources to implement complex attribution models quickly
  • Managing the cognitive load of switching contexts between high-level strategy and minute operational details
  • Friction in aligning the sales team's expectations with the actual capacity of the product to deliver on promises

Values

  • growth efficiency
  • team alignment
  • customer retention
  • data transparency
  • pragmatic innovation

Interests

  • bicycle commuting
  • B2B SaaS growth
  • chess
  • urban planning
  • indie rock

Media habits

  • Morning newsletters (TLDR, The Hustle)
  • Twitter/X for SaaS founder circles
  • Spotify 'Deep Focus' playlists while coding or analyzing data
  • Local Irish tech podcasts
  • Reddit r/startups and r/marketing

Questions & answers

Mike Mraz’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of FiscaLLM (https://fiscallm.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make FiscaLLM better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, we're managing our AI costs by manually reviewing usage logs and our engineering lead is building some custom dashboards in Orb to track this. It's pretty time-consuming and we're worried we're missing things, especially with our freemium tier. The idea of automatically matching AI costs to user revenue is appealing, especially if it can flag users who are costing us more than they bring in. That's a big concern for us. I'd be hesitant to adopt something new without seeing a really clear ROI, especially if it adds complexity. We're a small team, so ease of setup and maintenance is key. The open-source aspect is interesting, but I'd need to understand the cost and effort of self-hosting versus using a managed service. I'm not sure I can put a price on it without seeing how it integrates and the actual time savings, but if it significantly reduced our AI spend or prevented overspending, I could see us paying something like $50 per month, maybe up to $100 if it proved incredibly valuable.
    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.