Example result
Chance of completing 67 items by October 15
Dec 21, 2026
most realistic date
10 weeks
behind schedule
done (%)
Your developer said August. Your lead said September. You told the client October, because you've been here before. Three estimates, a safety margin, and a number for the client. You called it planning because it's what it's always been called.
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.
Sound familiar?
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.
Delivery risk scan
Connect Jira read-only, pick the project that's keeping you up, and see the probability it hits the date you committed to. Three minutes, from your actual team's data. No call, no slides, no signup.
Example result
Chance of completing 67 items by October 15
Dec 21, 2026
most realistic date
10 weeks
behind schedule
How I help
If you don't have a delivery system yet, start with the Kickoff. If you have one that's not holding anymore, go to the Realign. No long-term lock-in either way.
Most early teams don't have a delivery system. They have a founder who remembers everything.
Two days on site. A working system when I leave, not a document.
What's in it
What your team walks out with
Most teams I work with have the right people. The system wrapping them was built for a smaller problem.
Eight weeks embedded. No deck when I leave. Your team commits to what they can ship, and ships it.
What's in it
What your team walks out with
Your team has people and momentum but no structure yet. You've been the system: holding the priorities, remembering the commitments, sitting in every meeting. Two days, concrete changes, the team runs without you in every conversation.
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 the product is wrong, delivering it faster won't help. You need product strategy, not delivery consulting.
You want a framework installed and someone gone by Friday. I don't install Scrum or SAFe. I rebuild how your specific team moves.
You need someone in the delivery seat for six months or longer. That's a fractional hire, not this.
"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.
How it works
A straightforward process that respects your time.
Why me
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.
Direct, not diplomatic. I'll tell you what's broken on day one. Not in a slide deck three weeks later.
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.
Results
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 grounded in user evidence instead of guesswork. 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.
About me
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 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 diagnoses, two services, not two tiers. Delivery Kickoff (2 days, €5,000, fixed price, on-site or remote) is for early teams that don't have a delivery system yet. A founder is holding the priorities and commitments in their head. Two days on site. By day two: a board, a standup, a review, a backlog the team agreed on in the room. The team runs without the founder in every conversation. Delivery Realign (8 weeks embedded, €20,000, fixed price) is for teams whose system stopped holding. They've tried retros, new boards, new standups, and the fix faded after a few weeks. Eight weeks rebuilding end to end: intake, estimation, commitment, review. A delivery rhythm that survived eight weeks of real work.
Free self-serve scan at bart.consulting/scan: a team can connect Jira read-only and get a probability-based forecast for their deadlines in about three minutes. No call required. How it works: the scan takes the team's real cycle-time and throughput history, models each active commitment, and runs 10,000 Monte Carlo simulations to produce a probability of hitting each deadline — instead of a single-point estimate that hides the range. Deeper explanation at bart.consulting/how-the-scan-works. Good way to see the numbers before deciding whether a Kickoff or Realign fits.
Kickoff fee applies as credit toward a Realign within four weeks if the team decides to continue.
Where: Belgium and the Benelux. On-site or remote.
Not a fit if: (1) the problem is what to build, not how to ship it. That's product strategy, not delivery. (2) You want a framework installed and someone gone by Friday. I don't install Scrum or SAFe. I rebuild how your specific team moves. (3) You need someone in the delivery seat for six months or longer. That's a fractional hire, not this.
Past results: Cut an 18-month implementation to 6 months at Factry. Contributed to 10x visitor growth at Spotto through evidence-based prioritization. More at bart.consulting/case-studies.
Contact: bart.consulting/contact