Vic van Dijk

Why this persona fits the audience

Oversees operations for a 22-person logistics software company in Amsterdam, including vendor follow-up, QA handoffs, and weekly KPI reporting. He manages a mix of CRM notes, spreadsheet trackers, and internal Slack threads, and the team already relies on Lindy for inbox triage plus a few Zapier automations.

• Age: 36
• Location: Amsterdam, Netherlands
• Occupation: Operations Lead
• Income: €80k
• Education: Bachelor's in Industrial Engineering
• Company size: 22
• Years in role: 4

“If you can't measure it or automate it, you're just guessing, and in logistics, guessing is how you lose money.”

Vic van Dijk is a 36-year-old Operations Lead based in Amsterdam, serving as the operational backbone for a nimble 22-person logistics software startup. Holding a Bachelor's degree in Industrial Engineering, he applied his academic foundation to the real-world chaos of scaling a tech firm. For the past four years, Vic has been the gatekeeper of efficiency, tasked with translating complex logistical requirements into actionable workflows. His tenure has been defined by a relentless pursuit of 'operational clarity'; he believes that in a high-growth environment, the only way to scale is to systematize the mundane. Currently, he finds himself in a transitional phase, having outgrown the company's initial patchwork of Excel sheets and basic automation scripts. While the team utilizes Lindy for inbox triage and has deployed several Zapier automations, Vic sees these as temporary fixes rather than a permanent solution. He spends his days wrestling with fragmented data sources, manually reconciling CRM notes against Slack threads, and chasing vendors who fail to adhere to agreed-upon timelines. His recent decisions have focused on identifying specific pain points in the QA handoff process, where human error still introduces significant delays. Despite the pressure of managing a small team's expectations, Vic remains grounded, drawing energy from his morning cycling routines and his belief that every inefficiency is a solvable puzzle. He is financially stable, earning €80k, but views his career trajectory through the lens of impact rather than accumulation, aiming to build a lean, self-sustaining operation that requires minimal oversight. To Vic, the future of his role lies in the seamless integration of intelligent agents that can handle the repetitive cognitive load, allowing him to focus on strategic optimization.

Background & daily life

A day in their life

Vic wakes at 05:30, brews coffee using a V60 pour-over, and hits the trails on his bike until 06:30. By 07:45, he's at his desk in the office near Westerpark, checking emails and reviewing overnight server logs before the team arrives. The morning block is dedicated to deep work: updating the master KPI dashboard and auditing the latest vendor invoices. At 10:00, he joins the daily standup, focusing on blockers rather than status updates. Lunch is a quick sandwich eaten while reading a supply chain case study. Afternoons are dominated by meetings with engineering leads regarding QA handoffs and troubleshooting the broken Zapier integrations. Around 16:30, he spends 30 minutes documenting a new SOP for the team. He leaves by 17:30 to pick up groceries, then heads to the gym or meets Elise for a walk. Evenings are reserved for reading or light cycling prep, avoiding screens after 21:00 to ensure restful sleep.

Lifestyle

Vic lives in a renovated canal house near Oud-West, balancing his love for structure with the need for escape. His mornings begin at 05:30 with a strong black coffee and a 45-minute ride on his carbon road bike through the polder roads outside Amsterdam, a ritual that grounds him before the workday. He is financially prudent, maxing out his pension contributions and avoiding lifestyle inflation despite his solid income. Socially, he prefers one-on-one dinners or small gatherings with close friends over large parties, often discussing recent productivity hacks or industry trends rather than gossip. He keeps his home organized to a fault, viewing a cluttered environment as a direct threat to mental clarity.

Work life

As the Operations Lead, Vic is the central nervous system for his 22-person team, bridging the gap between engineering output and client delivery. His day is a constant juggling act of managing vendor contracts, ensuring QA handoffs are seamless, and generating weekly KPI reports that the CTO uses for investor updates. He currently navigates a chaotic digital landscape of fragmented tools: CRM notes buried in email threads, critical metrics tracked in disconnected spreadsheets, and urgent alerts lost in Slack channels. While the team has adopted Lindy for basic inbox sorting and some Zapier flows, Vic constantly identifies bottlenecks where these tools fall short, leaving him manually reconciling data that should be automated. The pressure comes from the fragility of their small-scale infrastructure; one missed detail in a shipment or a delayed report can ripple into significant client dissatisfaction.

Relationships

Vic is married to Elise, a graphic designer who shares his appreciation for minimalism and travel. They rely on each other for emotional support, though Vic tends to process stress through solitude and physical exertion. His closest professional influence is the CTO, with whom he has a long-standing friendship built on mutual respect for engineering rigor. He maintains a tight-knit circle of four friends from university who meet monthly for dinner, providing a necessary counterbalance to his work-focused life. He looks up to older department heads in the logistics sector who successfully scaled teams without losing operational control.

How they decide

Vic is a deliberate researcher who avoids impulsive choices. When evaluating new solutions, he prioritizes technical feasibility and integration capability over flashy marketing claims. He typically builds a small-scale proof-of-concept or runs a parallel test before committing any resources. He values peer validation and technical whitepapers over sales pitches, preferring to understand the underlying architecture and cost-benefit analysis before making a final decision. He is cautious about changing established workflows unless the data clearly demonstrates a net gain in efficiency.

How they sound

His speech is measured, precise, and devoid of unnecessary filler words. He speaks in clear, structured sentences, often pausing to verify facts before continuing. He avoids hyperbole and corporate buzzwords like 'synergy' or 'disrupt,' preferring concrete terms like 'latency,' 'bottleneck,' and 'throughput.' He tends to ask clarifying questions when something is vague, signaling a desire for absolute precision. In casual settings, his tone remains calm and analytical, even when discussing hobbies, always looking for the underlying mechanics or efficiency of an activity.