AssetShop · EOS
The public record

The pilot charter · published before it is negotiated

The whole engagement, readable before the first call.

Every term below was written and published before any negotiation, which is exactly why it can be trusted: nothing here was bent to flatter a result that already happened. When the first pilot signs, it runs against this page, and its results are measured by the definitions below, not by definitions invented afterward.

Fit

Who this is for, and who it is not.

For: enterprises running two or more systems of record for the same objects (multi-ERP after acquisitions, ERP plus WMS plus procurement), and private equity operating teams holding a portfolio of them. Not for: single-system estates, greenfield implementations, or anyone shopping for a system of record; EOS never becomes one, and that sentence is enforced in code.

Selection is deliberate. The first cohort is three, chosen for the quality of the eventual case, because one undeniable result outranks ten mediocre pilots. The strongest candidates share a shape: two or more systems of record after acquisition, a nine-figure inventory or payables base, a named executive who owns the number, and an appetite to be measured under the standard below.

Shape

Thirty days, two systems, one object family.

  1. Scope and access. You name the two systems and the object family (purchase orders, inventory positions, supplier balances). Access is read-only and minimum-privilege: exports or scoped API credentials, your security team's choice. Nothing is installed inside your systems, and no write permission is ever requested because no write method exists to use it.
  2. Connect and normalize. Both sources land in one canonical shape. Every figure carries its source, timestamp and record reference from the first day.
  3. Reconcile. The contested figures surface, each one preserved with both values and traced to the dated records that produced them. Your named authority sees the register as it grows, not at a reveal meeting.
  4. Findings and decisions. The finding register is walked with your team, figures are validated or rejected in writing, decisions are recorded with a name and a timestamp, and the evidence packs are exported. Day 90 measurement is scheduled before we leave.

The standard

What the words mean, committed in advance.

These definitions are the same ones on the public record, fixed ahead of the first engagement so results cannot be softened to fit.

FindingA contested figure where two systems of record disagree about the same object, each value traces to a dated record, the gap is quantified in currency on your own valuation basis, and your named authority confirms it was previously unknown or unresolved.
ValidatedYour team confirms the figure and its basis in writing. Our arithmetic never validates itself.
CapturedCash or working capital movement your team attributes to the resolution, measured at day 90 against the pre-engagement baseline.
Not a findingModeled savings, projected annualizations, data-quality observations without a currency figure, or anything your team has not confirmed in writing.

Deliverables

What you hold when it ends, whichever way it ends.

The finding register with every contested figure and its evidence. Exported evidence packs that verify offline, without us, forever. The decision log with names and timestamps. And the day-90 measurement appointment. If the pilot finds nothing material, that result is stated plainly in the same register; a clean estate is a legitimate finding about your estate, and it will be reported as exactly that.

Commercials

A share of validated findings, scoped before work begins.

The structure is published in full: a fixed, scoped assessment fee set at the free thirty-minute scoping call, and a share of validated findings under the definitions above. No seats, no modules, no number anchored before anything is found. Either side can stop at any weekly boundary; you keep everything delivered to that point.

Security posture

Stated honestly, because your CISO will ask anyway.

What exists: read-only architecture with no write method, independently executed at 9 of 9 write-path checks and 45 of 45 tenant-isolation checks; a public verification harness your security team can run cold and offline before the first call; evidence packs that outlive the vendor.

What does not exist yet: SOC 2 (funded, not started, and marked not claimed on every page that could imply otherwise) and a third-party penetration test (same status). Export-based access exists precisely so a pilot can run without extending trust we have not yet earned certificates for.

Publication

What we may say about you, and when.

Nothing, by default. With written permission: your name, or an anonymized profile (industry, revenue band, systems connected). The finding and its measured impact enter stages 4 through 6 of the public record only under that permission, and a failed pilot is publishable as a failure with the same consent rules. You will never discover yourself on our website.

Book the thirty minutes Start smaller: one session Have security run the harness first