AI, tools and transformation — Benedict Evans

Benedict Evans ·

Benedict Evans discusses enterprise software complexity, AI’s impact on tool creation, the difficulty of spotting automation opportunities, and a three-question framework for strategic AI adoption. Read 4 viewpoints with supporting evidence and source links.

Understand this piece

4 key points

Synthesis

  1. Large companies often lack a clear software inventory

    Typical large U.S. companies have hundreds, perhaps thousands, of software tools, including systems such as SAP and Workday, vertical SaaS apps, workflows, scripts, automations, databases and spreadsheets. They often do not know how much software they have, what is used or what they are paying for.

    Supporting evidence 1

    Original excerpt

    The typical big American company today has hundreds, and perhaps thousands, of different pieces of software. It has giant ‘big iron’ horizontal systems of record like SAP and Workday, it has hundreds of vertical SaaS applications, and then there are hundreds more workflows, scripts, automations and databases, right down to the 10 meg spreadsheet running a department. Very often, the company doesn’t even know quite how much it has, what’s actually being used, and what it’s paying for.

    Benedict Evans · Paragraph 1

    Context

    And yet, with all this software, the company is full of boring, repetitive tasks.

    Read in source context →
  2. AI lowers barriers to building task-specific tools

    Evans discusses how AI lets people create tools without being engineers or writing code, contrasting this with software built in advance and considering the possibility of software becoming dynamic and generative.

    Supporting evidence 1

    Original excerpt

    But with AI, now you can make that tool in five minutes, and you don't need to be an engineer, and you don’t need to write code. You can just ask the model to make the tool for you, or, more fundamentally, just do the task for you itself . Instead of having to create those tools one at a time, software might be dynamic, generative, free-form, and spontaneous. Massively more tasks can be automated, with massively less software.

    Benedict Evans · Paragraph 2

    Context

    It can be very tempting to think that AI will sweep most of this away. There’s an old joke that an engineer is someone who’ll spend an hour building a tool to automate a task that would take 10 minutes.

    Read in source context →
  3. Recognizing the need for a tool remains the hard part

    Evans argues that making code easier to write does not solve the problem of knowing when a tool is needed and what it should do.

    Supporting evidence 1

    Original excerpt

    None of this is solved by making easier to write code - by making it easier to make tools. The hard part is knowing that you need a tool for this in the first place, and then knowing what the tool should do.

    Benedict Evans · Paragraph 8

    Read in source context →
  4. Three questions for a new transformative technology

    Evans outlines three questions companies face with a new transformative technology: how to buy, build and deploy it; how far it changes their operations, with answers differing by industry; and whether it creates challenges to their business economics, new competitive pressures or, perhaps, an existential threat.

    Supporting evidence 1

    Original excerpt

    Stepping back, it seems to me that with each new transformative technology, every company has to ask three kinds of questions. First, how do we buy, build and deploy this? Do we do pilots? Should we take the product that's bundled from Microsoft/Google/Oracle, build something ourselves, pay someone to build something, or buy this new thing from a startup? Second, they have to ask how far this changes their operations. What does it mean?

    Benedict Evans · Paragraph 21

    Context

    What does email mean for us? What does spreadsheets mean for us? The answer to that might be radically different if you were an insurance company or a law firm. And third, you have to ask whether this creates new challenges to your business’s economics, new competitive pressures, or, perhaps, some kind of existential threat.

    Read in source context →

Key passages4

Attributed passages with the context to verify them. Open the original text to check the source.

enterprise software sprawl

Large companies often lack a clear software inventory

Original excerpt

The typical big American company today has hundreds, and perhaps thousands, of different pieces of software. It has giant ‘big iron’ horizontal systems of record like SAP and Workday, it has hundreds of vertical SaaS applications, and then there are hundreds more workflows, scripts, automations and databases, right down to the 10 meg spreadsheet running a department. Very often, the company doesn’t even know quite how much it has, what’s actually being used, and what it’s paying for.
Context

And yet, with all this software, the company is full of boring, repetitive tasks.

AI-enabled tool creation

AI lowers barriers to building task-specific tools

Original excerpt

But with AI, now you can make that tool in five minutes, and you don't need to be an engineer, and you don’t need to write code. You can just ask the model to make the tool for you, or, more fundamentally, just do the task for you itself . Instead of having to create those tools one at a time, software might be dynamic, generative, free-form, and spontaneous. Massively more tasks can be automated, with massively less software.
Context

It can be very tempting to think that AI will sweep most of this away. There’s an old joke that an engineer is someone who’ll spend an hour building a tool to automate a task that would take 10 minutes.

strategic AI adoption framework

Three questions for a new transformative technology

Original excerpt

Stepping back, it seems to me that with each new transformative technology, every company has to ask three kinds of questions. First, how do we buy, build and deploy this? Do we do pilots? Should we take the product that's bundled from Microsoft/Google/Oracle, build something ourselves, pay someone to build something, or buy this new thing from a startup? Second, they have to ask how far this changes their operations. What does it mean?
Context

What does email mean for us? What does spreadsheets mean for us? The answer to that might be radically different if you were an insurance company or a law firm. And third, you have to ask whether this creates new challenges to your business’s economics, new competitive pressures, or, perhaps, some kind of existential threat.

problem identification gap

Recognizing the need for a tool remains the hard part

Original excerpt

None of this is solved by making easier to write code - by making it easier to make tools. The hard part is knowing that you need a tool for this in the first place, and then knowing what the tool should do.

Mentioned here

All mentioned things

SAP

Mention only

Benedict Evans lists SAP as a representative example of large horizontal enterprise software systems used by major U.S. companies.

Read supporting evidence · Benedict Evans

Workday

Mention only

Benedict Evans lists Workday as a representative example of large horizontal enterprise software systems used by major U.S. companies.

Read supporting evidence · Benedict Evans

Source & methodology

These viewpoints are linked to their original sources. Paraphrases are labeled and are not verbatim quotes.

Open transcript or source material (opens in a new tab)Report an issue

Explore these viewpoints by person