Szczepan Aleksandrowicz

Why this persona fits the audience

He co-runs a three-person software consultancy in Warsaw and reviews site visits, contact conversions, and campaign referrals himself. He has used GA4 for years, occasionally cross-checks with server logs, and tends to compare tools before standardizing a reporting setup.

• Age: 45
• Location: Warsaw, Poland
• Occupation: Technical Co-founder
• Income: €78k/year
• Education: Master's degree
• Company size: 3 people (including himself)
• Years in role: 12 years as a developer, 6 years as co-founder

“If I cannot verify the number myself, it does not exist.”

Szczepan Aleksandrowicz is a 45-year-old Technical Co-founder based in Warsaw, Poland, operating a lean three-person software consultancy. Holding a Master's degree in Computer Science, he has spent over a decade navigating the complexities of enterprise software development before establishing his own firm six years ago. His career trajectory is defined by a relentless pursuit of technical accuracy and a deep skepticism toward opaque data systems. Currently, he manages a diverse portfolio of clients ranging from fintech startups to public sector entities, all requiring robust, GDPR-compliant analytics solutions. Szczepan's daily reality is a blend of high-level architectural oversight and granular, hands-on debugging. Unlike many founders who delegate operational details, he personally reviews site visits, contact conversions, and campaign referrals for every client. He has utilized Google Analytics 4 for years, yet remains perpetually uneasy with its black-box nature. Consequently, he frequently cross-checks platform data with raw server logs, a labor-intensive practice that ensures no metric is accepted on faith alone. This habit of comparing tools before standardizing a reporting setup has become his signature, driving a workflow that prioritizes data integrity over speed. Financially, he earns approximately €78,000 annually, a sum he manages with caution, prioritizing savings and reinvestment into the company's infrastructure over personal luxuries. His living situation in Mokotów reflects his personality: functional, uncluttered, and efficient. While he enjoys the company of his wife and a select few friends, his social circle is small, reflecting his introverted nature and high conscientiousness. He values independence above all else, often resisting industry trends that lack empirical backing. Recent decisions have seen him investing time in exploring self-hosted analytics alternatives, driven by a desire to reduce dependency on major tech giants. Despite the pressure of running a business, he maintains a disciplined routine, balancing his professional rigors with a commitment to physical health and continuous learning. For Szczepan, technology is not just a tool for profit but a system of truth that must be understood, controlled, and respected.

Background & daily life

A day in their life

Szczepan wakes at 5:30 AM, immediately heading out for a forty-minute run along the Vistula embankment, regardless of the weather. Back home, he prepares black coffee and checks his email briefly before diving into work at 7:15 AM. His morning is dedicated to deep coding and reviewing server logs, a time when his mind is sharpest. By 10:00 AM, he joins a brief stand-up with his two co-founders to align on client deliverables, often challenging their assumptions about project scope. Lunch is a quick, healthy meal eaten while reading a technical article. Afternoons are reserved for client calls and manual data verification, where he meticulously compares GA4 dashboards against raw log files to spot anomalies. He avoids meetings after 4:00 PM to preserve focus time. At 6:30 PM, he closes his laptop, exercises again or cycles to a local park, and returns home for dinner. Evenings are for reading, personal server maintenance, or watching documentaries, ensuring a clear boundary between professional obligations and personal rest.

Lifestyle

Szczepan resides in a functional, sparsely decorated apartment in Mokotów, favoring utility over interior design trends. His mornings begin at 5:30 AM with a run along the Vistula River, a non-negotiable ritual that grounds him before the workday. He maintains a strict diet of home-cooked meals, avoiding processed foods, and tracks his macronutrients with a simple spreadsheet. Financially, he is conservative, prioritizing savings and debt reduction over luxury purchases or status symbols. Socially, he is selective, preferring deep one-on-one conversations or small gatherings with close friends over large parties. He values his solitude and uses evenings for reading technical literature or tinkering with personal servers, often staying up late to optimize code or configure new hardware.

Work life

As a co-founder of a boutique software consultancy in Warsaw, Szczepan wears multiple hats, though his primary focus remains on architecture and quality assurance. The team consists of only two other developers, necessitating a flat hierarchy where everyone contributes to client-facing strategy. He personally audits every analytics report generated for clients, refusing to delegate this task to avoid blind spots. His daily workflow involves heavy reliance on terminal-based tools, custom bash scripts for log parsing, and a rigorous comparison of third-party services against internal benchmarks. He spends significant time cross-referencing Google Analytics 4 data with raw Nginx logs to ensure no discrepancies exist, a habit born from past frustrations with inaccurate reporting. Pressure stems from tight deadlines and the expectation of flawless delivery, requiring him to balance client demands with his own standards for technical rigor.

Relationships

Szczepan is married to a graphic designer named Katarzyna, whom he met in university; they share a quiet domestic life focused on mutual professional respect. He has a small circle of four trusted friends, mostly fellow engineers, with whom he discusses technology and politics over beer on weekends. He is not deeply embedded in community organizations but volunteers occasionally as a mentor for young developers at local meetups. His decision-making is rarely influenced by peers, except when validating technical assumptions, and he relies heavily on his own experience and direct testing rather than industry hype.

How they decide

His approach to decisions is intensely methodical and research-heavy. He operates on a 'measure twice, cut once' philosophy, gathering extensive data points before committing to any change. He avoids impulsive choices and prefers to create detailed comparison matrices, often running parallel tests for weeks before standardizing a tool. Peer influence is minimal unless the peer is a recognized technical authority, and even then, he demands empirical evidence. He values independence in his process, often working through problems in isolation before seeking external validation.

How they sound

Szczepan speaks with a measured, precise cadence, avoiding filler words and colloquialisms. His tone is neutral and factual, leaning towards formal Polish syntax even in casual conversation. He rarely uses hyperbole or emotional language, preferring terms like 'statistically significant' or 'verified' over 'great' or 'amazing'. He avoids marketing jargon, buzzwords, and vague promises, often interrupting to ask for specific definitions or data sources. His speech reflects a background in engineering, prioritizing clarity and logical flow over persuasion or charm.