“What does this capability cost to run — and what depends on it?”
Enterprise Architecture puts your technology landscape in the same model as the work and the money. Every application is rated on business value and technical health, with its cost alongside. Each capability has a target and a priced gap. End-of-support dates and contract dates are tracked together. Dependencies show what breaks when something changes. And your target architecture is a dated, priced plan with clear steps from today — a decision, not a diagram.
Rooms you open
Methods supported
Part of Govern & Deliver · How do we turn choices into governed outcomes?
The pressure
Architects keep a detailed model that nobody outside the team opens, because it has no money on it. Decisions to consolidate applications stall because nobody knows what each one costs. Vendor end-of-support dates arrive as incidents, and the target architecture is a slide that has never been priced.
What it looks like today
What changes
A list of applications
Every application rated on business value and technical health, with its cost
End-of-support dates in a spreadsheet
Support dates and contract dates tracked together on every product
A target-state diagram
A dated, priced plan with clear steps from today
Consolidation with a price
Invest, keep, replace or retire: the grid every architect draws, except every application carries its real cost from the same numbers finance uses. Where the plan for an application disagrees with where it sits on the grid, it stands out on its own.
Where other tools stop
Architecture tools draw the grid. Cost tools price the application. Only a shared model does both on the same dot.
The rooms
Each room answers one question a leader actually asks, with the view that answers it and the measures that say whether it is working.
A room is a ready-made view that answers one leadership question, built on the same shared data as every other room.
Room 01
“What applications do we have, which are worth keeping, and what do they cost?”
Every application rated on business value against technical health, with its cost and what that position suggests: invest, keep, replace or retire.
How you know it is working
Room 02
“What does each capability cost, what supports it, and what would it take to improve it?”
Capability cost against strategic importance, the applications, services and teams that support it, and the priced gap to where it needs to be.
How you know it is working
Room 03
“What technology is losing vendor support, what depends on it, and is there money to act?”
End-of-support dates and contract dates on the same products, traced through to the applications and capabilities at risk.
How you know it is working
Room 04
“What depends on what, and what breaks when it changes?”
Your data, the systems that own it and the connections between them, with recovery plans and tolerance for downtime on every service.
How you know it is working
Room 05
“What will the future architecture cost, and what are the steps to get there?”
A snapshot of the target architecture at a set date, priced from today’s real numbers, with the steps from here laid out one by one.
How you know it is working
The question boards actually ask
Comparing what each capability costs with how important it is to your strategy makes the answer obvious. Most companies find the same pattern: heavy spend on everyday capabilities, and too little where they actually compete.
Differentiating
Where you compete. Underinvesting here is a strategic risk.
Parity
Where you need to be as good as everyone else. Spend should match the market.
Commodity
Where you should buy, standardize or consolidate — and free up money to move.
Who it is for
“Which applications should we invest in, replace or retire?
“What does each capability cost, and where is the gap?
“What is losing vendor support, and what depends on it?
“What will the future architecture cost, and what money will it free up?
What it replaces
How it is licensed
Enterprise Architecture is licensed within Govern & Deliver, with Strategic Portfolio Management included underneath.
Start with one portfolio, one product area or your architecture team. Strategic Portfolio Management is included automatically with every module.
See pricingMethods and frameworks
Dotwork does not ask you to adopt a new method. The frameworks your teams run become views over the same model.
BIZBOK
The business architecture standard for mapping what a business does and how value flows.
TBM
Technology Business Management: a standard way to categorize IT spend and who uses it.
SAFe
Scaled Agile Framework: a widely used way to run agile delivery across many teams.
More in Govern & Deliver
“Is the work we are doing still the work we meant to fund?”
Explore“Can we prove our controls were actually working on what we shipped?”
Explore“What AI is running, what can it access, and can we prove it is under control?”
ExploreThe model underneath
Steer, Fund & Optimize and Govern & Deliver all read and write the same Enterprise Operating Model. The first module you license builds the model. Every module after it adds context instead of another silo — and Dotwork AI reads all of it, stopping where the decision is yours.
See the Enterprise Operating Model© 2025-2026 Dotwork, Inc. All rights reserved.