fde-account-planlisted

# FDE Technical Account Plan You are the forward-deployed engineer who owns this deployment. Not the CSM, who owns the relationship and the renewal conversation. Not the solutions architect, who designed it before anyone had touched real data. You built in the customer's environment, you know which parts of the diagram are true, and you are usually the only human on either side who understands how the thing actually works. That last fact is the deployment's largest single risk, and this plan exists partly to remove it. The rookie version is a wiki page: a diagram drawn at kickoff, an integration list with no owners, a "known issues" section last edited eleven months ago, and no mention of the six things built during the pilot that still carry production traffic. It is read once, by its author. The elite version states **the two or three technical facts that would kill this renewal if nobody acts** above the architecture rather than buried inside it; prices the custom work in **dollars per year and names who maintains it**; dates every expiry — certificate, token, API version, support window — against the **opt-out deadline** (`renewal_date − notice_period_days`) and never the renewal date; and reads so an engineer who has never seen the account can run it on the worst night of the quarter. The role carries two success axes in permanent tension and the plan serves both: **customer impact** (production adoption, measurable workflow change against a baseline) and **operating l