{
  "schema_version": "1.1",
  "id": "s8:https://www.youtube.com/watch?v=7wu2hsRfvV0",
  "slug": "how-forward-deployed-engineering-is-done-at-decagon-sunny-rekhi-02myrh1",
  "url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-decagon-sunny-rekhi-02myrh1",
  "title": "How Forward Deployed Engineering is done at Decagon — Sunny Rekhi",
  "why_included": "Decagon splits deployment between configuring each customer’s agent and turning repeated enterprise requests into product features. The scarce skill is resisting brittle one-offs.",
  "summary": "Decagon describes two deployed functions: configure the customer’s agent and turn field requests into reusable product work. After roughly **25 custom integrations**, it built a self-serve path; the company also grew from **50 to 500 people** in a year.",
  "practical_implication": "Builders should record the desired outcome before implementation, prove value on a narrow workflow, and inspect every custom request for reuse. If engineers repeatedly configure the same behavior, move that capability into natural-language or self-serve product controls.",
  "agent_context": "Decagon describes two deployed functions: configure the customer’s agent and turn field requests into reusable product work. After roughly **25 custom integrations**, it built a self-serve path; the company also grew from **50 to 500 people** in a year.\n\nBuilders should record the desired outcome before implementation, prove value on a narrow workflow, and inspect every custom request for reuse. If engineers repeatedly configure the same behavior, move that capability into natural-language or self-serve product controls.\n\nThe approach depends on distinguishing repeatable needs from genuinely customer-specific ones. Productizing too early can overgeneralize a single account’s constraints, while moving fast with patches can leave customers owning a brittle black box.",
  "source": {
    "name": "AI Engineer",
    "url": "https://www.youtube.com/watch?v=7wu2hsRfvV0",
    "published_at": "2026-07-28T17:00:35.000Z"
  },
  "source_class": "video",
  "content_type": "Video",
  "layer": "agent",
  "domains": [
    "coding"
  ],
  "topics": [
    "harness-engineering",
    "context-engineering",
    "enterprise"
  ],
  "verification": {
    "status": "source_linked",
    "label": "Source Linked",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "The approach depends on distinguishing repeatable needs from genuinely customer-specific ones. Productizing too early can overgeneralize a single account’s constraints, while moving fast with patches can leave customers owning a brittle black box."
  ],
  "connected_context": {
    "meaning": "This makes repeated customer configuration a concrete product signal: prove a narrow outcome, detect recurring requests, then replace bespoke engineering with reusable controls. It confirms forward deployment as a route to product leverage while defining its central judgment call—when evidence is sufficient to generalize—because premature productization and prolonged patching create different forms of brittleness.",
    "corpus_size": 262,
    "generated_at": "2026-07-29T10:05:45.020Z",
    "connections": [
      {
        "title": "How Forward Deployed Engineering is done at Kepler — Vinoo Ganesh",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=1OMHGsUZiqA",
        "feed7_url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-kepler-vinoo-ganesh-0thtvuc",
        "reason": "Kepler independently reinforces Decagon’s discovery mechanism: small field fixes and repeated customer language become inputs to durable product capabilities."
      },
      {
        "title": "How Forward Deployed Engineering is done at Ramp — Leo Mehr",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=ITMXwI6QL6A",
        "feed7_url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-ramp-leo-mehr-1w1rztz",
        "reason": "Ramp’s structured intake is a prerequisite for Decagon’s reuse decision because urgency, users, workarounds, and platforms help distinguish recurring needs from account-specific requests."
      },
      {
        "title": "Forward Deployed Engineering at Cursor — Pauline Brunet",
        "source_name": "YouTube",
        "source_url": "https://www.youtube.com/watch?v=APqXGyCoGW4",
        "feed7_url": "https://feed7.dev/p/forward-deployed-engineering-at-cursor-pauline-brunet-1wkd3r1",
        "reason": "Cursor’s customer ownership and documented handoff address Decagon’s risk that fast custom patches leave customers dependent on a brittle black box."
      },
      {
        "title": "How Forward Deployed Engineering is done at Factory — Eno Reyes",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=wpOA-UXynoM",
        "feed7_url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-factory-eno-reyes-0zgscmd",
        "reason": "Factory’s instrumentation and validators provide an implementation consequence for Decagon’s model: the path from field request to reusable feature needs observable outcomes and validation before autonomy expands."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-07-28T17:00:35.000Z",
  "modified_at": "2026-07-28T17:00:35.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-decagon-sunny-rekhi-02myrh1",
    "json": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-decagon-sunny-rekhi-02myrh1.json",
    "markdown": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-decagon-sunny-rekhi-02myrh1.md"
  }
}