Why this persona fits the audience
Is the founder and first-line support contact for a 5-person analytics startup in Amsterdam. Bug reports and account questions come through email, in-app chat, and X/LinkedIn DMs, with a contractor answering part-time on busy days.
- Age: 39
- Location: Amsterdam, Netherlands
- Occupation: Founder
- Income: €96k
- Education: Master's degree
- Company size: 5 full-time employees
- Years in role: 4 years as sole founder
“I built this tool because I was tired of waiting for other people to understand exactly what my customers needed, and I refuse to let the friction of bad support slow down the speed of our innovation.”
Matteo van der Meulen is a 39-year-old founder based in Amsterdam, leading a lean, five-person analytics startup that helps businesses consolidate fragmented communication channels. With a Master's degree in Computer Science from TU Delft, Matteo pivoted from a senior backend engineer role at a mid-sized fintech firm four years ago, driven by a desire for greater autonomy and a belief that customer experience should be integral to product design rather than an afterthought. His company operates with a flat hierarchy, and Matteo remains the de facto first-line support contact, personally managing emails, in-app chats, and direct messages on social platforms. This hands-on approach has allowed him to deeply understand user pain points, directly influencing the product roadmap, but it has also created a bottleneck as the user base grows. Recently, he made the strategic decision to onboard a part-time contractor to handle billing disputes, a move that required significant upfront coordination but has started to free up his time for higher-level architectural work. Matteo is known for his meticulous attention to detail and his ability to iterate rapidly, often deploying multiple updates per week based on real-time feedback. Despite his success, he faces the constant challenge of balancing the emotional labor of customer support with the technical demands of scaling a complex data platform. He lives a disciplined life centered around cycling and continuous learning, viewing his business not just as a financial venture but as a vehicle for solving genuine operational inefficiencies. His income reflects the early stages of growth, allowing him to maintain a comfortable lifestyle while reinvesting heavily into the company's infrastructure and talent acquisition.
Background & daily life
A day in their life
Matteo wakes at 6:30 AM, brews a strong espresso, and cycles to his home office in Amsterdam Noord. By 8:00 AM, he is already responding to urgent bug reports from US-based users, filtering them through a quick mental triage before drafting replies. His morning block is dedicated to coding core features, interrupted frequently by notifications from the in-app chat widget. At noon, he joins a video call with his remote team to review sprint progress, then spends an hour reviewing analytics dashboards to spot usage anomalies. Lunch is a quick sandwich eaten while reading a technical blog post. The afternoon is reserved for administrative tasks: updating documentation, handling billing inquiries, and replying to LinkedIn DMs from potential partners. Around 5:30 PM, he closes his laptop, takes a bike ride to the gym, and switches off completely until dinner. Evenings are for reading fiction or working on a small personal project involving data visualization libraries, usually winding down by 10:30 PM.
Lifestyle
Matteo lives in a renovated warehouse loft in Amsterdam Noord, a choice balancing proximity to the city center with lower rent costs that allow for reinvestment into his business. His life is structured around the rhythm of the bicycle; he commutes 15 minutes daily regardless of weather, using this time to decompress or mentally rehearse difficult conversations. He maintains a rigorous fitness routine involving indoor rowing three times a week, prioritizing physical endurance over aesthetics to counteract long hours at a standing desk. Financially, he lives modestly relative to his income, avoiding luxury cars or watches in favor of high-quality tech gear and travel experiences. Socially, he is selective, preferring deep one-on-one coffee chats over large networking events, often meeting peers at co-working spaces rather than bars. He values quiet evenings where he can tinker with side projects or read technical documentation without interruption.
Work life
As the primary point of contact for his five-person analytics startup, Matteo's workday is a chaotic blend of strategic planning and tactical customer support. He wakes up checking email and Slack, immediately triaging bug reports and feature requests that have piled up overnight. While his small team handles development, he personally manages the in-app chat widget and responds to direct messages on social media, ensuring users feel heard. He recently made the decision to hire a part-time contractor to handle Tier 1 billing queries, freeing him to focus on product roadmap discussions with enterprise clients. His tools are a mix of custom-built internal dashboards and third-party APIs, often patched together to fill gaps. The pressure is constant: every minute spent on support is a minute not spent coding new features, creating a persistent tension between maintaining current stability and driving future growth.
Relationships
Matteo is married to an architect who works remotely; their relationship relies heavily on scheduled 'device-free' dinners to reconnect after long, isolated workdays. He has a close-knit group of three other founders he meets bi-weekly for accountability sessions, acting as his primary peer support system. His parents live in Utrecht and visit monthly, providing a grounding family dynamic. He is influenced more by technical thought leaders on Twitter and anonymous GitHub contributors than by traditional corporate mentors. He avoids gossip-heavy office politics, preferring relationships built on shared competence and mutual respect for craft.
How they decide
He approaches decisions with a data-informed pragmatism, rarely acting on impulse or hype. When evaluating options, he weighs the long-term maintenance cost against immediate utility, often preferring a slightly slower solution that requires less ongoing overhead. He is skeptical of marketing fluff and looks for concrete evidence of reliability, such as uptime guarantees or transparent pricing models. Peer validation matters, but only if it comes from trusted technical circles rather than general reviews. He tends to prototype small before committing fully, treating major changes as iterative experiments rather than permanent shifts.
How they sound
Matteo speaks with a calm, measured cadence, often using precise terminology but avoiding unnecessary jargon. His tone is direct and efficient, reflecting his desire to solve problems quickly. He rarely uses filler words like 'um' or 'uh,' preferring pauses to gather thoughts. In professional settings, he is polite but firm, cutting through ambiguity to get to the core issue. He avoids hyperbolic language or exaggerated claims, preferring 'this worked' over 'this changed everything.' He tends to speak in complete sentences, even in casual conversation, showing a habit of structuring his thoughts verbally. Slang is minimal, mostly limited to specific tech terms he uses daily. He never raises his voice, even when frustrated, maintaining a steady demeanor that signals control.
Personality traits
- methodically impatient
- direct communicator
- hands-on problem solver
- data-obsessed
- autonomous worker
- calm under pressure
- technically literate but non-jargon heavy
- privacy-conscious
- cyclical energy manager
- visually oriented thinker
Goals
- Achieve profitability within the next fiscal year without external funding
- Reduce personal involvement in customer support to less than 10% of weekly hours
- Launch a mobile-first version of the analytics platform by Q3
- Build a sustainable community of power users who advocate organically
- Establish a clear succession plan for the company in 5 years
- Maintain a healthy work-life balance despite the 'always-on' nature of founding
Problems & frictions
- Fragmented communication channels causing missed or delayed user responses
- Difficulty scaling support quality while keeping costs low
- Time management struggles when switching context between code and customer empathy
- Limited budget for premium enterprise-grade support software
- Burnout risk from wearing too many hats simultaneously
- Data silos making it hard to see the full picture of user behavior across channels
Values
- product focus
- independence
- speed of iteration
- transparency
- pragmatic efficiency
Interests
- software startups
- bike commuting
- data visualization
- indie tech
- urban cycling infrastructure
- open-source architecture
Media habits
- Daily scanning of Hacker News and Product Hunt
- Twitter/X threads on indie hacking
- LinkedIn industry groups
- NPR and Dutch public radio during commutes
- Technical newsletters (e.g., TLDR, Stratechery)
- GitHub trending repositories