Repeat-case operators
You need a stronger operational route than a single one-case purchase: repeated records, workflow helpers, and predictable handling across multiple matters.
Start with workflows →Teams, integrations & adoption
Repeat-case operations, cross-pack adoption routes, and the future diagnostic layer live here.
This route exists to keep the self-serve buyer path clean. If you need repeated use, reviewer tooling, SDK help, schema work, or white-label diagnostic adoption, start here instead.
Choose the adoption route
Reviewers & portals
You need read-only verification surfaces like the widget, browser extension, PWA, or offline reader support.
Reviewer tooling →Developers, implementers & adopters
You need SDK, CLI, protocol reference, schema work, or embedded-case infrastructure to work with ERF-compatible records inside your own environment.
Platform adoption
The long-term product is an adoptable diagnostic layer.
Schema
One canonical case object for orders, payments, shipments, messages, deadlines, and evidence relations.
Fault registry
One language of case weakness that partner systems can understand and surface inside their own workflows.
Integration layer
API, SDK, widgets, and white-label outputs — after the wedge is proven, not before.
Why this route is separate
The one-case buyer, the recurring-ops buyer, and the adopter of the diagnostic engine should not share the same sales logic.
Self-serve buyers need clarity, speed, and a single job to be done. Teams and implementers need routing, lifecycle expectations, tooling boundaries, compatibility detail, and later conformance. Separating the routes makes both clearer.
Embeddable scorecards
Portable case health and review-readiness surfaces for products and partners.
Scan widget
The lowest-friction adoption surface after hosted scan.
Adoption kit
Fast evaluation pack for agencies, products, and strategic buyers.