MOD 17
Enterprise Architecture Thinking, Applied to Deals
Every EA discipline you already have maps directly onto a sales opportunity — just compressed into weeks instead of quarters.
- Current‑to‑future state mapping: the same exercise you've run for a transformation programme, run instead against "where this customer is today" vs. "where they'd be after buying this" — it's what makes a Level 1 solution narrative (Module 09) credible at enterprise scale rather than product‑deep, account‑shallow.
- Capability mapping: showing which of the customer's business capabilities the solution actually strengthens, and which it doesn't touch, is far more convincing to a CIO than a feature list — and it's a skill most Sales Engineers never formally learned.
- Integration, data and security architecture: at this scale, the technical objections that kill deals are rarely about the core product — they're about how it sits inside an existing estate. Bringing real architectural judgement to those questions in real time, instead of "let me check and get back to you," is a visible differentiator.
- Deliverability as a first‑class constraint: the biggest risk at this level isn't losing the deal, it's winning a deal that can't be delivered as sold — the single fastest way to burn a large account relationship. Architects are expected to know, or find out fast, whether delivery can actually build what's being proposed.
The reframeYou are not learning a new discipline at this level. You are applying enterprise and solution architecture — current/future state, capability mapping, integration design, deliverability judgement — under sales timelines and sales stakes instead of programme timelines and programme stakes.