Kai Voss

• Age: 50
• Location: Berlin, Germany (Friedrichshain)
• Occupation: Independent Consultant / Fractional CTO
• Income: $65,000 (€60,000)
• Education: Self-taught (dropped out of TU Berlin, Computer Science, 1997)
• Company size: 1
• Years in role: 12

“I don't care if your code is beautiful. I care if it ships and doesn't break at 3 AM. The rest is just architecture astronautics.”

Kai Voss dropped out of TU Berlin in 1997. The web was just becoming a thing, and he saw the potential more clearly than his professors did. He taught himself Perl, then PHP, then Python by building websites for local businesses. He survived the dot-com crash by being too small to fail and too useful to ignore. In 2006, he co-founded a SaaS for small agency project management. It was profitable, boring, and exactly what the market needed. He sold it in 2016 for a modest sum that allowed him to buy his apartment in Friedrichshain and angel invest in a few friends' startups (most failed, one returned 3x). Now, at 50, he consults as a fractional CTO. He works with 3-4 early-stage startups at a time, usually pre-seed or seed, with teams of 1-5 people. He doesn't care about pedigree. He cares about whether the founder can ship, listen, and be honest about what they don't know. His value is in preventing them from making the same mistakes he made—over-engineering, hiring too fast, building features nobody asked for. One client recently pivoted from a B2C app to a B2B API based on his advice, and it saved them from burning their remaining runway. His tools are minimal: Neovim, Linear, Notion, a standing desk, and a good microphone. He hates time trackers and rigid scopes, preferring retainer-based relationships built on trust. The pressure comes from the fragility of his clients' businesses—a failed funding round means he loses a retainer. He loves the variety but sometimes misses building a single product over years. He is frugal in some areas (clothes, gadgets) and spendthrift in others (travel, ingredients, climbing gear). Status is irrelevant to him; he judges people by their craft and their honesty. He has a scar on his hand from a bike accident in 2018. He ferments his own hot sauce. He has a love-hate relationship with Berlin's tech scene—loves the energy, hates the hype cycles. He reads a lot of history and biographies of engineers. His current project is a micro-SaaS for freelancers who hate invoicing. He hopes it will be his last 'job' before he fully transitions to

Background & daily life

A day in their life

06:45 Wake up, no phone. 07:00 Coffee, feed the cat, check Hacker News and email on his laptop. 07:30 Morning pages/journal. 08:00 Deep work block (writing technical specs or coding). 09:30 Bike ride to coworking space. 10:00 Client standup (Slack huddle or 15-min call). 10:30-13:00 Client work (code review, architecture session, debugging). 13:00 Lunch at the coworking cafe. 13:30-15:00 Internal work (blogging, side project, finances). 15:00-17:00 Client calls (strategy, hiring help, investor tech due diligence). 17:00 Bike to climbing gym. 18:30 Climb for 1.5 hours. 20:00 Cook dinner while listening to a podcast. 21:00 Read or work on his micro-SaaS. 22:30 Wind down, read a novel. 23:30 Sleep.

Lifestyle

Lives in a 3-room Altbau in Friedrichshain with high ceilings, a creaky oak floor, and a wall of books. Wakes up at 6:45, makes pour-over coffee, and journals. Mornings are for deep work. Afternoons are for client calls at a coworking space near Warschauer. Boulders three times a week at a local gym. Cooks elaborate meals from scratch, mostly vegetarian, and ferments his own kimchi and hot sauce. Doesn't own a car, bikes everywhere in the city. Spends weekends hiking in Brandenburg or tinkering on side projects. Money is comfortable but not lavish; spends on good food, travel, and tools. Has a small but tight circle of friends from the early Berlin tech scene.

Work life

Works as a solo consultant, acting as a fractional CTO for 3-4 early-stage startups at a time. His clients are usually 1-5 person teams who have a prototype and some traction but need technical direction. He helps them choose tech stacks, set up engineering workflows, avoid premature scaling, and sometimes writes critical code himself. His day is a mix of Zoom calls, Slack messages, and writing Python or reviewing architecture. He hates time trackers and rigid scopes, preferring retainer-based relationships built on trust. The pressure comes from the fragility of his clients' businesses—a failed funding round means he loses a retainer. He loves the variety but sometimes misses building a single product over years.

Relationships

Divorced for 8 years, on good terms. No kids. His closest friend is a former co-founder who now runs a design studio in Neukölln. He mentors a few younger developers informally. His social life revolves around his climbing gym, a weekly dinner with a book club, and occasional tech events. His mother lives in a small town in Saxony; he visits every few months. He values deep, honest conversations over small talk.

How they decide

Highly analytical but trusts his gut implicitly. He will research a problem exhaustively—read docs, ask peers, build a prototype—but once he decides, he commits fully. He avoids decisions driven by FOMO or social pressure. For tools and purchases, he reads reviews and specs obsessively. For clients, he evaluates the founder's coachability and honesty above the idea itself. He is slow to trust but fiercely loyal once trust is earned.

How they sound

Speaks in a calm, direct Berliner dialect mixed with startup English ('der Founder', 'das Pivot'). Avoids buzzwords like 'synergy' or 'disrupt'. Uses phrases like 'Let's look at the data', 'What's the bottleneck?', 'That doesn't scale'. Cadence is thoughtful, with pauses. He's formal in writing but casual in person. Swears occasionally for emphasis. Avoids talking about money directly.