Most SaaS integrations run for years without anyone knowing how they work or why they were built that way.
This package changes that — with two documents, built from your codebase.
The integration specification answers "how was this designed?" — business purpose, data model, field mappings, source of truth, and design assumptions.
The operational runbook answers "what do we do when it breaks?" — monitoring signals, failure modes, triage steps, and recovery guidance.
They're written to reference each other, serving different readers for different situations.
What's included:
Integration specification: scope, data flow, field mappings, error handling design, dependencies
Most SaaS integrations run for years without anyone knowing how they work or why they were built that way.
This package changes that — with two documents, built from your codebase.
The integration specification answers "how was this designed?" — business purpose, data model, field mappings, source of truth, and design assumptions.
The operational runbook answers "what do we do when it breaks?" — monitoring signals, failure modes, triage steps, and recovery guidance.
They're written to reference each other, serving different readers for different situations.
What's included:
Integration specification: scope, data flow, field mappings, error handling design, dependencies