ChatDiagram
ENTERPRISE ARCHITECTURE

Enterprise Business Capability Map

This enterprise business capability map connects external customers and partners to sales, customer-service and finance capabilities. CRM supports sales and service, while ERP supports finance. Both applications use master data as a shared information point. It is a useful early enterprise architecture view because it connects business responsibilities to application support without becoming an organizational chart or a detailed process model.

UPDATED 2026-09-24
TYPEBlockdiagram
EXAMPLEEnterprise Business Capability Map
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Connecting business capabilities to the applications and information that support them.

Key decisions

  • Customer scope: Start with customers and partners as external actors.
  • Capability view: Separate sales, service and finance work.
  • Application support: Map CRM and ERP to those capabilities.
  • Shared information: Join application records through master data.

When to reuse this

Use it for a concise business-to-application enterprise architecture view.

FAQ

Frequently asked questions

What is a business capability map?01
It organizes what an enterprise needs to be able to do, independent of its current teams or systems.
Why map capabilities to applications?02
The mapping shows which systems support important business abilities and where dependencies exist.
What is master data in this view?03
It is shared core information, such as customers or products, used consistently across applications.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.