{ "video": { "id": "7wu2hsRfvV0", "title": "How Forward Deployed Engineering is done at Decagon — Sunny Rekhi", "duration": 1089, "upload_date": null, "channel": "AI Engineer", "source": "AI Engineer", "event_format": "In person" }, "analysis": { "video_id": "7wu2hsRfvV0", "title": "How Forward Deployed Engineering is done at Decagon — Sunny Rekhi", "one_liner": "Decagon's CTO of Forward Deployed Engineering explains how they scaled from 50 to 500 people by splitting FDE into agent builders and agent software engineers, treating forward deployment as identical to product engineering, and turning every custom fix into product — because now that AI coding is cheap, the scarce skill is restraint.", "summary": "Sunny Rekhi describes Decagon's two forward-deployed motions: configuring the AI customer-service agent brain for each enterprise (tonality, intents, handoffs, backend actions) and acting as the front line that pulls customer product asks back into the platform. He argues the line between forward deployed and product engineering is gone at Decagon — same bar, same reporting structure, often the same team — and that at 500 people the job shifted from doing deals to designing a system where field knowledge compounds. The recurring discipline is refusing the easy one-off: when enterprise A asks for something, build it so B, C, D and E get it before they ask, and keep converting custom work into self-serve.", "key_points": [ "Decagon replaces IVR phone trees and two-to-three-business-day email support with a 24/7 multilingual, omni-channel human-like agent; it lands on complex inbound support deflection then expands into revenue workflows — Hertz now uses Decagon to proactively reach out when a customer's car lease is due to renew or extend.", "Two kinds of forward deployment: configuring the agent brain (what to say when a user asks X, brand tonality, which intents hand off to a human, backend integrations so the agent can act — e.g. auth system access for a password reset), and being the front line for customer product asks.", "Forward deployment engineering is identical to product engineering at Decagon — same bar, same reporting structure, often the same team, reflected in the org chart; a Fortune 20 pain point is usually a product feature to build and prioritize.", "Growing from 50 to 500 people in a year forced a split of the old 'agent software engineer' role into two lanes: agent builders (Decagon pros with intuition for the models, living in the UI, flagging when work must go off-UI) and agent software engineers (productizing enterprise asks).", "The temptation is to prompt Codex or Claude Code to ship a customer's one-off ask immediately; Rekhi's counter is that agents are built to be owned by the customer, and a black box of prompts and patches is far too brittle.", "After building roughly 25 custom CRM-style integrations one at a time, they stopped and built a self-serve path — what took an engineer writing custom code is now done by the customer or the agent-building team.", "Industry experts are staffed by vertical: the team that ran financial services A, B and C gets the new financial services D logo, so lingo, credibility, ramp speed and the definition of success carry over and every deployment is faster than the last.", "Decagon ingests a customer's historical support data and tells them which workflows to automate first for highest ROI — often not what the customer originally reached out about.", "Scope success in the very first conversations and get it in writing: target metrics and which channels (phone, email, text, WhatsApp), because AI coding has pushed more effort up front into requirements gathering and alignment." ], "takeaways": [ "Before shipping a one-off for your loudest customer, ask how the same ask lands for customers B through E in two weeks — architect for them, and exercise restraint even though AI coding makes the quick patch trivial.", "Count how many times your team has hand-built the same thing; when the number gets embarrassing (25 integrations, in their case), stop and build the self-serve version so the work leaves engineering entirely.", "Treat 'custom becomes self-serve' as a standing rule: every manual step a forward-deployed person takes should be upstreamed into the product.", "Lock down what success means — specific metrics and channels, in writing — in the earliest scoping conversations rather than racing to start building for a large enterprise.", "Use the cross-customer pattern knowledge you have as a forward-deployed person to advise, not just execute: recommend the highest-ROI thing to automate first even when the customer asked for something else.", "In enterprise deals, deliberately pick the fastest path to demonstrated value instead of the full kitchen-sink scope, then expand inside what is meant to be a multi-year partnership." ], "topics": [ "forward-deployed-engineering", "agents", "customer-support-automation", "enterprise-ai", "scaling-teams", "productization", "deployment" ], "tools": [ "Decagon", "Hertz", "Codex", "Claude Code", "WhatsApp" ], "quotes": [ { "text": "the scarce skill now that AI coding is so good, the scarce skill is actually exercising restraint.", "at": "08:16", "url": "https://www.youtube.com/watch?v=7wu2hsRfvV0&t=496s" }, { "text": "at Decagon, forward deployment engineering is identical to product engineering.", "at": "05:21", "url": "https://www.youtube.com/watch?v=7wu2hsRfvV0&t=321s" }, { "text": "enterprise A made this ask. I know in 2 weeks enterprise B is also going to have the same ask.", "at": "04:46", "url": "https://www.youtube.com/watch?v=7wu2hsRfvV0&t=286s" }, { "text": "How do we smoothen out that path? Custom becomes self-serve. Custom becomes self-serve.", "at": "15:16", "url": "https://www.youtube.com/watch?v=7wu2hsRfvV0&t=916s" }, { "text": "you're you should treat yourself as an advisor rather than just an executor", "at": "14:00", "url": "https://www.youtube.com/watch?v=7wu2hsRfvV0&t=840s" } ], "words": 3907 }, "summary_url": "/#7wu2hsRfvV0", "transcript": { "html": "/transcripts/7wu2hsRfvV0.html", "txt": "/transcripts/7wu2hsRfvV0.txt", "vtt": "/transcripts/7wu2hsRfvV0.vtt" } }