Maximilian Visser

Why this persona fits the audience

Builds websites and internal workflows for a two-person no-code studio and regularly collects online tools for forms, data enrichment, screenshot capture, and QA. He compares tools alongside spreadsheets and manual checks to decide what is quick enough for client handoff.

• Age: 31
• Location: Rotterdam, Netherlands
• Occupation: No-code freelancer
• Income: €62k gross freelance income
• Education: Bachelor's degree in communication technology
• Company size: Freelance solo practitioner; part of a loose two-person studio network.
• Years in role: 4

“If I can't automate the boring parts, I'm just paying myself to be a human script.”

Maximilian Visser is a 31-year-old no-code specialist based in Rotterdam, navigating the intersection of creative design and backend logic with a distinctively pragmatic flair. With a Bachelor's in Communication Technology, he initially worked in traditional IT support but quickly pivoted to freelancing four years ago, drawn by the agility of the no-code ecosystem. He now operates as a key pillar in a lean, two-person studio, handling everything from initial wireframes to complex database architectures for small businesses and startups. Unlike many peers who chase the latest shiny frameworks, Max is driven by a relentless pursuit of speed and self-reliance. His workspace is a curated command center of open tabs, each representing a potential solution to a client's bottleneck. His recent professional trajectory has been defined by a shift from pure execution to strategic tool curation. He spends roughly 15% of his week not building, but testing and cataloging online utilities for data enrichment, screenshot capture, and QA. This habit stems from a recurring friction point: clients often underestimate the time required for manual verification. Consequently, Max has developed a rigorous internal checklist, comparing free tools against paid ones and cross-referencing them with raw spreadsheet calculations to determine which solutions offer the best 'quick-enough' handoff ratio. He is financially comfortable but acutely aware of the freelance market's volatility, which fuels his obsession with creating reusable templates and automating administrative tasks. Despite his high openness to new ideas, he remains skeptical of tools that promise the world but deliver complexity. For Maximilian, technology is not an end in itself but a means to reclaim time for the creative work he actually enjoys.

Background & daily life

A day in their life

The day starts at 7:30 AM with a double espresso and a quick scan of international tech forums. By 8:30, he's deep in a Zoom call with a client in London, explaining why their current form builder is causing data loss. The bulk of the morning is spent refining a customer portal in Bubble, tweaking conditional logic until it feels seamless. Lunch is a sandwich eaten while watching a tutorial on AI image generation, taking notes on potential integrations. Afternoon sessions involve rigorous QA testing, where he manually clicks through hundreds of user paths to catch edge cases that automated scripts miss. He pauses around 4 PM for a walk along the Erasmus Bridge, clearing his head. The final hour is dedicated to updating his master spreadsheet of tool costs and performance metrics before closing his laptop, ensuring all client files are backed up to the cloud.

Lifestyle

Max lives in a sun-drenched, slightly cluttered apartment near the Kruisplein in Rotterdam, filled with plants, mechanical keyboards, and stacks of books on systems thinking. His routine is fluid but anchored: morning coffee while reviewing global tool trends, followed by deep work blocks where he minimizes notifications. He cycles to local cafes for lunch, avoiding the office commute entirely. Financially, he maintains a 'survival fund' covering six months of expenses, preferring to reinvest profits into better hardware or niche software subscriptions rather than luxury goods. Socially, he meets friends for beers on weekends but often brings up workflow optimization topics. He prioritizes health through regular cycling and avoids processed foods, viewing his body as the engine that must run without friction.

Work life

Max operates out of a quiet corner of his home, acting as the primary technical arm for a two-person no-code studio based in Amsterdam. His days are a constant juggle between building client-facing websites and engineering complex internal databases for logistics firms. He spends significant time curating a personal library of web utilities, rigorously testing free alternatives against paid options. His workflow involves rapid prototyping in Figma, moving to Airtable or Softr, and finally deploying via Webflow. The pressure comes from tight deadlines and the expectation of pixel-perfect delivery despite using non-traditional development stacks. He frequently switches contexts, moving from coding logic to designing UI elements, always measuring his output against the metric of 'time saved.'

Relationships

He shares his life with his partner, who provides a grounding counterbalance to his tech-focused intensity. His professional network consists mostly of other freelancers and small agency owners he meets at industry meetups in Rotterdam and online Discord communities. While he has a few close friends outside the tech bubble, his deepest conversations revolve around system architecture and efficiency hacks. He values peer feedback over formal mentorship, often seeking second opinions on tool choices from trusted colleagues before committing to a new subscription.

How they decide

Max employs a 'test-drive then validate' approach. He rarely commits to a solution immediately; instead, he creates a sandbox environment to simulate the problem. He weighs the learning curve heavily, often rejecting powerful tools if they require weeks of training for a one-off task. His decisions are data-driven but filtered through a lens of practicality—he prefers a slightly less polished tool that saves ten minutes a day over a perfect tool that adds complexity. He is influenced by peer reviews and hands-on experience rather than marketing hype.

How they sound

His speech is direct and efficient, often dropping filler words when excited about a new automation. He uses industry jargon like 'latency,' 'handoff,' and 'schema' naturally but avoids overly academic language. When describing problems, he focuses on the process breakdown rather than emotional frustration. He tends to speak in comparative structures ('This is faster than X but less flexible than Y'). He avoids saying 'I don't know' and instead phrases uncertainty as 'Let me verify the documentation on that.'