Vendor Crosswalk
Who this is for. You are the vendor-side FDE or delivery engineer, on site at a client under contract, pushing an AI system from demo to production. The text keeps saying "the business side", "your manager", "project approval", "renewed funding", and you wonder what they mean for you.
One Judgment First
The last mile is defined by crossing one organizational boundary and keeping an AI system alive in the real workflow beyond it. Whether that boundary is a company wall or a department wall changes how visible the mechanisms are, not the mechanisms themselves. The text is set inside a company because that scene hides them deepest. Contract, price tag, payment milestones, exit date, none exist there, so the book rebuilds their functions one by one. Your scene is the explicit version of the same mechanisms. Trust starts at zero, commitment is contractual, exit has written clauses, every mechanism is on the table.
Read it this way. Learn the mechanism from the text, then use this table to land it in the document you hold. Usually what the text labors to rebuild is one line in your contract, and the reminder is that a line is not a working mechanism.
Concept Crosswalk
| Concept in the Text | Vendor-Side Equivalent | Chapter |
|---|---|---|
| Business side / requesting side | The client | Whole book |
| Your team, the Digital Center | Your vendor firm, delivery team | Whole book |
| Your manager (Owen Hartley) | Your commercial and delivery leads | Chapters 2, 4, 22 |
| Project approval form, old ticket's wording | Procurement contract, acceptance clauses | Chapter 4 |
| Four charter signatures (business line head, business owner, you, your manager) | Three signatures, client decision-maker, client owner, you; commercial contract signed separately | Chapter 4 |
| Business-side commitment (charter element 5) | Client commitment, same names, hours, calendar slots | Chapters 4, 15 |
| Your team's commitment and protection conditions | Staffing clauses in contract | Chapter 4 |
| Three tiers of resource reassessment | Exit clauses, "if the client's committed input goes unmet two weeks running, we may propose a pause" | Chapters 4, 13, 18 |
| Launch release conditions | Acceptance clauses tied to the eval | Chapters 4, 11 |
| Three resource gates (named commitments claimed / renewed funding tied to the gates / fixed reassessment date) | Three money gates (paid pilot / payments tied to thresholds, not dates / expiry exit in contract) | Chapter 14 |
| The two claims-ops IT engineers, co-build engineers | Client engineers | Chapters 8, 10, 15 |
| Module CODEOWNERS, merge rights, oncall ownership | Code in client's repo, external collaborator accounts | Chapter 15 |
| Annual budget and headcount review, renewed funding | Renewal meeting, keeping the engagement alive | Chapters 19, 22 |
| Three mandatory handoff mechanisms (no ops headcount / into your OKRs / transfer ledger) | Contract end date | Chapter 22 |
| Responsibility transfer agreement, stepping out of the daily | Exit agreement, account revocation, physical exit | Chapter 22 |
| Capacity ledger | Day-rate pricing and margin | Chapter 23 |
| Group platform team | Your own product team | Chapter 24 |
| Intake gate and its non-monetary price | Screening requests by quote | Chapter 25 |
| Switching subsidiaries, dual Group and subsidiary sponsors | Switching clients | Chapter 26 |
| Stakeholder map, field archaeology, data fitness, eval as spec, action queue, adoption engineering | Apply as is, change nothing | Chapters 5–21 |
Five Real Divergences
The crosswalk translates. These five are structural. Six chapters carry a "Vendor View" sidebar (4, 14, 15, 22, 23, 26). Here is the summary.
1. You have an exit (Chapter 22). The text spends three paragraphs rebuilding mandatory handoff mechanisms because the internal deliverer cannot leave. You have a contract end date, so the deadline is ready-made. The cost is the flip side, a clean break. The response window is not a given. It goes into the exit agreement, with the account revocation date. The five self-sufficiency tests and four stages apply as is, and for you the fourth stage is a physical event.
2. You can name a price (Chapter 25). The intake gate and its non-monetary price filter for teams that cannot quote. Your quote alone screens out half the ideas. The cost is sales pressure. The gain from taking a job is booked at once to the taker, the cost of delivery late, to you. The vendor-side failure mode 1 is still taking everything. The three red lines and the three steps to no hold as is.
3. You are the hired expert (Chapter 5). The internal deliverer is no prophet at home, low start, low ceiling. You are the reverse, negative opening balance, high ceiling. "Hired" carries authority, and the expectation of "use and dismiss". You have no depth here. The last failed project's real cause of death takes you six weeks to unearth, and what an internal reader says in a sentence, you probe for with a pre-mortem. Helping Kevin Doyle for 40 minutes and no more is a strong signal. You are an outsider, so not overstepping is itself evidence.
4. Money has a shape (Chapters 4, 14). The text replaces the price tag with named commitments, funding milestones, and a reassessment date. You have a price tag. "Let's wait and see" costs the client an invoice, so a zombie pilot dies faster than inside. The cost is contract language dragging the charter into legalese, the vendor-side failure mode 1. Charter and contract must be two documents.
5. Complexity jumps by changing clients (Chapter 26). The internal reader must ask for the awkward business lines, because one company's projects converge in difficulty. Changing clients changes complexity, and the risk of moving sideways is more visible. Ten clients in five years at one difficulty, and your rate will not move. The three paths out are the original for you, founder, product leader, field CTO.
Two Natural Assets, Two Traps
Asset one, explicit mechanisms. Contract, price tag, and exit date force out expectations, filtering, decisions, and handoff, so the three chapters that rebuild them (4, 14, 22) read faster. Asset two, the neutral seat. You are an outsider. "That is not mine to decide" is a buffer, and the client owner issuing the governance pledge comes naturally.
Trap one, dependency addiction. Stable renewals, comfortable revenue, being needed. Three comfortable parties, none with a reason to break it, the vendor-side failure mode 3 of Chapter 22. Trap two, resetting to zero. Field archaeology, trust balance, constraint baseline, dug up anew with every client. You lack the internal reader's depth, so the pattern library (Chapter 23) is priced higher.
Reading Advice
Start at Chapter 0 as written. The opening 48 hours hold, only the clock starts the day you arrive. Read straight through, and at project approval, renewed funding, or your manager's signature, come back here to translate. Chapters 4, 14, 15, 22, 23, 26 each end with a "Vendor View" on where that chapter's boundary truly differs.