business engineering

The arc · why this discipline, why now

Every company became a software company. That era is ending, because it succeeded.

For a century, the scarce skill decided what kind of company everyone became. When production was scarce, every serious firm became an industrial company and built engineering departments. When code was scarce, every serious firm became a software company, IT grew from a back office into the center of the enterprise, and "digital" stopped being a strategy because it became the water.

Now frontier models write the code. Intelligence is abundant and getting cheaper every quarter. When the same capable model succeeds in one company and stalls in another, the variable is not the model. The scarce skill has moved up a level. It is no longer engineering the software. It is engineering the business the software serves: which work exists at all, how it flows, where judgment sits, and what proves it got better. Software ate the world; now the org chart is on the menu.

Companies will stop calling themselves IT companies or software companies. They will be business engineering companies, or they will be customers of one.

The parentage · where the discipline comes from

A discipline with two parents.

From business process re-engineering: the work itself is the unit of change. Walk the floor, map the real flow, take the steps out before you touch the tooling. From software engineering: the ability to make change permanent. Evals instead of opinion. Systems that hold the gain instead of training that decays.

For thirty years the two lived in different buildings. The process people drew future states they could not build; the builders shipped systems into processes nobody had examined. The forward-deployed engineer was the first proof the wall was artificial: one person, fluent in the workflow and the codebase, at the client's desk. It worked so well the industry made it a job title, then a commodity.

The forward-deployed solver finishes the thought: the same hybrid, made accountable to a number both sides signed. The FDE deployed a platform. The fds re-engineers the business, because in the agentic era the software is not the deliverable. The working business is.

Process re-engineering knew what to change. Software engineering knew how to ship. Business engineering is the child that can do both, raised on frontier intelligence.

The definition · drawn precisely

Not IT with a new name. Not transformation with a new deck.

Digital transformation was a project: it had a budget, a deadline, and an end. Business engineering is a permanent function, the way finance and engineering are permanent functions. Consulting produces advice; software engineering produces applications; business engineering produces something neither can produce alone: a business that works measurably better, in production, with the proof read from its own systems.

The discipline · five practices

What makes it engineering rather than opinion.

A discipline is not a point of view; it is a set of practices that produce repeatable results and can be taught. These five are the core of business engineering as we practice it, each one testable, each one already proven in production.

The profession · a title that will spread

In ten years, "business engineer" will be on org charts everywhere.

Every discipline eventually becomes a department. Enterprises that once hired their first software engineers will hire their first business engineers: people fluent in both the operating reality of the business and the frontier of what intelligence can do, accountable not for systems that run but for numbers that move. The profession starts with three roles.

The discipline's output has a name: outcome engineering, outcomes that are intelligent, because the system keeps learning; impactful, because the number moves; and real, because they are read from the business's own systems.

We are hiring the first generation of this profession now, and training it in public.

The shift · in the field's own words

You don't have to take our word for the premise.

The people building the frontier have already described the world business engineering is built for, code becoming abundant, natural language becoming the interface, and verification becoming the discipline that separates demos from deployment.

Two ways in

Every discipline needs practitioners, and proof.