Article by Krystal

Business consultants are often good at presenting ideas. That is partly the job. They need to explain problems clearly, structure recommendations and persuade decision-makers that a particular approach deserves consideration. A polished presentation can therefore be encouraging. It should not be the main reason for appointing someone. The more important questions concern what happens after […]

Business consultants are often good at presenting ideas.

That is partly the job.

They need to explain problems clearly, structure recommendations and persuade decision-makers that a particular approach deserves consideration.

A polished presentation can therefore be encouraging.

It should not be the main reason for appointing someone.

The more important questions concern what happens after the presentation. Does the consultant understand the business? Can they identify the real problem? Are their recommendations practical? Who will actually perform the work, and how will success be assessed?

Comparing consultants on these points can provide a much clearer picture than judging proposals by appearance alone.

Start With the Problem You Need to Solve

Before comparing consultants, define why you need one.

"Improve the business" is too broad.

The requirement may be reducing operating costs, improving a sales process, reviewing organisational structure, preparing for growth or addressing a specific operational problem.

The clearer the objective, the easier it becomes to assess whether a consultant has relevant experience.

It also reduces the risk of appointing someone based on an impressive general presentation that does not address the actual issue.

Write down the problem, desired outcome and important constraints before requesting proposals.

That gives each consultant a clearer brief and makes their responses easier to compare.

Look for Relevant Experience

Years of consulting experience can be useful, but relevance matters more than the headline number.

Ask what similar problems the consultant has worked on.

Industry experience may matter when the assignment depends heavily on sector-specific regulations, operating models or customer behaviour.

In other cases, experience solving the same type of problem across several industries may be equally valuable.

Ask for examples.

What was the situation? What role did the consultant play? What changed as a result?

The purpose is not to find an identical previous client.

It is to establish whether the consultant has dealt with challenges close enough to yours to bring useful experience to the assignment.

Pay Attention to the Questions They Ask

A consultant's questions can tell you a great deal before you appoint them.

Do they spend most of the meeting explaining their methodology, or do they try to understand your business?

Useful questions may cover current performance, previous attempts to solve the problem, internal constraints, customer behaviour and how decisions are made.

Be cautious when someone reaches firm conclusions before gathering much information.

A consultant may recognise familiar patterns from previous work, but your business still has its own circumstances.

Early conversations should involve enough investigation to show that recommendations will not simply be copied from another project.

Ask How They Diagnose the Problem

A good proposal should explain more than what the consultant intends to deliver.

It should give you some understanding of how they will reach their conclusions.

Will they interview employees?

Review financial or operational data?

Speak to customers?

Assess existing processes?

Compare performance across locations or business units?

The appropriate method depends on the assignment.

What matters is that there is a credible process for moving from the current situation to the recommendations.

If the methodology consists mainly of workshops and presentations without explaining what evidence will be examined, ask for more detail.

Separate Analysis From Assumptions

Consultants often begin with hypotheses about what may be causing a problem.

That can be useful.

Problems arise when assumptions are treated as conclusions before sufficient evidence has been gathered.

Ask how the consultant intends to test their initial view.

For example, declining sales could result from pricing, lead quality, weak follow-up, market conditions or several factors acting together.

A recommendation to restructure the sales team would be premature without understanding which of these factors is actually contributing to the problem.

Strong consulting work should be able to distinguish what is known, what is suspected and what still needs to be investigated.

Ask Who Will Actually Do the Work

The people presenting the proposal are not always the people who will complete the assignment.

This is particularly relevant when working with larger consulting firms.

Senior consultants may lead the initial meetings while much of the day-to-day analysis is assigned to other team members.

That arrangement is not necessarily a problem.

You simply need to understand it before appointing the firm.

Ask who will be responsible for the project, who will attend important meetings and how much involvement senior team members will have.

You are choosing the team that will perform the work, not only the person delivering the pitch.

Compare the Scope Carefully

Two consulting proposals with similar prices may contain very different amounts of work.

Review what each proposal actually includes.

Look at the number of meetings, interviews, workshops, reports and other deliverables.

Check which areas of the business will be assessed and which are specifically excluded.

Also consider what happens after the recommendations are presented.

Does the engagement end there, or is implementation support included?

A clear scope protects both parties.

It helps the business understand what it is buying and reduces disagreements about additional work later.

Understand the Deliverables

A long report is not necessarily a valuable deliverable.

Ask what you will have at the end of the engagement.

The answer might include an implementation plan, revised process, financial model, operating structure, research findings or specific recommendations.

Deliverables should relate directly to the problem being addressed.

Think about who will use them after the consultant leaves.

A sophisticated presentation that nobody inside the company can apply has limited practical value.

Useful consulting work should leave the business with enough clarity to act.

Look for Practical Recommendations

A recommendation can be strategically sound and still be unrealistic for the organisation expected to implement it.

Consider the resources available.

A small business cannot necessarily implement a system designed for a large corporation with dedicated teams and substantial budgets.

Ask how recommendations will account for your existing staff, technology, finances and time.

Good consultants should recognise constraints rather than treating them as inconveniences.

The objective is not simply to describe an ideal future state.

It is to identify changes the organisation can realistically make and explain what those changes require.

Ask How Implementation Will Be Handled

Some consultants specialise in analysis and recommendations.

Others remain involved during implementation.

Either approach can work, depending on what the business needs.

Clarify this before signing the agreement.

If implementation is included, ask what the consultant will actually do.

Will they manage parts of the project, train employees, monitor progress or provide periodic reviews?

