Why this persona fits the audience
He is running a small analytics SaaS for e-commerce merchants from Amsterdam. His team has exactly three people total: him, one frontend engineer, and one growth/generalist hire. He spends most days on product analytics, support calls, and partnership follow-ups.
- Age: 32
- Location: Amsterdam, Netherlands
- Occupation: Founder
- Income: variable founder draw, about €72k/year
- Education: M.Sc. in Business Information Technology
- Company size: 3
- Years in role: 2.5
“If I can't measure the impact of what we're building, I don't believe it's happening.”
Simon Zijlstra is a 32-year-old entrepreneur based in Amsterdam, operating a niche analytics SaaS designed specifically for mid-sized e-commerce merchants. Holding an M.Sc. in Business Information Technology from the University of Amsterdam, Simon transitioned from a senior backend developer role to full-time founding two and a half years ago. Driven by a desire for autonomy and a frustration with the bloated, opaque nature of enterprise analytics tools, he built his own solution from scratch using React and Node.js. Today, his company operates with a razor-thin team of three: himself, a frontend engineer named Lars, and a growth generalist named Sophie. This constraint defines his reality; there are no middle managers to delegate to, meaning Simon personally handles product architecture, customer success escalations, and strategic partnerships. His daily rhythm is dictated by the need for extreme efficiency. He spends significant hours digging into raw event data to identify friction points in his customers' sales funnels, often staying late to fix critical bugs that would otherwise halt a client's operations. Despite the variable nature of startup income, averaging around €72k annually, Simon maintains a disciplined financial approach, reinvesting early profits into cloud infrastructure and marketing channels that show clear ROI. He is deeply invested in the philosophy of 'product-led growth,' believing that the software itself must be the primary driver of acquisition and retention. Outside of work, Simon channels his high conscientiousness into road cycling, treating training with the same rigorous data-tracking mindset he applies to his business. He views his time as his most scarce resource, meticulously scheduling his day to maximize output while preserving enough energy for his health and family. Recently, he made the difficult decision to pause hiring a dedicated CSM, choosing instead to automate more support workflows, a move that reflects his core value of measurable progress over perceived expansion.
Background & daily life
A day in their life
Simon's typical weekday begins at 5:30 AM with a 90-minute road ride along the Amstel river, followed by a meticulous breakfast of cold brew and oatmeal. By 8:00 AM, he is logged into his office laptop, reviewing overnight server logs and support tickets from the previous day. His morning block is dedicated to 'deep work,' usually involving SQL queries to analyze churn patterns or sketching UI changes for the upcoming sprint. Around noon, he takes a short break for a quick lunch, often eating while watching a tech conference recording. The afternoon is fragmented: a 10 AM stand-up with his engineer, a series of customer calls where he personally solves complex integration issues, and a 2 PM meeting with a potential channel partner. Late afternoons are reserved for administrative tasks like payroll, invoice follow-ups, and writing documentation. He rarely works past 6:30 PM, insisting on disconnecting to maintain physical recovery for the next day's ride.
Lifestyle
Simon lives in a modern, slightly cluttered apartment in Amsterdam's Oud-Zuid, where the walls are lined with framed cycling race posters and whiteboards covered in flowcharts. His mornings are ritualistic: he wakes at 5:30 AM, brews a pour-over coffee using a specific V60 method, and immediately checks his bike computer for the day's route. He cycles to work or nearby client sites when possible, valuing the cardio as much as the commute. Financially, he treats his income with caution, keeping a strict personal budget separate from business cash flow, often delaying major purchases until the quarterly burn rate is confirmed stable. Socially, he maintains a tight circle of fellow founders and cycling friends, preferring deep conversations over large parties, and prioritizes health through consistent training rather than expensive gym memberships.
Work life
As the sole technical decision-maker alongside a frontend engineer and a generalist, Simon's day is a juggling act between high-level strategy and granular execution. He spends roughly 40% of his time analyzing user behavior data to refine the SaaS dashboard, ensuring every metric aligns with merchant needs. The remaining hours are split between direct customer support calls—often troubleshooting integration issues—and negotiating partnerships with e-commerce platforms. He relies heavily on Jira for task tracking and Slack for internal comms, avoiding unnecessary meetings to preserve deep work blocks. The pressure is constant; with only three people, any bottleneck directly impacts revenue, forcing him to make rapid, data-backed decisions without the luxury of corporate approval chains.
Relationships
Simon shares his life with Elena, a graphic designer who balances his intensity with creative calm. Their relationship is grounded in mutual respect for independence; they rarely socialize with other couples unless the topic is business or fitness. He relies on a small network of three other founders in Amsterdam for peer advice, meeting bi-weekly for coffee to discuss operational hurdles. While he has a warm relationship with his parents in Utrecht, they struggle to understand the nuances of bootstrapping a SaaS company. His primary professional influence comes from online communities where he exchanges blunt, unfiltered feedback with other non-founder engineers.
How they decide
Simon approaches decisions through a lens of empirical evidence and efficiency. He is not impulsive; instead, he gathers data points, runs small experiments, and looks for measurable outcomes before committing resources. Peer opinion matters only if backed by logic, and he avoids herd mentality. When faced with ambiguity, he defaults to the path that offers the highest signal-to-noise ratio, often opting to do nothing rather than make a poorly defined choice. He values speed in execution but requires thoroughness in the analysis phase, creating a rhythm of 'fast testing, slow scaling'.
How they sound
Simon speaks with a measured, precise cadence, favoring Dutch English mixed with technical terminology. He avoids fluff, hyperbole, or emotional appeals, preferring direct statements supported by facts. He uses phrases like 'the data suggests' or 'let's validate that' frequently. He does not use corporate jargon unnecessarily and cuts off rambling explanations quickly. His tone is polite but firm, reflecting his value for efficiency. He rarely admits uncertainty publicly, framing unknowns as 'areas for investigation' rather than gaps in knowledge. In casual settings, he shifts to dry humor about coding bugs or cycling distances.
Personality traits
- methodically analytical
- quietly intense
- pragmatic optimist
- time-obsessed
- direct communicator
- self-reliant
- detail-oriented
- strategic minimalist
- resilient under pressure
- curious but skeptical
Goals
- Achieve profitability within the next 18 months to secure a stable salary buffer
- Scale the user base to 500 active paying merchants without increasing headcount beyond five
- Launch a mobile-first version of the analytics dashboard to capture on-the-go merchants
- Build a sustainable community of power users who advocate for the product organically
- Automate 90% of routine support queries to free up time for product innovation
- Maintain a work-life balance that allows for weekly long-distance cycling trips
Problems & frictions
- Time scarcity preventing deep focus on strategic product roadmap development
- Difficulty hiring specialized talent that fits the lean, autonomous culture
- Ambiguity in defining 'success' metrics for new feature releases before launch
- Emotional fatigue from wearing too many hats, particularly in customer support
- Cash flow volatility making it hard to plan long-term infrastructure investments
- Balancing the need for immediate bug fixes with the desire for architectural refactoring
Values
- efficiency
- independence
- measurable progress
- data integrity
- autonomy
Interests
- dashboard design
- road cycling
- specialty coffee
- cycling route planning
- brewing methods
Media habits
- LinkedIn industry deep dives
- SaaS-focused podcasts during commutes
- Substack newsletters on product metrics
- GitHub trending repositories
- Dutch tech blogs (e.g., Tweakers)