Checklist

Third-Party Integration Readiness Checklist

28 questions that show whether a vendor outage would hit one feature or your whole platform.

Who it’s for

For engineering leads whose services call CRMs, payment providers or ERPs directly, and who suspect a provider change would break more than one team.

The full checklist has 28 checks. Here is the first section.

An inventory lists every third-party system and every service that calls it.
You cannot reduce coupling you have not counted.
Each integration has exactly one owning service or team, and everyone else goes through it.
When a provider changes, there is one place to fix and one person to call.
The number of services calling each vendor directly is one, or is known and shrinking.
Three services calling a payment provider means three places to break.
A named person watches each vendor's changelog and deprecation notices.
Breaking changes should arrive as planned work, not as a production incident.
Vendor credentials live in one secret store with one rotation owner.
Scattered credentials mean a rotation breaks something nobody remembered.

Is it really free?: Yes. No payment and no sales call. You give me an email address and the PDF is yours.
What will you do with my email?: Send you the occasional note about similar resources and new writing. Reply “stop” and I’ll remove you.
Can I share it with my team?: Please do. Print it, adapt it, put it in your wiki. A link back to the site is appreciated.