What Do Entry-Level Consultants Actually Do All Day?

Last Updated on July 16, 2026

By Florian Smeritschnig, former McKinsey Senior Consultant. Updated July 2026.

Entry-level consultants spend most of their week on four repeating tasks: collecting data, analyzing it, turning the answer into slides, and presenting it to clients. Almost everything else is a variation on that loop.

You accepted the offer, and now you’re not quite sure what you’ll do on your first Monday. “Solving problems for Fortune 500 clients” sounds great and tells you nothing about the actual work. After five years at McKinsey and coaching 700+ people into these roles, here is the honest, task-by-task version, built around one real project so you can see how the pieces connect.

What is an entry-level consultant and what do entry-level consultants do?
An entry-level consultant, usually titled business analyst or associate, is the most junior member of a consulting team at a firm like McKinsey, BCG, or Bain. They own one slice of the project, called a workstream, and do the hands-on work: gathering data, running the analysis, building the slides, and presenting the findings to clients.

Key Takeaways

• Entry-level consultants (business analysts and associates) run four repeating tasks: collect data, analyze it, build slides, present to clients.
• You own a workstream within weeks, not months. Firms expect you fully operational fast, with a short grace period at the start.
• The hardest skill isn’t the analysis. It’s the “so what?”, turning a spreadsheet into a recommendation a CEO can act on.
• AI now drafts much of the data-gathering and first-cut slides, pushing junior work up toward judgment, quality control, and client interaction.
• Feeling behind in your first weeks is near-universal. The learning curve is steep enough that it fixes itself.

What Do Entry-Level Consultants Do? The Four Core Tasks

Once you understand why companies hire management consultants, your own job gets easier to picture. You are there to help the team answer the client’s questions by forming and testing hypotheses. The content changes with every project, but the shape of the work rarely does.

On a daily and weekly basis, you cycle through four tasks:

1. Collect the data needed to test the team’s hypotheses.
2. Analyze the data to turn it into an insight.
3. Build the slides that communicate that insight.
4. Present the findings to your team and the client.

At first you do each step alongside a senior consultant or your project manager. They might decide which analysis matters, hand you the data pull, then show you how to visualize the result so you can rebuild it in PowerPoint.

Within a few weeks, you own more of the loop yourself. This walkthrough is adapted from my book, Consulting Career Secrets.

Task 1: Collecting the Data

Data collection is the foundation of everything that follows. Once you know which analysis will answer the client’s question, you spend real time gathering the right qualitative or quantitative inputs.

Your sources are broad: client interviews, field research, employee conversations, surveys, client and internal firm databases, expert networks, in-house specialists, and external sources like industry reports, news, research, or competitors’ financial statements.

Getting clean data in the right format is harder than it sounds. Clients go quiet, files arrive incomplete or inaccurate, and you often need several pulls and iterations before the numbers are usable. Cleaning the data to prepare it for analysis is a task in itself.

So a big part of the job is judgment: figuring out which data you actually need, making assumptions to bridge the gaps, and triangulating across sources. Some analyses need granular, precise figures. Others only need a quick, rough calculation, and knowing the difference saves you days.

Practical example. Say you’re working with a cargo airline to cut fuel consumption. One idea on the table: strip the paint layers off the aircraft and keep only the protective coating, something a few cargo carriers have actually done. To size the impact, you structure the analysis and collect a handful of data points:

• Weight saved per aircraft from one coat of paint
• Fuel saved per kilogram of reduced weight, per flight hour
• Average yearly flight hours per aircraft
• Aviation fuel price
• Number of aircraft in the fleet

Not all of it comes from one place. Flight hours might come straight from the client’s operations team, while the weight saved per coat could mean contacting external experts, aircraft manufacturers, or the painting companies themselves.

Task 2: Analyzing the Data

Analysis is where information becomes an insight. With the data cleaned and formatted, you run the numbers to test the team’s hypotheses.

