HomeVideos

I Just Did a Full Day of Analyst Work in 10 Minutes. The $120K Job Description Just Changed Forever.

Now Playing

I Just Did a Full Day of Analyst Work in 10 Minutes. The $120K Job Description Just Changed Forever.

Transcript

822 segments

0:00

I used Opus 4.6 to build in 10 minutes

0:02

what it takes a Goldman analyst to build

0:04

in a day. I'm not a Goldman analyst. And

0:07

then I built a board deck for that in

0:08

just 20 more minutes. General

0:10

intelligence just showed up in Excel and

0:13

PowerPoint and its name is Claude. I

0:15

built a full operating model last week.

0:17

Revenue projections, cost structure,

0:19

unit economics, the works. And that just

0:21

took a few minutes. And after that,

0:22

Claude in PowerPoint took over and built

0:25

slides, executive summaries, financials,

0:27

key metrics using an actual slide deck

0:30

template. Just a few minutes later, I

0:32

had a presentation with charts

0:34

referencing live Excel data formatted in

0:36

the correct fonts and colors. And this

0:38

is something that would have taken a

0:39

couple of days just a few months ago.

0:42

And yes, I did mean it about Goldman. A

0:44

Goldman Sachs analyst looked at the

0:46

model and told me it was solid. It's the

0:48

kind of output that would have probably

0:49

taken him a day to build. and it took me

0:51

30 minutes total with a deck included.

0:54

This is the piece of the week's news

0:56

that most people are going to sleep on

0:58

because it doesn't have the drama of a

1:00

benchmark score. It doesn't have the

1:03

spectacle of 16 agents building a

1:05

compiler or an agent managing 50

1:07

developers. This is just Excel, right?

1:09

It's just PowerPoint. The tools nobody

1:12

thinks about twice. And yet, we spend

1:14

our days there. And as of this week,

1:16

effectively, they have general

1:18

intelligence inside them. The same

1:20

intelligence that built that C compiler,

1:22

the same intelligence that found 500

1:23

zeroday vulnerabilities on its own after

1:26

security researchers had passed the code

1:28

as secure. And here's the point that

1:29

should really stop you. It's not about a

1:32

single product release. I don't care if

1:34

you think Opus 4.6 is the sauce or not.

1:38

The point is that this ship into Excel

1:40

and PowerPoint paves the way 4.7 and

1:44

then 5.0. It's not that the applications

1:47

are going to change. PowerPoint will

1:48

look the same. Excel will look the same,

1:50

but the intelligence inside them is

1:53

going to compound. This is the dumbest

1:56

Excel and PowerPoint will ever be. Now,

1:58

I covered Opus 4.6 in a separate piece

2:00

earlier this week. What the model can

2:02

do, why it matters. I talked a lot about

2:04

agents. This is about what happens when

2:07

that intelligence shows up out

2:12

billion people use every single day and

2:15

why it turns Microsoft into just a dumb

2:18

pipe and what that means for how you

2:20

think about work when your tools are

2:22

getting smarter faster than you can

2:24

update your assumptions about them. So

2:26

what actually shipped? Two things

2:27

happened in the past couple of weeks and

2:29

taken together they represent something

2:31

bigger than either one of them by

2:33

themselves. On January 24th, Anthropic

2:36

opened Claude and Excel to pro

2:37

subscribers. Anyone paying 20 bucks a

2:40

month or more. The feature had been

2:42

limited beta. The feature had been in

2:44

limited beta since October of last year,

2:47

but the January release made it broadly

2:49

available. Then on February 5th,

2:51

alongside the Opus 4.6 6 launch, two

2:54

things happened at once. Claude and

2:56

Excel upgraded to 4.6, the same model

2:59

that powered all of those amazing coding

3:01

results. And Claude and PowerPoint

3:03

launched for the first time. The Excel

3:05

integration is not a chatbot bolted onto

3:08

the sidebar, even though it looks like

3:10

it. It actually operates directly

3:12

against your work. It reads your

3:13

existing data. It understands your tab

3:15

structures. It writes and debugs

3:17

formulas. It builds pivot tables. Yes,

3:20

it's absolutely not perfect. Yes, it

3:22

needs work sometimes and a check from an

3:25

experienced analyst, but I'm going to

3:27

keep reminding you this is the dumbest

3:29

that model is ever going to get in

3:30

Excel. The PowerPoint integration is

