Ira Kuhlman

Why this persona fits the audience

Runs a 3-person revenue operations function for a 60-person cybersecurity firm in Dublin; maintains lead routing, webinar follow-up, and renewal reminders in Make.com connected to Salesforce, Intercom, and Google Sheets.

• Age: 33
• Location: Dublin, Ireland
• Occupation: RevOps Manager
• Income: €72k
• Education: Bachelor's degree in information systems
• Company size: 60 employees
• Years in role: 4

“If you can't measure it, automate it, and verify it, it doesn't exist in my world.”

Ira Kuhlman is a 33-year-old Revenue Operations Manager based in Dublin, Ireland, currently navigating the complexities of scaling a mid-sized cybersecurity firm. Holding a Bachelor's degree in Information Systems, Ira has spent the last decade bridging the gap between raw data and actionable business strategy. Currently leading a three-person RevOps function, he serves as the invisible engine behind the company's €15 million annual recurring revenue, ensuring that every lead captured from a webinar finds its way into Salesforce without human error. His expertise lies in the intricate architecture of Make.com, where he has constructed dozens of robust workflows connecting disparate systems like Intercom, Google Sheets, and their core CRM. Despite his technical prowess, Ira operates with a distinct sense of isolation; he is the only person in the organization who truly understands the full scope of their data ecosystem. This responsibility weighs heavily on him, driving his high conscientiousness score. He is constantly balancing the need for speed against the necessity of precision, often working late to debug a failing integration just as the sales team prepares for a major product launch. His income of €72k reflects his seniority and specialized skill set, though he remains acutely aware of the market volatility in the tech sector. In his personal life, Ira is a man of routine and discipline. He channels his need for control into cycling and maintaining a meticulously organized home. He is skeptical of flashy solutions that promise miracles without substance, preferring the slow, steady grind of building reliable systems. Recently, he made the difficult decision to reject a lucrative offer from a larger enterprise to stay in Dublin, citing a desire for greater autonomy and a better work-life balance. His recent focus has shifted toward automating manual reporting tasks to reclaim time for strategic planning, reflecting his core value of measurable outcomes. He is not looking for a magic bullet; he is looking for a partner who can handle the messy reality of real-world data.

Background & daily life

A day in their life

Ira wakes up at 6:30 AM, immediately checking his phone for any critical alerts from his Make.com monitors. After a quick jog and a black coffee, he heads to his home office, where he spends the first hour reviewing the previous day's lead flow metrics. By 9:00 AM, he's deep in code, refactoring a webhook scenario that keeps timing out during the morning sales rush. Lunch is usually a quick sandwich eaten while reading a whitepaper on data privacy regulations. The afternoon is reserved for meetings: a sync with the sales ops team to discuss pipeline bottlenecks, followed by a deep-dive session with a developer friend about optimizing database queries. Around 4:30 PM, he performs a final audit of the day's integrations, ensuring no data was lost or duplicated. He logs off by 6:00 PM to spend time with his partner, leaving his laptop closed unless a critical system failure occurs.

Lifestyle

Ira lives in a modern, slightly noisy apartment in the Liberties district of Dublin, sharing rent with his partner, Sarah, a graphic designer. Their weekends are split between active recovery—long road bike rides along the River Liffey or into the Wicklow mountains—and quiet evenings at home tinkering with smart home setups. He is financially disciplined, prioritizing high-quality work gear over luxury cars, and maintains a modest but healthy savings rate. Socially, he prefers deep conversations with a small circle of close friends rather than large networking events, often meeting for craft beers where the talk drifts toward tech ethics or cycling routes rather than industry gossip.

Work life

As the sole architect of the RevOps stack for a fast-growing cybersecurity firm, Ira manages the delicate balance between rapid sales growth and operational stability. His day is dominated by maintaining complex Make.com scenarios that route leads from webinars directly into Salesforce while triggering personalized Intercom messages. He spends significant time debugging failed webhooks and ensuring data hygiene across three different platforms. With only two direct reports, he operates with high autonomy but carries the weight of the entire revenue engine; a single broken automation can stall a quarter's worth of deals. He works remotely most days but insists on being in the office on Tuesdays and Thursdays to sync with the sales leadership team.

Relationships

Ira is married to Sarah, who acts as his primary sounding board for stress management. His closest professional influence is the VP of Sales, whom he respects but often has to push back against regarding unrealistic timelines. He maintains a loose network of fellow RevOps professionals on LinkedIn, exchanging tips on Make.com modules, but avoids formal communities. He is not deeply embedded in the local tech scene socially, preferring digital connections for career advice.

How they decide

Ira is a cautious, research-heavy decision-maker who relies heavily on logic and peer validation. He rarely adopts new tools based on marketing hype; instead, he builds small-scale proof-of-concept environments to test functionality, latency, and security compliance before considering any long-term commitment. He values transparency in pricing and technical specifications above all else, often spending hours reading documentation forums and user reviews.

How they sound

Ira speaks with a calm, measured cadence, typical of someone used to explaining complex technical concepts to non-technical stakeholders. He uses precise terminology like 'latency,' 'payload,' and 'attribution' casually. He avoids hyperbole and marketing speak, preferring factual statements. He tends to pause before answering questions to ensure accuracy, rarely interrupting others. His tone is professional yet approachable, never condescending but firmly grounded in logic.