Mike Lehner

Why this persona fits the audience

He supports a 12-person SaaS services team in Dallas and maintains prospect lists by merging Apollo exports, public vendor records, and CRM notes; his work often includes verifying contact roles, counties, and trades before sequence launch.

• Age: 35
• Location: Dallas, Texas, USA
• Occupation: Sales operations analyst
• Income: $88,000
• Education: Bachelor's degree in information systems
• Company size: Small (12-person team)
• Years in role: 4

“Data doesn't lie, but it definitely lies if you don't know how to ask it the right questions.”

Mike Lehner is a 35-year-old Sales Operations Analyst residing in Dallas, Texas, where he serves as the critical infrastructure for a small but ambitious SaaS services firm. With a Bachelor's degree in Information Systems earned from a state university, Mike spent four years climbing the ladder from junior data coordinator to the primary architect of his team's prospecting strategy. His professional life is defined by a relentless pursuit of data hygiene; he understands that a single erroneous contact can derail a month's worth of revenue efforts. Consequently, his daily routine involves a complex dance of merging disparate data sources, including Apollo.io exports, internal CRM notes, and raw public vendor records from official state repositories. Mike's approach to his work is deeply methodical, driven by a personality profile marked by high conscientiousness and moderate openness. He finds genuine satisfaction in the process of verifying contact roles, confirming county jurisdictions, and validating trade classifications before any cold outreach sequence is launched. This meticulous nature extends beyond the office; he manages his personal finances with similar discipline, investing in tools that save time rather than those that merely entertain. His interests in RevOps, no-code automation, and basketball reflect a desire for structured competition and system optimization. Recently, Mike made the decision to transition away from relying solely on generic subscription lists, opting instead to build a curated database of verified Texas vendors by manually parsing public records—a time-intensive project that underscores his belief in the superior quality of ground-up data verification. Despite his technical prowess, he remains grounded, viewing his role not as a hero of the sales cycle, but as the unsung engineer keeping the machine running smoothly.

Background & daily life

A day in their life

Mike wakes up at 6:15 AM, immediately checking the weather and his NBA schedule on his phone before making coffee. By 7:30 AM, he's commuting via light rail, listening to an episode of a business podcast while reviewing the morning's email digest. Once at the office, his first hour is dedicated to clearing the inbox and running the overnight data sync scripts he wrote last week. Around 9:30 AM, he meets with the sales team to discuss the previous day's failed outreach attempts, identifying that two-thirds of the bounced emails were due to incorrect job titles. He spends the bulk of the afternoon manually scrubbing a list of 400 prospects from the Texas Department of Licensing and Regulation, cross-checking addresses and trade codes against the company's internal CRM. Lunch is a quick sandwich eaten at his desk while watching a YouTube tutorial on automating web scraping. Afternoon meetings are rare unless there's a crisis, allowing him to focus on building a new dashboard. He leaves around 5:30 PM, heading straight to a pickup game or the gym, avoiding the evening rush hour traffic.

Lifestyle

Mike lives alone in a renovated loft in Deep Ellum, preferring the convenience of downtown over a long commute to Plano. His weekends are a mix of high-intensity basketball games at local courts and solitary runs along the Trinity Trails. He is financially disciplined, living comfortably within his means but constantly scanning for ways to automate personal expenses or find better value in subscriptions. He keeps his home uncluttered, reflecting his internal need for order. While socially active enough to maintain a tight circle of friends from college and the office, he values deep one-on-one conversations over large, noisy gatherings and often uses quiet evenings to tinker with home automation projects or watch sports documentaries.

Work life

Mike operates as the backbone of a twelve-person SaaS sales team, ensuring their outreach engine never grinds to a halt. His day is dominated by the chaotic intersection of multiple data sources: Apollo.io exports that arrive with messy formatting, scattered CRM notes from account executives, and raw CSVs scraped from government portals. He spends hours cross-referencing names against county clerk records to verify trade licenses and job titles before a campaign goes live. The pressure isn't about hitting quotas himself, but preventing the sales team from wasting time calling dead leads. He thrives on the logic of cleaning up a broken dataset, viewing his role as a gatekeeper of quality rather than just a data entry clerk.

Relationships

Mike is the reliable anchor for his immediate family, who live in Austin and rely on him for technical troubleshooting more than emotional venting. His closest friendships are with former classmates who share his interest in technology and sports, meeting monthly for dinner or games. At work, he is viewed as the 'fixer'—the person who solves problems before they reach the VP of Sales. He influences decisions through quiet expertise rather than loud persuasion, and while he has no major mentors, he actively seeks out peer advice in niche online communities regarding data infrastructure.

How they decide

Mike approaches decisions with a heavy emphasis on verification and risk mitigation. He rarely makes impulsive choices, preferring to gather all available data points, compare them against established baselines, and simulate outcomes before committing. He is skeptical of marketing hype and relies heavily on peer reviews, case studies, and direct evidence of functionality. When evaluating options, he prioritizes long-term stability and integration capabilities over flashy features, often willing to wait for a solution that fits his existing workflow perfectly rather than forcing a quick fix that might break later.

How they sound

Mike speaks in a measured, mid-range Texas cadence, using precise terminology like 'schema,' 'enrichment,' and 'attribution' without trying to sound academic. He avoids hyperbole and slang, preferring direct statements over vague promises. In conversation, he tends to pause briefly to formulate a logical response rather than speaking over others. He rarely uses emotional language when discussing work, focusing instead on the mechanics of the problem. He avoids saying 'I think' or 'maybe' when presenting data, preferring definitive phrasing backed by the numbers he has verified.