3:32

more interesting than most coverage

3:34

suggests. It doesn't just generate

3:36

slides. It reads your slide masters,

3:38

your layouts, your fonts, your color

3:40

schemes, your template, your colors,

3:42

your template, your font hierarchy. It

3:44

produces slides that don't look like AI

3:46

made them because they match the design

3:48

system your team already uses. And that

3:51

has been a huge breakthrough for AI in

3:53

the past month or two that most people

3:55

have slept on. Back in the fall of 2025,

3:57

building an AI PowerPoint meant you had

4:00

to give up your own templates. Not

4:03

anymore. The combination of Excel and

4:05

PowerPoint together matters more than

4:07

any of these tools by themselves.

4:09

Because both run on the same underlying

4:11

model, Claude is able to bring the same

4:14

intelligence to bear across both. and

4:16

claude produced Excel documents play

4:18

very nicely with claude produced

4:20

PowerPoints. So if you're building an

4:22

analysis in Excel and then you tell

4:24

Claude in PowerPoint to generate the

4:26

board deck off of that analysis, it's

4:29

going to be very easy to get from data

4:31

to decision in a single sitting. That's

4:33

the promise of working with Claude

4:36

seamlessly across a bunch of different

4:38

Microsoft artifacts. So how do you get

4:40

it? This is the part most of the

4:41

coverage skips. So let me be specific.

4:43

Claude and Excel is available now to

4:46

everybody on Claude's pro plan at 20

4:48

bucks a month. That's it. Very simple.

4:50

Same price as Netflix. Just install the

4:52

Claude desktop app, enable the Excel

4:54

integration, and it appears inside

4:56

Excel. Claude in PowerPoint is harder to

4:58

get right now. It launched on February

5:00

5th and is currently only available on

5:02

Max Plan, which is like a hundred bucks

5:04

a month. I think it's because you burn

5:06

more tokens on PowerPoint than Excel.

5:08

It's not yet out on Pro. And if you need

5:10

both tools and you're an individual, the

5:12

max plan is the only option you've got.

5:14

The pricing matters because of what it

5:16

implies about the cost of intelligence.

5:18

Junior financial analysts can cost, I

5:21

don't know, six figures, $100,000,

5:23

$120,000 fully loaded. An associate at a

5:25

consulting firm can build 300 to 500 an

5:28

hour. At that price, between 20 and 100

5:31

bucks a month for Claude and Excel and

5:33

PowerPoint, there are a lot of

5:35

organizations that are going to start

5:36

asking themselves if junior analysts are

5:38

adding incremental value. I'm not saying

5:40

the junior analyst role is obsolete. I'm

5:43

saying the junior analyst who only

5:44

builds models and decks manually has a

5:46

big big problem because that scarce

5:49

skill is no longer scarce and you're

5:51

going to start to get measured by how

5:52

quickly you can ramp on AI tooling and

5:55

expand your spam. Here's where it gets

5:57

really interesting because most people

5:59

comparing Claude and Excel to Microsoft

6:00

Copilot miss the point entirely. They're

6:03

stuck in formulas. They're stuck talking

6:04

about Microsoft native integrations,

6:06

etc. Pay attention. Anthropic partnered

6:09

with Moody's, the London Stock Exchange

6:11

Group, Thirdbridge, and others to build

6:14

financial data connectors directly into

6:16

the Claude ecosystem. These are not

6:18

generic web scrapers. their

6:20

authenticated structured data feeds from

6:22

platforms that institutional finance

6:24

runs on. Which means in practice, you

6:26

can ask Claude to build a comparable

6:27

company analysis and instead of manually

6:30

pulling data from a terminal, the model

6:32

will query live financial data through

6:34

those connectors and populate your

6:36

spreadsheet with real numbers. Anthropic

6:38

also ship pre-built financial skills,

6:40

purpose-built workflows for the tasks

6:42

that eat most of the analysts week,

6:44

comparable company analysis, discounted

6:46

cash flow models, due diligence, data

6:48

packs, etc. These aren't templates that

6:50

you fill in. They're intelligent

6:52

workflows that understand what a

6:54

discounted cash flow model actually

6:56

needs and how to structure the

6:58

assumptions tab to support them. For

6:59

anyone who has built a discounted cash

7:01

flow model from scratch, you know that

7:03

the mechanical work involved takes a

7:05

long time. Not because it's conceptually

