Niek van Leeuwen · GTM engineer

I build the systems that find your next deal.
Before it's obvious to anyone else.

My systems watch your market and flag the companies that are about to move: a warranty about to expire, a regulation kicking in, a hire that signals budget. You reach them while the window is still open.

Tell me what you're building See the work →

GTM expertise

Four fields I work in, end to end.

The through-line: I build systems that get smarter the longer they run. Every reply and every booked meeting is logged against the signal that triggered it, and that log decides next week's list. One person, from strategy to the actual build.

Market and signal intelligence

Some buying decisions are predictable if you know where to look. A warranty about to expire, a regulation going live, a hire in a role that signals budget. I build the monitoring that catches those events and turns them into a weekly shortlist of who is worth a conversation right now.

In practice

Signal sourcing: job posts, tech-stack changes, funding, reviews, expiring contracts, new regulations
A scoring model that ranks accounts by how many signals are firing at once
A weekly shortlist of the accounts worth reaching right now
Live dashboards to watch the triggers as they happen
ICP and segmentation built from your own closed-won and closed-lost

AI Outbound Systems

Cold email and LinkedIn machinery that starts real conversations: building the lists, writing the messages, setting up the sending infrastructure, and making sure the emails land in inboxes rather than spam folders. The whole outbound operation, built and run end to end.

In practice

Sending infrastructure: domains, inboxes, warmup and deliverability
List building and enrichment waterfalls (Apollo, Apify, Clay, Hunter)
Copy and campaign build in Instantly and Lemlist
AI personalization at scale, drafted inside the workflow
Reply handling and routing straight into the CRM
LinkedIn outreach flows running alongside the email

AI workflow engineering

Most teams already have the tools they need: they just have not connected them. I wire together what is already there, CRM, inbox, Clay, n8n, so AI handles the repetitive reading and writing and the results feed back into the next run. Classifiers clean up and route thousands of contacts, each step informed by what the previous one found, without anyone opening a spreadsheet.

In practice

n8n automations that connect the tools you already use
Claude steps for reading, classifying and drafting
Enrichment and data pipelines across Clay, Neon and HubSpot
Reply classifiers and routing logic
Custom scripts and API glue where no off-the-shelf tool fits

Web design and build

I design and build websites myself, this one included. From a quick prototype to a full build with a CMS, so the owner adds content without touching code. Doing both the design and the build solo turns out to produce cleaner decisions.

In practice

Portfolio and marketing sites, designed and built end to end
Client sites on Wix and Next.js
A CMS setup so you can edit the content yourself
Landing pages for campaigns
Hosting and deploy on Vercel

Selected work

A few systems I actually built.

View all projects →

@vanleeuwendigital

Building

Talk to me

Niek van Leeuwen

Founder, Van Leeuwen Digital

Who's behind this

I build systems that keep working
after I leave.

I started in sales and recruitment. Cold calls, spreadsheet pipelines, the same follow-up emails on a loop. At some point I automated the repetitive half of my own job, before anyone asked me to. Partly because I'm curious about how things work, partly because I found the repetition genuinely unbearable. (The curiosity sounds better, so let's go with that.)

Those systems turned out to work better than my manual version, and they kept working whether I paid attention or not. So I started building them for teams. Over time that became the profession: I come into a sales or marketing team, figure out where the real friction is, and build the system that handles it. That's what I do now, for my own clients.

“ICP isn’t a filter. It’s a living context.”
The belief behind every system I build

Diagnosis before build.I look at what's broken before I write a single formula.
You can run it without me. I teach your team how it works.
You keep everything. Accounts, tables, docs, all yours.

For companies past 80 people, this work scales further at Paioneers, where I'm co-founder. Below that, you're in the right place here.

I build in public on LinkedIn, if you want to follow along.

Partners

Tools I build with.

Every system I build for clients runs on some combination of these tools. I only list what I'm actively using in paid client work, which keeps this page short. A few links are affiliate links, and when I onboard a new client I send them here so they're not hunting around for the right plan.

Clay

Clay is the table most of my client data flows through. I hold Clay expert certifications for inbound automation, outbound automation and CRM enrichment, and use it daily: pulling in company data, qualifying leads, and the multi-step lookups that would otherwise take five separate tools. Most of the systems on this page have a Clay table at the center.

Inbound AutomationOutbound AutomationCRM Enrichment

Try Clay →

How I choose partners

A tool earns a spot here by being in active use on a real client account. When something better does the job, the old one comes off. That's the whole filter.

Stack size: 18 tools. Last reviewed: July 2026.

Also in the stack

Exa

n8n

Wix

Tell me what you're building.

Write a few lines about what you're working on or where you're stuck. I read everything myself. If I can't help, I'll say so and point you somewhere better.

Send me a message

The button opens a short form. Mail works too: niek@vanleeuwendigital.nl

I build the systems that find your next deal.
Before it's obvious to anyone else.