Today's new engagement, I walked into a boardroom where the Product Head wanted a digital transformation, the CEO wanted to integrate AI anyhow, the Sales head wanted no disruption whatsoever, and somehow it was my job to make all three of them happy in the next 3 days.
That's the unglamorous truth about technology consulting that nobody tells you before you sign up.
You're not just a technologist. You're part translator, part therapist, part firefighter and on most days, the scapegoat.
The gap between Request for Proposal (RFP) and response is a chasm.
The RFP said: "Streamline our new product strategy." What that actually meant was: untangle three years of technical debt, navigate a political war between two departments that barely speak, convince a skeptical senior engineer that yes, we actually do know what we're doing, and do all of it while the business keeps running at full speed.
Nobody prepares you for the post-dinner 9PM calls when the latest TestFlight has missing features or spelling mistakes, and that's before next day launch. Or the moment you realise the "simple integration" the client described is actually seven legacy systems stitched together with hope and hardcoded credentials.
"The best tech consultants aren't the best technologists. They're the ones who know which question to ask before writing a single line on Statement of Work (SOW)."
I've sat in rooms where I had to explain why the thing they asked for isn't the thing they need. Where I had to push back on MVP ideas because there was no value.
That's the work nobody puts on their LinkedIn post. But look at me!
And then vibe coding walked in and changed the entire conversation.
Suddenly, a carpenter with the right AI tools is shipping in two days what used to take two sprints. Clients are watching YouTube videos of solo builders launching full products in a weekend. And the question I'm starting to hear in discovery calls?
"Do we still need a consulting team for this?"
[Image]
Let me be direct: every IT consulting company right now is watching the wind. Nobody is fully sure which direction it turns. Some are leaning in fast, integrating AI-assisted development into their delivery model. Others are quietly hoping the hype settles and things return to normal.
Things won't return to normal!?
The consultants who are thriving right now? They're the ones who pair AI speed with something no tool can replicate — deep domain expertise, hard-won stakeholder instinct, and the ability to walk into a chaotic room and know exactly what's actually broken.
The ones struggling were never really solving problems. They were filling seats and raising invoices. That game was always going to end.
Here's what the best engagements I've been part of.
They weren't the ones with the biggest budgets or the flashiest tech stack. They were the ones where we earned trust early by being honest about what we didn't know, by asking uncomfortable questions, and by measuring success in outcomes, not deliverables.
If you're in IT consulting right now, whether you're a practitioner, a leader, or building your own firm, this is the moment to get clear on what you actually bring to the table. Not the tools you use. Not the methodology on your website. You, specifically. What do you see that others miss?
The industry is at an inflection point. And the consultants who will matter on the other side of it are the ones who were never just coders to begin with.
They were problem solvers who happened to know how to build things.
That skill? No AI generates it. No vibe session shortcuts it. It comes from years of sitting in the messy middle of real organisations, making real decisions, with real consequences and Post-Dinner 9PM calls!
If this resonates — I'd love to hear your story. What's the hardest consulting moment that made you better?