7:08

difficult, but because there are

7:10

hundreds of cells that all need to

7:11

reference each other correctly.

7:13

Enthropic spied that pile of mechanical

7:16

work and realized with the right data

7:18

feeds and the intelligence of Claude,

7:20

they could knock that out and it would

7:21

just make the spreadsheet dumb plumbing.

7:24

And the intelligence is what would

7:25

matter. I do need to address the is this

7:27

real or is it a demo question heads on

7:29

because I get so many questions in the

7:31

comments after videos like this. Nate,

7:33

this is hype. Nate, you're overhyping

7:35

things again. I think the answer really

7:37

matters here. Enthropic announced a

7:39

Goldman Sachs partnership on February

7:41

6th, and that has already been ongoing

7:44

for months and months and months, while

7:46

Goldman essentially pioneered this

7:48

behind the scenes. Goldman is deploying

7:51

Claude across accounting and compliance

7:53

workflows now as a production tool. When

7:56

the most prestigious investment bank in

7:58

the world puts this in production for

7:59

internal ops, I think you know the demo

8:01

question got answered. AIG reported that

8:03

Claude made their document reviews five

8:06

times faster with accuracy improving

8:08

from 75% to over 90%. Not faster at the

8:12

expense of quality. Faster and more

8:15

accurate at the same time. The error

8:17

rate went down while the speed went up.

8:19

That was impossible in the 2010s era of

8:22

software and earlier. That is a

8:24

signature of a tool that does not get

8:25

tired, that does not skip the boring

8:27

rows, that does not assume the numbers

8:29

in the summary tab match without

8:31

checking. Meanwhile, the banks that

8:32

manages Norway's $1.7 trillion sovereign

8:35

wealth fund reported an estimated

8:38

$213,000

8:39

hours saved from Claude and Excel. This

8:42

is what it looks like when you target a

8:44

painoint that is scaled across a 1 and a

8:47

half billion user base in Microsoft. And

8:50

this is why Microsoft should be worried

8:52

because Claude's entire strategy

8:55

disintermediates Microsoft's influence

8:57

on their own user base in their own

8:59

tool. Let me walk through a few specific

9:01

workflows because not everybody's a

9:03

financial analyst and I want to give you

9:05

a sense of what general intelligence in

9:07

your tools actually looks like. Let's

9:09

start with an operating model. Let's say

9:10

you open a blank workbook and you have a

9:12

dream of a small business and you tell

9:14

Claude, "Please build me a three-year

9:16

operating model for my small business.

9:18

This is my revenue target. This is my

9:21

dream of how many people I want to hire.

9:23

This is how many customers I want to

9:25

get. This is the kind of product I have

9:26

and what I want to sell it for. I don't

9:28

know how to build a business operating

9:30

plan. I need your help. It turns out

9:33

Claude does a really, really good job at

9:35

that. It may not be perfect, but it gets

9:38

you about 90 95% of the way there out of

9:40

the gate. How about a board deck? Let's

9:42

say you've built the model and you want

9:44

Claude to build a PowerPoint you can

9:46

show your banker to get a small business

9:48

loan to get started. Claude can read the

9:50

Excel file you upload. It can understand

9:52

it because again, it's the same

9:54

intelligence underneath both. It can

9:56

generate the charts that reference

9:57

actual numbers. It can apply your

9:59

company's slide template and put out

10:00

something that you can go to a banker

10:02

with or you can go to an investor with.

10:03

Let's say you're a startup founder and

10:05

you're pitching a series B. You have

10:07

your financials in Excel and a pitch

10:08

template your designer built last

10:10

quarter. All you have to do is tell

10:12

Claude, "Hey, build a 12 slide pitch

10:14

deck from these financials. Here's where

10:16

we want to go. Here's the arc of the

10:17

story." Claude will just do it. It will

10:19

use your fonts, your colors, your layout

10:22

grid. And by the way, that is all new

10:24

since last fall. The last time I talked

10:25

about Excel, I had to be like, "It's

10:28

amazing. It does PowerPoint, but one,

10:30

it's not in PowerPoint, and two, good

10:32

luck using your own templates and

10:35

layouts." Not anymore. Not anymore.

10:37

That's how fast things move. What about

10:38

due diligence? Let's say you're trying

10:40

to understand a small business you want

10:42

to buy. So, you upload 3 years of

10:44

