# orr-zapier-support-ship-code-app-erosion-2025-11-23

## Veille

Autonomous support delivering code - Solving app erosion - Zapier engineering

## Titre Article

Empowering Support to Ship Code: Solving App Erosion

## Date

2025-11-23

## URL

https://www.youtube.com/live/cMSprbJ95jg?si=4HnxK8w1ELvSr4tz

## Keywords

technical support, app erosion, Zapier, support agents, code delivery, support automation, API integrations, continuous maintenance

## Authors

Lisa Orr

## Ton

**Profile**: Engineering leader at Zapier, pragmatic operational perspective, solution-oriented register, presentation focused on real-world problems

**Style**: Practical and direct presentation, centered on solving concrete problems. Professional yet accessible tone, using examples drawn from Zapier's experience. Authority derives from managing integrations at scale. Target audience: technical leaders, support teams, and developers dealing with the maintenance of complex integrations.

## Pense-betes

- **App Erosion**: Zapier's 8,000+ integrations, 14 years of existence, constantly changing APIs
- **Grand Canyon analogy**: Natural erosion vs app erosion, which never stops
- **Backlog crisis**: Tickets arrive faster than they are resolved
- **Experiment 1**: Support moves from triage to fixing bugs (guardrails, 4 target apps)
- **Experiment 2 - Scout**: Codegen project to solve erosion
- **Pain points**: 50% of time spent gathering context
- **Solution architecture**: Context Analyzer → Diff Generator → Test Generator
- **Results**: 97% MR success rate, resolution time reduced from 72h to minutes

## RésuméDe400mots

Lisa Orr, engineering leader at Zapier, presents how the company combats "app erosion" by empowering support teams to ship code. Using the Grand Canyon analogy - where natural erosion creates beauty over millions of years - she contrasts it with app erosion, which continuously degrades Zapier's 8,000+ integrations built over 14 years.

The problem is critical: third-party APIs change constantly, creating a **backlog crisis** where tickets arrive faster than they can be resolved. This generates reliability issues, poor customer experience, and potential churn. Faced with this reality, Zapier launched two parallel experiments two years ago.

**Experiment 1** transforms the support role: from simple triage to active bug fixing. The approach is cautious, with guardrails: focus on 4 target apps, mandatory engineering review, limited to app fixes. The motivation is strong because erosion represents a major source of bugs, support is eager to learn (many want to become engineers), and some members were already helping informally.

**Experiment 2 - Scout** uses generative AI to accelerate fixes. The process begins with "dog fooding" (Orr herself fixes apps), observing engineers and support, and identifying pain points. Key discovery: **50% of the time is spent gathering the context** needed to understand the problem.

Scout's architecture comprises three main components:
1. **Context Analyzer**: Automatically gathers tickets, error logs, API documentation, source code
2. **Diff Generator**: Creates fixes based on the analyzed context
3. **Test Generator**: Generates tests to validate the fixes

The results are remarkable. The **merge request success rate reaches 97%**, with only 3% requiring minor modifications. Resolution time drops from **72 hours to a few minutes**. The cultural impact is profound: support feels valued, engineering is freed up for innovation, and the boundary between roles blurs.

Orr emphasizes that this transformation is not merely a technical optimization but a strategic necessity. In an ecosystem where integrations are central and erosion is inevitable, the capacity for agile maintenance becomes a competitive advantage. Empowering support through AI represents a fundamental organizational evolution for surviving in a world of perpetually changing APIs.

## GrapheDeConnaissance

- Lisa Orr —travaille_chez→ Zapier (ORGANISATION, 0.98)
- Zapier —mesure→ 8000+ intégrations gérées (MESURE, 0.97)
- érosion applicative —observé_dans→ Zapier (ORGANISATION, 0.95)
- changements constants APIs tierces —a_créé→ érosion applicative (CONCEPT, 0.93)
- Scout —résout→ érosion applicative (CONCEPT, 0.92)
- Context Analyzer —fait_partie_de→ Scout (TECHNOLOGIE, 0.9)
- Diff Generator —fait_partie_de→ Scout (TECHNOLOGIE, 0.9)
- Test Generator —fait_partie_de→ Scout (TECHNOLOGIE, 0.9)
- Scout —mesure→ 97% de taux de réussite des MR (MESURE, 0.95)
- Scout —réduit→ temps de résolution de 72h à quelques minutes (CONCEPT, 0.93)
- équipe support —converge_avec→ livraison de code (CONCEPT, 0.9)
- Lisa Orr —mesure→ 50% du temps passé à rassembler le contexte (MESURE, 0.88)

---
Canonical: https://www.thekb.eu/en/fiches/orr-zapier-support-ship-code-app-erosion-2025-11-23/