What Is the Value Architecture?

The Value Architecture is the structured approach that connects what your product does to why it matters to your buyers. It gives sales, marketing, product, and engineering a shared language for making aligned decisions — which problems the company is solving, for whom, and how success gets measured. Teams that lack this shared language end up arguing about solutions rather than agreeing on problems.

Components

The Value Architecture has six interconnected components.

Offerings

The products, features, packages, or services you present to customers — what a customer can understand, buy, subscribe to, or engage with. Offerings bridge your internal capabilities and your customers' understanding by packaging what you do into commercially meaningful names.

Value Drivers

The core pain areas your product addresses. Value drivers create urgency around real business problems rather than product features, and give every function a shared reference for which customer problems are being solved. When product, engineering, and sales all name the same problems the same way, decisions that would otherwise require constant renegotiation become straightforward.

Key Capabilities

The concrete elements that deliver business impact, translating value drivers into solution requirements. These include product features, but also non-functional qualities like a support SLA, implementation methodology, or direct influence over the product roadmap. Key capabilities answer three questions for every claim you make: Why you? So what? Says who?

Personas

The people inside target companies who influence, evaluate, use, or approve your solution. Personas define who is involved in decisions, what they care about, and how to reach them at the right moment with the right message.

Ideal Customer Profiles (ICPs)

The types of companies that are the best fit for your product — those most likely to see strong results and generate repeatable revenue. Defining your ICP clearly is what allows you to focus resources on accounts with the highest probability of success rather than spreading effort thin.

Metrics Library

The specific ways customers measure whether a problem has been solved well. These metrics are not invented by the vendor; they reflect how customers already think about success. Sharing the same success measures across sales, product, and engineering means everyone builds toward the same outcome, and sales has the quantifiable proof points to back its claims.

How the Components Connect

Each component builds on the previous one:

ICPs (Companies to Target)
  ↓
Personas (People to Engage)
  ↓
Value Drivers (Problems to Solve)
  ↓
Offerings (What Customers Buy)
  ↓
Key Capabilities (How You Solve It)
  ↓
Metrics (How Success Is Measured)

The Five Pain Categories

Value drivers map to five strategic pain categories that enterprise buyers care about:

These categories help you align messaging with what executives actually care about and connect individual capabilities to business-level outcomes.

Build Your Value Architecture

There are three ways to get started.

Self-paced: Work through the ACT Playbook implementation at your own pace. The material walks you through each component step by step with structured exercises and templates. Enroll at actplaybook.com/playbook/course.

AI-assisted: Build your Value Architecture through a guided, chat-based conversation with an AI assistant. Early access is free while we are improving the product. Join the waitlist at actplaybook.com/waitlist.

With us: Work through the Value Architecture with the ACT Playbook team directly. Book a call or reach out via the contact form.