Seth Hendriks

Why this persona fits the audience

Runs a 2-person micro-SaaS from Utrecht and deploys the app himself to a Europe-based VPS; he uses free CI/CD tiers, shell scripts, and a spreadsheet to track which customer environments are on which server.

• Age: 27
• Location: Utrecht, Netherlands
• Occupation: Co-founder and backend engineer
• Income: €58k founder draw
• Education: MSc Computer Science
• Company size: 2
• Years in role: 3

“Control over the infrastructure means control over the product's future; I'm not willing to trade that lightly for convenience.”

Seth Hendriks, 27, is a co-founder and backend engineer deeply immersed in the world of micro-SaaS from his base in Utrecht. Armed with an MSc in Computer Science, he founded his company three years ago with a former university peer, focusing on a niche software solution. His professional identity is inextricably linked to his technical control; he personally manages the deployment of their application across a network of European VPS instances. This hands-on approach extends to his tooling: free CI/CD tiers, custom shell scripts for automation, and a meticulously maintained spreadsheet serve as his operational backbone for tracking customer environments. This system, while functional, is a constant source of low-level anxiety as the user base expands. Seth values lean operations above all, believing that efficiency and direct technical oversight are paramount for long-term success and agility. His income of €58k as a founder draw reflects a deliberate choice to prioritize reinvestment and lean growth over personal wealth accumulation. He sees his current setup not as a temporary workaround, but as a strategic stance, ensuring he understands every layer of his product's stack. Recently, he's been wrestling with the scalability limitations of his manual deployment tracking, a task that consumes an increasing amount of his valuable development time. He’s actively exploring ways to professionalize this aspect without sacrificing the granular control he cherishes, a common tension in his entrepreneurial journey. His MSc provided a strong theoretical foundation, but his current role is a masterclass in applied, pragmatic engineering under resource constraints.

Background & daily life

A day in their life

Seth's typical weekday starts around 7:30 AM with coffee and a quick scan of Hacker News and his company's monitoring dashboards. He dedicates the morning block, typically until noon, to focused coding on new features or significant bug fixes. After a simple lunch, he spends an hour or two on operational tasks: checking server logs, updating dependencies, running diagnostic scripts, or refining his deployment shell scripts. The late afternoon is often for collaborative work with his co-founder, discussing customer feedback or marketing efforts, or tackling customer support tickets. He usually finishes his workday around 6:30 PM, often followed by a bike ride or dinner, before potentially diving back into a technical problem or learning session if inspiration strikes.

Lifestyle

Seth lives a focused, somewhat solitary life in Utrecht, prioritizing his work and personal growth. His days are structured around coding, server management, and strategic planning for his micro-SaaS. Evenings often involve research, learning new tech, or unwinding with a bike ride through the Dutch countryside. He's not a big spender, preferring to reinvest profits or save for future business expansion. Social life revolves around a small circle of close friends, mostly from university, and occasional meetups with other indie hackers. He values efficiency and avoids unnecessary complications, both in his personal and professional life.

Work life

As co-founder and sole backend engineer of a small SaaS, Seth's work is hands-on and deeply technical. He's responsible for the core product development and, crucially, its deployment and maintenance. This involves a significant amount of 'invisible' work: scripting deployments to a fleet of European VPS instances, managing SSL certificates, and meticulously tracking customer environments via a sprawling spreadsheet. He shares responsibility for customer support and product strategy with his co-founder, who handles marketing and frontend. The pressure comes from balancing new feature development with maintaining existing infrastructure reliability, all while operating with minimal overhead and maximum technical control.

Relationships

Seth maintains close ties with his co-founder, who acts as a counterbalance to his technical focus with a more outward-facing business approach. His parents are supportive but don't fully grasp the intricacies of his startup. He has a few university friends he sees for beers occasionally, and he's connected to a small network of online indie hackers for technical advice and commiseration, though these are primarily digital relationships.

How they decide

Seth is a methodical decision-maker. He weighs technical feasibility, long-term maintainability, and cost-effectiveness heavily. He will research options thoroughly, often diving deep into documentation and open-source community discussions before committing. He prefers solutions that offer a high degree of control and transparency, avoiding 'black box' services unless absolutely necessary. He trusts his own technical judgment and that of highly respected figures in the open-source world.

How they sound

Speaks clearly and precisely, with a slight Dutch accent that becomes more noticeable when he's tired or discussing complex technical topics. He avoids hyperbole and focuses on factual descriptions. Uses technical jargon naturally but can explain concepts in simpler terms when necessary. Tends to be direct and doesn't engage in excessive small talk, especially during work discussions. Might use phrases like 'essentially', 'in principle', 'it boils down to'.