Module 21 maps one bridge in detail — enterprise architecture in, Pre‑Sales Architect out — because that happens to be the best‑documented one. It is not the only real path in. The sheet after it does the same translation exercise for HR, teaching, customer support, recruiting and project management, because presales draws from all of them often enough that the pattern deserves naming honestly rather than assumed away.
MOD 21
Enterprise Architecture → Pre‑Sales Architect
You are not starting a new career. You're renaming and re‑pointing one you've already been running for years.
Translate the competency, don't relearn it
| What you've done as an EA | What it is in Pre‑Sales Architect language |
|---|---|
| Ran current‑to‑future‑state assessments across banking, government, mining, telecom, retail, education | Multi‑industry solution‑narrative fluency (Mod 09, Mod 17) — most SEs have one industry; you have six |
| Presented architecture roadmaps to boards and steering committees | Executive presence and stakeholder management (Mod 18), already proven at a level many Pre‑Sales Architect candidates haven't reached |
| Built the business case for major transformation investment | ROI/TCO and value engineering (Mod 14), the exact discipline behind winning executive sign‑off |
| Navigated politically complex stakeholder environments across multiple regions or industries | Buying‑committee psychology and power/interest mapping (Mods 03, 18) — international, cross‑cultural experience most competitors won't have |
| Owned deliverability of the architectures you designed | The exact "winnable and deliverable" discipline (Mod 01, Mod 17) that separates an Architect from a Senior SE |
| Built an independent framework, consulting practice, or body of published thinking outside full‑time roles — if you have one | Direct, demonstrable evidence of the "market voice" the top of the ladder is built on (Mod 20) — most internal candidates have none of this. Skip this row honestly if it doesn't apply yet |
Reframing your resume and LinkedIn
- Lead bullets with the business outcome and the stakeholder you influenced, not the architecture artefact you produced — "influenced a multi‑million‑dollar platform decision at board level" (use your own real figure) outranks "delivered target-state architecture" for this audience
- Name specific frameworks by name where you used them (MEDDPICC, ROI modelling, capability mapping) even if you didn't call it that at the time — hiring panels pattern‑match on this vocabulary
- Put any independent practice or published framework near the top, not buried as a side project, if you have one — for a Field CTO‑track Pre‑Sales Architect role, it's a differentiator, not a gap to explain
- Reframe any career gap explicitly as time spent deliberately — building an independent practice, publishing, studying — stated plainly, in one line, closes the question before it's asked
What the interview process usually looks like
- Recruiter screen — expect direct questions about quota exposure and comfort with a metrics‑driven, deadline‑driven role; answer with the deliverable‑ownership evidence above, not defensiveness
- Hiring manager interview — usually probes "why pre‑sales, why now" — the honest answer ("I've been doing the architecture half of this role for years; I want to do the full cycle including the win") lands better than an over‑rehearsed one
- Panel / peer interviews — technical depth and how you handle pushback from other technical people (this is where EA credibility genuinely shows)
- Mock discovery call or case study — near‑universal at this level: you'll be given a scenario and asked to run discovery live, or present a solution to a "planted" skeptical stakeholder. Rehearse the discovery question bank (Template 1) and the situation‑slide structure (Mod 09) until they're reflexive, not read from notes
- Presentation / demo exercise — often "here's a fictional customer brief, come back in 3 days with a solution story" — this is a direct test of Module 09's narrative shape
- Executive / final round — usually about judgement and cultural fit at the altitude this role operates at
Portfolio to bring
- One redacted or anonymised discovery‑to‑solution narrative from your EA work, reframed in this manual's structure (Mod 09)
- One ROI/TCO one‑pager you'd have built for a real transformation business case (Template 8), rebuilt as a work sample
- A one‑page summary of your own independent framework or published thinking, if you have one, positioned explicitly as evidence of Module 20's "market voice"
- Two or three STAR‑format stories (Situation, Task, Action, Result) mapped directly to Modules 17–19: a deliverability trade‑off you navigated, a senior stakeholder you brought around, a virtual team you led without authority
Addressing the doubts a hiring manager will actually have
| Their unspoken question | Your answer |
|---|---|
| "Has this person ever been measured on deal outcomes, not just delivery quality?" | Point to specific instances where your architecture recommendation directly determined whether a deal/investment proceeded — you've always been closer to the commercial outcome than a typical EA title implies |
| "Can they handle the pace and pressure of a live sales cycle vs. a programme timeline?" | Reframe deadline‑driven board presentations and steering committee cycles as the same pressure, shorter cycle time |
| "Will a senior architect be difficult to manage, or resistant to sales process/CRM discipline?" | Directly commit to the discipline (MEDDPICC, forecast hygiene, CRM rigour) as a system you respect, not busywork you'll resist — this is the single most common failure mode hiring managers have seen from senior technical hires |
| "Have they ever owned the commercial construct or margin protection on a deal?" | Separate the two things that get conflated here. Carrying a quota is one specific thing; owning commercials is broader, and anyone who has run a service contract, a delivery budget or a scope has done the second without the first. Be explicit about which you have, then connect it to what this role actually owns — wording in the scope that protects or destroys margin, and cost to serve. |
| "Is their depth only in one area, or can they operate across a broad stack?" | Name your strongest domain, name the one you are actively growing into, then give the operating model for everything else — foundations solid enough to ask the right questions, and a clear sense of which specialist to pull in and when (MSP 07). It is the same model most pre‑sales teams already run. |
Your 30‑60‑90 day plan (bring this to the final interview, unprompted)
30 / 60 / 90 Day PlanPre‑Sales Architect, first quarter
Days 1–30 — Learn the product, the market, the machine
Complete product/technical certification on the core stack; shadow 5+ discovery calls and demos; read the last 4 quarters of win/loss notes; meet delivery leadership to understand real deliverability constraints and standard‑stack boundaries; learn the CRM and forecast cadence cold; map the distributor relationships (especially Microsoft CSP / licensing partners) and any compliance‑framework audit offerings (Essential Eight, Cyber Essentials, NIST/CMMC, or your market's equivalent).
Days 31–60 — Contribute on live deals
Own discovery and solution narrative on 2–3 real opportunities under a mentor's review (ideally a mix of existing‑customer strategic review and new business); build your first MEDDPICC scorecards; produce at least one tight SOW with clear in/out of scope, risks, assumptions and commercial‑construct notes for the AE; deliver your first demo solo; start a personal competitive battlecard library.
Days 61–90 — Own outcomes
Lead technical strategy on at least one deal end‑to‑end; give one internal enablement session drawing on your EA / governance background (immediate credibility, low risk); propose one concrete improvement to a scoping, hand‑over or template process, backed by evidence from your first quarter.