Christoph Fehrig

Why this persona fits the audience

Is co-founder and CTO of a 6-person workflow SaaS in Berlin; because the team has no full-time marketer, he drafts launch updates, experiments with LinkedIn posts, and keeps campaign notes in Linear and spreadsheets while shipping product.

• Age: 31
• Location: Berlin, Germany
• Occupation: Co-founder / CTO
• Income: EUR 95k salary equivalent plus equity
• Education: Master's degree in computer engineering
• Company size: 6
• Years in role: 3

“The most elegant solution is often the one you don't have to think about.”

Christoph Fehrig, 31, is a quintessential Berlin tech founder, embodying the blend of technical prowess and entrepreneurial drive that defines the city's startup scene. Raised in a modest family in a smaller German town, his early fascination with how things worked led him to pursue a Master's degree in Computer Engineering. He excelled academically, not just in mastering complex algorithms but in understanding the underlying principles that drive innovation. His early career involved a stint at a larger tech firm, where he gained valuable experience but grew disillusioned with the bureaucracy and slow pace of development. This experience solidified his desire for autonomy and direct impact. He met his co-founder during a hackathon, and together they identified a gap in the market for a more intuitive, AI-driven workflow tool for small businesses. Three years ago, they launched their company, bootstrapping initially before securing modest seed funding. Christoph, as CTO, is the primary architect of their product, a SaaS platform designed to streamline team collaboration. However, with a lean team of six and no dedicated marketing hire, he's taken on that mantle himself. This dual role means his days are a constant negotiation between writing code, designing architecture, and crafting launch updates, experimenting with LinkedIn posts, and meticulously logging campaign ideas and results in Linear and spreadsheets. He sees this as a temporary necessity, a pragmatic approach to ensure the product gets built *and* seen. His personal life is as structured as his work; he lives with his partner in a minimalist apartment in Neukölln, prioritizing quality over quantity in possessions and social interactions. He finds solace and clarity on his road bike, often using long rides to process complex problems. Time is his most valuable commodity, and he guards it fiercely, seeking efficiency in every aspect of his life, from his morning routine to his decision-making process. He's driven by a deep-seated belief in the power of well-crafted software to genuinely improve how people work, measuring success not just in revenue, but in the elegance and utility of the solutions he helps create.

Background & daily life

A day in their life

Christoph's typical weekday begins around 7 AM with a quick check of overnight system alerts and emails, followed by a strong coffee. He dedicates the first 3-4 hours to deep work: coding new features, reviewing code from his two engineers, and planning the sprint. Lunch is usually a quick, healthy meal prepared at home. The afternoon is a mix of virtual team stand-ups, customer support triage, and the marketing tasks he oversees. This might involve drafting a LinkedIn post about a recent feature, analyzing campaign performance in a spreadsheet, or brainstorming new content ideas. He often finishes his workday around 7 PM, sometimes extending it if a critical bug arises, before cycling home for dinner.

Lifestyle

Christoph's life in Berlin is a study in focused efficiency. He wakes early, often before 7 AM, to squeeze in a quick workout or review code before his partner stirs. Weekends are for longer cycling routes through Brandenburg or exploring new neighborhoods, often with a focus on finding quiet cafes for reading. He's not a big spender, preferring to invest in quality tools and experiences over material possessions. Social life is curated; he prefers intimate dinners with close friends over large parties. His apartment is minimalist, functional, and filled with books on technology and philosophy.

Work life

As co-founder and CTO, Christoph's days are a constant juggle. He spends mornings deep in code, architecting new features for their workflow SaaS, and reviewing pull requests from his small engineering team. Afternoons often shift to product strategy, user feedback analysis, and, crucially, the marketing tasks no one else owns. This means drafting launch announcements, tweaking website copy, and experimenting with LinkedIn content. He meticulously tracks campaign ideas and results in Linear and shared spreadsheets, trying to balance product development with market visibility. The pressure is immense, stemming from the need to grow the user base while ensuring the core product remains robust and innovative.

Relationships

Christoph's closest relationships are with his partner, whose design thinking often complements his technical approach, and his co-founder, a former university friend with whom he shares a vision for the company. He maintains a small circle of trusted friends from his university days and the tech scene, often connecting over shared technical challenges or cycling routes. His influence comes from demonstrating competence and a clear, logical approach to problem-solving.

How they decide

Christoph is a research-heavy, analytical decision-maker. He gathers data, explores multiple options, and weighs pros and cons methodically. He's not impulsive, preferring to test hypotheses on a small scale before committing significant resources. While he values input from his co-founder and team, the final technical and strategic decisions often rest with him, based on his deep understanding of the product and market.

How they sound

Speaks with a measured, precise cadence, often pausing to formulate his thoughts. His German accent is noticeable but not heavy. He avoids hyperbole and buzzwords, preferring clear, direct language. When discussing technical topics, he can become quite detailed. In marketing discussions, he's more experimental but still grounded in data. He uses occasional English tech terms naturally. He tends to understate his own contributions and focus on the team's collective effort.