How a system build works.
One workflow at a time, from discovery call to handover. Scoped and priced up front, built on your tools, running in production before you pay the final invoice. This page has the mechanics.
I build everything myself. No juniors, no outsourcing. A few builds per quarter.
From first call to handover.
It starts with a free discovery call. If there's a fit, I design a system plan around your team's actual workflows and build it.
Free Discovery Call
30 minutes. I learn about your team, your challenges, and what you're trying to solve. No cost, no commitment. We figure out if there's a fit.
Workflow Mapping
If we are a fit, we map the workflow in detail with the person who does the work. Then I design a system plan built around your team's real situation. We review it together before moving forward. Nothing happens without your sign-off.
Build
I build it for you, we build it together, or something in between. It depends on what your team needs. Custom AI systems on your tools, with your data, for your workflows.
Handover
Your team walks away knowing what systems to use, how to combine them, and how to keep building on their own. Full documentation. No dependency on me.
What a finished system looks like.
Process is one thing. Here's the product: two real systems, what the situation was, what I built, and what the team runs today.
An AI email agent for a 4-person e-commerce team
Four people selling trailer parts across 24 EU country domains. The inbox was the bottleneck: every product question a catalog lookup, every reply written from scratch in whatever language the customer wrote in.
An email agent that owns the support inbox. It classifies every message, drafts replies in the customer's language grounded in a knowledge base and live shop data, and auto-sends only after a 13-step safety gate passes. Anything that doesn't pass lands in a draft inbox with the reason logged.
The team reviews drafts in Dutch from their own admin panel. Categories, tripwires, knowledge base, prompts: all editable without touching code. A 10-15 minute reply is now a 30-second check.
I don't push tools.
Claude, ChatGPT, n8n, Make, custom scripts. I've worked with most of them. I won't walk in and tell your team to use a specific one. The point of the mapping is to understand what fits:
Your systems
What tools does your team already use? What integrations exist? We build on what's there. No rip and replace.
Privacy
What data are you working with? What can go through an API? We figure out the boundaries before touching anything.
Team skill level
How technical is the team? What's realistic for them to maintain after I leave? No point building something nobody can run.
Budget & scale
What makes sense for your volume and budget? Some tools are free. Some aren't worth the price. We pick what fits.
Three ways we can work together.
Pilot Build
Fixed scope, 2-4 weeks. We pick one workflow and I build it end to end, in production.
If the pilot doesn't run in production, you don't pay the final invoice.
- Built on your real workflow
- Runs in production before anything bigger
- Fixed quote once your workflow is mapped
- Good first step when the risk needs to stay small
Full System Build
Custom AI systems built on your tools and your workflows. Scoped, built, documented, and handed over.
Fixed quote once your workflow is mapped
- Discovery and workflow mapping
- Custom system built on your tools and data
- Team training included
- Full documentation for everything we create
- Your team runs it without depending on me
- You own the system, accounts, and docs
Team Training Day
One day with your team. I teach them how to build and run AI workflows themselves, on their real work, not slides.
One day with your team, fixed price
- Built around your team's real tasks
- Hands-on workflows, not a generic presentation
- Your team leaves with working examples
- Useful when you need capability before a bigger build
It starts with a free conversation.
A quick call where I learn about your team, your challenges, and what you're looking for. No commitment. If it's a fit, I put together a plan. If not, I'll tell you.
Book a free discovery callNo pitch. Fixed scope before anything starts.
Not theory. Systems running in production right now.
- TrailerPlus: an AI email agent answering customer support across 24 countries
- Built a full-stack AI prompt gallery for Plus AI, a product with 1M+ users
- Built PPCOS, a system used by 2000+ Google Ads experts worldwide
- An SEO content engine writing category pages end to end from 3M rows of real search data
Real projects. Real results.
Here's what these systems look like in practice.
An AI Email Support Agent for E-Commerce
A Laravel + Filament email agent that classifies, drafts, and auto-sends customer support email. Multilingual. 13-step safety gate. Running inside a Dutch trailer-parts shop that ships to 24 EU countries.
PPCOS. An AI Operating System for Google Ads
29 Google Ads skills and a setup course that takes a marketer from never opening a terminal to running their first AI agent the same day. Live inside a 2200+ member PPC community.
What people say.
Questions you probably have.
Look at the ones running: an AI email agent answering customer support for an e-commerce team across 24 EU countries, an SEO content engine writing category pages from 3 million rows of real search data, order processing, reporting. Yours will look like your workflow, because that's what it gets built on.
A pilot build is fixed scope and usually 2-4 weeks. A full system build typically runs 3-4 weeks once the workflow is mapped. The timeline is part of the proposal, so you know it before anything starts.
Depends on the system. I've built automations that cost less than €1,000 and full systems that run five figures. The price comes after we've mapped your workflow and I know exactly what I'm building: a proposal with a fixed scope and a fixed price. The scope-lock guarantee means that number doesn't move. The pilot build exists so the first number stays small.
We agree on exactly what you get before I write a line of code. The price is locked to that scope. If the final delivery doesn't match what we agreed on, you don't pay for what's missing. No surprise costs, no scope creep.
They don't need to be. The whole point of the discovery call is to understand their skill level and build around it. If your team can use Google Docs, they can use the systems we set up.
Whatever fits your team best. I've worked with Claude, ChatGPT, n8n, Make, custom scripts, and more. The discovery call is where we figure out what makes sense for your situation. I don't push any specific tool.
That's the whole point. I don't build things that need me to keep running. Everything comes with documentation and training. You won't depend on me.
I've built systems across e-commerce, SaaS, lead gen, B2B services, and content. Most of my clients sell trailer parts, rent equipment, or run agencies, not software. The principles are the same: understand your workflows, find where AI fits, pick the right tools.
Yes. The process is the same: discovery call, scope, build, handover. For larger teams, we might need more discovery time and a phased rollout. Let's talk about it in the call.
Let's start with a free call.
A quick discovery call to understand your team and your challenges. If it's a fit, I put together a plan. If not, I'll tell you straight.
Book a free discovery callI build everything myself. No juniors, no outsourcing. A few builds per quarter.