Your developer says August. Your lead says September. You tell the client October, because you've been here before. Everyone was guessing. Everyone called it planning.
I look at how your team actually ships and give you a number for each deadline: the real probability it lands on time. No more guessing. Even when the number is uncomfortable, at least you can walk into the next meeting with something real.
And this has been going on for months. The team isn't getting bigger. Every missed week is a week you can't get back. You know the fix isn't another team meeting about how to fix the team meetings.
Not a vague status update. A probability-based forecast built from your team's real delivery data. For each commitment: the likelihood of hitting the deadline, what's driving the risk, and what to do about it.
Every forecast is based on 10,000 simulated outcomes using your team's actual completion rates — not averages, not gut feel. The output tells you things like "this has a 28% chance of landing on time, and here's why."
Click the images to view in high resolution
Start small with a hands-on kickoff, or go deeper with an embedded engagement. No long-term lock-in required. Even a small team missing deadlines by a month costs more in wasted salary than the kickoff below.
For teams that spend more time in meetings than doing the work
Your team has the people. What's missing is a way of working that doesn't rely on you being in every conversation. I spend two days with the team — mapping how work actually moves, fixing the meetings that aren't working, and setting up a structure that fits. You walk out with something the team can follow on their own.
Less than what one wasted meeting per week costs your team in a quarter.
For teams that have had this conversation before
You've reorganized the board before. You've tried new standups. It worked for a few weeks, then everything drifted back. The Reset is eight weeks embedded — long enough to set things up, coach the team through real problems, and prove it works with data before I leave.
Less than two months of a problem that's been costing you all year.
Your team has people and momentum but no structure. Or you had a process that worked once and doesn't anymore. You need a reset, not a consultant for months. Two days, concrete changes, you run with it.
You've tried to fix this before. It worked for a bit. Then you were back in the same meeting wondering the same thing. You need someone embedded long enough to make the changes stick — and to prove it worked.
Your problem is what to build, not how. If you're building the wrong thing, delivering it faster won't help. You need product strategy, not delivery consulting. Also: if you need someone to attend steering committees and produce slides, I'm not your person.
"My dev lead could probably build something like this with AI in a week."
The report, maybe. The thinking behind it, no. I spend the first days understanding how your workflow really works and cleaning the data before I run a single number. Without that step, you get a confident answer based on the wrong inputs — that's worse than no answer. And you don't audit your own books. An outside perspective with no stake in any specific date just sees things differently.
A straightforward process that respects your time.
Not here to introduce a methodology or sit in your meetings for six months. I fix what's broken and leave.
I've led product delivery in startups and scale-ups. I know the difference between what works in a textbook and what works when your team is under pressure and your roadmap keeps changing.
I'll tell your team what's broken on day one. Not in a slide deck three weeks later. If a meeting is wasting everyone's time, we'll fix it in real time — not write a report about it afterwards.
My engagements are designed to end. I coach your people, transfer the process, and step back. If you still need me after six months, I haven't done my job.
I've worked with teams across Belgium and the Benelux. I know the scale, the constraints, and the culture. Available on-site or remote.
Previous client implementation took 18 months and nearly broke the team. I went to the factory floor, talked to machine operators, prototyped with real users, and turned a one-hour daily meeting into 15 minutes. The next comparable implementation took 6 months. Three times faster.
Read the full story →The team was shipping, but there was no structured way to check whether any of it matched what users needed. I added what was missing: regular contact with real users and a process where decisions were based on evidence, not opinions. The team stopped building the wrong things. That focus — shipping fewer, better features — contributed to the platform growing from 10,000 to over 100,000 monthly visitors over two years.
Read the full story →I can't write a single line of code and I don't understand a word the development team says. But thanks to Bart, everyone knows what's being built, why, and when it's ready.
He took the time to understand our complex environment and our constraints to propose the best solution for us.
He sees the unique strengths of his colleagues, helps them grow, and brings them together around shared goals in a way that feels natural.
I started as a developer. I know what it feels like to sit in a meeting with no clarity on why you're building what you're building. That frustration pushed me into product and delivery work — not to manage people, but to build the kind of environment where a team can actually focus.
I did this for almost 10 years at companies like Factry and Spotto, on the boundary between deciding what to build and actually shipping it. That's where most things fall apart.
Based in Ghent. When I'm not doing this, I'm probably outside walking my Weimaraner, da Vinci.
You've scrolled past pricing, case studies, and testimonials. If you're still here, it's not because you're bored. 30 minutes. No pitch. Just the honest version of what's going on and whether I can help.
Book a free 30 min callWant to share this internally? Here's a message you can copy.
I want to bring someone in for our delivery problem. He runs simulations on your actual data and gives you the real chance of hitting each deadline. I'd like to book a call with him — have a look: bart.consulting
Who: Bart Pinnock, solo delivery consultant based in Ghent, Belgium.
What: I help tech teams of 5–50 people ship predictably. I run Monte Carlo simulations (10,000 runs) on real workflow data to forecast the probability of hitting each deadline. Then I fix the process: board structure, meetings, priorities, handoffs.
Two services: Delivery Kickoff (2 days, €5,000, fixed price) and Delivery Reset (8 weeks embedded, €20,000, fixed price). Kickoff fee applies as credit toward a Reset within four weeks.
Where: Belgium and the Benelux. On-site or remote.
Not a fit if: the problem is what to build, not how to ship it. That's product strategy, not delivery.
Past results: Cut an 18-month implementation to 6 months at Factry. Contributed to 10x visitor growth at Spotto through evidence-based prioritization.
Contact: bart.consulting/contact