financial statements, and you tell

10:46

Claude, "Please build me a due diligence

10:48

data pack and flag anything unusual."

10:50

Claude saves you dozens of hours combing

10:53

through those financial statements and

10:55

greatly increases the probability you're

10:57

going to see something that might be a

10:58

red flag that might stop that

11:00

acquisition and save you a business

11:02

deal. Let's say you're a product manager

11:03

and you want to do comparable company or

11:05

comparable product analysis. You name a

11:07

few companies that are competitors and

11:08

Claude can pull all of the relevant

11:10

trading data, but also the product data

11:12

and actually build you a competitor

11:15

spreadsheet analysis from scratch in

11:17

just a few minutes. What about a

11:18

quarterly business review? Your

11:20

department heads submit their numbers in

11:22

separate spreadsheets. You consolidate

11:24

it all in Excel. You can tell Claude and

11:26

PowerPoint, "Please build me the QBR

11:28

deck with 15 slides using our corporate

11:30

template using these numbers." Done.

11:32

Now, all of these are finance workflows,

11:35

but there are non- finance workflows

11:37

that are just as important. I want to

11:39

call out. What about a strategy

11:41

analysis? You have a spreadsheet of 50

11:43

competitors with market positioning and

11:45

recent funding routes. You want to

11:47

understand how to score each competitor

11:49

on six different dimensions and weight

11:51

by strategic priorities. You just give

11:53

it to Claude in Excel and it can do it.

11:55

You give it to Claude in PowerPoint

11:56

after that and it can build a

11:57

competitive landscape deck with a

11:59

positioning matrix, a threat assessment

12:01

by segment, recommended strategic

12:03

responses. What about sales enablement?

12:05

Your sales team sends the same 10 slide

12:08

pitch to every prospect. Why not

12:10

handclaw the company's CRM data and

12:12

their last three earnings transcripts

12:13

and tell it to customize the pitch for a

12:15

CFO audience at a mid-market

12:17

manufacturing company? That is trivial

12:19

to do. Now, what about HR and people

12:21

analytics? You export 12 months of

12:24

employee survey data, 2,000 responses,

12:26

free form text, like art scales, eight

12:28

departments. You tell cloud in Excel,

12:30

hey, analyze the sentiment by

12:32

department, identify the three strongest

12:34

predictors of attrition risk, and build

12:36

a summary dashboard. It'll do it. What

12:38

about program management? You have a

12:39

master tracker in Excel with 200 line

12:42

items across a dozen work streams.

12:44

Owners, deadline, status, dependencies.

12:46

Claude can oneshot a program status deck

12:48

for the steering committee. What about

12:50

the formula and data work that nobody

12:52

likes to talk about before you even get

12:54

to the headline workflows? There's just

12:56

the daily grind that cla and Excel can

12:59

eliminate. Debugging a VLOOKUP chain

13:01

that breaks when someone sorts a column.

13:03

Writing a Power Query transformation to

13:05

clean vendor data. building conditional

13:07

formatting rules, tracing a circular

13:09

reference across four tabs. This is the

13:12

kind of work that eats hours a day when

13:14

you live in spreadsheets. And it's just

13:16

and it's the first thing Claude handles

13:18

and the thing that frees up the most

13:20

time before you even start the big

13:21

workflows. Every one of these workflows

13:25

exists today, not next quarter, not as a

13:28

wait list, right now. And here's what

13:31

none of the individual workflows make

13:33

obvious enough. The time savings alone

13:36

aren't the thing that adds up. The time

13:38

savings don't just add up, they

13:40

multiply. Having Claude in Excel saves

13:42

you time on modeling. Having Claude in

13:44

PowerPoint saves you time on deck.

13:46

Having both can save you twice the time

13:49

because it eliminates an entire category

13:51

of work that existed solely because the

13:54

tools could not understand what each

13:57

other built in the age before shared

14:00

intelligence. Think about what actually

14:01

eats your week. It's not just building

14:03

the model. It's not just building the

14:04

deck. It's the mental work that comes

14:06

from the translation layer in between.

14:09

You finish the analysis in Excel. Then

14:11

you open PowerPoint. You have to start

14:13

thinking and reexplaining the same data.

14:15

You have to start trying to think about

14:17

how it changes when you position it in a

14:19

deck form versus a spreadsheet form.

14:22

That translation cost is where most

14:24

