Support should prove itself first.

Assay builds Trace, AI-run support for SAP ECC. It is tested on a company’s own closed tickets before it touches production, earns the right to work alone one task at a time, and is paid for results instead of hours.

Become a design partner Where we are today

Assay at a glance

Founded
2026
Based in
India, working with ECC teams anywhere
Building
Trace, AI-run support for SAP ECC
Stage
Working prototype, founder-led
Model
Free Replay, a paid pilot on one task, then a fixed annual fee with 15% at risk

ECC still runs thousands of businesses. Its support model has not changed in twenty years, and the clock is now running.

  1. 31 Dec 2027SAP’s mainstream maintenance ends for ECC 6.0, enhancement packages 6 to 8.
  2. End of 2030Optional extended maintenance ends. It costs more, and the daily support work stays the same.
  3. Until thenThe engineers who know each landscape are needed on the move to S/4HANA, while ECC still breaks every day.

Support is sold by the hour

Most ECC support is a team billed on effort. The vendor earns more when tickets take longer, and the knowledge leaves when the people do.

The work is repeatable

Stuck interfaces, cancelled jobs, locks and missing outputs come back every week. Repeatable work with reversible fixes is where AI is safe.

AI support is already real

SAP says AI fully resolves about 20% of its own support tickets (self-reported, 2026). What buyers lack is a way to check a vendor before they trust it.

Dates: SAP maintenance strategy for ECC 6.0. Check your own contract. Read our guide to ECC after 2027.

What we believe. Three rules we hold ourselves to, in the product and in how we sell it.

01

Proof before payment

A vendor should be tested on your own history before you sign. Every engagement starts with a blind Replay on 1,000 of your closed tickets, graded by an architect you choose. We never grade ourselves.

02

Safety before speed

Only reversible fixes ever run alone. Anything that moves money, changes access or can’t be undone waits for a person. Every action is written to an audit trail you can hand to your auditors.

03

Say what is true

No invented customers, logos or numbers. Product screens on this site are examples and say so. When we publish a result, we say how it was measured and what it doesn’t prove.

Where we are today. Early, and open about it.

  1. Done

    A working prototype of Trace

    Triage that reads tickets against SAP evidence, safety checks before any fix, approvals, and a hash-chained audit trail.

  2. Done

    A first Replay on 1,000 synthetic tickets

    30.6% handled alone, 0.3% unsafe. We wrote the tickets ourselves, so this tests the pipeline, not the market. What it taught us.

  3. Next

    Replays on real customer tickets

    The first Replays with design partners, with the pass mark agreed in writing before any ticket is graded.

  4. Next

    The design-partner programme

    Five places for ECC teams, open until 30 June 2027: a free Replay, then a paid pilot on one task.

  5. Plan

    From ECC to the move itself

    The system map Trace builds of each landscape could help scope and support the move to S/4HANA. We haven’t built this, and we’ll say so until we have.

The team. Founder-led today, and hiring the people who have kept ECC running at 2 a.m.

Hiring now

Founding SAP architect

Ten years or more in ECC basis, ABAP or functional support. Shapes the runbooks Trace runs.

See the roles Hiring now

Senior SAP engineers

Hands-on with IDocs, jobs and authorizations. Take the tickets Trace hands over and turn fixes into runbooks.

See the roles
Talk to us

Partners, investors and press

If you run SAP ECC support, have spent years doing it, or want to back the work, write to us.

hello@assayams.com

Be one of the first five.

Design partners get a free Replay on their own closed tickets and shape what Trace does next. Five places, open until 30 June 2027.