Skip to main content

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. Every pilot 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. Each cohort is small, chosen for the quality of the result, 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

Two weeks to assess two systems, then a pilot to day 90.

  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 the read connectors have no write method 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 register and the decision log are handed to you. Day 90 measurement is scheduled before we leave.
  5. Decided changes, in the pilot. Nerio reads and never writes. EOS holds no write credential to your systems of record. A change is made only by your own executor, for a request a named person approved, under a signed, single-use authorization from Minerva, and EOS then verifies the result. Nothing is sent to your executor until your organization has a signed contract, a verified pilot and your recorded approval. During the pilot, your team carries out decided changes and EOS verifies them. The two-week assessment changes nothing.

The standard

What the words mean, committed in advance.

These definitions are fixed ahead of every 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, each traced to its dated records (an evidence pack that verifies offline without us is specified, not built yet). 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

Fixed fees first, then a share of verified value.

The structure is published in full: the assessment is $15,000, fixed, for two weeks; the pilot is $50,000 with the assessment credited, so $35,000 more, and that $35,000 is refunded if the target written with your finance team is not achieved by day 90; after that, $0 a year plus a marginal share of value your finance function has verified (15% of the first $100,000, 10% to $500,000, 7.5% to $5 million, 5% above). No seat fee for your employees and no modules; external parties you invite are $100 per seat per month in the commercial term. The free step is the thirty-minute scoping call, and you keep everything delivered.

Security posture

Stated honestly, because your CISO will ask anyway.

What exists: read-only architecture with no write method, 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. EOS holds no write credential; during a pilot, your team carries out approved changes and EOS verifies them. Evidence packs that outlive the vendor are specified, not built.

Independent assurance: a SOC 2 examination and a third-party penetration test are planned, and no certification is claimed on any page until its report is issued. Export-based access exists precisely so a pilot runs with no new trust extended: nothing in your systems is reachable from ours.

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 are published only under that permission. You will never discover yourself on our website.

Book the thirty minutesTalk to us Start smaller: one session Have security run the harness first