Skip to main content
Enterprise onboarding, the ninety-day arc

From signature to your Outcome Warranty™ determination.

You do not have to take our word for it. Every figure on this page is computed at build or wears its label, and the harness that proves it ships with the product.

A structured ninety-day arc from MSA signature at Day 0 to a binary determination at Day 90, read-only throughout, your systems of record staying authoritative. The pace is honest because the success criteria are agreed in writing before Day 0. Shadow Key-led at roughly one hundred twenty hours per customer; your team commits roughly twenty-two hours across the full arc. Specific dates and criteria are set per your MSA; nothing real is connected on this page.

The six phases, Day 0 to Day 90

Day minus 7 to 0, pre-kickoff

MSA signed; Day 0 is signature plus fee receipt. Your side names a champion, an IT lead, and a business sponsor, about thirty minutes, and schedules the kickoff. AssetShop drafts the Day-14 success criteria from the signed exhibit. Output: named team, kickoff scheduled, draft criteria as a specific dollar, percentage, or count.

Days 1 to 7, foundation

A ninety-minute kickoff sets the Day-14 target in writing. Read-only credentials go into key management, the adapter shakedown begins, and the initial reconciliation starts. Output: signed Day-14 criteria, credentials held, reconciliation underway.

Days 8 to 14, first signal

Daily reconciliation hardens patterns. The Day-14 briefing presents the first signal as a specific attribution, anomaly, or recommendation, and you confirm: real signal or noise. If noise, the window re-baselines to Day 28 and says so transparently. Output: a written first-signal report.

Days 15 to 30, compound signal

Signals surface across procurement, operations, and planning; the top three per week are curated for about an hour of business-team validation, and the first quarterly-format review lands at Day 30 with the sponsor signing the assessment. Output: a written Day-30 review, sponsor-signed, with the Day-60 target set.

Days 31 to 60, trajectory

The cadence is established. At Day 60, with your CFO engaged, the projection is stated plainly: on track, extend, or remedy. If the trajectory is negative, that conversation happens honestly and early. Output: a written trajectory assessment with an explicit Day-90 projection, customer-signed.

Days 61 to 90, determination

The case tightens against customer-side ground truth; only signals your teams confirmed as real are included. The Day-90 binder supports a determination both parties sign. Output: SUCCESS, EXTEND, or the remedy, exactly as the Outcome Warranty defines them.


The determination is binary

One of three outcomes, against criteria you agreed before Day 0

SUCCESS: the metrics you defined in writing are met, the engagement converts, and the fee credits fully toward year one. EXTEND: the signal is real and needs more validation time, so the window extends by mutual agreement rather than forcing a premature call. REMEDY: the agreed threshold is not met, you choose not to continue, and the $35,000 pilot balance is refunded via ACH with no lock-in; the $15,000 assessment, credited against the pilot, is not refundable. The mechanics are the Outcome Warranty, defined on the Trust Center.


The engagement, both ways

What it gives you, and what it asks

It gives you: early-engagement terms scoped to your footprint and held flat for the term, with the figure fixed in your engagement letter and never on a public page; keyholder-direct access throughout; roadmap influence; monthly reviews in the Day-90 format; and the Outcome Warranty signed before Day 0. It asks: up to two reference calls per quarter of thirty minutes each, capped and honored, with each call earning a platform service credit; up to four written peer security-questionnaire validations per quarter; a named champion, IT lead, and sponsor; and about twenty-two hours of your team time. Genuinely separate businesses under a holding company are handled as additional engagements.

Your side of the arc, ten items

01

Designate the champion, IT lead, and business sponsor

02

Schedule the Day-1 kickoff call

03

Attend kickoff and sign the Day-14 success criteria

04

Provide read-only credentials into key management

05

Confirm the Day-14 first signal, real or noise

06

Validate weekly signals, about an hour per week

07

Attend the Day-30 review; sponsor signs

08

Engage the CFO and sign the Day-60 trajectory

09

Review the Day-90 binder

10

Co-sign the Day-90 determination

How references work, honestly: as the program grows, a reference rotation builds; until then Shadow Key serves as the direct reference and the calibration ledger, the worked evidence studies, and the synthetic walkthrough stand in for production proof. If you require a production reference at signature, deferring past Day 90 is a legitimate path and you will not be pressured otherwise.

Also from AssetShop

Fourteen other products, none of them part of EOS. Separate products, no shared runtime, tenancy or credential path. Nothing below is included in an EOS evaluation or an EOS contract. Each carries its status, and nothing is called built until it is.

Enter the consumer layer at assetshop.eth EOS is the Enterprise Operating System. The brand layer it belongs to is name-native. Past that line the rules are different, and it is built by Shadow Key.