knowledge workers spend the majority of

14:26

our production hours. It's not

14:27

necessarily even thinking, right? It's

14:29

translating into a different format for

14:31

a different audience. When one

14:33

intelligence spans both tools, that

14:35

translation cost starts to drop towards

14:37

zero. Claude doesn't just export the

14:39

data from Excel and import it to

14:41

PowerPoint. It deeply understands the

14:44

data in Excel because the same

14:46

intelligence built it and it carries

14:48

that understanding without you having to

14:50

mess with it directly into the

14:52

presentation. The chart it builds in

14:54

PowerPoint reflects an understanding of

14:56

what the model extracted from the

14:58

analysis. The narrative on the slide

15:01

reflects a deeper interpretation that

15:03

the model formed when building the Excel

15:05

spreadsheet. Context flows more easily

15:08

because the same model is building both.

15:11

Now, I'm not saying that there's a

15:13

direct export to PowerPoint from Excel

15:15

today, but I would bet you a lunch that

15:18

is coming in the next couple months. And

15:20

in the meantime, having that ability to

15:23

have a model understand how both Excel

15:25

and PowerPoint works and easily

15:27

translate context between them is a

15:29

godsend. What we're talking about here

15:31

is the context layer that is the future

15:33

of work and it's going to be enormous.

15:35

It's not really about the application

15:37

layer anymore. Microsoft owns that. It's

15:40

not even necessarily about the data

15:42

layer. Your databases own that. The

15:44

context layer sits between them. It's

15:46

the AI's accumulated understanding of

15:49

your data, your brand, your audience,

15:51

your goals. Every time the model touches

15:53

a new tool, the context layer is going

15:56

to get a little bit richer. Every time

15:57

it sees how your board deck differs from

15:59

your team Slack update, it's going to

16:01

learn something about how your org

16:03

translates information for different

16:04

audiences. Applications are containers.

16:07

The data is raw material. The context

16:10

layer is what Anthropic is making a play

16:12

for here. It's the intelligence that

16:14

understands what the data means and how

16:16

to express it for different audiences in

16:18

different formats. That is where the

16:20

value is accumulating and that is what

16:22

Enthropic is laser focused on with

16:24

claude in Excel and Claude in

16:26

PowerPoint. And unlike the application

16:28

layer which Microsoft has owned for

16:30

decades and which barely changes year

16:32

after year, no matter what they say, the

16:34

context layer improves automatically

16:36

with every single model upgrade and

16:38

every new tool integration. It's the

16:40

fastest compounding asset in your tech

16:43

stack and most organizations don't even

16:45

know it exists. And that's what

16:46

separates what happened this week from a

16:48

normal product launch because on Tuesday

16:51

night, the night before Opus 4.6 launch,

16:54

Claude and Excel ran on Opus 4.5, a

16:57

strong model, capable, useful, and on

17:00

Wednesday morning, it ran on Opus 4.6.

17:03

Nobody installed anything. Nobody

17:05

downloaded a patch. Nobody sat through a

17:07

migration wizard. The spreadsheet looked

17:09

the same, but it suddenly had x more

17:12

context and dramatically better

17:13

reasoning and the ability to hold an

17:15

entire multi-tab model in working memory

17:17

and understand how every cell relates to

17:19

every other cell. Think about what that

17:21

means for the next upgrade. Opus 4.7 is

17:24

coming. So is 5.0. Each time a new model

17:27

ships, every claw powered Excel and

17:30

PowerPoint on Earth gets smarter

17:31

overnight without you doing anything.

17:33

The operating model that took 10 minutes

17:35

with Opus 4.6 six might take five with

17:38

4.7 and be 99% right, not 95. The pitch

17:42

deck that needed 20 minutes of back and

17:44

forth with 4.6 might need 5 minutes with

17:48

5.0. The quality of reasoning continues

17:50

to improve. The depth of analysis

17:52

deepens. The output moves closer to

17:55

perfect. And it's not because you

17:56

learned a new tool. It's because the

17:58

tool learned on its own and got better.

18:00

This is a fundamentally different

18:02

upgrade cycle from anything the software

18:04

industry has produced. Microsoft ships a

18:06

new version of Office every few years.

18:08

Feature updates land quarterly. The pace

18:10

of improvement is set by the software

18:12

company's release schedule, its

18:14

engineering priorities, its QA cycle.

18:16

The pace of improvement is actually set

