Why this persona fits the audience
He co-founded a 4-person property-management SaaS in Berlin and built the login OTP and security-alert flow in-house; API logs, sender IDs, and webhook handling are maintained with free trial credits and hand-written scripts rather than a dedicated messaging platform.
- Age: 29
- Location: Berlin, Germany
- Occupation: Co-founder / CTO
- Income: €96k
- Education: M.Sc. Software Engineering
- Company size: 4
- Years in role: 2
“I'd rather debug a system I'm proud of at 3 AM than sell out early for a 'premium' feature that becomes tech debt in a month.”
Nathan Jürgens grew up in Dortmund, where his first programming project was a CSV parser for his father's history of local soccer scores. He studied Software Engineering in Munich, then worked briefly at a Finnish gaming company—leaving after 18 months because 'the architecture was a crime scene'. His current venture, a property management SaaS, was born from frustration with the tools his partner managed as a property agent. Their tiny team operates on shoestring infrastructure, with Nathan treating each server cost as a personal challenge to optimize. His technical philosophy is 'build it twice—the first time to learn the constraints, the second to get it right'. He's currently torn between his ideal of a self-hostable system and the pragmatism of attracting subscription revenue. Recent wins include halving their SMTP costs with a custom WebSocket relay, and a loss was spending 60 hours refining a feature that customers didn't use. Financially, he's hyper-aware of every €100 spent, often deferring purchases by building his own solutions. His social life is sparse but intentional—he prefers 2-hour deep conversations with peers over surface-level networking. Status means little to him; he'd rather his tool be used than praised. His next milestone is convincing his co-founder to invest another €30k in R&D, which may require him to finally admit their homegrown SMS system can't scale further.
Background & daily life
A day in their life
Nathan's day starts at 5:45 AM with coffee and a quick code review of last night's alerts system. By 7:30, he's cycling to the co-working space where their team rents a corner desk. Morning is 'firefighting': fixing a bug in the SMS confirmation flow that's caused 3 new support tickets. He then pairs with his co-founder to review upcoming features, where they butt heads over whether to add 'tenant portal self-service' (she says yes, he says not until they fix the backend first). Lunch is a tuna wrap at his standing desk while reading about feature flags in Firebase. Afternoon is deep work—rewriting the OTP retry logic in Go, which he hopes will reduce failed attempts. By 7 PM, he's at a café where Marina joins him, and they dissect why his team's self-serve signups plateaued. He orders a flat white, refuels, and cycles home to debug the automated sender rotation script until midnight.
Lifestyle
Nathan rents a small but well-organized apartment in Friedrichshain, where he brews pour-over coffee every morning using a V60 and freshly roasted beans. He cycles to work year-round, even in Berlin's wet winters, and keeps a minimalist wardrobe of functional outdoor wear. He eats out rarely, preferring meal prep—his apartment is always stocked with mason jars of overnight oats. Socially, he keeps a close circle of fellow indie hackers, often meeting for 'coffee hackathons' at local third-wave cafés. He runs 10Ks on weekends to clear his head, though he dislikes structured gym routines. Financially, he lives modestly—his biggest splurges are on a new MacBook every two years and a standing desk upgrade. Health-wise, he's careful but doesn't track metrics; if something hurts, he bikes it off (which sometimes backfires).
Work life
As the only technical team member at their property management SaaS, Nathan handles everything from backend to DevOps to customer support escalations. His current obsession is stabilizing their SMS alerts system, which currently runs on a patchwork of Twilio credits, Zoho Creator webhooks, and his own Bash scripts. He spends mornings debugging cryptic API logs, afternoons in coding sprints, and evenings reviewing infrastructure costs. His biggest frustration is the team's outreach features—currently, missed alerts during high tenant turnover cost them €500/month in penalties. He recently automated sender ID rotation after a regulator complaint, but the fix was clunky. His founder partner handles sales, so Nathan is hyper-focused on scaling what he can alone. He avoids Slack (prefers Matrix) and keeps documentation in Markdown files in a private repo.
Relationships
Nathan's parents, both teachers in Dortmund, are proud but don't understand his career. His closest friend is Marina, a product designer at a Berlin fintech, who he debates with about 'scaling ethics'. He's in a long-distance relationship with a data scientist in Amsterdam—weekend train visits are their lifeline. His biggest technical mentor is an anonymized author of a tiny but influential email newsletter on cloud infrastructure. He deliberately avoids most ex-colleagues from his corporate internships, finding their chatter about pay raises and promotions exhausting.
How they decide
Research-lite pragmatist. He won't buy a tool until he's debugged 80% of its promised features himself, then grudgingly pays for the 20% that would take forever. Prefers to patch around problems before accepting that a dedicated solution is better. Values maintainability over trends. When stumped, he'll cold-email a small vendor for an hour of their time—then spend weeks analyzing their reply.
How they sound
Speaks in measured, sometimes sarcastic German-accented English with heavy idiomatic English. Uses dry humor as a social buffer. Prefers sentence fragments in technical discussions ('No, really, it's the backpressure'). Avoided phrases: 'synergies', 'disrupt', 'thought leadership'. When frustrated, his German accent thickens. For billing arguments, he defaults to '€20 is €20,000 at scale'. Avoids small talk—if you're not talking about code, beer, or cycling, he'll return to his laptop.
Personality traits
- Pragmatic yet idealistic
- Hates premature optimization
- Quick to prototype, slow to refactor
- Prefers to debug before buying tools
- Obsessive about API design
- Attention to detail but impatient with bureaucracy
- Self-deprecating in public, exacting privately
- Loyal to open-source
- Dislikes jargon
- Enjoys teaching others
Goals
- Build a self-hostable version of their SaaS to attract enterprise clients
- Improve SMS delivery reliability without outsourcing completely
- Learn Rust to rewrite their critical auth system
- Save €15k to 'buy' himself 3 months of unpaid R&D time
Problems & frictions
- SMS alerts sometimes fail silently due to Twilio's free tier limitations
- No proper logging for failed delivery attempts complicates support
- Team growth means he has to spend 20% of his time on management
- Charging more for features feels like a betrayal of their 'simple tool' ethos
- His co-founder wants to hire a junior dev, but Nathan thinks it's too early
Values
- technical independence
- speed of iteration
- clean architecture
- self-reliance
- minimalism
Interests
- indie software
- cycling
- coffee brewing
- startup podcasts
- DIY server admin
Media habits
- Listens to 'Screaming in the Cloud' podcast
- Reads Hacker News in the mornings
- Occasionally reads 'The Information' for tech biz