If you work in-house, you may have sat in a meeting with a consultant and thought: I do more or less the same work. Why does their firm charge so much for it? And if the meeting went on long enough: Would I be any good at consulting myself?
I was working at a university when I put my PhD on hold to join a large consultancy. I started out taking notes in meetings and turning them into slides and architecture diagrams. I did some design and testing, too. Eventually, I led a small team and worked directly with the client. After five years, I moved to Coala, an enterprise architecture consultancy with three people at the time, including me.
Since then, I have done short advisory assignments and several longer ones, sometimes as part of the client’s team. I spent three years working almost full-time as an architect for one public-sector client. The client decided what I worked on and even invited me to its parties. On an ordinary Tuesday, you would have had a hard time telling me apart from an internal employee. The main differences were why I had been brought in and what would happen when the assignment ended.
It is easy to look at that assignment and conclude that an IT job is much the same whether you do it in-house or as a consultant. The work itself may be. Still, I know people who moved into consulting and later went back in-house. Their reasons are their own, but I can see how someone might enjoy the same work more in a different setup. Who sets your priorities, how quickly you are expected to get up to speed, and how long you get to stay with a problem can make for quite a different working week.
I have been in consulting for more than 18 years. I have changed employers a few times, but I have never seriously considered leaving consulting. If you are thinking about making the move, start by finding out what clients would actually hire you to do. You may already know how to do the work. The question is whether you would enjoy doing it on someone else’s timetable, in an organization you are still getting to know.
What the Client Is Buying
An IT team may need an architect for a project because its own architects are already busy. The client is buying extra capacity and, often, experience it needs for that particular project. You join the team, work from its priorities, and attend the same meetings as everyone else. If the priorities change next week, so does your work.
A client can also buy a project or a specific piece of advice. It might ask a consulting firm to plan an IT transformation or find out why an organizational change project keeps running into trouble. In that case, the firm is responsible for delivering what was agreed: a recommendation, a design, or perhaps a working solution. The client may want experience from similar projects or simply a fresh look at a problem its own people have been dealing with for months. Sometimes the first useful thing you deliver is a clearer account of what the problem is.
The same firm can sell both kinds of work under the same job title. If you are offered a job as a consultant, ask what clients usually buy from the people you would work with. Joining an established team for a year and figuring out what to recommend in four weeks are quite different jobs.
What the Work Feels Like
A well-scoped assignment can give you time to look at one problem properly. An internal HR specialist may be trying to improve onboarding while also dealing with recruitment and a payroll issue. A consultant can spend the afternoon finding out why new hires keep arriving before their equipment does. The HR specialist, of course, knows who tried to fix it the last two times and whom you as a consultant should speak to before trying a third.
Variety is still my main reason for doing this. After seeing several organizations tackle much the same problem, I have more ideas about what to try the next time. What I see less often is how a decision holds up a few years later. I may leave after making a recommendation or helping put the first changes in place. If you like owning a service and improving it over several years, you may get more chances to do that in-house.
I have not found the hours in consulting particularly long. In my experience, the organization and the assignment make more difference than whether you are internal or external. The pressure can come from different places, though. Two clients may need something on the same day, or a proposal may be due in the middle of a busy client week. And when a client brings you in for your experience, it may expect you to show progress sooner than it would from a new employee. That can feel quite different when you are still learning who makes the decisions.
Who Finds the Next Assignment?
I often have a fair amount of say in how I do an assignment. I can decide whom to talk to first, what to look at, and how to fit the work around the client’s meetings. How much say I have in the next assignment varies. Sometimes I am asked which assignments I would like to take on. Sometimes I help shape one from the first conversation with the client. Other times, there is a job that needs doing and I happen to be available.
Sales varies just as much. In a typical consultant role, someone else finds the work and you join once it is agreed. In other roles, you meet prospective clients, write proposals, and spend part of an afternoon explaining what the entries in your résumé actually mean. Ask how much of that you would be doing, whether time is set aside for it during client assignments, and what happens between assignments.
As for the hourly rate, the client pays the firm, and the firm pays you. The rate has to cover finding the work, running the business, and time the firm cannot bill. For the client, a high hourly rate may make sense if it needs a particular skill for six months. For you, the useful comparison is the salary, hours, travel, and work you would actually do. One thing I value about consulting is that I can make a living as a specialist without having to become a manager.
Would You Be Any Good at It?
If people outside your team already ask you to help with difficult problems, you probably do some of what consultants do. You take a request that could mean three different things, work out what people need, and explain what you would do about it. As a consultant, you may have to do that with people who met you last week. Knowing your specialty helps. So does being willing to ask someone to show you how the work actually gets done.
You also have to move the work along. If you find something that changes the plan, tell the client while there is still time to act on it. If you need a decision, explain what needs deciding and what you recommend. You can do all of this without being the loudest person in the room. I learned a fair amount by preparing material for more experienced consultants and watching what they did with it in front of the client.
Some consulting jobs involve a lot of switching between projects. You might spend the morning on one client’s problem and the afternoon on another, with a different set of people, applications, and constraints. My own record is nine billable projects at the same time, with internal work such as sales support on top of that.
Switching between projects is one thing. Changing course within a project takes some resilience, too. You may find out that your original plan will not work, or a client may push back on a recommendation you thought was fairly straightforward. You can handle all of this perfectly well and still prefer to spend most of your week working with one team. That is a question of what you want from the job, not whether you have what it takes.
Ask About an Ordinary Tuesday
I would make the move to consulting again. I like getting to know part of an organization well enough to help with a problem or a solution, then getting to do it somewhere else. If I wanted to own a service or solution and keep improving it over several years, I would look just as seriously at an in-house role. And if I mainly wanted fewer meetings, I would ask to see a consultant’s calendar before handing in my notice.
If you are considering an offer, ask the hiring manager to walk you through a recent assignment someone with your background actually did. What did the client buy? What did the consultant spend most of the week doing? What happened when the assignment ended? I would rather hear about an ordinary Tuesday than about the firm’s most impressive project.
📚 Related Reads from Expert Work by Design
If you found this useful, you might also enjoy the following articles:
👨💻About the Author
Eetu Niemi is an enterprise architect, consultant, and author.
Follow him elsewhere: Homepage | LinkedIn | Substack (enterprise architecture ) | Medium (writing) | Homepage (FI)
Books: Enterprise Architecture | The Senior Expert Career Playbook | Technology Consultant Fast Track | Successful Technology Consulting | Kokonaisarkkitehtuuri (FI) | Pohjoisen tie (FI) | Little Cthulhu’s Breakfast Time
Web resources: Enterprise Architecture Info Package (FI)





