Strategy Talk Track · Field Guide
A companion, not a replacement.
The Ascent parable ships with a rehearsed, beat-by-beat presenter script in EN and DE, bundled in this pack. This guide is the Wave 1 sales-play layer on top of it — the outreach choreography, persona-to-beat pairing, the turn to the AI Maturity Model, the claim discipline, and the workshop hand-off that the base talk track doesn't cover.
👤Audience CDO · Chief AI Officer · Head of Data Architecture
⏱Base script ~12 min (bundled)
📄Companion This guide
🌐Languages EN + DE (both live)
🎯Discipline Analyst-grounded · no fabricated scores
Section 01
Before the meeting · Persona-tuned outreach
Goal: Use the Executor's persona essay to identify which layer the prospect is publicly addressing, then send a parable-anchored cold outreach. The Executor is not a "sales assist" — it is the discovery layer that determines where in the base talk track to focus.
✉Sequence — Executor first, meeting second
- 01Open the AI Strategy Executor (executor.html). Paste prospect signals. Run Stage 1 to produce the persona essay.
- 02Read the essay's "Public gap" line — this tells you which of the 4 layers to open the conversation on. Almost always it is Knowledge or Translation for CDOs; Agentic for CAIOs; the full stack for Architects.
- 03Run Stage 2 to produce the outreach and send it with the parable link — the parable is the asset that travels. The Executor also anchors on the hosted model at aim.uderia.com, which the prospect may open to self-orient; never attach the model file, and never forward another customer's assessment.
- 04The meeting then opens with the customer already carrying the story — a named summit, a route made of camps, and a wall they cannot yet locate. That last part is exactly what the turn resolves, and it changes how hard each beat has to work.
🎯Persona → base talk-track beat pairing
CDO
Dwell on what compounds. Beat 4 (nothing is left behind) is theirs — every metre of height stands on the one below, which is the only honest argument for funding a foundation whose payoff sits two camps higher. Their public "grounding gap" language maps to the Translation Layer, which you name at the turn, never in the story.
Chief AI Officer
Dwell on the crux. Beat 5 (the wall) is theirs — it is where POC-to-production frustration actually lives. In the model that wall sits at Level 3, the crossing from workflow automation into supervised autonomy, and it is gated by the Translation Layer. Hold that location back until the turn.
Head of Data Architecture
Dwell on the route. Beat 3 (the camps) is theirs — architects want the whole route and what each stage demands before they will engage a narrative. Give them the camps in the story and the 27 requirements at the turn, on tab 3, where completeness is visible in one screen.
▶Cue — what to test before the meeting
1Run the parable once on the machine and screen you will present from — Beat 3 is the only interactive beat, so tap the camps before the room does. Then open the model URL you intend to use and confirm the header controls you plan to reach for are actually there: Industry lens · Technology · Capability · EN/DE. Editions differ, and 30 seconds of paranoia saves a live meeting.
2Have both talk-track languages open in tabs —
why-the-ascent-talktrack.html and why-the-ascent-talktrack-de.html. If the prospect is DACH-based, default to DE unless they wrote back to your outreach in EN.3Have this guide open too — you will reference the persona pairing above during the meeting to know where to focus. Do not read it aloud.
?Ask the Executor essay first
- Which layer(s) does the essay identify as this persona's publicly active concern? — This is where you start in the base talk track.
- Which layer(s) does the essay identify as their public gap? — This is where the base talk track will surprise them, and where the 2-hour workshop earns its keep.
- Does the essay identify a memorable public phrase (keynote quote, LinkedIn post) you can quote back verbatim? — If yes, open the meeting with it before you start the parable.
🔀Cross-play routing signals
SIGNAL AThe essay flags Policy Layer or "jurisdictional reach" language. → Route to AI Sovereignty for a joint conversation. Send them The Kill Switch parable as follow-up.
SIGNAL BThe essay flags AI capex on the P&L, "variable pricing", or CFO-office pressure. → Route to AI ROI for a joint conversation. Send them The Cost of More parable as follow-up.
SIGNAL CThe essay flags "we already have a maturity assessment". → Use their existing assessment as the anchor, and use the AI Maturity Model to challenge specific requirements in their frame. Do not compete on the framework.
Transition to Section 2
Now the meeting starts. The base talk track is your storyline. This guide's Section 2 tells you what to do between the beats.
Section 02
During the meeting · Working the base talk track
Goal: Run the base talk track naturally — but use these Play-specific pauses, questions and interaction cues to make the story land as a conversation about their journey rather than a lecture about a mountain.
◉Beat-by-beat pairing with the base talk track
Base TT · Beats 0–1 ~2:15
The buzzword cloud · buying tools is not making progress
Play addition: After the three failure cards — noise, no summit, high risk — pause and ask: "Where do you think your organization sits on this journey today?" Do not answer for them and do not correct them. Whatever they say becomes your anchor for the rest of the meeting, and it is the claim the model will either confirm or contradict in the workshop.
Open base TT · Beat 0
Base TT · Beat 2 ~1:30
Picture a mountain · the two climbers
Play addition: The two compare cards are the whole argument in miniature — let the room read them before you speak over them. Then land the hinge: "Same mountain. Same ambition. The only difference is a route." That sentence is the reason a maturity model exists, and it is the last thing you say before the interactive beat.
Open base TT · Beat 2
Base TT · Beat 3 ~2:00
The route is made of camps (interactive)
Play addition: This is the parable's only interactive beat. Tap three camps, not six — Base Camp, Camp III, the Summit. Dwell on Camp III and then walk away from it: "hold that thought — we're coming back to it." The camps you leave unclicked do more work than the ones you open.
Open base TT · Beat 3
Base TT · Beats 4–5 ~2:45
Nothing is left behind · the crux
Play addition: Beat 4 is the CDO's beat — every metre of height stands on the one below it, which is the only honest argument for funding foundations whose payoff sits two camps higher. Then slow all the way down for the crux and keep the verdict exact: "It is rarely a failure of ambition. It is structural." Do not say where the wall sits. The parable never does, and neither do you until the model is open.
Open base TT · Beat 4
Base TT · Beats 6–7 ~2:30
Start where you are prepared · the reveal
Play addition: Beat 6 is the good news and it earns its minute — "you don't always start from the valley" is what turns the assessment from a verdict into a choice. Then the reveal. Open the model only after "This was never really about a mountain" has landed and the six map pairs have been read.
Open base TT · Beat 6
▶Live discipline cues
1Do not open the AI Maturity Model during the story. The parable never names it before the reveal, and neither do you. Three tabs, in this order:
why-the-ascent.html (live), why-the-ascent-talktrack.html (your script), dist/AI_Maturity_Model-viewer-plus.html (for the turn — and not before).2Never volunteer a level for the customer. The play rests on them naming a position first and the model calibrating it. Assert a level in the first meeting and you have spent the workshop before you booked it.
3The buzzword cloud is not mockery. Every word in it is real, and their team has probably shipped something with most of them. The villain is the missing route, never the people who bought the tools.
?Ask between base TT beats
- After Beat 1: "Which of these three moves — data-first transformation, agentic AI, or governance — is the loudest on your board agenda right now?"
- After Beat 3: "If you had to name the camp you are standing on today, which is it — and who in your organization would disagree with you?"
- After Beat 5: "When an AI program of yours has stalled, was it ambition that ran out — or was it something structural that nobody had named in advance?"
⚠Objections the base script doesn't cover
"Can you send us the model so we can run it ourselves?"
Not as a file, and say why plainly: it is used live with a facilitator because the value is the disagreement it provokes in the room, and its own footer restricts sharing. What travels is the parable link. What they keep from the workshop is their own assessment.
"Can we see the Teradata mapping now?"
Yes — it is a toggle, and turning it on when asked is exactly what it is for. But finish the structure first. A customer who sees the vendor column before they have rated anything reads the whole model backwards.
"Our team has already picked a platform."
Then the model costs them less, not more: it rates capability, not products, and the technology toggle ships off. Where a requirement is already answered by what they own, they rate it Productionized and move on.
🔀Mid-meeting routing cues
MID-ACustomer volunteers "we can't put this on the internet" or the DPO/CISO enters the conversation. → Pause the base talk track. Pivot to Sovereignty. Say: "This is exactly where the Kill Switch conversation lives. Let me send you that link after this meeting."
MID-BCustomer volunteers "our AI capex has tripled" or the CFO enters. → Pivot to ROI. Say: "That is a different question, and it has its own model. Let me send you The Cost of More." Do not quote a savings figure in a Strategy meeting — the ROI numbers belong to the ROI play, spoken with their source in the same sentence.
MID-CCustomer says "we already scored ourselves at Level 4." → Do not challenge. Say: "Good — the workshop calibrates against 27 specific requirements. Let's compare notes." The model does the calibrating; you do not.
Transition to Section 3
The story ends on the reveal map, and the room asks what it always asks — "so where are we on it?" Section 3 of this guide is the turn.
Section 03
The turn · From the mountain to their estate
Goal: Hand off from the parable to the AI Maturity Model — six levels, four layers, 27 requirements, and a level computed from the customer's own ratings. Then, and only then, the answer: this section holds the only moment a product is named, and every claim spoken here is one the model can put on screen.
◉The four layers — the estate's version of the gear at each camp
- L1Knowledge Layer · 7 requirements. Unified storage, vectors, metadata and lineage, catalog, graph, industry schemas. Owner: CDO · Enterprise Architect. Without it, agents work on data dumps rather than enterprise knowledge.
- L2Translation Layer · 6 requirements. Semantic layer, ontology, reusable business logic, grounding against hallucination. Owner: CDO · Head of Data. This is the layer that gates The Wall — say that once, here, and let tab 1 prove it.
- L3Agentic Layer · 7 requirements. Agent building and orchestration, tool protocols, memory, evaluation and observability. Owner: Chief AI Officer.
- L4Policy Layer · 7 requirements. Embedded governance, AI guardrails, agent identity, FinOps controls, regulatory frameworks, sovereignty. Owner: CISO · DPO.
◉Working the model — tab by tab, their ratings only
- 01AI Maturity Model (tab 1) — the six levels. Walk only Level 2 → Level 3: that is where the model marks The Wall, and it is a role change, not a bigger budget — the machine goes from executor to bounded decider, the human from workflow designer to supervisor and approver. If the room is DACH, flip EN/DE in the header before you start.
- 02AI Architecture Vision (tab 2) — the four layers. Open only the layer the Executor essay flagged, click it, and let the inspector speak. Coverage is demonstrated, not recited.
- 03Requirement Mapping (tab 3) — all 27 across the six levels. Use the Industry lens in the header: it covers eleven industries plus generic, and reframing the same 27 requirements in the customer's own language is the fastest credibility move in the tool.
- 04Self-Assessment (tab 4) — rate live only if the room asks for it; otherwise show the rubric and hand off to the workshop. When you do rate: the level is a gate, the gap chips name the exact requirements between them and the next level, and anything nobody rates stands at Not in Place. The maturity percentage on that panel is a progress ring — do not read it aloud, and never let it become the finding.
- 05Roadmap (tab 6) — sequences their mapped use cases into milestones, building each requirement once and letting later use cases run in parallel on what earlier ones already delivered. This is the artefact the workshop produces.
◉The answer — the only place a product is named
- 01One platform, four layers.
Teradata Autonomous Knowledge Platformanswers at every layer of the architecture rather than at one of them. Read only the layers the customer named. - 02Turn the Technology toggle on, in the header, in front of them. It ships off — switching it on when asked is the whole design. Each of the 27 requirements then shows the Teradata technology that delivers it, with a note on how.
- 03The Capability toggle maps each requirement onto the Teradata Capability Model. Use it with architects; skip it with the CDO.
- 04Turn both off again before you close. The last thing on screen should be their gap list, not our product column.
!Claim discipline — do not slip
✓Never call the Maturity Model "our framework." It is analyst-derived, and the moment you claim authorship you have converted a diagnostic into a brochure.
✓Name the frameworks, not "three analysts." The structure rests on six published ones: Forrester Data Fabric Q4 2025 · Forrester Data Governance Solutions Q3 2025 · Gartner D&A Governance MQ 2026 · Gartner Semantic Layer for AI 2025 · Gartner AI Engineering 2025 · IDC MarketScape Unified AI Governance 2025-26.
✕Never attribute an individual requirement to a research firm. The sourcing is framework-level, and deliberately so: as of 2026-08-19 the 27 requirement descriptions carry no analyst attributions at all, in EN or DE. Ten of them used to and seventeen never did, and that inconsistency was the exposure — a customer who clicked the wrong requirement could falsify the sentence on the spot. Now none of them can. So say what is true and provable: the framework is research-based and its sources are published, and a requirement earns its place by describing something the customer's estate actually needs. If asked "which analyst says A7?", answer with the requirement, not with a name — open it, read it, and invite them to reject it.
✕Never fabricate or estimate a maturity level for the customer. The model returns the level their own ratings imply — including good news, when they have earned it.
?Ask at the turn
- "Of the four layers, which has your organization invested in most heavily — and which one has been hardest to fund?"
- "Of the 27, if you had to name the five your team is weakest on, could you do it right now?"
- "When we rate this properly, who will disagree loudest — and about which layer?"
⚠Anticipated objections
"Why is the wall at Level 3? Our problem is much further up."
The model puts it there for a reason you can show them: Level 3 is where agents begin deciding inside a policy envelope, and it is gated by the Translation Layer. Most estates that believe their problem is agentic find their Level 3 gap chips full of Translation requirements. Open the chips and let them read it.
"Can we buy our way across the wall?"
Partly — and the model shows which requirements are product-answerable and which are not. Ontology, business-concept modelling and reusable business logic are organizational work with a technology component, not the reverse. A model that pretended otherwise would not survive the workshop.
"Show us your other customers' scores."
There are none to show, and that is deliberate: every rating is self-reported and stays in the customer's own browser. We bring the framework and the facilitation; they bring the estate.
"Two hours is a lot of my leadership team's time."
It is, and it is the ask. Twenty-seven requirements rated by the people who own them, with the disagreement out loud, is what produces a roadmap their own board cannot unpick. If time is genuinely short, they rate asynchronously first and spend the session on the disputes.
Transition to Section 4
You leave the room with two dates for the workshop — or you don't. Section 4 covers both, and the workshop day itself.
Section 04
After the meeting · Workshop or follow-up loop
Goal: Convert the meeting into a scheduled 2-hour AI Maturity Assessment workshop with named participants, and run it. If it doesn't close on a date, run the follow-up loop back through the Executor. Either way: the parable link is the only asset you send — the model is used live, never distributed.
◉Path A — the meeting closed on a workshop date
- 01Same day. Send a calendar hold with the parable link — that one asset, nothing else. Say: "Ask your team to walk the story before we meet; it makes the workshop twice as productive."
- 02Day 3. Send one specific requirement — from the 27 — that connects to something they said in the meeting. Do not send product decks, and do not send the model: it is run live, with you in the room.
- 03Day 7. Confirm participants. Insist on their most engaged CDO / CAIO / Head of Architecture plus one skeptic. The skeptic is what makes the result credible inside their organization.
- 04Day of workshop. Run the Self-Assessment together, live. Then one use case through the Use-Case Studio. Then the Roadmap. Two hours flat — the flow is below.
◉The 2-hour workshop flow
- 00–15Framing. Skip the parable — they have seen it. Set the stakes: "By the end of these two hours you will have a scored self-assessment against 27 named requirements, one use case mapped to the six levels, and a written implementation roadmap. Nothing committed."
- 15–75Self-Assessment (60 min). Rate all 27 together. Let their team disagree with each other — that is the value. Use Save as version at the midpoint so they can see how the score moved as the debate ran.
- 75–105Use-Case Studio (30 min). Take their most-cited use case and map it. Let them see the distance between what they rated and what the use case actually needs.
- 105–120Roadmap (15 min). Walk the generated roadmap and show where use cases inherit each other's requirements — each requirement built once. This is what they take back.
◉Path B — the meeting did NOT close on a date
- 01Same day. Do not send "let me know when to reschedule." Send the parable link plus one requirement, from the 27, that their own words flagged.
- 02Day 3. Return to the AI Strategy Executor and regenerate Stage 2 with the Follow-up (Day 3) variant. Include a memorable quote from the meeting itself — the Executor will weave it in.
- 03Day 7. Send one paragraph from The Ascent as a quote — the crux beat works best. No link. Force a reply.
- 04Day 14. Route through the internal partner network. If they have not replied they need a different door — usually a peer, or their boss's boss.
▶Workshop and follow-up guardrails
ANever override the customer's rating. If they rate Productionized where you believe they are weak, ask "what evidence would demonstrate that to your auditor?" and let them lower it themselves.
BCheck what the build in front of you can hand over — before you promise it. The edition linked from this pack (
-viewer-plus) has its Export control removed; ratings live in the browser as named versions instead. Open the workspace panel and look before the workshop, and if Export is absent, promise named versions plus a walked roadmap, not a file. If a customer must leave with a file, raise the edition question internally first.CWhat travels and what never does. Travels: the parable link. Used live and never sent: the AI Maturity Model — its own footer restricts sharing. Internal only, never sent: the base talk track, this guide, the Executor and the landing page.
!Every follow-up email complies with Guide D044422. First reference always
Teradata Autonomous Knowledge Platform. Never AI Factory, Artemis, AI Workbench, or ClearScape Analytics (as a product name). In-Database references say "features included in Teradata Database."◉Hand-off to the paid engagement
- ASKClose the workshop with the ask: "The five requirements you scored lowest — plus the use case we mapped — are exactly what the 3-month AI Services engagement addresses. Two weeks to scope it. Ready?"
- HANDThe roadmap they built is the scope document. Both the 3-month AI Services Base Offering and the 12-month Strategic Roadmap are sourced from it — not from a proposal you write afterwards.
- NO?If they are not ready: "Take the roadmap back to your team. Thirty minutes in two weeks, with any three of them, and let's talk about what changed."
?Debrief with yourself
- Which of the four layers did the customer's language actually concentrate on? Was it what the Executor essay predicted? If not — update the essay in your notes.
- Did they volunteer a level for themselves? Write down the exact words. That sentence opens the workshop.
- Which routing signal did they trip — Policy language (Sovereignty), P&L language (ROI), an existing assessment (calibration)? Even weakly.
- What was the memorable phrase from this meeting that becomes the Day-3 hook? Write it down before you forget it.
🔀Post-meeting hand-off matrix
CLOSEDPath A · 2h workshop scheduled. Collect their top use cases and current assessment in advance — the session starts faster with them named.
STALLEDPath B · Day-3 / Day-7 / Day-14 sequence. Cycle back through the Executor.
PIVOTCustomer signalled Sovereignty or ROI concerns. Route to The Kill Switch or The Cost of More. Loop back to Strategy when the pivot conversation seasons.
SIGNCustomer engages with the hand-off ask. Route to Sales / Deal Desk for AI Services scoping.
STEWARDCustomer wants to run the assessment with a wider internal audience. Offer to facilitate a second session and give them their own saved assessment — the model itself stays seller-operated.
End of guide
The AI Strategy play converts through the workshop. Everything before it is getting to the workshop. Everything after is selling from the roadmap the customer built themselves. Use the base talk track. Use this guide. Do not improvise a level.
The guide in one paragraph
The base talk track is the storyline. This guide is the sales choreography. Outreach → story → the turn → workshop — every level the customer's own, every claim one the model can show.
🎯 What "landed" looks like
The customer volunteers which layer they're weakest on. They ask who else on their team should see the Maturity Model. They accept two dates for the 2-hour Assessment workshop before you leave the room.
🛑 What "did not land" looks like
The customer engaged with the layers but did not volunteer a level. They asked for the deck. → Do not push. Send the parable link, loop back through the Executor with a Day-3 follow-up, and try again in two weeks.
📄 Companion assets in order
1. executor.html — persona-tuned outreach.
2. Base Talk Track EN · DE.
3. Interactive Maturity Model — opened at the turn, used live.
4. Landing page — the sales-play landing page.
🎯 Discipline you must never break
Analyst-grounded, not marketing. Never fabricate a level for the customer — the model returns the one their ratings imply. Never call the Maturity Model a "framework we developed" — it is analyst-derived (Forrester, Gartner, IDC). Never attribute an individual requirement to a research firm — the sourcing is framework-level, and the model's 27 descriptions carry no attributions by design. Naming per Guide D044422.