Migration & Modernisation
Interface math calculator
How many interfaces does point-to-point actually cost you, against routing through a layer? Run it on your own estate size.
Save inputs locally to resume this tool. Files may contain sensitive entered information; review before sharing. No automatic storage or transmission. Report JSON is an output record, not an input import format.
Count everything: ERP, CRM, WMS, billing, the data platform, each partner EDI link, the reporting tool nobody owns.
Fully loaded, including the people who get pulled in when a partner feed breaks on a Sunday.
Point-to-point
66
interfaces to build, test and own
Through a layer
12
and one place to govern them
At 12 systems, point-to-point means 54 more interfaces than routing through a layer.
At a conservative 24 hours of upkeep per interface per year, that is 1,296 hours — about ₹77,76,000 a year, before anyone builds anything new.
The upkeep figure is an assumption, not a measurement — change it in your head if yours is different. The interface counts are not assumptions: n(n−1)/2 against n is arithmetic, and it is why estates that grew one urgent project at a time become impossible to change.
More in this category
These exist because the underlying problem is real. If the numbers you just put in look uncomfortable, that is usually worth a conversation.
Stay ahead of the integration layer.
Integronauts Signal — practical enterprise integration, API and agentic AI thinking. The tools stay free either way.
Integronauts Signal is launching soon.
Practical enterprise integration, APIs, agentic AI and emerging architecture. Sign-up opens when the list does — nothing to enter yet.