If implementation is not included, establish who inside the business will take responsibility once the recommendations are delivered.

A plan without an owner can quickly become another document stored on a shared drive.

Consider Whether They Transfer Knowledge

Consultants should not necessarily make themselves permanently necessary.

For many assignments, part of the value lies in helping the internal team understand the problem and maintain improvements after the engagement ends.

Ask how knowledge will be transferred.

Will employees be involved in the analysis? Will processes be documented? Will relevant staff receive training?

This becomes particularly important when the consultant is introducing new systems or ways of working.

If the organisation cannot continue without ongoing external involvement, make sure that dependency is intentional rather than an unexpected result of the project.

Check References Properly

Ask for references from clients who received similar consulting services.

Then speak to them.

Do not limit the conversation to whether they were satisfied.

Ask whether the consultant understood the business, met deadlines and communicated clearly.

Find out whether recommendations were practical and whether the organisation actually implemented them.

Ask what happened after the engagement.

Did the work produce lasting changes? Were there unexpected costs? Would the client use the consultant again?

Specific questions provide far more useful information than a general request for an opinion.

Look Beyond Testimonials

Testimonials on a consultant's website can provide context, but they are selected by the consultant.

Independent feedback can add another perspective.

Depending on the type of consultant, you may be able to review professional profiles, published work, client references or other credible sources.

Look for consistency.

Does the consultant's stated experience match the type of work described elsewhere?

Are case studies detailed enough to explain the problem and work performed, or do they rely mainly on broad claims?

Evidence does not need to be extensive.

It should be specific enough to support the experience being presented.

Ask About Confidentiality and Conflicts

Consultants may work with several businesses in the same industry.

That can provide valuable sector knowledge, but it can also raise questions about confidentiality or conflicts of interest.

Ask how sensitive information will be handled.

If the project involves financial information, customer data, strategy or proprietary processes, make sure confidentiality expectations are clear.

Where appropriate, ask whether the consultant is currently working with direct competitors and how potential conflicts are managed.

The answer may depend on the nature of the assignment.

The important point is to address the issue before sharing sensitive information.

Understand the Fee Structure

Consulting fees can be structured in several ways.

A consultant might charge a fixed project fee, daily or hourly rates, a monthly retainer or another agreed arrangement.

Focus on what the fee covers.

Ask which expenses are additional, how changes to the scope will be handled and when payments are due.

A lower fee does not necessarily represent better value if the scope is much narrower.

Similarly, a higher price needs to be supported by relevant expertise, a stronger methodology or additional work.

Compare the complete proposal rather than the headline figure alone.

Be Careful With Guaranteed Outcomes

Consultants can control the quality of their analysis and recommendations.

They cannot always control the final business result.

Market conditions, management decisions, employee participation and implementation all influence what happens after an engagement.

Be cautious about guarantees that depend on factors outside the consultant's control.

Instead, ask how progress will be measured.

What indicators will show whether the project is moving in the intended direction?

Clear measures provide a more useful basis for accountability than dramatic promises about future results.

Check Whether the Consultant Challenges Your Thinking

A consultant should not disagree merely to appear independent.

They also should not simply confirm everything management already believes.

External advice has limited value if the consultant is unwilling to question assumptions when the evidence points elsewhere.

Pay attention to how they handle disagreement during early conversations.

Can they explain a different view without becoming defensive or dismissive?

Are they willing to change their own position when presented with better information?

Productive consulting relationships require enough independence to challenge weak assumptions while still working constructively with the people responsible for the business.

Consider How They Communicate Complex Ideas

Consultants often work with complicated information.

Their ability to explain it clearly matters.

Watch how they discuss your problem during the proposal process.

Do they rely heavily on jargon, or can they explain concepts in terms that relevant employees can understand?

This becomes particularly important when recommendations need support from people outside senior management.

A solution that cannot be explained clearly may be difficult to implement.

Good communication does not mean making every issue sound simple.

It means making the reasoning understandable without removing important complexity.

Agree on How Progress Will Be Reported

Do not wait until the final presentation to find out what has been happening.

For longer assignments, agree on how progress will be communicated.

This could involve regular meetings, written updates or milestone reviews.

The appropriate frequency depends on the size and duration of the project.

Progress reporting gives the business an opportunity to raise concerns and provide additional information before the work is complete.

It also reduces the risk of reaching the final presentation only to find that the project has moved in an unexpected direction.

Make Sure Internal Responsibility Is Clear

Consultants cannot implement meaningful change entirely from outside the business.

Someone internally needs to own the project.

That person may provide information, arrange access to employees, make decisions and coordinate implementation.

Define this responsibility before the work starts.

The consultant should also be clear about what they need from the business.

Delays in providing data or obtaining decisions can affect timelines and results.

A successful engagement depends on both sides understanding their responsibilities rather than treating the consultant as solely responsible for everything that happens.

Final Thoughts

A polished presentation can demonstrate that a consultant communicates well.

It cannot tell you everything you need to know before appointing them.

Look at the substance behind the proposal.

Define the problem clearly, compare relevant experience and ask how the consultant intends to investigate it. Understand who will perform the work, what the scope includes and what you will receive at the end.

References, fee structures, implementation support and knowledge transfer also deserve attention.

Most importantly, consider whether the consultant's approach fits the reality of your business.

The strongest proposal is not necessarily the one with the most impressive slides or the most ambitious promises.

A useful consulting engagement should leave the business with clearer information, practical decisions and work that can continue after the presentation is over.