Business Capability Models

A business capability model describes the core functions an organization performs to operate and deliver value.

Capabilities represent what a business does rather than how it performs those activities.

For example, “Customer Relationship Management” is a capability. The specific CRM software used to support that capability may change over time.

Because capabilities are stable while technology changes frequently, many organizations use capability models as a foundation for evaluating their technology environments.

A capability model provides a structured way to map software systems to the business functions they support.

Common capability domains include:

• • customer relationship management

• • marketing management

• • sales management

• • product management

• • service delivery

• • finance and accounting

• • human resources

• • knowledge management

• • data and analytics

• • information technology services

• • infrastructure management

• • legal and compliance

• • strategic planning

• • program and project management

Within each domain, organizations may define more specific capabilities.

For example, the marketing domain may include capabilities such as:

• • campaign management

• • lead generation

• • marketing analytics

• • customer segmentation

• • digital advertising management

Capability models are commonly used in enterprise architecture and business architecture practices.

Several well-known frameworks incorporate capability modeling, including:

• • The TOGAF enterprise architecture framework published by the Open Group

• • Business capability modeling practices described by the Business Architecture Guild

• • Application portfolio management methods used in enterprise architecture programs

• • Capability-based planning models used in digital transformation initiatives

These frameworks emphasize that technology should be evaluated based on the business capabilities it enables.

Mapping software systems to capabilities allows organizations to identify patterns such as:

• • multiple tools supporting the same capability

• • fragmented ownership of business functions

• • opportunities to consolidate systems

• • automation opportunities across workflows

• Capability models are also useful when performing activities such as:

• • technology stack audits

• • application rationalization

• • digital transformation planning

• • enterprise architecture documentation

Because many organizations do not maintain a formal capability model, we provide a simplified capability taxonomy that can be used as a starting point.

This capability map reflects common functions found across many organizations and can be adapted to fit different industries.

You can download the capability model template and modify it to match your organization’s structure.

Once a capability model is defined, it becomes much easier to map applications to business functions and evaluate how technology supports the organization.

Business Capabilities vs Software Categories

Business capabilities and software categories describe technology environments from two different perspectives.

Business capabilities represent the functions an organization performs in order to operate and deliver value. Capabilities focus on what the business does.

Examples of business capabilities include:

• • customer relationship management

• • campaign management

• • financial reporting

• • employee onboarding

• • product development

Capabilities remain relatively stable over time even when technology changes.

Software categories describe types of tools used to support those capabilities. Categories focus on what the software is.

Examples of software categories include:

• • CRM systems

• • marketing automation platforms

• • accounting software

• • project management tools

• • business intelligence tools

Because multiple software tools can support the same capability, organizations often discover overlapping systems when they map applications to capabilities.

For example, two different CRM platforms may support the same customer management capability, or multiple project management tools may support work coordination across teams.

Mapping software to capabilities helps organizations evaluate whether technology is aligned with business needs and identify opportunities to simplify their technology environments.

The Frictionless Capability Model

The Frictionless Capability Model is a simplified business capability framework used to evaluate how technology supports business operations.

The model organizes common business functions into capability domains that appear across most organizations.

Rather than focusing on specific software products, the model focuses on the underlying activities businesses perform.

Each domain contains more specific capabilities that describe the activities required to operate that part of the business.

Because these capabilities remain relatively stable even when technology changes, they provide a useful foundation for analyzing software environments.

The Frictionless Capability Model is used within the Technology Physical™ diagnostic to map software tools to the capabilities they support.

This mapping helps identify patterns such as:

• • multiple systems supporting the same capability

• • fragmented ownership of business functions

• • integration complexity between systems

• • opportunities to simplify technology environments

The model can also be used as a starting point for organizations that want to document their own capability structure.

Companies are encouraged to adapt the model to match their industry, operating model, and organizational structure.

Related Knowledge Articles

/knowledge/business-software-categories
/knowledge/technology-stack-audit
/application-inventory-template
/technology-physical