Skip to main content
Legia

IT Support & Consulting

When Does a Company Need an IT Consultant?

An IT consultant is most useful before the budget is spent: when a vendor proposal is hard to judge, systems overlap, or the technology plan has no clear direction.

SEO and Content Specialist

4 min read

A whiteboard with sticky notes

Short answer: a company needs an IT consultant most before a large budget is spent: when it receives a vendor proposal that is hard to judge, when subscription costs and systems feel overlapping, when it is drawing up a technology plan for the next few years, or when it has no internal person who can give an independent view. A good consultant hands over a recommendation document you can use with any vendor.

In many companies, technology decisions are made from vendor presentations. That is natural, since the vendor knows its own product thoroughly. The problem is that the vendor also has an interest in what it recommends. An IT consultant fills that gap: giving a view from your side, before money and time have been spent. This article covers when that view is most valuable, and when it is not actually needed.

Seven situations where an IT consultant is most useful

SituationQuestion to answer
Receiving a large vendor proposalAre the scope, timeline, and cost reasonable? What can be removed?
Subscription costs keep growingWhich systems overlap, and which can be stopped?
An old system is starting to fail oftenRepair it, replace it, or leave it until a set date?
Preparing next year’s budgetWhich technology work matters most, and what is the estimated cost?
Choosing between several vendorsWhat criteria are fair for comparing them?
Expansion, a merger, or opening a branchHow will existing systems follow the organizational change?
No senior IT person in-houseWho can give an independent view for the board?
Illustration: IT consulting

A second opinion on a vendor proposal

This is the most compact form of consulting and often the quickest to pay back. The consultant reads the proposal you received and judges whether the scope matches the need, whether any work is unnecessary, whether the time estimate is realistic, and whether any costs have not been mentioned, such as licenses, maintenance, or integration. The result can be a smaller proposal, a clearer one, or a decision not to proceed.

A review of running systems

Over time, companies accumulate applications and subscriptions: two applications for the same thing in different divisions, licenses for employees who have left, and old systems that are still paid for because no one dares to switch them off. A systems review maps what is used, for what, at what cost, and which parts overlap or are risky. The result is material for saving money and reducing risk at the same time.

Technology plan and budget

Without a plan, technology work tends to be reactive: decided when a problem appears, not when there is time to weigh options. A one-to-three-year plan arranges the work in order of impact and dependencies, along with estimated costs, so a budget can be proposed on a clear basis.

What a good result looks like

A useful consulting result is not a presentation that ends in a meeting but a document that can be acted on. At a minimum, it contains:

  • a map of the current state: which systems, for what, at what cost;
  • several options, each with its cost, time, and risk consequences;
  • a priority order with the reasons;
  • a short summary that can be brought to a board meeting.

If you cannot explain the recommendation to someone else after reading the document, the document is not finished.

When an IT consultant is not needed

Not every decision needs a consultant. For small purchases, common needs served by mature products, or decisions that are easy to reverse, the cost of consulting can outweigh the benefit. If your internal team already has a senior person who understands the systems and is not tied to a particular vendor, a second opinion may only need to be requested for the biggest decisions.

How to choose a consultant without a conflict of interest

Many IT consultants also sell products or build services, Legia included. That is not automatically bad, but it needs to be handled openly. Ask these questions before starting:

  1. Does the recommendation include options that do not involve the consultant itself? For example, using an off-the-shelf product, continuing with the existing system, or postponing.
  2. Does the recommendation document belong to you and can it be freely taken to another vendor?
  3. How is the consulting billed? Per engagement with a written scope is easier to control than hourly with no limit.
  4. What form does the output take? A document with the reasoning behind each recommendation is more useful than a presentation with no attachments.
  5. Who will be interviewed? A consultant who only talks to management often misses the problems faced by the people doing the work.

How Legia handles it

In the IT Consulting service, Legia handles four kinds of work: a second opinion on vendor proposals (generally 1 to 2 weeks), a review of running systems, a technology plan and budget (the systems review and plan generally take 3 to 6 weeks), and technology and vendor selection. Consulting is billed per engagement with a written scope. Because Legia also builds and manages systems, the recommendation document always includes options that do not involve Legia, and the document is entirely yours.

If the decision you are facing is adding team capacity, the article Dedicated Team, Project Outsourcing, or In-House Hiring? covers the options.

Frequently asked questions

What is the difference between an IT consultant and a system integrator?

An IT consultant helps decide what needs to be built, fixed, or stopped. A system integrator connects existing systems so they work together. The two often come in sequence, but they answer different questions.

Does a small company need an IT consultant?

Usually only for big decisions, such as choosing the company’s core system or judging a proposal of significant value. For everyday needs, IT support is often more suitable.

What should be prepared before the first session?

A description of the problem or the pending decision, the vendor proposal if there is one, and a rough list of the systems and subscriptions in use today.

Other services in the same area are on the IT Support & Consulting page.

Category IT Support & Consulting

Keep reading

Related articles

All Articles