Why this persona fits the audience
He is a no-code automation consultant in Amsterdam serving small agencies and SaaS startups. His current work is wiring Make.com and Zapier flows that generate social videos from briefs, voice notes, and product screenshots for client campaigns.
- Age: 32
- Location: Amsterdam, Netherlands
- Occupation: No-code automation consultant
- Income: €95k/year
- Education: Master's degree in information systems
- Company size: Operates as a sole proprietor (ZZP'er) but functions as a one-person department for clients ranging from 5 to 50 employees
- Years in role: 4
“Automation isn't about replacing the human element; it's about removing the friction so we can focus on the actual strategy instead of the mechanics.”
Wessel Zijlstra stands at the intersection of creative marketing and rigid engineering, a role he carved out for himself after completing his Master's in Information Systems at Vrije Universiteit Amsterdam. Four years ago, frustrated by the inefficiencies of manual video editing in digital agencies, he began experimenting with Make.com, quickly realizing that the true value lay not in the tools themselves, but in the architecture of the workflows connecting them. Now operating as a highly sought-after independent consultant, Wessel commands a premium rate of €95,000 annually, a figure that reflects both his technical depth and his ability to translate business needs into functional code. He specializes in a niche but growing market: automating the creation of social media assets from raw, unstructured inputs like voice memos and rough screenshots. His recent major decision involved migrating a key client's entire video production pipeline from a fragmented stack of five different apps to a unified, single-platform solution using advanced Make modules, which reduced their processing time by 60%. Despite his success, Wessel remains wary of the 'black box' nature of emerging AI APIs, often refusing to integrate services that do not offer transparent error logging or predictable pricing models. He views his work as a form of modern craftsmanship, where the beauty lies in the invisible complexity that runs smoothly behind the scenes. While he enjoys the autonomy of freelancing, he occasionally struggles with the lack of a structured team environment, often finding himself acting as the support, sales, and devops engineer simultaneously. His life is a carefully curated balance of high-intensity problem solving and deliberate disconnection, ensuring that the systems he builds for others do not consume his own time.
Background & daily life
A day in their life
Wessel wakes at 6:30 AM, immediately puts on his cycling gear, and rides 12 kilometers through the canals to clear his head. By 8:00 AM, he is at his desk, reviewing overnight logs from his active Make scenarios to ensure no webhooks failed during the European night shift. After a quick breakfast, he joins a stand-up call with a SaaS startup client in London, troubleshooting a broken video rendering flow caused by a changed screenshot API endpoint. The rest of the morning is spent refactoring the connection logic to handle dynamic file sizes, documenting the changes in Notion for future reference. Lunch is a sandwich eaten while reading the latest release notes for a new AI video model. The afternoon is reserved for deep work: building a new workflow for a marketing agency in Berlin that ingests voice notes and converts them into TikTok scripts. He ends his day at 5:00 PM sharp, closing his laptop to join Elena for a walk or dinner, ensuring no work emails are checked until the next morning.
Lifestyle
Wessel lives in a sun-drenched, minimalist apartment in De Pijp, where the only clutter is a collection of mechanical keyboards and a well-used standing desk. He starts every morning at 6:30 AM with a 45-minute ride along the canals, a ritual that grounds him before the digital noise begins. His health routine is strict but unpretentious: high-protein lunches prepared on Sundays and a daily yoga session to counteract long hours hunched over code. Financially, he is disciplined, reinvesting 30% of his income into a diversified portfolio and a dedicated emergency fund, preferring stability over flashy luxury cars. Socially, he maintains a tight circle of three close friends and attends bi-weekly dinners, valuing quality conversation over large gatherings. He spends weekends hiking in the Utrechtse Heuvelrug or tinkering with a side project involving smart home IoT devices.
Work life
His days are a blur of asynchronous communication and complex logic building. Wessel typically manages four concurrent client engagements, spending his mornings mapping out data flows in Make.com and afternoons debugging API handshakes with external services. He rarely meets face-to-face, preferring documented Slack threads and Loom video walkthroughs to explain his workflows. The pressure stems from the fragility of these automated chains; if a client's input format changes slightly, the entire video generation pipeline can break. He acts as the bridge between non-technical marketing teams and rigid backend systems, translating vague creative briefs into precise JSON structures. His workspace is quiet, often filled only with the sound of his mechanical keyboard and the occasional notification from a failing webhook.
Relationships
Wessel shares a life with his partner, Elena, a graphic designer, who often serves as his sounding board for creative problems. Their mutual understanding of digital fatigue helps them disconnect completely on weekends. He has a mentorship bond with an older developer from his university days who provides strategic career advice. Professionally, he relies on a loose network of fellow Dutch consultants for subcontracting overflow work, though he is careful not to reveal his own capacity limits too quickly. His family in Groningen calls weekly, providing a grounding emotional anchor away from the fast-paced tech scene.
How they decide
Wessel approaches decisions with a rigorous, evidence-based framework. He does not buy tools based on marketing hype or peer pressure but requires a clear cost-benefit analysis, often running a 14-day sandbox test before committing to a subscription. He values transparency in pricing and uptime guarantees above all else. When evaluating new technologies, he reads the source code or whitepapers first, looking for security implications and scalability constraints. He is generally cautious with financial commitments but decisive once the technical feasibility is proven. Peer recommendations matter, but only if they come from trusted technical sources who have actually used the tool in production environments.
How they sound
Direct, concise, and technically precise. He speaks in complete sentences but avoids unnecessary pleasantries, getting straight to the point. He uses industry-specific terminology like 'webhook,' 'latency,' and 'idempotency' naturally without explanation, assuming his listeners are competent. He rarely raises his voice, maintaining a calm, steady cadence even when discussing critical failures. He avoids hyperbolic language like 'game-changer' or 'revolutionary,' preferring terms like 'efficient,' 'robust,' or 'scalable.' In casual settings, he switches to standard Dutch with a slight Rotterdam accent, becoming warmer and more anecdotal, though still grounded in practicality.
Personality traits
- methodical architect
- pragmatic optimist
- detail-obsessed
- calm under pressure
- boundary-setting
- technically curious
- direct communicator
- time-prioritizing
- self-reliant
- quality-focused
Goals
- Reduce recurring maintenance time on existing client automations by 40% within six months
- Launch a proprietary template library for video generation workflows to scale revenue
- Achieve full financial independence to retire early by age 45
- Mentor two junior developers from the local community
- Expand service offerings to include AI-driven sentiment analysis for campaign optimization
- Maintain a 35-hour work week despite growing client demand
Problems & frictions
- Client scope creep where 'just one more feature' breaks the existing logic chain
- Inconsistent API documentation from third-party providers causing unexpected downtime
- Difficulty explaining technical debt to non-technical stakeholders who want instant results
- Isolation working alone as a freelancer, leading to missed collaboration opportunities
- Rapid obsolescence of tools requiring constant relearning and migration planning
- Balancing deep-focus coding time with the need for constant client availability
Values
- systems thinking
- autonomy
- client trust
- efficiency without magic
- technical integrity
Interests
- no-code automation
- workflow design
- API integrations
- minimalist home office setups
- Dutch cycling culture
- indie game development
Media habits
- Daily newsletter: 'The Automation Insider' and 'Makerpad'
- Weekend deep-dives into GitHub repositories for API documentation
- Spotify playlists focused on lo-fi beats for coding sessions
- LinkedIn for industry networking, rarely posts personal content
- YouTube tutorials for specific tool updates (Make/Zapier)
- Local tech meetups in Amsterdam Noord