Progress

0 of 10 answered

1 · API Coverage

How many of your core business systems (CRM, billing, finance, ops) are connected via API integrations?

None — everything is exported to CSV and uploaded manuallyOne or two — the most painful flows are integrated, the rest are manualMost of the core systems — manual work happens only for edge casesAll core systems integrated, with documented data contracts between them

2 · API Coverage

What proportion of your business data lives in queryable, integration-ready systems?

Most of it is in spreadsheets, email, or legacy systems with no APIImportant data is queryable; long tail still in legacy systemsVast majority is in modern API-accessible systemsEverything is in API-accessible systems with documented schemas

3 · Integration Architecture

How do your integrations connect to each other architecturally?

Point-to-point — every system talks directly to every other systemMostly point-to-point with a couple of central hubs emergingClear hub-and-spoke architecture through a warehouse or integration platformMature event-driven architecture with documented contracts and versioning

4 · Integration Architecture

When you need to add a new integration, what does the process look like?

Greenfield every time — no reusable pattern to draw onSome patterns exist but each integration ends up bespoke anywayEstablished patterns; new integrations follow the same shape as existing onesStandardized template; new integrations ship in days using reusable infrastructure

5 · Observability

When an integration fails, how do you typically find out?

A user complains, or someone notices missing data days laterMix — some flows have alerts, others we find out reactivelyActive monitoring on most integrations; we usually catch failures within hoursComprehensive monitoring with paging; failures detected within minutes

6 · Observability

When you need to debug a failing integration, what tools do you have?

Whatever logs the source/destination systems happen to expose, ad-hocSome logging in place but reconstructing failures is hardStructured logs, metrics dashboards, and historical records for most flowsDistributed tracing, replay capability, full audit trail of every event

7 · Reliability

How often do your integrations fail in ways that require manual intervention?

Weekly or more — it's a meaningful part of someone's jobA few times a month — annoying but tolerableRarely — once a quarter at mostAlmost never — failures are self-healing or auto-retried

8 · Reliability

How are integration failures typically resolved?

Manual data fixes, often without root-cause analysisManual fixes plus occasional follow-up to prevent recurrenceRoot-cause analysis is standard; fixes prevent the same failure recurringAutomated remediation handles most failures; humans only handle novel ones

9 · Ownership

If a key integration broke tomorrow, who would own fixing it?

Nobody clearly — someone would scramble, then it would become whoever's freeOne person knows the system but they're already overloadedA named owner with documented runbooksNamed owner + on-call rotation + escalation paths

10 · Ownership

How well-documented are your integrations?

Tribal knowledge — the person who built it knows; nobody else doesSome integrations have docs; many do notMost integrations have architecture docs + runbooksAll integrations have version-controlled documentation that's kept current

Answer all 10 questions to see your score

What we measure

What This Assessment Measures

5 dimensions, 2 questions each. Each dimension predicts a different way integration efforts fail.

API Coverage

How many of your core business systems are API-accessible and actively integrated. Closed legacy systems set a hard ceiling.

Integration Architecture

Whether your integrations form a coherent design or point-to-point spaghetti. Spaghetti scales poorly past 10-15 integrations.

Observability

Whether you find out about failures from monitoring, or from users complaining. The single biggest gap at most maturity levels.

Reliability

How often integrations break, how fast they recover, how much manual cleanup follows. Reliability compounds; small failures become culture.

Ownership

Whether integrations have named owners and runbooks, or live in someone's memory. Bus-factor risk gets worse as the system grows.

Why it matters

Why Take 5 Minutes for This

→Most integration projects fail at the foundational layer, not the build layer — knowing your tier tells you where to invest.
→The dimension you score weakest on is usually the one that will cause your next integration project to stall.
→You'll get a specific recommendation for the highest-leverage next step, calibrated to your tier.
→Honest assessment beats vendor sales pitches — most iPaaS/integration platform purchases are premature for the buyer's actual maturity level.

What we measure

What This Assessment Measures

5 dimensions, 2 questions each. Each dimension predicts a different way integration efforts fail.

API Coverage

How many of your core business systems are API-accessible and actively integrated. Closed legacy systems set a hard ceiling.

Integration Architecture

Whether your integrations form a coherent design or point-to-point spaghetti. Spaghetti scales poorly past 10-15 integrations.

Observability

Whether you find out about failures from monitoring, or from users complaining. The single biggest gap at most maturity levels.

Reliability

How often integrations break, how fast they recover, how much manual cleanup follows. Reliability compounds; small failures become culture.

Ownership

Whether integrations have named owners and runbooks, or live in someone's memory. Bus-factor risk gets worse as the system grows.

Why it matters

Why Take 5 Minutes for This

→Most integration projects fail at the foundational layer, not the build layer — knowing your tier tells you where to invest.
→The dimension you score weakest on is usually the one that will cause your next integration project to stall.
→You'll get a specific recommendation for the highest-leverage next step, calibrated to your tier.
→Honest assessment beats vendor sales pitches — most iPaaS/integration platform purchases are premature for the buyer's actual maturity level.

How Mature Is Your Integration Infrastructure?

How many of your core business systems (CRM, billing, finance, ops) are connected via API integrations?

What proportion of your business data lives in queryable, integration-ready systems?

How do your integrations connect to each other architecturally?

When you need to add a new integration, what does the process look like?

When an integration fails, how do you typically find out?

When you need to debug a failing integration, what tools do you have?

How often do your integrations fail in ways that require manual intervention?

How are integration failures typically resolved?

If a key integration broke tomorrow, who would own fixing it?

How well-documented are your integrations?

What This Assessment Measures

API Coverage

Integration Architecture

Observability

Reliability

Ownership

Why Take 5 Minutes for This

System Integration Decision Framework

System Integration

How Mature Is Your Integration Infrastructure?

How many of your core business systems (CRM, billing, finance, ops) are connected via API integrations?

What proportion of your business data lives in queryable, integration-ready systems?

How do your integrations connect to each other architecturally?

When you need to add a new integration, what does the process look like?

When an integration fails, how do you typically find out?

When you need to debug a failing integration, what tools do you have?

How often do your integrations fail in ways that require manual intervention?

How are integration failures typically resolved?

If a key integration broke tomorrow, who would own fixing it?

How well-documented are your integrations?

What This Assessment Measures

API Coverage

Integration Architecture

Observability

Reliability

Ownership

Why Take 5 Minutes for This

System Integration Decision Framework

System Integration