← All cases and insights Knowledge base →

ARTICLE · Research

What management consulting is — in plain words, without the gloss

Nikita Nechaev · 16.07.2026 · 6 min

In the simplest possible terms, management consulting is when a company hires an outside specialist to help solve a management problem it cannot crack on its own — for lack of experience, time, or an outside perspective. That sounds banal, which is exactly why the profession is shrouded in so much fog: the word "consulting" is used to sell just about anything, from lectures and "tracking" sessions to outsourced bookkeeping. Below is what the word actually means, how a consulting project works from the inside, and how to tell a consultant from someone who merely talks well — in five minutes flat.

A definition without the corporate-speak

Management consulting is work on problems that sit squarely with the CEO: where to grow, why profit is falling, how to restructure processes or the team, whether to buy a competitor. These problems share three traits. First, the cost of error is high — the decision is hard and expensive to reverse. Second, no one inside the company has quiet time for them: day-to-day operations always shout louder. Third, the view from inside is distorted — every executive sees the problem from their own chair, and those pictures do not match.

A consultant is not hired for being smarter than the team. The advantage lies elsewhere: they have seen dozens of similar situations across different companies, they have no past decisions to defend, and they have dedicated time to work on this one problem and nothing else. My favorite definition of the profession: "a person who is paid to tell the truth that no one inside the company can — or dares to — say out loud."

How a consultant differs from everyone they get confused with

From an outsourcer. An outsourcer takes over a function and performs it for you — keeps the books, runs the advertising. A consultant does not take the function over: they work out how it should be set up and hand the solution to your team. An outsourcer leaves you with a task completed; a consultant leaves you with a changed system and people who understand why it now works the way it does.

From a freelance expert. A freelancer is strong at their craft: they will write a promotion strategy or build a financial model. But they work within the brief they are given. A consultant starts earlier — by checking whether you are solving the right problem in the first place. In my experience, in roughly half of all projects the client's initial request and the real problem do not match: they come in asking to "lift sales," while the bottleneck is in production, which cannot keep up with existing orders.

From a mentor or a coach. A mentor shares experience, a coach asks questions — both work with a person. A consultant works with a company: the project has a measurable outcome, a plan, and a deadline. These are different tools, and a good consultant will tell you honestly when what you need is not a consultant (we have a breakdown on the blog — mentoring versus coaching).

From a "tracker" and the infobusiness crowd. This one is the easiest: ask who is accountable for the result, and with what. A consultant signs up to specific project outcomes and shows similar completed projects, client contacts included. If what you are being sold instead is "energy," "leveling up," and group calls — that is a different market.

How a consulting project works from the inside

A project almost always consists of four phases, whatever the proposal says.

Diagnosis. The consultant assembles the picture: interviews with executives and employees, numbers from the books, sometimes customers and the market. The goal is to find the root problem, not the symptom. This is the most underrated phase: to the client it feels like paying for "conversations about things we already know." In reality, this is where the project pays for itself or fails — treating the wrong disease is expensive.

Solution. Hypotheses, calculations, scenarios, a choice. Good practice is to develop the solution together with the client's team rather than deliver a "here is how it should be" binder from another world. Binders written without the team end up on a shelf — I have seen more of those shelves than I would like.

Implementation plan. Who does what, in what order, and what counts as success. The difference between a report and a result lives in this document.

Follow-through. The best projects do not end with a presentation: the consultant stays close through the first weeks of implementation, when the system resists change the hardest.

If the project in the proposal consists only of the first two phases, it is still consulting — but the deliverable will be knowledge, not change. Sometimes that is enough. You just need to understand what you are buying.

Three myths that keep companies from using consulting

"The consultant will tell us what we already know." Sometimes yes — and that is a perfectly good outcome. A hypothesis confirmed by outside analysis is the permission to act that the team has been missing for months. More often, though, the diagnosis shifts the picture: the problem turns out to be somewhere other than where it hurts. The pain is felt in sales, while the cause sits in the product or the processes.

"This is only for large corporations." Historically true; today it is not. Mid-sized businesses are the core clients of small consulting teams, and for them the effect is often more visible: in a company of 100 people, one right management decision shows up in the profit and loss statement within a quarter.

"The consultant will leave and everything will fall apart." It will — if the project was built around the consultant. The mark of professional work is a boring one: after the project, the company is left with processes, metrics, and people who know how to use them without the author.

How to tell a consultant from a stage prop

My short checklist from practice. A real consultant asks more questions than they answer — especially in the first hour. They turn a project down if they cannot see how they can help, and say so plainly. They show similar projects and do not hide their clients. They bring up implementation before you ask. And they never promise a result before the diagnosis — because promising a cure before running the tests is what charlatans do.

If you want to dig deeper: we have a breakdown of the seven signals that it is time to bring in a consultant, a guide on how to choose a consulting firm, and an honest conversation about the ROI of management consulting.

Short answers

What is consulting, in plain words?
It is bringing in an outside specialist to solve a management problem: diagnosing the issue, developing a solution, and planning the implementation. Unlike an outsourcer, a consultant does not take over a function — they change the system and hand it back to the team.

How is consulting different from outsourcing?
An outsourcer does the work for you on an ongoing basis. A consultant works out how the system should be set up, implements the change together with the team, and leaves.

What does a management consultant do?
They run the diagnosis (interviews, analysis of the numbers), find the root problem, develop the solution together with the team, draw up an implementation plan, and support the first steps.

Who needs management consulting?
Companies facing a management problem with a high cost of error: growth has stalled, margins are falling, processes do not scale, or a major change lies ahead.

Shall we discuss your task?

Get in touch →