The discipline here is staying focused on the objective. Consultants call the failure mode “boiling the ocean,” getting lost in irrelevant detail until you’ve burned days on analysis nobody needed. Keep a clear question in front of you and most of that risk disappears.

Simple quantitative work happens in tools like Excel or Alteryx. Larger or messier datasets often go to a dedicated support team that runs advanced software or builds custom tooling. Qualitative inputs, like expert opinions, usually sit alongside the numbers to explain the logic or draw out implications. The more solid the data, the more convincing your recommendation.

As the analyst, you run this process. It usually involves regular problem-solving sessions to review interim results, align on assumptions with the team and sometimes the client, and decide what to analyze next. Typical outputs include financial forecasts, market predictions, business cases, operational improvements, and pricing changes.

Practical example. Back to the airline. You’ve modeled multi-million-dollar annual fuel and cost savings across the fleet. Then you review it with your team and in-house experts and two things surface. First, stripping all the paint would cause corrosion over time, even with the protective layer. Second, your fuel-price assumption used a multi-year average, but prices are projected to climb over the next five years. So you rework the model: lower the weight savings, add one protective layer back, and build several savings scenarios across different fuel-price paths.

Task 3: Building the Slides

Once the analysis holds up, you have to make it land, almost always as one or more PowerPoint slides. Early on, your manager may hand you a template slide to populate. Before long, you’re building full decks from scratch, with a storyline that carries the argument.

You learn fast which chart types and which words convey a specific message and highlight the insight that matters. At the top firms, slide specialists often help draft, refine, or polish final deliverables overnight, so the deck is client-ready by morning.

Here’s the pitfall that catches almost every new consultant: presenting the analysis instead of the answer. Disappearing into Excel models and analytical drivers, rather than the recommendation that comes out of them.

I remember confidently walking a partner through an analysis early in my first engagement. He looked distinctly unimpressed, and I could feel my slides raising more questions than they settled. When I finished, he thanked me and then asked the only question that counted: “So what?”

Clients and partners want a recommendation they can act on, not a tour of your number-crunching. Your job is to contextualize the analysis, pull out the actionable insight, and simplify it enough that the intended audience gets it immediately.

Practical example. You build an output slide that recommends removing only the paint layers you don’t need, to capture meaningful fuel and cost savings. It follows slide-writing best practices, leads with the “so what?”, and backs the message with clean data. It answers the client’s questions and moves the project toward its goal.

One more piece of reality: decks iterate a lot. Several may circulate in the team room at once, one per workstream, plus a consolidated deck that becomes the final deliverable. That consolidated deck is often built first as a draft storyline with template slides, then filled in with analysis over the engagement. It is not unusual for a document headed to a final C-level meeting to reach version 40 or higher.

Task 4: Presenting to the Client

You’ll be in client meetings regularly to present and discuss your analyses, results, and next steps. Depending on the meeting and your experience, you might present to senior client leaders within your first few weeks. Meetings with middle managers and working-level clients are often run independently by fairly junior analysts and associates.

These meetings do more than share results. They’re where you build client relationships, work around political constraints, gather senior perspectives, and pressure-test your recommendations against requirements you didn’t know existed. Each one usually produces new deliverables or sharper objectives for the next big client checkpoint.

Practical example. You first use your output slide with your team and working-level clients, walking them through your logic. Their input prompts tweaks to the analysis and the slide. Once it clears your team’s leadership, it goes into a C-level update, where you might hear something like: “the CEO likes the idea but wants to keep the airline’s colored tail for marketing.” So you revise the model for that constraint (less weight saved from the tail), update the output, and fold it into the final deliverable as a key fuel-saving recommendation.

That loop, collect, analyze, visualize, present, then adjust and repeat, is the real rhythm of the job. In practice you run several of these at once across a larger workstream.

How Much Responsibility You Get, and How Fast