18:18

by Anthropic's insanely fast pace of

18:21

model releases. And those are happening

18:23

every couple of months with capability

18:25

jumps that would be measured in years by

18:27

traditional software standards. That

18:29

3mon gap between 4.5 and 4.6

18:33

context expansion. 5xed in just 3

18:36

months. What's 4.7 going to bring?

18:38

Almost certainly your mental model of

18:40

what AI tools can do is now behind

18:43

reality. It is hard to keep up with how

18:45

fast reality is moving right now. The

18:47

task that Claude maybe couldn't handle

18:49

last month in Excel, maybe it handles it

18:52

now. The presentation quality that

18:54

wasn't sufficient in January because it

18:56

didn't match your templates, maybe it

18:58

works now. And by April, both will have

19:00

improved again. The assumption is that

19:02

you learn your tools once and they stay

19:04

the same. That the thing you tested last

19:06

quarter is the same thing that's running

19:08

today. That assumption is dead. Your

19:11

tools are getting smarter faster than

19:13

you're updating your expectations of

19:15

them. And the practical consequence is

19:17

that you're going to need to re-evaluate

19:19

your workflows continuously. Not

19:21

annually, not when someone sends you a

19:23

blog post all the time. because the

19:25

boundary between the tasks I do myself

19:28

and the tasks that it is smart to

19:29

delegate to AI just keeps moving and

19:32

it's moving in one direction and it's

19:34

moving real fast. I can hear the

19:36

Microsofties in the comments saying,

19:38

"Doesn't Microsoft Copilot already do

19:40

this?" Well, the answer is sort of and

19:42

the real answer leads somewhere more

19:44

important than a feature comparison.

19:46

Pilot's advantage of course is a native

19:48

integration. It's built into Microsoft

19:50

365 from the ground up. The UI is

19:53

seamless. It understands the Office

19:55

ecosystem in a way a third party tool

19:57

doesn't. If your org lives within

19:59

Microsoft, C-pilot is the path of least

20:01

resistance and sometimes it's sold that

20:03

way. Claude's advantages of course are

20:05

reasoning depth, local file support,

20:07

financial data connectors. Claude wins

20:09

on the tasks that require genuine

20:11

reasoning over complex multi-step

20:13

problems like debugging a formula chain

20:15

across 12 tabs or structuring an

20:17

analysis that requires judgment about

20:19

what matters. And the local file setup

20:21

matters a lot as well. C-pilot will

20:23

require one drive for most of its

20:25

functionality, which means your files

20:27

live in the Microsoft cloud. Of course,

20:29

it's a Microsoft play. For orgs handling

20:32

sensitive financial data, it's kind of

20:34

nice to not have to do that with claude.

20:36

But in the end, the co-pilot comparison

20:38

is the wrong frame for what's actually

20:40

going on. I think the real story is more

20:42

structural than that. In September of

20:44

2025, Microsoft added Claude models to

20:47

its co-pilot. Yes, that's right. There's

20:49

Claude in co-pilot, too. So Microsoft,

20:51

the company that invested $13 billion in

20:54

OpenAI, built C-pilot on OpenAI's models

20:56

originally, now hedged by putting a

20:58

competitor's brain, quote unquote,

21:00

inside its own product. When the company

21:02

that owns the application layer starts

21:05

offering someone else's intelligence

21:06

inside it, it tells you where the value

21:08

is migrating. Microsoft really is

21:11

becoming a dumb pipe. It's not

21:13

overnight. It's not completely, but the

21:15

pattern is unmistakable and it mirrors

21:17

what is happening to every platform that

21:20

is getting caught between a

21:21

commoditizing interface and a rapidly

21:24

improving capability layer. AT&T built

21:26

the network. Then the network became a

21:28

pipe for Google and Netflix. The value

21:30

migrated from the carrier to the

21:32

service. Browsers were supposed to be

21:34

the platform and then they became

21:35

rendering engines for web applications.

21:38

Value migrated from the container to

21:40

what ran inside it. Excel is a grid of

21:42

cells. has been essentially the same for

21:44

20 years. New features are at the

21:45

margins. It's the same fundamental tool.

21:48

PowerPoint is just a canvas for slides.

21:50

Same story. The intelligence layer is

21:52

what is compounding. The application

21:54

layer is frozen. And that is why

21:56

Microsoft is hedging by offering every

21:59

