Get the Journal

Business design is the competitive edge for any team

Why business design moves to the forefront as AI commoditizes software.

Eli Wood headshot

Eli Wood

October 18, 2026 6 min read Updated October 18, 2026
Business design, from canvas to growth: a five-step flow from the Business Model Canvas to the Value Proposition Canvas, an experiment plan, validation with real users, and growth, looping back to the canvas after each round.

Building software used to be the hard part. AI is making it cheap and fast, and that moves the advantage somewhere else.

When almost any team can ship a working product in a couple of weeks, the product stops being the moat. The business around it becomes the thing worth designing: who it serves, how it earns, how it runs and why people trust it. That work is business design, and we think it moves to the front over the next five years.

As code gets cheap, the value moves to the business around it. When building was hard, most of the effort went into building the product. As building gets cheap, the hard work moves to the right problem, customer access, trust, operating know-how and the money model.

The signal: building is getting cheap

In 2026 the cost of making software fell faster than most leaders planned for, and the markets priced it in. After agent tools like Claude Cowork arrived in early February, the S&P 500 software and services index shed roughly $1 trillion in value (ACS Information Age). By March 31 the SEG SaaS Index, which tracks more than 120 public software companies, was down 25.7% for the year (Long Angle).

Inside the companies, the shift is just as plain. By April 2026, human-written code had fallen to about a quarter of Google's total (Betterment). Investors are now asking whether the per-seat subscription can survive when one person with an agent does the work of five.

The speedup is real but it only covers part of the job. Writing and testing code is about 25 to 35 percent of the software lifecycle in Bain's research, so even doubling coding speed moves the whole system less than people expect (Philipp Dubach on Bain; Bain Technology Report 2025). The rest of the work is deciding what to build, for whom, and how it runs once it's live.

What gets scarce when building is cheap

When anyone can make the product, the advantage moves to the parts of the business that AI can't copy overnight. Even the analysts defending software stocks make this case: building AI features is one problem, and reaching 50,000 enterprise customers and earning their trust is a much slower one (Bravia Capital).

We see five things getting scarcer and more valuable:

  • The right problem. A cheap build of the wrong idea is still a waste. Knowing which workflow to build first is now the expensive decision.
  • Customer access. Relationships, channels and reputation take years, and no model ships them.
  • Trust. Security, compliance and clear accountability decide who gets to sell into regulated markets like finance, health and education.
  • Operating know-how. The way a team actually does the work, turned into code, is hard to copy because it lives in the people.
  • The money model. As agents replace seats, pricing by outcome or by service becomes a design choice someone has to make on purpose.

None of these show up in a code review. All of them are business design.

What business design is

Business design is shaping the whole system a product lives inside: who it serves, what value it creates, how the work gets done, how it earns and why people trust it. Product design asks whether the screen works. Business design asks whether the company works.

It also changes how fast you can learn. When a working version costs two weeks instead of six months, you can test the business itself, with real customers and real operations, before you scale it. Suzanne Schmitt of Healthspan Wealth described our work together as entering markets fast and turning operations into code, and that is the practice we mean.

At BFD we run it as a ladder of questions, each one a little bigger than the last:

  1. What does AI mean for us? A two hour AI World Café gets everyone in the room on the same page.
  2. What should we build, and why? A two day Foundations Sprint picks the direction.
  3. Will this idea work for people? A five day Design Sprint tests it with users.
  4. How does the whole business work? A ten day Business Sprint designs the model, the operations and the path to launch.

The build comes after, and it goes faster because the hard choices are already made.

Four futures, 2027 to 2030

Nobody knows how fast this goes, so we plan against the two things we're least sure of: how cheap building gets, and how heavy the bar for trust becomes.

Scenario map of four futures on two axes, how cheap building software gets and how heavy the bar for trust gets. Faster, same game rewards strong delivery teams. Software on tap rewards customer access and brand. The trusted few rewards incumbents with audits in hand. Designed trust, most likely in our view, rewards business design end to end.

  • Faster, same game. Building gets cheaper slowly and trust stays light. AI speeds teams up, but the market looks a lot like it does today. This rewards strong delivery teams.
  • Software on tap. Building gets close to free and trust stays light. Products get cloned in days and prices fall toward the cost of compute. This rewards customer access and brand.
  • The trusted few. Building gets cheaper slowly while rules tighten in finance, health and education. This rewards incumbents with audits in hand.
  • Designed trust. Building gets close to free and the bar for trust gets heavy. Anyone can build, few can be trusted, and proof of care and security decides deals. This rewards business design, end to end.

