Nothing all at once. Everything in motion.
Every project starts with something your team already recognises, not with a master plan nobody understands any more. One first step, and a next one that follows logically from it. The O in our logo is a ring under construction, small segment by small segment. That's how we work in practice too.
How to tell whether we're a fit for you.
Short statements without marketing claims. If you keep nodding along here, give us a call.
Yes
Listen and read first, and only then propose.
No
Arriving with a fixed template and trying to squeeze your context into it.
Yes
One person responsible for the whole and one report a week.
No
Splitting the work to dodge risk until nobody is the point of contact any more.
Yes
Leaving once your team runs it themselves.
No
Making ourselves indispensable so you can never get rid of us.
Yes
Saying honestly when we don't know, or when the scope is unrealistic.
No
Bluffing to win an assignment and making up for it during delivery.
Call us for half an hour and we'll talk without a sales pitch.
Four steps in one project.
We listen first, then say honestly what we see, make sure it happens and then hand it back to your team. Every step ends with something you can hold in your hands, not with a vague promise.
Listen first
We talk to your team. We spend a day in the workshop or the office. We call your most important partner and ask what the quote was really about. We read old emails, last year's financial figures, project plans that were never finished. We don't judge. We try to understand. If you're an SME, we outline how to tackle digitalisation step by step in a separate guide. If you don't recognise our summary, we haven't listened properly and we'll say so ourselves.
Then say it honestly
You get one page with what we saw, what we think is missing and which three priorities we would tackle in the first months. Sometimes that's the project you had in mind, sometimes something else, and sometimes we tell you it's better to hire someone in-house. We aren't the right answer to every problem. If nothing in it surprises you, you didn't need that page, and we'll say that too.
Then make sure it happens
We set up one schedule across all partners, with a weekly rhythm and a clear path to escalate when something gets stuck. We guard scope and budget, steer partners and make the technical calls when no partner can. Every Friday we send a two-paragraph report, in plain language and honest about what is and isn't working, including about ourselves. If the delivery date slips by a month every month, we're not doing our job.
And then hand it back
We only leave once your team runs it themselves. You get documentation that is correct and actually gets read, and an honest evaluation of what went well and what didn't. Sometimes the collaboration turns into a coaching role for three months, but more often that isn't needed. And then we say so. If your team can't manage on its own after our last week, we left too early.
How do you know it's working?
We won't dangle a percentage in front of you about how much faster your project will be done. Nobody can measure that, because nobody knows how long it would have taken without us. Anyone who puts a number on it anyway has made it up.
What you can check, and early:
After four weeks there's one page with what's really going on. After eight weeks you know when it will be done. And that answer then stays the same, instead of slipping by a month every month.
That last part is the real difference. A project that keeps dragging on announces it again every month. So what you get from us isn't speed but certainty: you know where you stand, and you know it early enough to still do something about it.
On a project that had been dragging on for four years, a first finished release was there within three to four months. Not because people worked harder, but because there was finally one plan and someone aligning the partners.
Which role when depends on what the programme needs.
Sometimes we're the orchestrator, sometimes the coach, and sometimes the one who makes sure a product keeps growing after delivery. Never all four at once, and rarely in the same order.
When several partners work on a project together and nobody sees the whole, we become the central point of contact: one schedule, one report and one place where decisions get made.
When your internal project lead or IT manager has the role but isn't fully there yet. We sit alongside: we help prioritise, prepare for difficult conversations and feed back what we see. Not a replacement, but reinforcement.
After delivery, when a digital product is live and needs to keep growing. We help with choices about the next releases, supplier management for ongoing development, and make sure end-user feedback comes back into the plan.
When a process, team or organisation wants to stay permanently sharp. We set small movements going that we keep repeating, without leanVerspilling uit processen halen zodat enkel waardevol werk overblijft. evangelism or Kaizen worship. We simply look at what works less well today than last month, and what we'll do about it this week.
We don't replace anyone or push anyone aside, we add to what's there.
We're not your IT department. Nor are we the supplier who builds everything. We're the lead that makes sure your people and your partners work together towards your goal.
What we take on
The things you don't have time for, that aren't part of your core role.
- Leading the wholeOne place where partners, scope and schedule come together. You no longer have to set up three separate meetings to get one answer.
- Guarding scopeEvery change request goes through us first. Nobody quietly adds something you'll get the bill for later.
- Weekly reportingOne page with what worked, what didn't, and what needs to come next week. Not a 47-slide deliverable.
- Making the technical callsWhen partners can't agree on the substance, we help decide, neutrally and with no agenda of our own.
- Adoption and changeAdoption stands or falls with people. We support key users, write the communication and organise training, from kick-off to after go-live.
What you keep doing
Work only you can do. You no longer have to squeeze it in between other things.
- Decisions about your businessWe advise, you decide. Always in that order.
- Being visible at critical momentsYou're the sponsor. Kick-off, go-live, tough choices: that's where you need to be, not us.
- Your team's availabilityWe ask internal people for time for interviews, validation and key moments. You make sure they get it.
One concrete question is enough for a first conversation.
Four years, three suppliers, one governance rhythm.
At an industrial designer, it started with chaos around three suppliers and nobody owning the whole. Four months later there was one governanceDe afspraken over wie beslist, bewaakt en verantwoordelijk is. rhythm and the lead time for a design dropped from 9 to 4 months. Three years on, we fill a lifecycle role there for a product that keeps growing.
“Make IT So brought our partners together around one rhythm. What was chaos became predictable, and stayed that way even after the project officially ended.”
Questions that usually come up in a first conversation.
Missing one? Call or email us and we'll answer without a sales pitch.
Another question? Call us for half an hour
Do you work agile or waterfall?
It depends on what your partners can handle and what the scope requires. Often hybrid: a long-term plan with sprints within each phase. We don't force anyone into a rigid straitjacket. That's counterproductive.
How long does a typical project take?
The project phase lasts three to twelve months, sometimes followed by a lifecycle role that can run for years. We work in phases of 3 to 6 months, and after each phase you can stop or carry on.
What if we decide to stop somewhere halfway?
You're not tied to anything. Our contracts run in phases of 3 to 6 months, and if you stop after a phase you get a clean handover to your team or a successor. We don't hang around where we're no longer needed.
How many people do you put on one client?
Usually one of us as the main point of contact, possibly plus a second who reads along or joins at key moments. You won't get a team of five consultants: that doesn't fit how we work or the scale of SME projects.
How often are we in touch during a project?
You get a weekly report in plain language and a half-hour status conversation every month. In between we're reachable for anything urgent, not for what can wait until Friday. We don't want to fill your time, we want to save it.
Which tools do you use?
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 the names matter less than how we use them: the difference is in human alignment, not in which dashboard you open.