major AI model inside its own products.

22:01

That's exactly what a dump pipe does. It

22:03

carries whatever traffic flows through

22:05

it. The implication for your

22:06

organization is to stop thinking about

22:08

your tool choice quite as much and start

22:11

thinking about your intelligence choice.

22:13

The question is not should we use Excel

22:15

or Google Sheets. It's which AI model

22:18

powers our spreadsheet and is it the

22:19

best one for the work that we do and our

22:21

workflows. You need to start thinking of

22:24

applications as containers and asking

22:26

about where the intelligence is coming

22:27

from and whether the intelligence has

22:29

the value you're looking for. This is

22:31

the thing that we aren't talking about

22:32

enough. If the cost of producing these

22:35

artifacts is collapsing towards zero

22:37

extremely rapidly, what happens when

22:40

these artifacts are free? So much of our

22:44

traditional human-drived software model

22:47

starts to break apart. Consulting

22:48

breaks. Not because consultants are

22:50

unnecessary, but because the business

22:52

model depends on a very large time

22:55

component that is about to disappear.

22:57

When a deliverable that build at 40

22:59

hours of associate time could be

23:01

produced in 40 minutes, that whole model

23:03

isn't going to work anymore. The correct

23:05

response here is not panic. It's

23:08

recognizing what becomes valuable when

23:10

artifacts go to zero. Analysis is

23:13

becoming a commodity. Judgment is

23:15

becoming very, very valuable. Knowing

23:18

how to build a discounted cash flow

23:19

sheet, well, Claude can do that. knowing

23:21

which assumptions you want to stress

23:23

test, which scenarios to run, what

23:25

stories the numbers are telling, and how

23:26

to read the clawed spreadsheet and find

23:29

the mistakes. There's judgment there,

23:31

and judgment is what clients are going

23:33

to pay for and boards are going to need.

23:35

The people who thrive in this

23:37

environment are not the ones who will

23:39

build the best artifacts with AI.

23:42

They're the ones who know which

23:44

questions to ask before whatever the

23:46

model is building gets gets built.

23:48

They're the ones who can look at a

23:49

completed analysis and say, you know,

23:52

this is technically right, but the whole

23:54

question is wrong. It's framed wrong.

23:57

That's value. That's where human value

23:59

is going. They're the ones who

24:01

understand the business well enough to

24:03

know which of the 17 possible analyses

24:06

Claude produced is the one that should

24:08

actually drive the decision. This is the

24:09

strategic skill I keep coming back to.

24:11

When production is free, economic

24:14

returns flow to people who know what's

24:16

worth making. Not necessarily more of,

24:18

not necessarily better of, not even

24:20

faster, because the 10-minute operating

24:23

model is worthless if you're modeling

24:25

the wrong thing. The 30 minute board

24:27

deck I talked about is worthless if it

24:29

tells a story that doesn't match reality

24:31

and doesn't line up with investor

24:32

expectations. Sometimes reality and

24:34

investor expectations don't line up, but

24:36

that's a different story. The tool will

24:38

make you faster. Only you can make sure

24:42

it's right. And there's an uncomfortable

24:44

truth here that is hiding inside all of

24:46

this. capability and that is a tidal

24:48

wave of slop. Every tool that makes it

24:51

easy to produce excellent work makes it

24:53

super easy to produce garbage and we are

24:56

about to drown in AI generated garbage

24:59

that looks professional. Researchers

25:01

have started calling it work slop and

25:02

it's true. It's AI generated

25:05

professional content that looks

25:07

technically competent and is completely

25:09

hollow. The estimated productivity cost,

25:11

by the way, $186 per employee per month

25:15

in time wasted processing work. That

25:17

sounds like it means something and says

25:19

nothing. That adds up and I bet it's

25:22

underelling. This isn't really about an

25:24

AI adoption problem. It's not about

25:27

whether you rethink your workflow or

25:28

just bolt AI onto the old workflow. This

25:31

is a fundamentally different problem.

25:33

This is about whether you have the

25:34

judgment to know which work should exist

25:36

and whether you work on a team that

25:39

displays that judgment as well. The same

25:41

capability that lets a thoughtful

25:43

strategist produce a day's work in 10

25:45

minutes lets a careless operator produce

25:47

a week's worth of polished nothing in an

25:50

afternoon. The tool will never know the

25:53

difference because you are the one that

25:56

