The Politics of Forward Deployment: Stakeholders, Saboteurs, and Sponsors

Your RAG pipeline achieves ninety-two percent faithfulness on the golden set. Adoption is four percent. The problem was never technical. Forward Deployed success is roughly forty percent engineering and sixty percent organizational navigation. Naming the political patterns early keeps engineers from blaming the model when the room was the bottleneck.

Stakeholder archetypes you will meet

The Champion wants you to succeed — sometimes too much — and may overpromise upward before production readiness. Protect them with honest status and never let them demo features you have not tested on their data.

The Gatekeeper in IT or Security is not evil; they are risk-averse. Invite them early. Show guardrails, logging, and data flow diagrams before they ask. Surprise security reviews kill timelines.

The Saboteur loses budget or status if your project wins. They will not attack openly; they will slow credential approvals, question vendor risk, or redirect attention to competing initiatives. Document decisions in shared systems; escalate blockers with facts, not emotion.

The Enthusiast wants forty-seven use cases without prioritization. They are valuable for discovery and dangerous for scope. Channel enthusiasm into the backlog; ship one win before expanding.

The Ghost Sponsor signed the SOW and disappeared. Without executive air cover, Gatekeepers win by default. The FDM or senior FDE must re-engage sponsors with metric readouts, not technical deep dives.

Tactics that work in the field

Weekly demos to end users, not only executives. Practitioners tell you what breaks; VPs tell you what sounds good.

Make the power user your co-designer. If Sarah is the workaround, Sarah should feel ownership of the tool that replaces her Slack DMs.

Kill use cases publicly with data — "transactional intent only twelve percent of volume; we defer to phase two." Clients trust FDEs who say no with evidence.

Security as partner: run a thirty-minute threat modeling session in week one. Show PII redaction and escalation paths. Faster approvals follow.

When to escalate versus absorb

Absorb: minor UX complaints, training gaps, one-off data quirks you can script around. Escalate: blocked production credentials past agreed date, scope changes that double timeline without budget change, compliance objections that require architectural shifts, Saboteur behavior affecting mission-critical timelines.

Partnership with Forward Deployed Managers

FDMs handle commercial framing and executive cadence; FDEs handle technical truth. Never let commercial pressure ship unaudited high-risk automation. The dyad works when both can say "not yet" to the client without blame between them.

Red flags to re-scope or exit

Sponsor refuses to join a single status call for six weeks. Customer will not provide sample data but expects production dates. Success criteria redefine after every demo. You are the only person who understands the system and they treat that as permanent staff augmentation without renewal conversation.

Politics is not distraction from engineering — it is part of the system you deploy into. FDEs who learn this early stay in demand long after the LLM framework hype cycle moves on.