LinkedIn Post Ideas for Consulting Partners

I lost a seven-figure engagement over one slide. The lesson, in the end, cost far less than the deal did. The slide was our executive summary, positioned first in the deck per our usual template. It led with our firm's credentials and methodology before addressing the client's specific situation — a sequencing choice that, in hindsight, read to that particular CEO as us talking about ourselves before proving we understood his problem. I watched his attention leave the room somewhere around slide two. The deal, which I'd been genuinely confident about heading in, was gone within the week. I now pressure-test every executive summary against one question before any pitch: does the first slide prove we understand their specific problem, or does it prove we're credentialed? If it's the latter, it moves to slide six. Partners rarely admit losses like this publicly. I'm sharing it because the fix was cheap and the lesson wasn't.

The best business development I do isn't business development at all. It's a project delivered well two years ago. Looking honestly at where my current book of business actually originates: roughly 65% traces back to former clients, either returning directly or referring someone in their network, sometimes years after the original engagement closed. Conference networking, cold outreach, formal BD activities — real, and worth doing, but they account for a much smaller share of my actual pipeline than the firm's official BD metrics would suggest matters most. The implication most junior partners underweight: the quality of delivery on your current engagement is your highest-leverage business development activity for work you haven't even pitched yet, three years out. I've started treating every engagement's closing conversation as seriously as a pitch, because in a very real sense, for the alumni relationship it either builds or fails to build, it is one.

How I prepare for a first meeting with a CEO, my actual pre-meeting ritual, not the version I'd present in a training deck. I read the last four earnings calls, listening specifically for language they repeat across calls — repeated phrases usually signal what's actually keeping them up at night, more reliably than the official strategic priorities slide. I review board composition, looking for who else has influence in that room and what their backgrounds suggest they'll push back on. I walk in with exactly one hypothesis, stated plainly, about what I think their real problem is — not a menu of possibilities, one specific point of view I'm willing to be wrong about in the room. Being wrong, stated confidently and then updated live based on their reaction, builds more credibility in a first meeting than a cautious, hedge-everything opening ever has for me. Aspiring partners study posts like this closely, because this ritual is rarely taught explicitly anywhere in a firm's formal training.

Our proposal win rate by source, rough numbers but directionally solid, because every partner knows this and almost none of us write it down. Referral-sourced proposals: roughly 55% win rate. RFP responses, even well-crafted ones: roughly 11% win rate. Cold pursuits we initiated ourselves: roughly 8%, and most of those wins came from relationships that predated the formal pursuit by years. Referrals convert nearly five times better than RFPs, and yet I'd estimate most partners, myself included in earlier years, still spend a disproportionate share of BD hours on RFP responses relative to relationship cultivation, largely because RFPs feel like tangible, trackable activity in a way relationship maintenance doesn't. Rising consultants reading this: the map of where to spend your energy is right here in these numbers. Most firms just never share them out loud, so everyone re-learns this the expensive way, one deal at a time.

A client asked us to validate a decision they'd already made. It's the most awkward engagement type a partner encounters, and how you handle it matters more than any deliverable. The brief, thinly disguised, asked us to build the analysis supporting an acquisition the CEO had clearly already committed to internally, with the actual scope designed to produce a predetermined conclusion rather than an honest one. I renegotiated the engagement openly rather than quietly delivering what was asked: told them we'd run the analysis honestly, and if it supported the decision, great, and if it didn't, we'd say so directly, with the option for them to walk away from our findings if they preferred not to hear it. I offered explicitly to walk away from the engagement myself if that condition wasn't acceptable to them. They accepted the honest terms. The analysis, as it turned out, did surface a real risk they hadn't fully considered. Integrity in that renegotiation is what actually builds a pipeline over a career, even when it costs a deal in the moment.

The mistake that nearly ended my partner candidacy: I overcommitted my team across two engagements simultaneously, believing I could manage both without either client noticing the strain. Both clients noticed. One engagement slipped its timeline by three weeks. The other's quality dipped enough that a normally supportive sponsor raised a formal concern with my managing partner directly. My candidacy, which had felt close to certain that cycle, got quietly pushed to the following year, with feedback that was blunt and, in hindsight, entirely fair: capacity judgment is exactly the skill partnership is supposed to certify you have. I rebuilt trust over the following year by deliberately under-committing, twice, even when it meant turning down interesting work, until my managing partner had clear, repeated evidence that my capacity judgment had genuinely changed. The partner track is opaque by design in most firms. This is the closest I can get to an honest account of one of its near-failures, and why it happened.

Five signs an engagement will go sideways, visible to me in week one now, after enough engagements taught me to watch for them early. An absent executive sponsor at kickoff, represented by a delegate instead — often signals sponsorship is weaker than the org chart suggests. A contested problem statement, where two stakeholders describe the actual problem differently in the same meeting — a near-certain sign of political complexity the scoping document hasn't captured. Data access delays starting in week one, before any real analysis has begun — a preview of every future data request across the engagement. A prior consulting relationship that ended badly, mentioned defensively rather than neutrally — worth probing gently rather than assuming you'll simply be different. And a client team that seems relieved rather than engaged at kickoff — often signals the project exists to satisfy someone above them, not the team itself. Delivery teams forward posts like this before every kickoff, because each sign is genuinely actionable if caught early.

Clients are asking, in nearly every steering committee now, what AI changes about our fees. Here's my honest answer, not the deflection most partners default to. Some of what we bill for is genuinely compressing — first-draft analysis, data synthesis, slide production that used to take a team days now takes hours with the right tools. What isn't compressing: the judgment call on which recommendation to actually stake our name on, the relationship trust that gets a hard truth heard in a boardroom, and the accountability we carry when a recommendation goes wrong. My firm's honest answer, in practice: we're moving toward pricing more explicitly around the judgment and outcome, less around the hours or deliverables that AI is genuinely compressing, which is an uncomfortable transition but the more defensible one long-term. Clients respect the direct answer more than the deflection. The deflection is what actually erodes trust in this conversation, not the honest acknowledgment that some of the work is changing.

Behind the scenes of staffing season: how partners actually pick teams, which consumes junior consultants with anxiety every single cycle for reasons that don't always match what they assume. I don't just look at performance ratings, though they matter as a baseline filter. I look for specific skill spikes — someone who's unusually strong at exactly the kind of stakeholder navigation a specific difficult client will require, even if their overall rating is merely solid rather than exceptional. I also weight client chemistry heavily, sometimes more than raw skill: a brilliant analyst who rubbed a prior client the wrong way gets staffed carefully, deliberately, away from anything resembling that client profile again. What gets someone requested twice by the same partner: not just doing good work, but doing it in a way that made the partner's own job easier during a stressful engagement — anticipating a need before being asked, flagging a risk early instead of burying it. That's the actual, unglamorous mechanism behind staffing decisions that feel opaque and anxiety-inducing from the junior side.

What's the hardest thing you've ever had to tell a client? I'll go first, since I'm asking senior advisors to be candid here. I once had to tell a CEO, in a private pre-wire call before the full board readout, that the strategy he'd publicly championed for over a year, the one he'd built real personal capital on, was not going to work given what our analysis had found — and that continuing to fund it was going to cost the company more credibility with the board than reversing course now would. He was quiet for a long moment. Then he asked me to help him figure out how to say it to the board himself, in his own words, rather than have us deliver the finding coldly through the deck. That conversation, more than any deliverable I've ever produced, is the actual reason he's referred me to two other CEOs since. The replies to this question, from people who've done this work at a senior level, tend to become a genuine masterclass in candor under real commercial pressure.