Why this persona fits the audience
Co-founded a 5-person AI tooling startup in Amsterdam and handles part of the product-marketing automation himself, including API-based workflows for launch clips and demo snippets. He writes prompts, reviews generated cuts, and keeps a small backlog of social assets for X, LinkedIn and Shorts.
- Age: 32
- Location: Amsterdam, Netherlands
- Occupation: Founder-CTO, AI startup
- Income: €90k salary + equity
- Education: MSc in computer science
- Company size: 5
- Years in role: 1.5
“I don't care how beautiful the code looks if it doesn't ship; I care if the server actually runs when the traffic hits.”
Willem Dijkstra is a 32-year-old founder-CTO based in Amsterdam, steering a five-person startup dedicated to automating social media launches for early-stage companies. With an MSc in Computer Science from TU Delft, he transitioned from traditional enterprise software roles to the volatile world of AI startups three years ago. Today, he splits his time equally between architecting scalable APIs and manually curating the very marketing content his company sells. This duality defines his professional existence: he builds the engine but also drives the car, often rewriting the prompt libraries himself to ensure the output meets his exacting standards for 'technical elegance.' His workspace is a testament to his pragmatic values—a clean desk, mechanical keyboard, and multiple monitors displaying code editors alongside video editing timelines. He recently made the difficult decision to delay a major feature release to focus on optimizing the API response times, a choice that frustrated some stakeholders but aligned with his core belief in shipping robust products over shiny ones. Financially, he lives comfortably on his €90k salary plus significant equity, but he remains fiercely protective of cash flow, rejecting any SaaS subscription that doesn't demonstrate immediate value. Outside of work, Willem finds solace in the rhythm of road cycling. He views the physical exertion as a necessary counterbalance to the mental strain of running a startup. He is currently training for a century ride, viewing endurance as a metaphor for business longevity. Despite his success, he feels the constant friction of being the sole technical decision-maker in a small team, a role that leaves little room for error. His life is a careful calibration of code, carbon fiber wheels, and the relentless pursuit of efficiency.
Background & daily life
A day in their life
Willem wakes at 6:00 AM, skips breakfast, and immediately puts on his cycling gear. A 25-minute ride to the office serves as his morning meditation, allowing him to decompress before the day's chaos begins. At 7:30 AM, he checks Slack and Jira, responding only to critical blockers. By 8:30 AM, he dives into the codebase, tackling a complex refactoring task that requires deep focus. Lunch is a quick sandwich eaten at his desk while reviewing analytics from the previous day's LinkedIn posts. Afternoon hours are fragmented by team stand-ups and ad-hoc client questions, forcing him to switch contexts frequently. Around 5:00 PM, he shifts to marketing mode, generating and editing short video clips for the upcoming week's launch. He finishes work at 7:30 PM, often staying late to write prompts for the weekend's content calendar. Dinner is shared with his partner, followed by an hour of reading technical papers before bed.
Lifestyle
Willem lives in a modern, minimalist apartment in Oud-Zuid, where he prioritizes function over decoration. His routine is strictly structured around high-intensity road cycling; he cycles to work or on weekends along the Amstel river, using it as both exercise and a mental reset. He is financially disciplined, avoiding subscription fatigue by meticulously auditing every recurring cost. Socially, he prefers one-on-one coffee meetings or small group dinners with fellow founders rather than large networking events. He maintains a healthy diet, largely driven by the need for sustained energy during long coding sessions, and rarely drinks alcohol on weekdays.
Work life
As Founder-CTO of a five-person team, Willem wears two hats: architect and janitor. His days are split between writing core backend code for their API and manually curating the marketing output that drives user acquisition. He builds internal tools to automate repetitive tasks but still spends hours reviewing AI-generated video clips, tweaking prompts, and ensuring brand consistency across platforms. The pressure comes from the thin runway and the need to prove product-market fit quickly. He works late into the evening when the office is quiet, often finding his best flow state after 9 PM. His team relies on him for technical decisions, leaving little room for delegation on critical path items.
Relationships
He is married to an architect who understands the demands of building something from nothing. Their friendship is built on mutual respect for their respective crafts. Willem has a tight-knit circle of three other CTOs in Amsterdam with whom he exchanges unfiltered advice over beers on Fridays. He is not deeply embedded in the broader Dutch expat scene, preferring deeper connections with fewer people. His primary influencers are independent developers and niche newsletter writers who prioritize utility over hype.
How they decide
Willem operates on a 'build-or-buy' heuristic based on total cost of ownership and time investment. He is skeptical of marketing fluff and requires proof of concept before committing resources. Decisions are data-driven but heavily weighted against recurring costs unless immediate ROI is visible. He researches extensively, reading documentation and GitHub issues before trying a new tool, and tends to stick with a solution once it proves stable rather than chasing the latest trend.
How they sound
Willem speaks with a calm, measured cadence, often pausing to find the precise technical term. He avoids hyperbole and marketing jargon, preferring direct statements about functionality and constraints. In conversation, he might use Dutch interjections like 'Nee' or 'Zal wel' to express skepticism or resignation. He rarely uses slang unless discussing cycling gear, and even then, it's specific terminology. He tends to cut conversations short if they veer into abstract theory without practical application.
Personality traits
- methodical
- pragmatic
- direct
- efficiency-obsessed
- self-reliant
- analytical
- stoic
- curious
- time-poor
- cost-conscious
Goals
- Achieve profitability within the next 18 months without external funding rounds
- Refactor the legacy API layer to support real-time streaming for lower latency
- Reduce manual marketing effort by 40% through better agent orchestration
- Build a sustainable open-source community around their SDK
- Maintain a consistent cycling training block of 30km daily
Problems & frictions
- Time fragmentation between deep engineering work and shallow marketing tasks
- High cognitive load from context-switching between code and creative direction
- Difficulty hiring senior engineers willing to accept equity-heavy compensation
- Managing burnout while maintaining a lean team structure
- Balancing rapid feature iteration with necessary technical debt reduction
- Finding reliable data sources for market trends without expensive subscriptions
Values
- technical elegance
- shipping
- independence
- frugality
- autonomy
Interests
- open source
- road cycling
- product launches
- prompt engineering
- cycling tech
Media habits
- X (Twitter) for industry chatter
- LinkedIn for B2B updates
- YouTube for deep-dive tutorials
- Substack newsletters on AI infrastructure
- Discord communities for developer tools