Watch 90 seconds
Think ChatGPT or Gemini — but for your enterprise architecture. See how DecisionPen works as an Architecture Decision Workspace.
Ready to try it yourself?
See it liveDecisionPen
The Architecture Context Plane
DecisionPen is the institutional memory of how your enterprise is built and why those choices still matter.
Agents keep that memory current as work happens, and humans review what becomes trusted before it joins the Enterprise Knowledge Graph.
Architecture Decision Workspace. No credit card is required.
Traditional Enterprise Architecture vs DecisionPen
Most IT transformation programmes burn months rediscovering what documents already know. The ambition is the same — know the estate — but DecisionPen uses a different operating model for an agentic world.
Getting started
Traditional EA
Teams start with manual modelling and workshops, and often wait months before a usable baseline exists.
DecisionPen
DecisionPen starts with automated discovery from a CMDB plus unstructured documents such as HLDs.
What gets captured
Traditional EA
Traditional tools mainly capture thin structural factsheets such as names, owners, and lifecycle status.
DecisionPen
DecisionPen captures structure plus evidence — High Level Designs, decisions, requirements, NFRs, security notes, and related institutional memory.
Freshness
Traditional EA
The repository is often outdated within weeks of being declared complete.
DecisionPen
Context stays fresh through continuous publish from where work happens via MCP, while stewards confirm what joins the map.
Who updates it
Traditional EA
Architects act as data clerks on a quarterly cadence to keep the inventory filled in.
DecisionPen
Agents publish updates as delivery evolves, and humans approve what joins the Enterprise Knowledge Graph.
EA vs solution design
Traditional EA
Enterprise architects and solution architects work in silos: EAs live in the EA tool, while SAs keep designs in SharePoint, Confluence, and similar stores.
DecisionPen
Living enterprise architecture and agentic solution architecture share the same Context Plane in Claude, Cursor, and the workspace.
Delivery & agents
Traditional EA
There is little sync with project delivery, so designs, ADRs, and pipeline work stay outside the EA tool and agents hallucinate when the repository is empty or stale.
DecisionPen
The Context Engine (MCP) hooks into the agentic SDLC so design and delivery use current architecture truth.
Institutional memory
Traditional EA
How and why remain scattered across documents, chat threads, and people’s heads.
DecisionPen
How and why stay attached to each entity — including meeting transcripts — and remain citable when you ask.
Governance
Traditional EA
Success is measured mainly by completeness of the inventory.
DecisionPen
Success is measured by curation before Confirmed status: AI proposes, and people decide.
| Dimension | Traditional EA | DecisionPen |
|---|---|---|
| Getting started | Teams start with manual modelling and workshops, and often wait months before a usable baseline exists. | DecisionPen starts with automated discovery from a CMDB plus unstructured documents such as HLDs. |
| What gets captured | Traditional tools mainly capture thin structural factsheets such as names, owners, and lifecycle status. | DecisionPen captures structure plus evidence — High Level Designs, decisions, requirements, NFRs, security notes, and related institutional memory. |
| Freshness | The repository is often outdated within weeks of being declared complete. | Context stays fresh through continuous publish from where work happens via MCP, while stewards confirm what joins the map. |
| Who updates it | Architects act as data clerks on a quarterly cadence to keep the inventory filled in. | Agents publish updates as delivery evolves, and humans approve what joins the Enterprise Knowledge Graph. |
| EA vs solution design | Enterprise architects and solution architects work in silos: EAs live in the EA tool, while SAs keep designs in SharePoint, Confluence, and similar stores. | Living enterprise architecture and agentic solution architecture share the same Context Plane in Claude, Cursor, and the workspace. |
| Delivery & agents | There is little sync with project delivery, so designs, ADRs, and pipeline work stay outside the EA tool and agents hallucinate when the repository is empty or stale. | The Context Engine (MCP) hooks into the agentic SDLC so design and delivery use current architecture truth. |
| Institutional memory | How and why remain scattered across documents, chat threads, and people’s heads. | How and why stay attached to each entity — including meeting transcripts — and remain citable when you ask. |
| Governance | Success is measured mainly by completeness of the inventory. | Success is measured by curation before Confirmed status: AI proposes, and people decide. |
One shared Context Plane
Your CMDB, documents, and enterprise architecture model share one Context Plane, and then Claude, Cursor, and SDLC agents connect to it through MCP. Enterprise discovery, institutional memory, agentic SDLC, agentic solution architecture, and living enterprise architecture all run on that same plane.
Architecture Decision Workspace. No credit card is required.
Where it helps
The same Context Plane supports different jobs across discovery, delivery, and living architecture.
Rapid enterprise discovery
You get a living landscape in days instead of another workshop marathon.
See how it worksM&A and transformation diligence
Carve-outs and wave plans are grounded in shared context rather than blank factsheets.
See how it worksAgentic SDLC
Architecture context moves at the pace of the pipeline instead of lagging behind it.
See how it worksAgentic solution architecture
Cursor designs against enterprise standards held in DecisionPen, and design artefacts flow back so the Context Plane stays current.
See how it worksInstitutional memory
The organisation still knows why decisions were made months later.
See how it worksLiving enterprise architecture
The landscape stays current through MCP as the estate changes, rather than becoming another stale repository.
See how it worksSee the workspace
Watch a short look at DecisionPen as an Architecture Decision Workspace, then try it yourself.
Built for anyone who decides under change pressure
CTO / CIO
Move change faster without flying blind across the estate.
Enterprise architect
Maintain a living landscape instead of another failed inventory project.
Solution architect
Design against shared truth in Claude, Cursor, or any other connected agent.
Engineering / Operations
Give delivery agents context they can trust before change ships.
Transformation / M&A
Surface dependencies from institutional memory rather than from blank workshops.
Wider organisation
Get grounded answers and bring people up to speed faster.
Try the Architecture Decision Workspace
See the Context Plane live. Start with the example workspace, then bring a system of interest of your own.
No credit card is required.