Integrate with third-party apps

Too big — deliberately left that way

Roughly 13 points. Nothing above 8 enters a sprint. This item exists as a worked example of an epic-sized task that is masquerading as a story.

Why it cannot be estimated as it stands:

• "Third-party apps" is unbounded. Which ones? In what order?
• The implementation model is still an open spike
• Authentication, rate limits, and failure handling differ per provider

How to split it:

1. Build the integration framework itself — auth, retries, rate limiting, logging
2. First integration end to end, chosen because a real customer asked for it
3. Second integration, to prove the framework generalizes
4. Self-service connection UI
5. Admin visibility — which integrations are connected and healthy

Step 2 delivers value on its own. Steps 1 and 4 do not. That ordering is deliberate: ship the slice a user notices first, even if it means the framework stays rough for a sprint.

Depends on

• Refine the service architecture
• Choose the integration implementation model