Contrary to the intern-fetching-coffee stereotype, entry-level consultants are not parked on busywork. Firms expect you to integrate quickly and take on more each week. There’s a short grace period, but you’re generally expected to run your own work independently within a few weeks. “Your work” means the tasks handed to you, whether brand-new work packages or ones inherited from a colleague rolling off.

The team expects you to own the content of your workstream and to hold the deepest knowledge on it. Project managers and partners come to you for information and advice, sometimes on questions that end up in front of the CEO. Understanding how consulting projects get staffed helps you see why that ownership lands on you so early.

I still remember the pressure of it. Two weeks into my first engagement, a partner pulled me in to help prep for a last-minute CEO meeting: “Help me understand this better. What should we do? What do you recommend, and why?”

That’s how fast the expectations arrive.

How AI Is Changing the Entry-Level Consultant’s Job in 2026

The four tasks haven’t changed. How you do them has. Firms now run internal generative-AI tools (McKinsey’s Lilli is the best-known) that summarize documents, pull first-pass research, and even draft PowerPoint slides in the firm’s own template. McKinsey reports Lilli cuts the time staff spend gathering and synthesizing information by more than 30%, so work that used to eat a junior consultant’s afternoon now takes a prompt and a review.

The practical effect is a shift in where your time goes. Less of it on mechanical data-gathering and first-draft decks, more on judgment: checking whether the AI’s output is actually right, framing the problem, and handling the client. The collect-analyze-visualize-present loop is intact; the grunt-work share of it is shrinking.

Our take at StrategyCase is that this creates a real trap. If you lean on AI for the “so what?”, you never build the judgment that gets you promoted. A model can draft the slide. It can’t read the room in a C-level meeting or decide which of three defensible recommendations the client will actually accept.

That’s still your job, and it’s the part that compounds into a career. We cover this shift in depth in our guide to how AI is reshaping the junior consultant role.

Culture Shock and Imposter Syndrome: What’s Normal

Imposter syndrome hits most new consultants, and it usually shows up as a culture shock in the first weeks. Everyone around you, even people a few months ahead, seems faster, more confident, and more knowledgeable. It’s easy to feel underwater.

I felt it on day one. A fairly simple analysis took me far longer than expected while the rest of the team wrapped up. They offered to help more than once, but I wanted to finish on my own. That evening, I felt pretty lost.

Here’s the reassuring part: the steep learning curve that overwhelms you at first is the same one that makes you competent fast. A year in consulting builds the kind of experience that takes three to five years elsewhere. The discomfort of constantly starting on unfamiliar problems never fully goes away, because that’s the job, but your ability to handle it grows quickly.

The move is to lean on your strengths, use your firm’s resources and network, and give yourself the first few weeks. Everyone around you went through the same thing. Protecting your work-life balance from the start makes the adjustment far more sustainable than white-knuckling it.

Frequently Asked Questions

The Bottom Line

Strip away the mystique and the entry-level consulting job is a tight loop: collect the data, analyze it, build the slide, present it, then do it again with sharper questions. Ownership lands on you within weeks, the “so what?” is the skill that separates good from average, AI is reshaping how the work gets done, and the early overwhelm is normal and temporary.

If you’re reading this to decide whether the offer is worth chasing in the first place, start with StrategyCase’s free guide on how to get into consulting, then come back to this once you know the day-to-day is what you want.

Related Guides

• AI’s impact on consulting careers and hiring
• 9 practical tips to survive your first months as an analyst
• How to prepare before your start date at McKinsey, BCG, or Bain
• The honest pros and cons of a consulting career
• How to get promoted in consulting

About the author: Florian Smeritschnig spent five years at McKinsey as a Senior Consultant, where he evaluated candidates, and has since delivered 2,200+ mock interviews and coaching sessions. He founded StrategyCase.com and has helped clients secure 700+ offers at McKinsey, BCG, Bain, Tier-2, and Big 4 firms. He is the author of “The 1%: Conquer Your Consulting Case Interview,” “The 1%: Case Interview Workbook,” and “Consulting Career Secrets.”