Several partners and no internal project lead with enough time or expertise. We take the wheel, see the project through to a good end, and then hand it back. Without imposing ourselves for good.
Three of the four moments when companies call us. If one of them sounds familiar, you're in the right place.
ERPEén systeem dat je kernprocessen zoals voorraad, boekhouding en orders samenbrengt., custom development, hosting. Each supplier works on their own piece, but nobody feels responsible for the whole. We become the central point of contact and push the project through to delivery.
Quotes waiting for 6 months, scope shifted three times, the original business caseDe onderbouwing waarom een investering de moeite en het geld waard is. has become unreadable. We create one overview, say what needs to happen and send a report in plain language every Friday.
Plenty of ideas, unknown priorities, no plan of action. We turn ambitions into a plan your team understands, your suppliers respect and the bank approves. Then we take on the delivery.
Your IT manager or CTO is doing 100 things at once. We step in temporarily as external lead, without claiming a permanent role. We only leave after consultation, once there's more focus and the right rhythm, and your team runs it themselves.
Listen first. Then structure. Then steer. Then hand back. Every step ends with a deliverable result. No open ending.
We talk to your team, your partners and, where possible, your customers. We read contracts, quotes and old project reports. We deliver one page with the scope, the risks and the first three priorities. No judgement, just understanding.
One schedule across all partners. A weekly reporting rhythm. An escalation path for blocking issues. RACI clarity where things were foggy. Your partners know again what to expect from whom.
We keep an eye on scope and budget, steer partners, make the technical calls when no partner can, and send a report in plain language every Friday. Honest about what is and isn't working, including about ourselves.
We only leave once your team has things back under control, including documentation that is actually correct. An honest evaluation of what went well and what didn't. Sometimes a coaching role carries on for another three months. Often that's no longer needed.
No need to worry that we'll replace your team or push your partners aside. We fill the one role that's usually missing: someone who makes sure the whole works.
The things you don't have the time or appetite for, and shouldn't have to.
The work only you can do. Except you no longer have to squeeze it in between other things.
I write the Friday report myself. Not because I like writing reports, but because it forces me to think clearly. If I can't explain it in two paragraphs, I haven't worked it out yet myself.
Industrial designer SPG Dry Cooling worked in silos with manual designs. We brought the partners together and guided the move to a central cloudSoftware en opslag die je via internet afneemt in plaats van op eigen servers. platform with parametric design. Three years later, design time has more than halved.
“With Make IT So's guidance, we brought our suppliers and internal teams together around one platform. Designs that used to take 9 months now take 4. And we keep automating further.”
Combined experience of Jan and Walter in CxO and PMO roles, in large and small organisations.
Total budget of the projects we have helped steer in recent years, from a few tens of thousands to multi-million euros.
How many people typically work on a project. Enough expertise, small enough to stay agile.
Five questions that keep coming up in a first conversation. Missing one? Call or email. We answer without a sales pitch.
Another question? Call us for half an hour
Usually when one of the four situations above sounds familiar: several partners without a lead, a project that drags on, no internal PM with time, or at the start of a big programme. Sometimes also when your IT manager is temporarily unavailable and you need someone to keep things on course.
We don't build ERP systems, don't write software and don't host anything. So we have no agenda to push you towards a particular partner or technology. Our only brief is your interest as the client, not a supplier's.
We work with what you or your partners already use. Usually Jira, Confluence, Microsoft DevOps, sometimes Miro. We have our own lightweight tool for hours and costs, but tools are secondary: the difference is in human alignment, not in which dashboard you open.
It depends on what your partners can handle and what the scope requires. Often hybrid: a long-term plan with agile sprints within each phase. We don't force a rigid straitjacket on a team that isn't ready for it. That's counterproductive.
No lock-in. Our contracts usually run in phases of 3-6 months. If you stop after a phase, you get a clean handover to your team or a successor. No black box. We don't hang around where we're no longer needed.
