The delivery of your new platform has slipped for the third time. Your developers say the old code is the problem, the vendor says the requirements were unclear, and next month you have to explain to the board where the budget has gone. Nobody is lying, but nobody has the full picture either. At a moment like that, an outsider with technical knowledge isn't a luxury. It's a way to establish what is actually going on.
You hire an IT advisor when a technical decision is expensive to reverse, when you have no independent opinion in-house, or when a project is stuck and it's unclear why. An advisor is most useful before the decision, not after it. If you already know exactly what needs to be built and by whom, you don't need an advisor, you need a builder.
Signs you need an advisor
Not every problem calls for outside advice. These are the situations we see most often in practice:
- You're facing a big choice. Choosing a platform, breaking up a monolith, moving to the cloud: decisions you can't simply undo. A second pair of eyes stops you from choosing based on the best sales presentation.
- Your team can't agree. When two senior developers argue for two different directions, you need someone with no stake in the outcome who can lay out the trade-offs.
- A project is stuck. Deadlines slip, costs climb and nobody can explain where the friction is. An assessment shows whether the cause is the architecture, the process or the requirements.
- You've inherited a system nobody understands anymore. The builder has left, the documentation is missing and every change feels risky. Before you start modernizing, you want to know what's actually there.
- You're about to buy or acquire something. In an acquisition or a major purchase, you want to know how sound the technology behind it is before you sign.
- The board wants a plan. You know what needs to happen technically, but you don't have a roadmap that executives can work with.
Do you recognize one or two of these? Then a conversation with an advisor makes sense. If you don't recognize any, you can probably solve it with your own team.
What does IT consultancy cover?
The term is broad, which makes it hard to compare quotes. With Isatis IT consulting, it comes down to four things:
- An independent technical assessment. An honest picture of your systems, your architecture and your development processes: where the real problems are and where improvements will make the biggest difference.
- Architecture and roadmap. A translation of an expensive decision into a plan with milestones and trade-offs, in language your board can work with.
- Project guidance. A consultant who joins your team and helps with a complex project, for example with technical choices or with keeping the project on course.
- A second opinion or technical due diligence. An independent judgment before a big decision, such as a purchase, an acquisition or a major contract.
The advice comes from engineers who build and run production systems themselves. That sets it apart from advisors who mainly make presentations: the recommendations are tested against how software behaves in the real world. You get the findings on paper, with the trade-offs included, so you can share them with people who weren't part of the conversation.
Hiring in outside expertise is common
If you wonder whether it's normal to bring in outside expertise for technical knowledge: yes. According to Computable, the Dutch government spent €3.7 billion on external hires in 2024, of which almost half, €1.8 billion, went to ICT professionals. That figure comes from the Jaarrapportage Bedrijfsvoering Rijk and covers all external hiring of ICT professionals, not just advice. Above all, it shows that even large organizations with their own IT department routinely bring in specialist knowledge from outside.
So the question isn't whether you hire in outside expertise, but what for. For a well-defined question with a clear outcome, such as an assessment or a roadmap, an advisor works well. For structural work that runs for months, a different arrangement is often a better fit.
When you're better off hiring something else
Honest advice also means admitting that sometimes an advisor isn't what you need. Watch out for these situations:
- You mainly lack capacity. You know what needs to happen, you just don't have enough hands. In that case you're looking for developers, not an advisor. You can read how that works in what staff augmentation is.
- The design is already settled. If the requirements, design and approach are clear, you can go straight to looking for a builder and don't need to pay for an extra round of advice.
- Your question is about choosing a platform. A question like 'do we build this on a low-code platform or have custom software made?' does need advice, but you can first explore the trade-offs yourself through low code versus custom development.
- The problem is organizational. If the project is stuck because nobody makes decisions or because requirements change every week, a technical report won't help much. Fix the decision-making first.
A good advisor will tell you this themselves. At Isatis, you'll hear it from us if we're not the right party.
How to prepare for the conversation
The sharper your question, the more useful the advice. You don't need to write a technical document; a few points are enough:
- Describe the problem in one paragraph. What is happening, since when, and what has already been tried? Write down what you see, not what you think the cause is.
- Name the decision and the deadline. Do you have to choose before the end of the quarter? Does the board need to approve a plan? An advisor works differently when there's a decision moment attached.
- Gather what already exists. Architecture diagrams, quotes, reports from previous vendors, an overview of the systems in use. If documentation is missing, just say so.
- Decide who will use the advice. Is it going to your board, your own developers or a vendor? That determines the language and level of detail of the report.
- Be open about sensitivities. Is there a vendor who won't be happy about a second opinion? Is there disagreement within the team? Then the advisor can take that into account.
At Isatis, you start with a 15-minute conversation. You tell us what you want to achieve and we tell you whether we can help. You're also welcome to ask questions beforehand. If you send a message through the form, we'll reply within 24 hours. In the form you can optionally choose an indicative, non-binding budget range; we don't quote fixed rates.
What good advice delivers
The risk with advice is that it ends up as a thick report that disappears into a drawer. That's why it helps to agree up front on what you want to walk away with:
- An honest, independent picture. Where are the real problems, and which improvements make the biggest difference?
- Trade-offs instead of a single answer. With technical choices there is rarely one right route. You want to know what each option delivers, costs and risks.
- A roadmap with milestones. A plan tied to your business goals that your teams can plan against.
- An explanation your board can work with. If only your developers understand the report, you only have half of what you need.
- The freedom to carry it out yourself. Good advice lets you choose: build it yourself, bring in another party or continue together with the advisor.
Isatis has been delivering software for more than 30 years and has completed over 100 projects. The people who advise also build themselves. You notice that in the practical side of the recommendations: they're based on what works in production, and that's what you're ultimately judged on as a client.
Frequently asked questions
What exactly does an advisor do?
At Isatis, this includes a technical assessment, an architecture with a roadmap, guidance within an ongoing project, and a second opinion or technical due diligence. You get the findings on paper, with the trade-offs included.
How much does an IT advisor cost?
Isatis doesn't quote fixed rates. In the contact form you choose an indicative, non-binding budget range: under €10,000, €10,000 – €25,000, €25,000 – €50,000, €50,000 – €100,000 or €100,000+. What an engagement costs depends on your question and is discussed afterwards.
What is the difference between IT and ICT?
ICT stands for information and communication technology and emphasizes the communication side, such as networks and telecom. IT is the broader term for everything to do with computers and software. In practice, most companies use them interchangeably, and it makes little difference for your search for an advisor.
How do you get started?
Book a 15-minute conversation and tell us what you want to achieve. We'll tell you honestly whether we can help. We answer a message sent through the form within 24 hours.
Still unsure whether you need an advisor or a builder? That often gets sorted out in a short conversation. Feel free to get in touch and tell us about your situation, no obligation.
About the author: Jeroen Penninx, Director and co-founder of Isatis.





