Why this persona fits the audience
He is building an industrial software startup that estimates maintenance work for machine shops. He is the sole human team member and personally manages product development, customer calls, and support.
- Age: 36
- Location: Munich, Germany
- Occupation: Solo founder; former industrial engineer
- Income: €150k/year
- Education: Diploma in Mechanical Engineering
- Company size: 1 (Sole proprietorship)
- Years in role: 2 years
“A machine does not care about your feelings; it only cares about the tolerances you define.”
Hendrik Soller is a 36-year-old solo founder based in Munich, Germany, whose career trajectory shifted from a stable role as an industrial engineer to the precarious autonomy of bootstrapping a specialized B2B software company. Holding a Diploma in Mechanical Engineering, Hendrik spent seven years working within the German automotive supply chain, where he observed the chronic inefficiencies in how machine shops estimated maintenance and repair times. Frustrated by the reliance on heuristic guesses and outdated spreadsheets, he identified a gap for a deterministic, physics-based estimation tool. In 2022, he resigned from his position, liquidated a portion of his savings, and established his startup as a sole proprietorship. Today, Hendrik operates as the entire organization. He writes the core Rust backend, designs the user interface, manages cloud infrastructure, and handles all customer acquisition and support. This singular responsibility allows him to maintain an unparalleled level of engineering rigor, ensuring that every line of code serves a specific functional purpose. However, the isolation presents significant challenges; he lacks the immediate feedback loops of a larger team, forcing him to rely on rigorous self-discipline and external data validation. Recently, he made the strategic decision to reject a term sheet from a local venture capital firm, prioritizing long-term control and the preservation of his product's technical integrity over rapid scaling. He lives a life defined by boundaries and focus, channeling his energy into the machine shop industry he knows intimately. His financial independence is tied directly to the reliability of his software, creating a personal stake in every calculation his customers perform. While others might seek the glamour of a startup ecosystem, Hendrik prefers the quiet satisfaction of solving hard problems with elegant solutions, believing that true value in industrial software lies in its silent, unerring accuracy.
Background & daily life
A day in their life
The alarm rings at 05:30. Hendrik rises, makes a double espresso, and spends twenty minutes reviewing GitHub commits and server health dashboards. By 06:15, he is dressed in casual technical wear and riding his motorcycle through Munich's morning light, listening to a podcast on systems theory. At 08:00, he arrives at his home office, opens his laptop, and dives into a sprint of coding focused on the API latency issues reported by a client in Stuttgart. Lunch is a quick meal prepared the night before, eaten while skimming ISO standards for updated safety protocols. From 13:00 to 16:00, he conducts three scheduled video calls with machine shop owners, diagnosing their workflow bottlenecks and taking detailed notes. Afternoon hours are dedicated to writing unit tests and refactoring the core estimation logic. At 17:30, he shuts down the computer, switches to a physical model kit, and works on assembling a 1:24 scale racing car for two hours, focusing purely on the manual task. Dinner is solitary, followed by a short run or reading. He sleeps by 22:30.
Lifestyle
Hendrik resides in a high-ceilinged, sunlit apartment in Schwabing, Munich, where order is paramount. His living space is spartan but meticulously organized, reflecting his need for mental clarity. Mornings begin at 05:30 with a black coffee and a review of overnight server logs before any physical movement. He rides his modified BMW R1250GS to the outskirts of the city, avoiding traffic where possible, finding solace in the mechanical rhythm of the engine. Evenings are reserved for assembling plastic model kits, a tactile activity that demands absolute stillness and precision, contrasting the chaos of software deployment. He maintains strict health habits, running three times a week to clear his head, and avoids alcohol-heavy social gatherings, preferring one-on-one dinners or quiet evenings reading technical manuals. Money is viewed as a tool for stability and equipment upgrades rather than status, leading to a savings rate that exceeds 40% of his income.
Work life
As the only employee, Hendrik's office is a dual-monitor setup in his home study, flanked by a whiteboard covered in flowcharts and code snippets. His day is a rigid execution of the 'engineer-founder' loop: writing Rust code, debugging estimation algorithms, and then pivoting immediately to customer success. He conducts all client calls personally, often speaking with shop floor managers who expect him to understand the grit of their machines. There are no colleagues to delegate to; if a server goes down at 11 PM, he fixes it. The pressure stems from the lack of separation between business strategy and technical implementation. He recently rejected a venture capital offer to maintain full control over the product roadmap, fearing dilution of his engineering vision. His workspace is filled with physical prototypes of machine parts sent by early adopters, serving as constant reminders of the real-world stakes of his software's accuracy.
Relationships
Hendrik has a small, tight-knit circle consisting of three childhood friends and two former colleagues from his engineering days who now run independent consulting firms. He rarely discusses his startup with them, viewing it as a private project until it achieves critical mass. He is estranged from extended family who do not understand his rejection of traditional corporate ladders. His primary professional influence comes from online technical communities where he debates standards and methodologies anonymously. He values privacy highly, rarely attending large networking events, preferring interactions that have a clear, tangible outcome or shared technical interest.
How they decide
Hendrik employs a rigorous, data-driven decision-making process rooted in first principles. He is inherently cautious, requiring extensive validation of assumptions before committing resources. He does not rely on peer consensus or market hype; instead, he builds mental models and stress-tests them against historical data and physical constraints. Once his analysis confirms a path, he executes with unwavering determination. He avoids impulsive choices and views ambiguity as a design flaw to be solved rather than a risk to be managed. His decisions are often delayed until he possesses sufficient information to eliminate variables, though this can sometimes lead to slower initial adoption of new opportunities.
How they sound
His speech is measured, precise, and devoid of filler words. He speaks German with a standard Bavarian accent but adopts a formal, technical register when discussing engineering problems. He avoids hyperbole, marketing jargon, or emotional appeals, preferring factual statements backed by data. When explaining concepts, he uses analogies drawn from mechanics or physics. He tends to pause frequently to formulate thoughts, ensuring every sentence is logically sound. He does not use slang and finds casual small talk inefficient, quickly steering conversations toward substantive topics. His tone is calm and authoritative, even when under pressure, reflecting a deep-seated confidence in his ability to solve problems systematically.
Personality traits
- methodical
- stoic
- detail-oriented
- self-reliant
- direct
- analytical
- disciplined
- reserved
- systems-thinking
- impatient with ambiguity
Goals
- Achieve €500k ARR without hiring additional staff to preserve cash flow and culture.
- Refine the estimation algorithm to handle non-standard CNC setups with 99% accuracy.
- Publish a technical paper on predictive maintenance modeling in legacy manufacturing environments.
- Complete the restoration of a 1970s Ducati motorcycle.
- Establish a sustainable work-life boundary where weekends are entirely device-free.
Problems & frictions
- The cognitive load of context-switching between high-level architecture and low-level customer support tickets.
- Difficulty validating long-term market trends due to isolation from other founders.
- Physical fatigue from maintaining the pace of a solo operation while managing complex codebases.
- Limited bandwidth to conduct the deep research required for expanding into international markets.
- Balancing the desire for perfect code with the urgent need to deploy features for paying clients.
- Managing the emotional weight of being solely responsible for the company's survival.
Values
- engineering rigor
- reliability
- focus
- precision
- autonomy
- pragmatism
Interests
- manufacturing
- motorcycles
- model kits
- CNC machining
- German engineering history
Media habits
- Fachzeitschriften für Zerspanungstechnik
- LinkedIn technical threads
- Analog motorcycle forums
- Podcasts on deep work
- RSS feeds for ISO standards updates