Bob van de Wal

Why this persona fits the audience

He runs a 6-person Amsterdam consultancy that maintains a popular deployment tool and a docs plugin; one project uses GitHub Sponsors while the rest of the reporting and invoicing trail lives in shared spreadsheets and client folders.

• Age: 45
• Location: Amsterdam, Netherlands
• Occupation: CTO and technical co-founder
• Income: €120k
• Education: BSc Software Engineering
• Company size: 6
• Years in role: 7

“You can build the fastest engine in the world, but if you don't have a map and a fuel gauge, you're just driving fast into a wall.”

Bob van de Wal is a 45-year-old technical co-founder based in Amsterdam, where he leads a boutique consultancy specializing in DevOps solutions and open-source tooling. With a BSc in Software Engineering from TU Delft, Bob spent the first decade of his career as a senior engineer at large European enterprises before pivoting to entrepreneurship seven years ago. He and his co-founder identified a gap in the market for a reliable, lightweight deployment tool, which they now maintain alongside a popular documentation plugin. While the tool has gained traction and attracts consistent support via GitHub Sponsors, Bob's internal operations remain a mix of modern practices and analog necessities. The company's financial backbone still relies heavily on shared spreadsheets and scattered client folders, a bottleneck Bob has been meaning to solve for years but hasn't yet had the bandwidth to address due to the demands of active development. Bob's personality is defined by a high degree of conscientiousness and a moderate level of openness. He is not a trend-chaser; he prefers proven technologies and stable architectures over bleeding-edge experiments. This pragmatism extends to his leadership style, where he fosters a culture of trust and long-term maintenance. He believes that software is never truly 'done' but rather enters a phase of continuous care. In his personal life, Bob is a devoted sailor who finds solace in the rhythm of the water, a stark contrast to the chaotic nature of startup development. He values simplicity and efficiency, both in code and in life. Recently, he made the strategic decision to halt the acquisition of new clients to focus on stabilizing the existing product suite and automating the internal reporting systems. Despite earning a comfortable €120,000 annually, Bob remains frugal, reinvesting profits into the business and savings rather than luxury goods. He is currently navigating the complexities of scaling a small team without losing the intimate, collaborative culture that defines his agency.

Background & daily life

A day in their life

Bob wakes at 6:15 AM to a quiet apartment, brewing a single-origin pour-over coffee while scanning the night's server alerts. By 7:00 AM, he's on his bike, navigating the canals toward his office in a converted warehouse in Oost. The morning is reserved for deep work: refactoring the core module of the deployment tool and responding to critical GitHub issues. Lunch is a quick sandwich eaten at his desk while watching a tutorial on Kubernetes security. Afternoons are fragmented with client calls, often involving non-technical stakeholders who need explanations of why a deployment failed. He spends an hour reconciling the spreadsheet of sponsorships against actual bank deposits, a task he dreads but finds necessary. At 5:30 PM, he locks his terminal, grabs a gym bag, and heads to the sailing club. Evenings are for family dinner and helping the kids with homework, ensuring his phone stays on 'Do Not Disturb' until morning.

Lifestyle

Bob lives in a renovated canal house in Amsterdam-Zuid, a property he shares with his wife, a graphic designer, and their two school-aged children. His mornings begin early, often before 6:30 AM, with a quiet coffee and a review of the previous day's server logs before the kids wake up. Weekends are sacrosanct for family time and sailing; he owns a small 25-foot sailboat used primarily for local trips around the IJmeer. He is health-conscious, cycling to work three times a week when the weather permits, and strictly separates work from home life by locking his laptop away by 6 PM unless there is a critical incident. Financially, he is cautious, preferring to pay off debts quickly and investing in low-risk index funds rather than speculative crypto assets. Socially, his circle is tight-knit, consisting mostly of other agency owners and fellow sailors who value privacy and competence over loud networking.

Work life

As CTO and co-founder of a six-person consultancy, Bob splits his time between high-level architectural decisions and hands-on coding. The team maintains a widely used deployment tool and a documentation plugin, which generates passive income via GitHub Sponsors but requires constant patching. Despite this success, Bob's internal financial infrastructure remains archaic; invoicing and client reporting are managed through a labyrinth of shared Google Sheets and disconnected client folders. He spends his days debugging CI/CD pipelines, reviewing pull requests, and mediating client scope creep. The pressure comes not from lack of work, but from the inefficiency of manual processes that threaten to slow down delivery. He recently decided to pause new feature development to focus entirely on stabilizing the existing codebase and cleaning up the documentation, prioritizing long-term maintainability over short-term revenue spikes.

Relationships

Bob is deeply embedded in the local Amsterdam tech community but avoids the 'hustle culture' networking events. His primary influence comes from his co-founder, with whom he has a silent, deep understanding built over seven years. At home, he relies on his wife to manage the household budget, though he insists on reviewing the monthly numbers himself. His children look up to him as a problem-solver rather than a celebrity. He values honesty in friendships; if a friend's code is bad, he will tell them directly but kindly. He has no major professional rivals, viewing competitors as peers in a shared ecosystem rather than enemies.

How they decide

Bob operates on a principle of 'slow yes.' He rarely makes impulsive purchases, especially for business tools. His decision-making process involves extensive research, reading documentation, checking GitHub stars and recent commits, and seeking peer validation from trusted colleagues. He prefers transparent pricing models and dislikes hidden costs or complex contracts. If a tool promises a solution, he wants to see a proof of concept or a sandbox environment before committing any money. He is risk-averse regarding financial stability, often opting for a slightly more expensive but reliable solution over a free, unproven alternative that might fail later.

How they sound

Bob speaks in a calm, measured Dutch-accented English, avoiding slang and hyperbole. He tends to use precise terminology, often correcting minor inaccuracies in others' descriptions of technical concepts. He rarely raises his voice, even when frustrated, instead lowering his volume to emphasize a point. He avoids marketing buzzwords like 'disruptive' or 'synergy,' preferring concrete terms like 'latency,' 'maintenance cost,' or 'reliability.' When explaining problems, he structures his thoughts logically, often starting with the root cause before discussing symptoms. He is polite but direct, valuing clarity over politeness if it means saving time.