Short answer: Only in very specific cases, and it usually means you need to hire a different type of person.
Most CSMs aren’t built for FDE work. That’s not a knock on them — they’re doing a completely different job.
A CSM manages relationships, mitigates renewal risk, and drives expansion across a portfolio of 8–12 accounts. An FDE embeds with 1–3 customers, writes and debugs workflows, clears deployment blockers daily, and owns whether the AI actually works in production. Those are not the same skill set. They’re barely the same profession.
When it can work:
You’ve got CSMs with actual engineering backgrounds or deep technical AI domain expertise. These folks can sometimes make the transition into embedded implementation roles. But they’re rare. And even then, you’re usually better off hiring purpose-built FDEs than trying to retrain relationship managers into builders.
The economic reality:
FDE work is expensive and slow by nature. A single customer deployment can take 30–60+ days of daily embedded time. Most CSMs can’t do that inside their existing book of business — they’d have to drop accounts or go part-time on implementation. That’s a losing trade on both sides.
What actually works:
Hire one strong FDE. Embed them with your top 3–5 customers. Document exactly what they do. Then systematize it.
Once you’ve cracked the implementation process and have a real playbook, you can scale with CSMs or implementation specialists who’ve seen it work. At that point, the CSM’s job is maintaining the relationship after deployment is solved — not fixing deployment itself.
Trying to turn your existing CSMs into FDEs usually tanks both roles. You lose the relationship coverage. You don’t gain real implementation depth. And your best CSMs get frustrated doing work they weren’t hired for.
Get one great FDE first. Build the playbook. Then scale.
Have a question for Dear SaaStr? Submit it at saastr.ai/ai-mentor
