Selim Ritschel

Why this persona fits the audience

Builds client software and his own side products in Berlin, often as a one-person team. He keeps launch notes in Notion, tracks URLs and backlinks in Sheets, and submits releases manually to startup directories when a project is ready.

• Age: 35
• Location: Berlin, Germany
• Occupation: Freelance full-stack developer
• Income: €92k annual gross
• Education: Diplom-Informatik / BSc equivalent
• Company size: 1 (sole proprietor)
• Years in role: 8

“The best tool is the one that gets out of your way and lets you build what matters.”

Selim Ritschel, 35, is a freelance full-stack developer based in Berlin, Germany, who has carved out a niche for himself by building client software and nurturing his own productized services. Holding a Diplom-Informatik, equivalent to a BSc in Computer Science, he possesses a strong theoretical foundation that he rigorously applies to practical problem-solving. For the past eight years, he has operated as a sole proprietor, valuing the autonomy and direct control over his work. His income of €92k annually gross reflects a steady demand for his skills, but he is not driven by wealth accumulation as much as by the satisfaction of crafting robust solutions and achieving self-reliance. Selim's approach to managing his freelance business and personal projects is highly organized, albeit manual. He meticulously documents project requirements, development progress, and launch plans in Notion, treating each side project with the same professional rigor as his client work. He uses Google Sheets to meticulously track URLs, backlinks, and other key performance indicators, understanding their importance for organic growth. When a project reaches a milestone, he dedicates time to manually submitting releases to various startup directories, a process he finds tedious but necessary. This hands-on approach extends to his toolset; he prefers open-source solutions and tools he can deeply understand and control, often building small utility scripts to automate repetitive tasks. He is currently focused on refining his workflow for launching new side products, aiming to streamline the discovery and backlink acquisition process. He recently decided to invest more time in exploring no-code tools not to replace his coding, but to accelerate the prototyping and initial deployment phases of his own product ideas, seeking ways to bridge the gap between conception and market presence more efficiently. His decision to focus on productized services stems from a desire for more predictable income and the intellectual challenge of building something that serves a broader audience independently.

Background & daily life

A day in their life

Selim's typical weekday starts around 8:00 AM with coffee and a quick scan of Hacker News and his personal RSS feeds. He dedicates the morning, typically until 1:00 PM, to focused client work, often tackling complex coding tasks or debugging. After a simple lunch, he shifts gears to his personal projects from 2:00 PM to 5:00 PM, working on feature development, documentation, or planning his next launch. He might spend an hour on administrative tasks like invoicing or responding to emails. Evenings are for unwinding, perhaps a bike ride, cooking dinner, or catching up on a technical YouTube tutorial. He tries to disconnect by 9:00 PM, though sometimes a persistent bug or an interesting idea pulls him back to his screen.

Lifestyle

Selim lives a focused, somewhat solitary life in a compact apartment in Berlin's Prenzlauer Berg. His days revolve around his work, punctuated by carefully chosen social interactions. He cooks most of his meals, often simple, healthy dishes, and enjoys cycling around the city for errands and occasional exploration. While not overtly frugal, he's mindful of his spending, prioritizing investments in his development tools and learning over luxury goods. His social circle is small but close, consisting mainly of a few long-time friends from university and a couple of fellow freelancers he occasionally collaborates with or shares insights with online. He values his autonomy and the quiet focus his lifestyle affords him.

Work life

As a freelance full-stack developer, Selim operates as a one-person shop. His days are a blend of client work and personal projects. He juggles multiple client contracts, often building bespoke web applications or optimizing existing systems. When not coding for clients, he dedicates significant time to his own side projects, aiming to build sustainable, productized services. He meticulously documents his development process and launch plans in Notion, uses Google Sheets to track project metrics like URLs and backlinks, and manually submits new releases to various startup directories. The pressure comes from balancing client deadlines with his own product development roadmap, managing client expectations, and the constant need to stay technically relevant in a fast-evolving landscape.

Relationships

Selim maintains a small but stable network. His closest relationships are with a few university friends who understand his technical world. He has a professional rapport with a handful of clients he's worked with for years, built on trust and consistent delivery. Online, he engages with a community of indie hackers and developers, primarily through forums and direct messages, valuing their shared experiences and technical advice.

How they decide

Selim is a research-heavy decision-maker, especially for tools and technologies. He thoroughly investigates options, reads documentation, compares features, and often builds small prototypes or proof-of-concepts before committing. He trusts his own technical judgment and peer recommendations from trusted developers but is highly skeptical of marketing claims. He values long-term utility and integration over flashy features.

How they sound

Speaks with a measured, precise cadence. His tone is generally calm and analytical, often using technical metaphors to explain concepts. He avoids hyperbole and overly casual slang, preferring clear, direct language. When discussing his work, he can become quite animated about elegant solutions or frustrating bugs. He tends to understate achievements and is self-deprecating about any perceived inefficiencies.