In three of the four futures the advantage sits outside the code. Our bet is designed trust, where building gets close to free while customers, regulators and boards ask harder questions about who they can trust.

The signposts we're watching are big SaaS vendors cutting per-seat prices, outcome-based terms showing up in contracts and RFPs, and new AI rules landing in regulated sectors. The more of those we see, the faster that future arrives.

What to do now

Whichever future arrives, the same few moves pay off. They matter most for corporate spin-outs, commercialization teams and new ventures, because those teams have to design the business and the product at the same time.

  • Pick the workflow before the feature. Choose the one job your customer pays to get done and build that first. Everything else can wait for evidence.
  • Treat prototypes as cheap evidence. A vibe-coded demo is a fine way to learn. Keep what works and rebuild it into something your team can run and your customers can trust.
  • Price the outcome. If an agent can do the work of five seats, charging by the seat is a bet against your own product. Test outcome or service pricing early.
  • Design trust in from release one. Security and compliance are part of the product in regulated markets, and they are much cheaper to plan than to retrofit.
  • Write down how your best people work. Your operating know-how is the part competitors can't generate. Turn it into the system before someone else's agent turns their guess into one.

Where we stand

We think the next great companies will be designed more than coded. Software is turning into a material, like steel or electricity, and the value moves to what people build with it and how well that business runs.

That's why BFD calls itself a business design studio. We still build, and we build fast, but the work we're proudest of starts with a better question. If you're holding a big idea, a new service or a prototype that needs to become a real business, let's talk.

Sources

About the author

Eli Wood headshot
Eli Wood

CEO, Black Flag Design

Eli Wood leads Black Flag Design, a creative technology company focused on shipping ambitious digital products, AI systems, and design-forward software with a direct point of view on how technology changes work.

BFD Journal

Field notes from building AI-native software in the real world.

Get the Journal

Related stories

More from the journal

Pen-and-ink sketch of a small clockwork robot working at a tool-covered workbench late at night while a human sleeps peacefully on a couch in the background, a wall clock reading 2:00 above
ai April 24, 2026 13 min read

The Agent Stays Up Late, Not Me

Every senior engineer knows the right way to set up a codebase. None of them do it. Here’s the four-stage framework we use — The Ratchet — to take a vibe-coded project all the way to a thing you’d trust in production, and the punchline about why this only just became worth doing.

Most teams have always known they should be running tests, type-checking, security audits, accessibility checks, dead-code analysis, prose linting, and a coverage floor. Most teams run two of those. Here’s why that math has finally inverted, and the four-stage framework we use to ratchet a vibe-coded project to a hardened one.

Keith Pattison, Founder of Black Flag Design

Keith Pattison

AI Builder @ Black Flag Design

Read
What a Year of Claude Code Trails Tells You About Your Team editorial image
claude code April 20, 2026 5 min read

What a Year of Claude Code Trails Tells You About Your Team

Claude Code leaves evidence — sessions, commits, PRs, review notes. Read it like a logbook and you'll find what devs actually need to know before they go deeper.

After a year of shipping with Claude Code across real client work, the signal isn't in any single session — it's in the trails. Here's what those trails told us about where Claude Code shines, where it drifts, and the habits devs should build before they lean in harder.

Eli Wood headshot

Eli Wood

CEO, Black Flag Design

Read
The Black Flag Playbook: Six Principles for Shipping with AI editorial image
playbook April 20, 2026 6 min read

The Black Flag Playbook: Six Principles for Shipping with AI

Battle-tested principles for teams building real software with AI-generated code. Human judgment, tight scope, and weekly evidence — the disciplines that keep AI-built systems reliable.

The six rules we use to ship production software with AI. Small scope, weekly demos, human-led oversight, and continuous improvement — drawn from six months of real client engagements.

Keith Pattison, Founder of Black Flag Design

Keith Pattison

AI Builder @ Black Flag Design

Read
Get the Journal