Rahul Kayala, Co-founder and CEO. 25 August 2026.
Early access opens September 8th, 2026, and you can sign up here.
A year of building across hundreds of enterprise systems
Over the past year, Echelon has implemented, enhanced, & maintained modules, objects & workflows across many enterprise systems, including security workflows, source-to-pay, employee onboarding, invoice reconciliation, and plenty more. We have become the most capable execution layer available for ServiceNow delivery teams, leading customers to push Echelon beyond ServiceNow to complete requests across other systems.
A source-to-pay request opens in Workday and settles in ServiceNow. Onboarding touches identity, HR, and finance before anyone gets a laptop. In each of those cases our customers often ask us to implement & maintain not just ServiceNow but the whole process across all other systems involved.
Across all systems requested in the last 12 months, SAP is by far the most common.
Why SAP? And why multi-system?
~90% of the Fortune 500 use ServiceNow. ~90% of the same group also use SAP.
For enterprises, ServiceNow & SAP means two systems of record, two sets of specialists, two backlogs, and two governance models. For many, the headaches are not only at each system’s level, but in the cross-system interface - i.e. where a workflow bridges from one to the other.
As a team uses Echelon to implement & maintain ServiceNow & SAP individually, the power of Echelon grows further. The platform absorbs the broader context graph of your business: i.e. the cross-system processes that make a business work. With Echelon capable of working in both SAP & ServiceNow, it can now reliably understand, architect, & maintain integrations & workflows between the two.
An agent swarm built for enterprise system complexity
The hard part of building inside ServiceNow is understanding what already exists & why it was configured that way:every enterprise platform, from SAP to Workday, suffers that problem. A platform accumulates a decade of decisions: custom tables layered on custom tables, business rules written by someone who left the company, a routing framework built in-house because the platform did not offer one yet. If an agent only knows the vendor documentation, that agent is useless in a live instance, because no live instance matches the documentation.
The same reality exists in SAP, whether you’re pre or post-SAP S/4Hana migration.
Building a harness capable of handling this variability was a critical step in Echelon’s roadmap. It is why Echelon asks questions back before it builds, why it pushes toward out-of-box before custom, and why it walks a person through a process step by step instead of committing to a build on the first prompt.
What happens on September 8
As of today, you can now sign up to gain early access to Echelon for SAP, which will release September 8th for a select number of SAP customers.
What can I do with Echelon on SAP
- Understand: Searches & documents every object in your SAP instance & how it is used: callers, dependencies, real usage, clean-core exposure.
- Triage: Turn tens of scattered logs from a failure into a ranked issue set: business object, failing layer, impact, owner, next action.
- Adapt:Turns every SAP release into a delta against your estate, with a consumable list of what changes, what breaks, and what to remediate.
- Modernize: Retires what is dead, moves what SAP now covers to standard, and rewrites the rest on released APIs.
- Prove: Ships before-and-after reconciliation and a regression pack with every object, ATC-clean against the target release.
Governance works the same way it does on ServiceNow. Output lands in a sub-production environment behind a developer approval gate, and nothing reaches production without a person signing off on it.
Frequently asked questions
When is Echelon for SAP available?
September 8th, 2026. Today is the announcement. If you want to be in the first group, the sign-up is open now and we are taking teams in order.
Does this change anything about Echelon for ServiceNow?
Nothing changes. We continue to invest heavily in Echelon for ServiceNow’s development, and every customer running Echelon on ServiceNow today keeps the same product, the same roadmap, and the same team. SAP is an addition to what Echelon can reach.
What comes after SAP?
Beyond the fact that we have the most demand from our customers for SAP, SAP was already the largest system on the other side of the workflows we were building. Source-to-pay, invoice reconciliation, and onboarding all cross into SAP.
Beyond SAP, we get constant requests for Salesforce, Workday, Oracle, Coupa, & more systems used by enterprises globally.
Tell us what system you’d want to see next & why.
Getting in
Early access opens September 8 and we are taking teams in order. Add your team to the list for early SAP access, or book a demo if you want to see what Echelon does on ServiceNow first. If you are new to what we build, the introduction is here.
.webp)