maps what is needed onto the business

25:59

context and what the market requires.

26:02

And that's on you. In this sense, taste,

26:04

which gets talked about a lot, it's not

26:06

an aesthetic preference. It's not

26:08

something that is impossible to learn.

26:10

It's just the ability to distinguish

26:12

between output that serves a really

26:14

interesting human purpose that matters

26:16

and output that just exists. It's

26:19

knowing that a 40 slide deck that Opus

26:21

can create may look impressive, but it's

26:23

not as valuable as the 10 slide deck.

26:26

It's knowing the third scenario in the

26:27

model is what the board needs to see,

26:29

not the other two. It's knowing when the

26:30

analysis is done,

26:33

you shouldn't add more data because

26:34

that's just going to dilute things.

26:36

Organizations that have people with good

26:38

judgment are about to massively

26:40

outexecute the same organizations with

26:43

the same tools in the same industry that

26:46

don't have people with good judgment.

26:48

Good judgment is about to supercharge

26:50

economic activity for organizations that

26:53

understand how to deploy it. I want to

26:54

leave you with the implication that I

26:56

think matters the most. For 30 years or

26:58

more, professional value has been built

27:00

on execution skills. Can you build the

27:02

model? Can you write the code? Can you

27:04

design the spreadsheet? Can you

27:05

structure the analysis? Those execution

27:08

skills created our whole modern

27:10

knowledge economy. They're what

27:11

universities teach. They're what hiring

27:13

managers were taught to screen for. That

27:15

execution premium is just evaporating

27:18

now. Not in five years. Now, the

27:20

10-minute operating model isn't a

27:22

preview of a future. It's a product you

27:24

could buy today. But what is not

27:27

evaporating is the thinking that sits

27:30

above the execution layer. We have to

27:32

move up a level of abstraction in our

27:35

work as knowledge workers all of us. Now

27:38

it's the ability to frame the right

27:39

question. It's the strategic awareness

27:41

to know which analysis matters because

27:44

the tools are going to keep getting

27:46

better. The thinking is the place that

27:48

has to have the value. Claude can build

27:51

the vehicle for your thinking, but

27:52

Claude cannot replace human judgment.

27:56

And in that sense, I think Anthropic has

27:57

done a great job calling out Claude as a

28:00

tool for human thinking, similar to a

28:02

chalkboard or a notebook. That's the

28:04

right frame. And I think that's a very

28:06

compelling frame for professionals who

28:10

are looking to elevate our art in the

28:12

age of AI. We got to do better because

28:15

the AI is coming for the traditional

28:17

execution skills that define knowledge

28:20

management. And so my challenge to you,

28:22

if you haven't tried Claude in Excel, if

28:24

you haven't tried Claude in PowerPoint,

28:26

give it a try. But more importantly, and

28:28

yes, I have tons of guides on that in

28:30

Substack, I wrote up a whole guide just

28:32

for that for today. It's going to be

28:34

great, but I don't care about that. The

28:36

point is that you need to try it and you

28:38

need to understand that it is your

28:41

ability to frame problems. It is your

28:43

ability to decide what is good that is

28:46

going to distinguish your value long

28:48

term. All of that stuff that you were

28:50

proud of around execution that's going

28:52

to go the way of the dodo. The models

28:54

are going to keep getting better. What

28:55

was 95% good will be solved by the

28:58

middle of the year. It's your ability to

29:00

say this is the right direction to go in

29:02

that is going to make or break your

29:04

career in 2026 and 2027. Good luck and

29:07

have fun in Excel. It's a lot less

29:09

painful now than it was 10 years ago.

29:11

And yes, it really is true. PowerPoint

29:13

can now work with your company's

29:15

templates. One of the biggest wins of

29:17

2026, I think. All right. Have fun,

29:18

guys.

Interactive Summary

Claude's integration with Excel and PowerPoint, powered by Opus 4.6, dramatically accelerates complex tasks like financial modeling and presentation creation, reducing days of work to minutes. This intelligence layer directly interacts with data, understands existing templates, and utilizes live financial data connectors. The speaker highlights that this represents the "dumbest" these AI models will ever be, emphasizing their continuous and rapid improvement. This shift redefines value for knowledge workers, moving it from execution skills to critical human judgment, while also positioning Microsoft as a "dumb pipe" carrying various AI intelligences.

Suggested questions

8 ready-made prompts