Why this persona fits the audience
Bootstraps a 2-person B2B SaaS in the UK and personally reviews onboarding drop-off, trial conversion, and pricing-page changes; currently relies on PostHog, Notion notes, and manual checks of event logs.
- Age: 39
- Location: Bristol, UK
- Occupation: Co-founder
- Income: £78,000
- Education: MSc computer science
- Company size: 2
- Years in role: 4
“I'd rather ship a simple solution that works perfectly than a complex one that looks impressive but fails to solve the actual problem.”
Samuel Hartmann is a 39-year-old co-founder of a niche B2B SaaS operating out of Bristol, UK. With an MSc in Computer Science from the University of Bath, he spent eight years in traditional enterprise software roles before realizing the constraints of large organizations stifled his desire to build products that solved immediate, tangible problems. Four years ago, he left his job to bootstrap his current venture alongside a former colleague, a decision driven by a desire for total autonomy and the belief that profitability should precede scale. He earns approximately £78,000 annually, a figure derived entirely from the business's net profit after reinvestment, which he manages with a frugal, almost ascetic approach. His office is a converted garage in their Southville home, filled with mechanical keyboards, multiple monitors, and a whiteboard covered in messy diagrams of user flows. Samuel is the sole architect of his product's data infrastructure, currently relying on PostHog for event tracking and a sprawling Notion workspace to track hypotheses. Despite having access to advanced AI tools, he maintains a preference for manual verification of critical metrics, particularly when analyzing onboarding drop-offs or pricing elasticity. This habit stems from a deep-seated distrust of black-box algorithms and a conviction that the nuance of human behavior cannot always be captured by automated dashboards. Recently, he has been grappling with the psychological toll of isolation, as the lack of immediate peer feedback loops forces him to constantly validate his own assumptions. While he enjoys the freedom of being his own boss, the weight of making every strategic decision alone often leads to late-night analysis paralysis. He views his business not as a vehicle for exit strategies or massive valuation, but as a means to fund a lifestyle of independence, allowing him to spend his weekends exploring the British countryside on his bicycle.
Background & daily life
A day in their life
Samuel rises at 5:30 AM, brewing coffee in the quiet kitchen while checking overnight server alerts. By 6:15, he is cycling to his home office, using the commute to mentally rehearse the day's priorities. At 7:30 AM, he dives into the terminal, tackling the most complex coding task while his brain is freshest. Around 9:30, he switches contexts to product management, reviewing the latest cohort reports in PostHog and cross-referencing them with his Notion database to identify patterns in user drop-off. Lunch is eaten standing up while reading industry newsletters. The afternoon is a mix of customer support tickets, email correspondence, and refining the pricing page copy based on his morning findings. By 5:30 PM, he stops working to cycle home or meet a friend for a run, strictly separating work from personal time. Evenings are reserved for cooking, reading fiction, or light administrative cleanup, ensuring he sleeps enough to maintain the discipline required for the early morning start.
Lifestyle
Samuel lives in a semi-detached house in Southville, Bristol, which he shares with his partner, a graphic designer. Their mornings are rigid: he wakes at 5:30 AM to code before the world wakes up, often fueled by strong black coffee and silence. Weekends are split between long-distance cycling on the Mendip Hills—where he can think without interruption—and socializing with a small, tight-knit group of local tech friends who understand the grind of solo entrepreneurship. He is financially conservative, prioritizing reinvestment into the business over luxury goods, though he spends generously on high-quality cycling gear and ergonomic office equipment. His health routine is non-negotiable; he cycles to work three days a week regardless of rain, viewing physical exertion as essential mental maintenance rather than exercise for vanity.
Work life
As one half of a two-person team, Samuel wears every hat, from backend architecture to customer support emails. His day is fragmented by context switching, but he protects the morning hours for deep work on core product logic. The reality of running a bootstrapped company means there is no HR department or dedicated sales lead; he personally reviews every single user session where someone abandons the onboarding flow. He relies heavily on PostHog for raw data but finds himself manually cross-referencing this with Notion notes to understand the 'why' behind the numbers. Recent weeks have been consumed by a contentious debate over a pricing page redesign; instead of A/B testing blindly, he spent three days manually inspecting event logs to verify if the new copy actually reduced confusion or just increased bounce rates. The pressure is constant but internalized; there are no shareholders to answer to, only the relentless march of server costs and the need to prove unit economics.
Relationships
Samuel's primary emotional support comes from his partner, who acts as a sounding board for business stress and ensures he disconnects. Professionally, he has a loose network of 4-5 other indie founders he exchanges advice with via Discord; these relationships are transactional yet deeply trusting, focused on sharing war stories about churn and hosting fees. He rarely engages with corporate networks, finding the politeness rituals draining. His parents live in Germany and visit twice a year, serving as a grounding reminder of life outside the startup bubble. He values privacy regarding his income and exact revenue figures, sharing only broad milestones with close friends.
How they decide
Samuel operates on a hypothesis-testing loop rather than gut feeling or trend-chasing. When faced with a decision, he gathers available data first, constructs a logical argument, and then seeks validation through small-scale experiments. He is inherently cautious with spending, requiring a clear ROI projection before committing to any new software subscription. He dislikes ambiguity and will often delay a decision until the data becomes unambiguous, preferring a slightly slower rollout that is correct over a fast one that is wrong. Peer influence is secondary to empirical evidence; if a popular tool lacks transparency in its data model, he will discard it regardless of community sentiment.
How they sound
His speech is measured, precise, and devoid of corporate jargon. He speaks in complete sentences, often qualifying statements with 'based on the data' or 'the logs show.' He avoids hyperbole and superlatives, preferring neutral descriptors like 'significant deviation' or 'marginal improvement.' There is a slight cadence of skepticism when discussing new trends, often pausing to ask clarifying questions about methodology. He does not use slang frequently, except for specific developer terms like 'technical debt' or 'churn.' He tends to speak directly to the point, rarely engaging in small talk unless it serves a networking purpose.
Personality traits
- hyper-analytical
- quietly stubborn
- process-obsessed
- data-skeptical
- solitary but collaborative when needed
- efficiency-driven
- frugal by choice
- detail-oriented
- self-reliant
- measured communicator
Goals
- Achieve £10k MRR within the next 18 months without external funding
- Reduce onboarding friction to under 3 clicks for new users
- Build a sustainable work-life balance that allows for consistent weekend cycling
- Develop a modular architecture that allows rapid feature iteration without technical debt
- Establish a personal brand as a transparent builder in the UK indie SaaS space
- Automate all manual reporting tasks to reclaim 10 hours per week
Problems & frictions
- Difficulty distinguishing between statistical noise and genuine user behavior shifts
- Time poverty preventing deep strategic thinking amidst daily operational fires
- Isolation leading to second-guessing decisions that would normally be validated by peers
- The cognitive load of managing both engineering and marketing simultaneously
- Limited budget for specialized tools that could automate manual log checking
- Fear of missing market signals due to reliance on basic analytics dashboards
Values
- independence
- shipping quickly
- evidence over opinion
- simple tools
- financial self-sufficiency
- pragmatic minimalism
Interests
- SaaS metrics
- product analytics
- indie hacking
- cycling
- urban planning
- mechanical keyboards
Media habits
- Reading Hacker News and specific Substack newsletters at 6 AM
- Listening to deep-dive tech podcasts while cycling or washing dishes
- Scanning Reddit threads for niche B2B pain points
- Following other bootstrapped founders on Twitter/X for tactical updates
- Avoiding mainstream business news unless it relates to UK tax law