The Executive's Guide to Hiring a Management Consultant

The single most useful thing you can do before calling a consulting firm is describe the problem in one plain sentence: "Revenue is up but cash keeps getting tighter," "our operations can't keep up with our sales team," "I don't trust our own numbers anymore," "I need someone to run finance for the next year while we find a full-time hire." The sentence you land on points toward the kind of help you actually need.

Consulting is a field of specialists wearing a generalist's business card. A firm built for cost-cutting turnarounds is not who you want scoping a market-entry plan, and a growth-strategy team is not who should build your 13-week cash model. Generalist firms like Redpath Consulting Group cover several of these under one roof, but even then, the first question a good partner asks is the one you should ask yourself first — what, specifically, is the problem?

• Something is underperforming — revenue, margin, cash — usually points to a diagnostic engagement.
• Something needs to be built — a forecast, a KPI system, a go-to-market plan — usually points to a build-focused engagement.
• A seat is empty or overloaded — a CFO who left, a founder doing too much — usually points to fractional leadership.

Owners wait too long far more often than they call too early. The instinct to solve it internally first is usually right — until the same problem is still on the agenda six months later, quietly costing more than a diagnostic would have. Outside help earns its fee fastest when a problem is real, expensive, and stuck: the team closest to it knows something is wrong but doesn't have the bandwidth, the data, or the outside perspective to fix it while also running the business.

A useful test: if you've discussed the same problem in three consecutive leadership meetings without a plan that survived contact with the next one, that's the signal. It doesn't mean the problem is unsolvable internally — it means it needs dedicated hours and an outside read that your team, understandably, doesn't have space for on top of their day jobs.

The rule of thumb: if the cost of the problem staying unsolved for another quarter is larger than the cost of a diagnostic, it's worth the working session. A good consultant will tell you plainly if the timing isn't right yet.

Consulting pricing has a reputation for meters that never stop running, mainly because so few firms explain which model applies before the work starts. There are really three, and the right one depends on the kind of engagement.

• Fixed-fee diagnostic — a defined scope and price for the assessment phase: findings, root causes, and a roadmap, quoted before work begins and usually credited against a follow-on engagement.
• Fixed monthly fee — common for execution sprints, scoped to deliverables and KPIs rather than hours. The fee is the fee; overruns are the firm's risk, not yours.
• Fractional retainer — common for embedded leadership roles, priced per day-per-week committed, with a minimum term and a defined notice period on both sides.

What you should never accept going in is vagueness. Before you sign anything, you're entitled to know which model applies, roughly what it will cost, and what happens if the engagement runs longer than expected. If a firm won't put the arrangement in writing before work starts, that's your answer.

A good working session is not a sales pitch — it's a scoping conversation. An experienced partner hears the problem as you see it and gives a candid first read: whether it's worth a diagnostic, roughly what that would look like, and what it would cost. You should leave better informed even if you never sign anything.

Come with whatever you have — a P&L, a board deck, a spreadsheet you don't trust anymore — but don't delay the call to assemble it. Plenty of sessions start with nothing more than "something is off and I can't name it yet." Bring your real questions instead:

• Who, specifically, will do the work day to day?
• How will we be billed, and what's your honest estimate of the total?
• What does a realistic range of outcomes look like, good and bad?
• What will you need from my team, and how much of their time?

A mutual NDA covers the conversation whether or not you continue, so you can speak freely about numbers you wouldn't put in an email.

When you decide to move forward, you'll be asked to sign an engagement letter — the document that governs scope, fee, and expectations. It's worth twenty minutes of careful reading, because it answers the questions that cause the most friction later.

Look for four things: the scope (exactly what's included and what isn't), the fee (the model, the amount, and what triggers a change order), the KPIs (the numbers that will define whether the engagement worked, agreed before work starts, not after), and data handling (where your information lives, who can see it, and what happens to it at handover). A clear engagement letter is a sign of a firm with nothing to hide. If yours raises questions, ask before you sign, not after the diagnostic starts.

At many firms, the partner who impresses you in the pitch is not the person who does your work — the engagement gets staffed down to a team of analysts you've never met, and the partner reappears only for the final presentation. That isn't automatically wrong; analysts do real, careful work. But you deserve to know the staffing model before you sign.

Ask directly: who runs the diagnostic day to day, who's in the room for the hard conversations, and how much partner time is actually on this engagement? At a firm built around senior operators, the answer should be a named partner who stays engaged from the first working session through handover — not a rotating bench you meet once. On decisions that affect payroll, pricing, or a sale, continuity of judgment matters more than a firm's logo.

Signing the engagement letter is the start, not the finish. A well-run engagement has a rhythm: a diagnostic phase that's mostly listening and data-gathering, a findings presentation you should be allowed to push back on, an execution phase with KPIs reported on a fixed cadence, and a handover that transfers real capability — not just a binder — to your team.

Your role as the client is smaller than it feels at the outset but genuinely matters: make data and people available promptly, be honest about the politics and history the consultant can't see from outside, and treat the KPIs set in week one as the actual scoreboard, not a formality. Diagnostics typically run about three weeks; execution engagements run sixty to a hundred twenty days. A firm that gives you an honest timeline up front — and flags it clearly if something slips — is doing the job right.

In a metro this size, local knowledge changes outcomes more than executives expect. A firm that works the Minneapolis area regularly knows the difference between a logistics operation on one side of town and a professional-services firm on the other, has a realistic sense of the local labor market for the roles you're trying to fill, and can be on your floor the same week a question comes up rather than flying in once a quarter.

As you choose, weigh the good signs against the warning ones:

• Good signs: a fixed-fee diagnostic before any larger commitment, KPIs agreed in writing before work starts, a named partner who stays on the engagement, and references from real local clients you can actually call.
• Red flags: guaranteed outcomes stated before any diagnostic, pressure to sign a long-term retainer immediately, reluctance to put fees or KPIs in writing, and a partner you can never reach once the contract is signed.

Trust the working session. A firm that tells you honestly when the timing isn't right, or when the problem isn't one they should solve, is usually the one that will tell you the truth once real money is on the table — and that, more than any pitch deck, is how an operator should choose.