Perspectives & 5 Rings

Brinker’s Composable Canvas. Built In.

Four pre-built Perspectives — Architecture, Data & Privacy, Operations, Integration Health — plus the 5 Rings of Capability lens. The first Martech tool that takes Scott Brinker’s model from blog post to working surface.

Try a Perspective Read Brinker’s original →

Four Perspectives, one click each

A Perspective bundles lenses, legends, and AI suggestions for a single concern. Switch between them to look at the same stack through different eyes.

Perspective 1

Architecture

For the architect doing the morning audit. Highlights ring placement, software palette type (platform / service / app / agent), and lifecycle stage. Stack DNA composite score visible top-right.

Active lenses: 5 Rings, Software Palette, Lifecycle Stage

Perspective 2

Data & Privacy

For the DPO and the consent architect. Highlights consent management, PII tags, data residency, and DPA coverage. Flags any tool processing personal data without a governance edge.

Active lenses: Governance, PII Tags, Data Residency

Perspective 3

Operations

For the team running the stack day-to-day. Highlights department ownership, cost concentration, contract renewal windows, and tools without an owner.

Active lenses: Department Ownership, Cost Distribution, Renewal Calendar

Perspective 4

Integration Health

For the data engineer. Highlights integration mode (batch/realtime/streaming), protocol, criticality, and vendor health status. Live outage dots pulse on affected tools.

Active lenses: Integration Mode, Vendor Health, Edge Criticality

The 5 Rings of Capability

Brinker’s framework classifies every Martech tool by its role in the architecture. We built the lens directly into the canvas — switch it on and every node auto-places into a ring based on its software palette type.

📚

System of Record

CDPs, warehouses, identity stores

📣

System of Engagement

Email, web, mobile, ads, on-site

🧠

System of Intelligence

Analytics, ML, decisioning

🧩

System of Productivity

Workflow, content ops, project mgmt

🔗

System of Integration

iPaaS, ETL, reverse ETL, event routers

Tool classification is editable per-node. Defaults come from our vendor knowledge base (187 vendors pre-populated).

AI suggestions, tied to the active Perspective

Switching to Data & Privacy doesn’t just change the colors — it runs a specific rule set against your diagram.

Architecture suggestions

· Tools missing a ring assignment
· Software palette type inconsistencies
· Lifecycle stage gaps (vendors with no status)

Data & Privacy suggestions

· PII-processing tools without consent linkage
· Missing DPA coverage flagged from agreements
· Sub-processor changes detected in uploaded DPAs

Operations suggestions

· Tools without a department owner
· Renewal windows opening in the next 90 days
· Cost concentration above your threshold

Integration Health suggestions

· Edges with unset integration mode
· Critical edges without a redundant path
· Vendors currently reporting outages

Every suggestion is reviewable. Accept, reject, or edit before it touches the diagram.

The method

Classify your stack by hand

The same stack answers different questions depending on how you sort it. This procedure runs one stack through several sorts and looks at what each one exposes. An hour per lens.

Sort by who the tool serves

Customer-facing or internal-only. The ratio tells you whether your stack is built for the customer or for reporting on them.
Sort by architectural layer

Collection, storage, decisioning, activation, measurement. A layer with one tool is a single point of failure; a layer with five is a consolidation candidate.
Sort by how recently it was chosen

Group by the year each tool was selected. Clusters show you which strategy each part of the stack was built for — and whether that strategy is still current.
Note what changes between sorts

A tool that looks central in one sort and peripheral in another is worth a closer look. That disagreement is the point of running more than one.

Worked example Illustrative

Travel brand, 21 tools, sorted three ways.

Customer-facing / internal	8 / 13
Decisioning layer	1 tool
Activation layer	6 tools
Chosen pre-2023	9 tools
Central in one sort only	4 tools

Reading it: One decisioning tool against six activation tools is a bottleneck you cannot see in a flat inventory. Nine pre-2023 choices means nearly half the stack was picked for a strategy that has since changed.

The shortcut: Perspectives and the 5 Rings lens re-sort the same diagram instantly, so comparing sorts costs nothing.

The argument behind this

The composable canvas and the cosmos

On why how you frame a stack changes what you notice in it.

Frequently Asked Questions

What are Perspectives?

Pre-built composite views of your stack that focus on a single concern — Architecture, Data & Privacy, Operations, or Integration Health. Each Perspective bundles relevant lenses, legends, and an AI suggestion runner that flags issues specific to that concern.

What are the 5 Rings of Capability?

A taxonomy from Scott Brinker (chiefmartec.com) that classifies Martech tools by their role: System of Record, System of Engagement, System of Intelligence, System of Productivity, System of Integration. We built it directly into the canvas as a lens — tools auto-place into rings based on their software palette type.

Why bundle "lenses" into Perspectives?

Most users don’t want to remember which six lenses to enable for a privacy review. A Perspective is one click: it dims irrelevant tools, highlights the ones in scope, and turns on the legends + AI suggestions that matter for that question.

Are the AI suggestions deterministic?

Rule-based suggestions are. KB-backed suggestions use vendor capability data from our knowledge base. Both can be reviewed, accepted, or rejected — the diagram only changes when you say so.

Can I build my own Perspective?

Custom Perspectives are on the Team+ roadmap. For now, you can combine any lens with any legend in the side panel.

Where can I read more about the Brinker model?

Scott Brinker’s original 5 Rings post is on chiefmartec.com. We don’t reproduce it here — read the source. Our contribution is making the model usable inside an actual stack tool.

Which system am I looking at?

Four things on this site have names, and two of those names appear twice. Here is the whole map.

Rings: classify what a tool is. Five of them, from Scott Brinker’s model: System of Record, Engagement, Intelligence, Productivity, Integration.
Perspectives: choose what you are looking at. Four composite views — Architecture, Data & Privacy, Operations, Integration Health. Each bundles lenses and legends for one concern. They filter the canvas; they do not score anything.
Dimensions: score how well the stack performs. 6 engine checks that produce the A–F grade. This is the only one of the four that puts a number on your stack.
Stack DNA: is the evidence the dimensions are scored from. Computed connectivity metrics, redundancy groups and composite health values. You rarely read it directly — it is what the grade is built on.

Why “Architecture” and “Integration Health” appear twice. Each is both a Perspective and a scoring dimension. Same subject, different job: the Perspective filters the canvas so you can look at it, the dimension puts a grade on it. Seeing the name in both places means they are deliberately about the same concern — not that one is a copy of the other.

One more grade, unrelated to these. The free instant audit also returns an A–F letter, but it grades one thing only — how much of your stack is duplicated. It is not a short version of the 6-check evaluation, and the two letters will not match.

Looking for the grades? See what the evaluation computes.

Stop fighting your own diagram

One click switches the canvas from architect-mode to DPO-mode to ops-mode. The data doesn’t change. The questions do.

Try a Perspective See pricing

No credit card required. Free plan available.