What transfers, what does not, and what to deliberately learn when you move from consulting into technology or a venture-building role.
The consulting-to-tech move is a common ambition and a poorly drawn map. Consulting hands you genuinely useful skills. It also builds habits and assumptions that can slow you right down in a different environment.
Knowing which is which, before you jump, helps you jump well. Here is what I would tell my younger self.
Structured thinking is the most portable thing consulting gives you. Breaking a complex problem into parts, prioritising clearly and explaining your logic to different audiences is valuable everywhere. Tech needs it. Startups need it even more.
Stakeholder management is underrated by people who imagine tech as a pure meritocracy of ideas. It is not. Internal alignment, board relationships, partner deals and customer conversations all reward the ability to read what different people need and adapt. Consulting builds that muscle well.
Clear writing transfers, and it transfers into something most people miss: prompting. The same structured thinking, the creativity that AI cannot supply on its own, the clarity about the outcome you actually want, and the discipline to spell it out precisely are exactly what separate a good prompt from a useless one. A consultant who can write a tight, well-reasoned two-page memo already has the raw ingredients to be an excellent prompter. That is a genuine edge right now, and most people are sleeping on it.
Speed, and the engagement model underneath it. Consulting is usually paid for time: a day rate, a number of hours, a fixed scope. That quietly rewards effort rather than result, and it does not survive contact with an operating role, where the only thing that counts is the outcome. The honest version is that you often need to be paid on outcomes, and that is not always possible, because some clients and some consultants simply cannot work that way. Spotting the mismatch early saves a lot of frustration later.
Being right versus the right answer for the client. Consultants are trained to find the right answer. Product and operating work rarely has one clean answer. It has hypotheses, experiments and learning loops, and you have to sit in that uncertainty until users tell you whether you were right.
The gap between the plan and the reality. In consulting you design the initiative. In operating you have to run it, and there is almost always a gap between how it looked on the slide and how it behaves in the real world. The skill is closing that gap fast: when the practical version does not work, you step in and make it work, rather than insisting it should work because the logic was sound.
Distance from the work. A consultant can advise on a supply chain without ever running one. In a venture you need to be close enough to feel the actual user experience, not just read the process map.
None of the gaps above are reasons not to make the move. They are simply the things to build deliberately, rather than hope you absorb them by osmosis.
Product sense. Use products hard, talk to real users, and form an honest opinion about what makes something genuinely useful rather than merely clever or analytically defensible. You only get this by building and shipping, not by reviewing.
Operating rhythm. Learn how weekly planning, delivery reviews and team rituals actually work, not as frameworks to present but as habits to live week after week. The muscle is consistency, not insight.
Commercial instinct that the product has to earn. In consulting the client pays the invoice whatever happens. In tech the product has to win the revenue every single time. Build a real feel for what drives that, because it changes every decision you make.
Ownership of the people part. As an operator the team is yours: hiring, culture, performance, the quiet conversation everyone is avoiding. That is not an HR ticket to escalate. It is the job, and it will take more of your week than any model ever did.
Make the move for the right reasons, and go in clear about what you are moving towards, not just what you are leaving behind.
Alex Collins
Co-founder & COO at RAI Digital & Infinite PL · Ex-EY Consulting Partner · Writing on agentic AI, venture building, logistics platforms and transformation leadership.
One honest read every fortnight on what agentic AI is doing to consulting, and what to do about it. For people moving from advice to outcomes, rebuilding a firm, or done buying decks. No hype, no fluff.
My old university asked me back to lecture on the future of consulting. The honest version is that the "scissors of death" are closing on advice-only work, faster now that AI has grabbed one of the blades, and what replaces it is a better job than the one it ends.
AI has not killed consulting. It has killed the part of it that was only ever a nicely formatted opinion. The premium has moved from the cleverest deck to the owned outcome.
What I learned moving from advisory work into operating and venture building: what transfers, what does not, and what catches most people off guard.
