The intelligence layer your ERP cannot be.
AssetShop SCO runs on top of your ERP, MRP, WMS, TMS, and Excel — reading what those systems already hold, surfacing the patterns and leakage they cannot see, reconciling across them when you run more than one.
Savings calibrated against your annual procurement spend base*. First signal delivered within 14 days of security-and-counsel sign-off.
* Outcome calculations applied against the customer's annual procurement spend base. Validated jointly at Day 0 with the customer CFO/CPO.
Your ERP gave you records. Not intelligence.
For forty years, every procurement and supply-chain suite has demanded the same trade: migrate to us, lose your existing system of record. Operators paid the price. AssetShop SCO ends the trade.
Every supply chain software asks you to make their system the center of operations. Years lost. Board-level risk on every renewal. Operators pay the cost of someone else's consolidation strategy.
Incumbents operate within one functional silo. Cross-domain decisions die in email threads. A demand signal that should reach procurement in hours instead surfaces as a margin problem weeks later.
When intelligence requires the next platform migration, operators wait quarters for answers their data already contains. The decision window closes before the deployment finishes. Value gets stranded behind implementation timelines.
Five outcomes your ERP cannot deliver alone.
AssetShop SCO is benchmarked against five concrete operational outcomes - what your team actually has after the platform is in their hands, not what the brochure says. Each scales linearly with addressable spend. ROI positive year one across every reference scenario.
Four advantages competitors cannot replicate without re-platforming their stack.
Coupa, Ariba, Anaplan, Kinaxis - each made architectural choices a decade ago that locked them into the "migrate-or-leave" model. AssetShop made the opposite choice. The result is a moat their existing product lines cannot cross.
One platform · five integrated domains.
Every domain is fully built and shipping today. Every domain shares the same intelligence layer, the same identity, the same audit chain - plus five canonical drill paths, role-aware filtering, per-persona executive briefings, mobile-responsive on every device, and Excel/CSV interop everywhere.
Generate audit-anchored QR codes for every lot, pallet, shipment, and asset transfer. Scans are signed events on your audit chain. Supplier-side scans, customs scans, customer-receipt scans - all tied back to the originating PO or work order.
Continuity, compliance, and cyber risk classification across your supplier network beyond Tier-1. Surfaces concentration risk you cannot see when you only buy from your direct suppliers. Geographic clustering, financial-trend monitoring, sanctions screening, and substitute-path identification. Ranks the bottlenecks and constraints across your network - single points of failure, choke points, and regional concentration - each with a recommended action.
6 reference currencies vs your procurement spend. 4 major exchanges with industrial-relevance ranking. Supplier-public-company stock signals as counterparty-health early warning. Commodity tickers (steel, aluminum, copper, oil, gas, fertilizer) for hedging context. Crypto exposure for treasury policy review.
Plus 85+ additional routes across the 13 capability groups - all in the no-sign-up demo →
Mass PO Release Recommendations · annual cash flow release.
Procurement teams sign off on individual POs all day, missing every consolidation opportunity. Mass PO Release Recommendations identifies supplier-blocked clusters, prices the consolidation against your carrier rate cards, and proposes one release per facility - with the full audit chain. AssetShop produces the recommendation; your buyer or planner executes the actual release in your MRP/ERP. Annualized business case baseline: example synthetic manufacturer profile at ~$54M annual procurement spend across 3 plants · $2.5M annual cash flow release from consolidation (mid-range of $1.8M-$3.2M depending on category mix). Smaller-spend and larger-spend profiles scale proportionally during Day-0 baseline validation. All figures aggregated across categories and weekly release cycles over a full year.
| Supplier | POs | After | Annualized |
|---|---|---|---|
Ardent Castings supplier-blocked bulk | 14 | 1 | $270K/yr |
Pacific Plastics supplier-blocked bulk | 9 | 1 | $169K/yr |
Eastern Components supplier-blocked bulk | 8 | 1 | $152K/yr |
Pruitt Forging 2 facilities | 14 | 2 | $270K/yr |
Other cadence: weekly | 5 | 2 | $11K/yr |
Optimization intelligence · recommendations, not dashboards.
Most platforms give you reports. We give you specific, dollar-quantified recommendations: which MOQs to renegotiate, which safety stocks to right-size, which releases to consolidate. Every recommendation cites its math, runs on live data, and writes the decision to a cryptographic audit ledger.
| Component | Today's MOQ supplier-required | Wilson EOQ economic optimum | Annual opp if renegotiated |
|---|---|---|---|
SMT Cap 22µF MOQ 4.0× EOQ | 50,000 | 12,500 | $48.2K/yr |
PCB Rev A MOQ 3.2× EOQ | 500 | 156 | $31.4K/yr |
MCU 32-bit MOQ 2.7× EOQ | 1,000 | 370 | $22.8K/yr |
Power SoC MOQ 1.8× EOQ | 500 | 278 | $14.5K/yr |
| Top 4 annualized · full 25-component scoring | $117K/yr of $2.4M/yr | ||
› release_wo 111 · 6 lines
› expedite 16 · sig-linked
✓ deterministic · two planners → identical output
release_po - PO release recommendations queued for buyer review + ERP upload
release_wo - WO release recommendations queued for planner review + ERP upload
expedite - Items flagged for expediting (with signal trace link)
deterministic - same inputs always produce same outputs (verifiable)
Note: "queued" = staged in AssetShop for export. Your buyer or planner executes the actual release in your MRP/ERP. AssetShop writes to your systems of record only the audit/approval entries you switch on (off by default).
Demand-Production Sync · before the gap becomes the headline.
Forecast bias is the silent margin killer. Demand-Production Sync catches it 4-6 weeks earlier than the typical S&OP cadence - and routes the action across procurement, operations, and logistics in one cross-domain signal trace.
vs nightly MRP batch
across 3 facilities · single run
from 23% pre-sync baseline
Methodology: MAPE improvement reflects shorter horizon at higher temporal resolution (daily re-sync vs. nightly batch) plus exception-routing that quarantines drift-flagged SKUs from rolling-up to the aggregate forecast. Not a model improvement claim - a workflow-and-data-freshness claim. Founding-5 baselines validated against customer's actual MAPE history in Day 0 calibration.
Demand forecast in. Consolidated supplier release plan out - with freight, pallets, and incoterms automatically determined.
One forecast file. The entire downstream procurement plan handled in a single integrated pass. No five disconnected reports across five systems. This is the value AssetShop delivers that no one else does - because no one else sits across procurement, planning, and logistics with shared truth.
Note: Meridian Industrials is a $450M-revenue synthetic demo tenant - intentionally tutorial-scale so the demo loads instantly and every metric is comprehensible at a glance. Production-scale customer runs typically generate 10-50× the record volume and proportional savings. Founding-5 customers see calibrated scaling against their actual procurement spend during Day 0 baseline validation.
Aggregate result from a single 13-week planning horizon. The 51% average truckload utilization with AssetShop SCO compares to the ~25% baseline that results from shipping each PO line individually. Each consolidated batch carries a recommended freight mode, pallet count, transit days, incoterms recommendation, and savings vs un-consolidated baseline. Click any batch in the demo to see line-by-line breakdown, freight mode comparison, and incoterms rationale with primary + alternate.
Optimization method: first-fit-decreasing bin packing on pallet volume + axle-load constraints with supplier-grouped origin clustering, then Clarke-Wright multi-stop routing for hub-and-spoke lanes. Solver: open-source Google OR-Tools - no customer-side licensing required; all optimization runs in the AssetShop tenant. Commercial solvers (Gurobi, CPLEX, FICO Xpress) supported as an Enterprise-tier upgrade.
- · Maximizes truckload utilization
- · Concentrates supplier frequency for negotiation leverage
- · Produces freight + duty handoff terms automatically
- · $2.5M annualized cash flow release (mid-range baseline)
- · Predictable annual order cadence
- · Improves supplier's own inventory planning
- · Batch ordering → volume-discount conversations
- · Compounds across next contract renewals
Integrating these three domains into a single coherent release plan requires shared truth across all three. AssetShop's read-only intelligence-layer architecture is the spine that makes it possible — the structural answer to "why couldn't I do this in my ERP?"
Cross-domain signals · the architecture in motion.
Every signal is a payload that carries from a source domain to a set of target domains, with a recommended action and a complete audit trace. Six signals are wired by default; tenants build more on the same primitive.
Targets · which domains need to act (operations, planning, analytics)
Trace · how the data flowed end-to-end (3-4 step path, full lineage)
Action · the wired workflow (dual-source, capacity sim, etc.)
Impact · monetized exposure or savings (in $ or units, with confidence)
When your suppliers run AssetShop SCO too, the chain becomes visible.
Most operational platforms see your operation. AssetShop SCO sees your operation today - and surfaces the chain as more of it adopts the same read-only layer. Tier 1 buyer reconciles against tier 2 supplier from inside their own tenant. Each customer's data stays private to that customer. The relationship between them becomes auditable, not assumed.
Your PO to tier 1 supplier matches what they shipped. Their PO to tier 2 sub-component supplier shows what they ordered to fulfill yours. Variance attribution traces back to its actual origin instead of stopping at the first vendor boundary.
A tier 3 raw material price spike or geographic event surfaces in tier 2's signals before it cascades to your tier 1 order book. Two-tier lead-time on disruption replaces "we got blindsided again."
SHA-256 hashes follow the component from raw material to final assembly. ESG certifications, conflict-mineral attestations, customs declarations all anchor to the same tamper-evident chain. Compliance becomes a query, not an investigation.
When distributors or channel partners run AssetShop too, your sell-through becomes visible upstream. Inventory positioning, channel sell-out, end-customer demand signal reconciles against your shipment plan in near-real-time.
Multi-tier visibility activates when two or more customers in the same supply chain run AssetShop SCO. Each customer's data stays private to their tenant; the shared visibility is opt-in per relationship, cryptographically scoped, and revocable at either party's discretion. The capability is built into the architecture today. The network value compounds as the Founding-5 cohort fills with customers whose chains overlap. Strategic roadmap captured in T2.6 · Multi-tier network effect.
Single-tier visibility is what every operational platform already promises. Multi-tier visibility is structurally different. No incumbent can deliver it by being good at their own product; it requires the same read-only layer running at both sides of every relationship. AssetShop's read-only architecture is the precondition - no customer trusts a vendor with write access to their ERP, so no write-capable platform reaches this configuration.
Comparable network platforms (Bloomberg Terminal in finance, CCC One in collision repair, SAP Ariba Network in procurement) reach economic moat status when ~30-40% of a category adopts the same tool. AssetShop's Founding-5 cohort is calibrated to seed that adoption density in industrial supply chains - 15 anchor customers whose suppliers and customers progressively enable the network as adoption deepens.
A layer, not a replatform.
AssetShop SCO is the intelligence layer on top of your existing systems-of-record. Your ERP, MES, WMS, PLM, and CRM remain the authoritative source. We read what they hold, compute cross-domain patterns, and surface signals to humans for decision-making.
From contract signature to continuous value.
A five-phase journey. Hours by role are honest planning estimates calibrated to your environment during Day-0 baseline. No 18-month rollouts; no surprise scope additions; no hidden lift.
Setup
Integration
Launch
Maintenance
Sustenance
Where AssetShop sits in your stack.
We are not a replacement for procurement platforms, BI tools, ERP modules, or risk-monitoring subscriptions. We are the cross-domain intelligence layer that composes with what you already run.
| Capability | AssetShop SCO | Procurement replatforms Coupa, Ariba, Oracle Procurement |
BI dashboards Tableau, PowerBI, Looker |
Risk-monitoring SaaS D&B, Interos, riskmethods |
|---|---|---|---|---|
| Architectural posture | Read-only on top of ERP | Write-back replatform | Read-only render layer | Vendor-cloud SaaS |
| Implementation time | 30 days | 12-18 months typical | Same-week (if data is curated) | 2-4 weeks |
| Migration required | None | Full procurement workflow | Data modeling per dashboard | Supplier-master enrichment |
| Cross-domain pattern computation | 60 surfaces joined | Within procurement only | User-defined queries | Risk-domain only |
| Multi-tier supply visibility | Tier-1 through tier-3 | Single-tenant tier-1 | Not applicable | Tier-1 + indirect signals |
| Anonymous weighted-vote governance | Native | Approval workflow ticketing | None | None |
| Data residency | Customer cloud per tenant | Vendor cloud | Customer cloud | Vendor cloud |
| Outcome warranty | Day-90 money-back | Service credits typical | None | Annual contract typical |
| Continuity on vendor wind-down | Open-source on event | Vendor escrow typical | Self-hosted available | No customer continuity |
| Adapter conformance | Cryptographic certificate | SOW-based integration | Per-connector spec | Vendor-managed |
What makes this defensible.
Eight distinct moat dimensions, each independently meaningful and collectively compounding. Founding-5 customers are buying into all eight as cohort founders, with corresponding pricing protection and roadmap influence.
Read-only architectural posture
Every write-capable platform faces the same friction: customer security teams object to vendor write access; integration scope expands to handle every workflow; failure modes block transactional operations. AssetShop's read-only design eliminates all three. No incumbent can pivot to this position without abandoning their core product.
Multi-tier supply network
Tier-1 visibility is table stakes. Tier-2 and tier-3 visibility is where modern disruptions actually originate. AssetShop indexes the network as observed from both customer-side and supplier-side adapters, producing choke-point detection no single-tenant platform can compute. Network deepens as the Founding-5 cohort adopts.
Cross-domain pattern computation
DPO change + safety stock policy + supplier acceleration are three names for one decision. CBAM exposure + Scope 3 Cat 1 + supplier substitution work the same lever. Point solutions cannot see these connections because they index one domain. AssetShop joins 60 platform surfaces into one composable intelligence layer.
Anonymous weighted governance
Every "proceed with supplier X from RFQ event" becomes auditable, defensible, anonymous. Procurement-savings claims to the board are no longer single-buyer judgment. SOC 2 and ISO auditors love this. M&A diligence loves this. Supplier-negotiation leverage benefits because counter-parties see formal governance.
30-day implementation commitment
The procurement-replatform category averages 12-18 month implementations. AssetShop commits to 30 days because the architecture allows it - no transactional workflow to migrate, no master-data reconciliation, no UAT cycles per business unit. Backstopped by the Day-90 Outcome Warranty: first captured value documented by Day 90 or fees refunded.
Founder Continuity Plan™
Your data lives in your isolated cloud project under your IAM. The Continuity license activates only on a wind-down or acquisition event; it governs maintained custody of the codebase by a third-party steward and continuity of customer operations. The architecture is read-only, so your data exits under your control; the product itself is materially more than a published codebase — governance, hosted infrastructure, model tuning, and operations continue under the Continuity steward — established software-escrow custody under Iron Mountain Software Escrow (or equivalent) with a deposit-and-release schedule defined in the MSA.
Full 4-tier custody chain on Trust Center →Conformance Certificate
Every adapter ships with a cryptographically-signed certificate documenting endpoints, fields, rate limits, and read-only attestation. Verifiable by anyone with the public CLI. Incumbents treat integration as a trust black box; AssetShop publishes the math. Auditors stop asking; security teams clear faster.
Day-90 Outcome Warranty™
Founding-5 customers receive a money-back outcome warranty: if first captured value isn't documented and signed by Day 90, the annualized fee is refunded. "Captured value" defined as a platform-surfaced opportunity executed in your source system with measurable financial outcome, jointly documented by your finance team and AssetShop CS. True money-back, not service-credit-toward-future.
The eight moat dimensions above compound. The Founding-5 charter prices this access at $175K annually for 3 years (vs $295K Enterprise rack rate), with locked-rate renewal and quarterly roadmap influence. After the cohort fills, charter pricing is closed. The structural advantages do not disappear; the pricing protection does.
Sits on top of what you already run.
Connectors are first-party, maintained by AssetShop, with deterministic data contracts and Founding-5 priority for what ships next. No third-party middleware. No ETL surprise.
Anchored at adapter release. Verifiable by anyone with npx @assetshop/verify-cli conformance <CCC-ID>. Incumbents treat integration as a trust black box; AssetShop publishes the math.
One platform. Multiple ERPs. System-of-record election per entity type.
Multi-ERP customers configure system-of-record per entity type: Purchase Orders may live in SAP S/4, Suppliers in Coupa, Work Orders in Oracle Fusion. AssetShop reads each authoritative source, surfaces cross-system variance, and never overwrites any of them.
Two NetSuite instances after an acquisition. Three SAP instances from regional rollouts. AssetShop deduplicates suppliers and materials by tax-ID + part-number normalization, surfaces same-vendor-different-terms variance for negotiation leverage, and gives finance a single consolidated view without forcing an ERP migration project.
Every input from your systems. Every output exported clean.
AssetShop slots into your stack rather than replacing it. Master data flows in through certified ERP / MRP / TMS / WMS connectors or through Excel and CSV templates handed to anyone on your team. Every view, chart, table, and dataset on the platform exports back to Excel with one click. And you can connect your own AI provider to query and reason over your tenant data without your information ever leaving your security boundary.
Every supported data flow runs through one of two paths: a certified read-only connector to your system of record (SAP S/4 · Oracle · NetSuite · Workday · Manhattan · Blue Yonder · Microsoft Dynamics · Coupa · Ariba · plus 35+ more), or a pre-formatted Excel/CSV template handed to your data team or supplier - round-tripped cleanly with the platform.
Six production analytics views shipping today: Variance Analytics · Working Capital live dashboard · Cost-to-Serve attribution · Risk Radar with live supplier signals · Spend Treemap · Kraljic Portfolio matrix. Plus eleven additional analytics views on the SCO roadmap through Q2 2027: global supplier network · network topology · risk heat maps · shipping lane flow · capacity projection · pallet storage forecast · decision audit trail with cryptographic provenance · supplier financial-trend monitoring · ESG attribution · scenario library · and more. Multi-level supplier filtering across category × capability × performance × financial trend. Scenario library with one-click what-if simulations, cascade modeling, and built-in collaboration messaging on every entity.
Every list, table, chart, dataset, and analytics view ships with one-click CSV and XLSX export. The procurement team that lives in spreadsheets keeps living in spreadsheets - but those spreadsheets now have audit-grade provenance, refresh on demand, and round-trip cleanly back to the platform.
Canonical schemas, field-level provenance, and integration specifications are shared during qualification with mutual NDA and engagement-grade access controls.
Beyond operations: the analytics that turn supply chain into strategic infrastructure.
Most supply-chain platforms optimize transactions. AssetShop layers on capabilities that turn your operational data into compounding strategic advantage - surfaces hidden in standard ERP reporting, decision quality measured over time, real-time signal integration, and working-capital outcomes that flow directly to the CFO conversation.
DPO, DSO, DIO trends with daily drift detection. When any metric drifts more than 0.5 days outside trailing-90 baseline, the platform surfaces the operational decisions driving it - which supplier extended terms, which customer slowed payment, which SKU is over-stocking. Collapses the CFO feedback loop from "discovered after quarter close" to "addressable today."
Beyond gross margin per SKU: full attribution including customer-specific freight, returns rate, custom packaging premium, payment-terms financing cost, and order-handling labor. Surfaces hidden margin destroyers and quiet-growth gems. Drives commercial conversations from intuition to evidence. Master-data precondition: attribution depth scales with the customer's master-data quality (clean SKU-customer linkage, customer-tagged freight invoices, labor allocation). Customers with messy master data see the platform surface the gaps first; full Cost-to-Serve attribution follows after data hygiene work (typical 6-12 weeks customer-side, out of subscription scope).
Every recommendation logged with hash-chained provenance: the data records consulted, the model version, parameter snapshot, actor, and outcome. After 90/180/360 days, the audit becomes institutional decision memory - which models earned trust, which decisions paid off, what tribal knowledge to preserve through team transitions.
Real-time signals across trade policy, weather, labor, regulatory, supplier credit, FX/commodities - mapped to your specific network and quantified for your impact. When a signal matches a pre-built scenario template, response playbook is one click away. Collapses awareness time from days to minutes.
Eight pre-built scenarios - tariff shocks, supplier insolvency, demand surge, plant outage, FX shifts, capacity constraint, port strike, regulatory expansion - each modeling impact across procurement, operations, planning, and logistics with auto-generated response playbooks. Run multiple in parallel to compare strategic resilience.
Filter suppliers by category × capability × performance metrics × financial trend. 21 capabilities organized in process / certification / commercial groups. Six performance/financial filters including credit grade, OTIF, quality, revenue trend. Stack filters across dimensions for surgical sourcing analysis.
Your operational data, normalized for AI consumption.
Operational data lives in 8+ systems with different schemas, different identifiers, and different authentication models. Without normalization, your AI sees fragmented, inconsistent, and unreliable inputs - which is why most AI initiatives stall on data quality. AssetShop's canonical model collapses ERP, MRP, WMS, MES, TMS, procurement, finance, and quality data into one shared structure with field-level provenance and SHA-256 anchoring. This is the data-prep work your AI cannot do for itself.
Then connect your existing AI provider - OpenAI, Azure OpenAI, Anthropic Claude, Google Vertex AI, AWS Bedrock, or a private deployment - to query the canonical model through scoped read-only API tokens. AssetShop never relays your tenant data to a third-party AI. Your AI provider sees only what your token scope permits. Data residency follows your AI's deployment region. Your governance, audit logs, and approved-models policy carry forward. Your AI, your security boundary, your governance.
Talk to the founder. Custom connectors are scoped collaboratively - most production-grade adapters take 4-8 weeks. We work with your stack rather than asking you to change it.
For teams that live in spreadsheets.
Two paths to data move through AssetShop SCO. The certified ERP/MRP/TMS/WMS connectors handle real-time observation harvesting. Excel handles everything else: legacy systems without modern APIs, supplier-side data your procurement team owns, supplemental data nobody bothered to integrate, and any team that simply prefers spreadsheets. Every export from the platform - every chart, every dataset, every insight - rounds back to XLSX with one click.
Upload a workbook. Get observations.
Drag a .xlsx or .csv that matches one of our seven canonical schemas. We detect the schema, validate columns, and produce observations identical in shape to API-connector output. Same provenance. Same audit chain. Same downstream analytics.
Download data, charts, and provenance.
Every view, chart, and signal in AssetShop SCO exports as a real XLSX or CSV file with cover sheet, data sheet, optional chart spec, and provenance sheet. SHA-256 hashed at generation. Identical in shape to the platform's authenticated POST /exports/{id}/render endpoint.
excel-ingestion), source row reference (file#sheet#row), observation timestamp, and raw-content SHA-256 hash. Every export carries a file-level SHA-256 hash plus the calibration ledger reference of the export spec. Excel files round-trip through the audit chain like any other observation source.
Every claim. Every status. Verifiable.
Every adapter, template, and export ships with an honest calibration bucket. BUILT_AND_OPERATING means it works today. BUILT_AND_INTEGRATING means the engine works; first customer integration triggers the operating transition. SHIPPING_Q3_2026 and ROADMAP_2027 are deliverables on a dated commitment, not aspiration. The full ledger is anchored to a tamper-evident chain; entries can be independently verified via npx @assetshop/verify-cli.
Questions the buying committee actually asks.
Procurement, CIO, CFO, CISO, and counsel reviews surface the same questions. We answer them on the record. Anchored to the calibration ledger; updated whenever the answer changes.
What is AssetShop SCO and how is it different from existing dashboard tools?
AssetShop SCO is the read-only intelligence layer that sits on top of your existing ERP, procurement suite, planning system, warehouse management, manufacturing execution, and transportation management systems. Five integrated domains: Procurement · Operations · Planning · Logistics · Analytics.
Traditional dashboards surface data from one system at a time. ETL platforms move data between systems and can break the source. AssetShop SCO does neither - it observes read-only across all five domains simultaneously, then surfaces the cross-system variance as actionable findings. We sit on top of your stack, never inside it, never in the request path of any of your existing tools.
Every observation carries source-system provenance and a SHA-256 raw-content hash anchored to a tamper-evident audit chain. The mathematical alternative to "just trust us."
Which enterprise systems does AssetShop SCO connect to?
32 canonical-mapped adapters cover ~85% of large enterprise ERP deployments plus the dominant adjacent specialist platforms across all five SCO domains:
- Core ERPs (8): SAP S/4HANA · SAP ECC · Oracle Fusion Cloud · NetSuite · Microsoft D365 F&O · Workday Financials · Coupa · Salesforce
- Procurement suites (3): SAP Ariba · Jaggaer · Ivalua
- Planning APS (4): Kinaxis RapidResponse · o9 Solutions · Anaplan · Blue Yonder Demand
- Warehouse management (5): Manhattan Active WM · SAP EWM · Blue Yonder WMS · Oracle WMS Cloud · Körber
- Manufacturing execution (3): Rockwell FactoryTalk · Siemens Opcenter · AVEVA PI System
- Transportation (3): Oracle OTM · Blue Yonder TMS · Manhattan TMS
- Visibility (2): project44 · FourKites
- Supplier risk & quality (3): TraceGains · ETQ Reliance · Riskonnect
- Excel ingestion (1): Alternative-to-systems-integration path with 7 canonical schemas - BUILT_AND_OPERATING today
The full matrix, large enterprise market share, and Year-2 roadmap are documented in the Connector Landscape addendum.
Can AssetShop SCO modify my ERP or break my production systems?
No. Read-only is enforced at the architectural level. Every adapter declares readWriteMode: 'read_only' in the adapter contract. OAuth scopes on customer-side identity providers are limited to read. We do not sit in the request path of any existing tool. We observe and surface patterns; we write back to your systems of record only the audit/approval entries you switch on (off by default).
Your ERP remains authoritative for every entity. AssetShop is additive intelligence - never middleware, never an integration target for write operations, never a system of record.
What if I do not have modern API access to my ERP?
Excel ingestion is the alternative-to-systems-integration path and the 32nd connector. Customers without API access submit observations through .xlsx or .csv files conforming to our seven canonical schemas (suppliers, purchase orders, contracts, inventory, work orders, forecast, shipments).
The Excel ingestion adapter is calibration status BUILT_AND_OPERATING - the engine works on Day 1 without per-customer IT integration. Observations flow through the same audit-chain provenance as API-connector observations. Try the working drag-and-drop upload in the Excel section above.
How does the Day 90 binary outcome warranty work?
Every Founding-5 pilot has a binary Day 90 outcome determination defined in MSA Exhibit F, signed by both parties before pilot Day 0. Three outcomes:
- SUCCESS - Customer converts to 3-year subscription commitment at locked Founding-5 pricing ($175K/yr).
- EXTEND - Mutual agreement to extend 30-60 days with new milestones; pilot fee retained.
- REFUND - Pilot fee refunded via ACH within 30 days; customer data returned per MSA Section 12.
The Day 90 dollar threshold and customer-side validation criteria are agreed in writing before Day 0 via MSA Exhibit F. No goalpost moving. The determination itself is signed by both parties and recorded in the audit chain.
Important methodological framing: the Day 90 SUCCESS criteria are leading indicators the platform directly drives - signals surfaced, decisions logged, recommended actions taken with documented customer follow-through - not lagging indicators like realized working capital change. Working capital movement requires CPO-driven supplier-term renegotiation, payment-cycle changes, and inventory rebalancing, which have multi-quarter operational lags outside the 90-day window and outside the platform's direct control. The lagging measurements (DPO improvement, DIO reduction, freight variance capture) are validated jointly at Day 180 and Day 365 QBRs against the Day 0 baseline and form the basis of the Year-3 reference-renewal pricing path.
What is the public audit chain and why does it matter for enterprise risk teams?
Every observation, template render, and export from AssetShop SCO carries a SHA-256 hash. Batches of hashes are aggregated into Merkle trees ready for anchoring to a tamper-evident external anchor. Live anchoring activates Q3 2026 post security audit; until then the system operates in dry-run mode - building Merkle roots and persisting batch records locally. The hash-chain is independently verifiable today via @assetshop/verify-cli regardless of anchoring state.
Anyone - auditors, customers, regulators, the press - can independently verify any AssetShop output without trusting AssetShop infrastructure, using our open-source verify-cli tool (published to npm as @assetshop/verify-cli).
This is the mathematical alternative to "just trust us" that enterprise procurement, risk, and audit teams require. SOC 2 reports certify processes; audit-chain anchoring certifies specific outputs.
What is the Founding-5 cohort?
The Founding-5 is a strictly capped cohort of up to 5 charter organizations on 3-year locked terms, selected through 2026. Pricing structure:
- Pilot fee: $50,000 (refundable via ACH if Day 90 SUCCESS not met)
- Annual subscription: $175,000/yr locked through Year 3 (vs $295,000/yr Enterprise tier post-cohort)
- 3-year cumulative commitment: $525,000 if SUCCESS
Founding-5 customers receive monthly QBRs, quarterly persona briefings rendered through the platform templates engine, founder-level engagement, and reference-program access. The cohort is intentionally small.
Is AssetShop SCO SOC 2 certified? What about GDPR, HIPAA, ISO 27001?
SOC 2: Type I bridge letter targeted Q4 2026; Type II report Q1 2027.
GDPR: AssetShop SCO does not process EU personal data by default (supply-chain data, not customer/employee PII). Data Processing Agreement template includes Section 8 (72-hour breach notification) and Section 12 (data return) as standard clauses.
HIPAA: Not in scope - AssetShop SCO is supply chain operational intelligence, not protected health information.
ISO 27001: Q4 2027 target post-SOC 2 Type II.
Customers requiring SOC 2 prior to Q1 2027 can run pilot under contractual letter-of-intent gating production subscription on the SOC 2 Type I bridge letter. The Trust Center at trust.sco.enterprise.assetshop.eth.limo declares calibration status for every security control.
Where can I find independent verification of AssetShop SCO claims?
Three independent verification paths:
- Calibration ledger at trust.sco.enterprise.assetshop.eth.limo - declares every claim with its calibration bucket and target/delivered date. Also live-filterable above in this section.
- Public anchor explorer - every audit-chain anchor transaction is queryable on a public explorer with no AssetShop dependency. Anyone can verify a hash without our involvement.
- Open-source verify-cli -
npx @assetshop/verify-cli verify --event 0x... --tx 0x...verifies any AssetShop output (render hashes, observation batches, calibration ledger entries) without trusting our infrastructure.
What does implementation look like? How fast can my organization see first signal?
For a typical 6-adapter customer (ERP + procurement suite + planning + WMS + TMS + visibility), total customer-side onboarding effort is ~30-40 hours over 14 days:
- Week 1: 2 hours customer IT for OAuth credential setup per adapter
- Week 1-2: 4-8 hours customer business team for field-map validation (one-time per adapter)
- Day 14: First-signal target - initial cross-domain variance findings surfaced
- Day 30: First formal QBR with customer-validated dollar impact
- Day 60: Trajectory assessment vs Day 90 dollar threshold
- Day 90: Binary outcome determination (SUCCESS / EXTEND / REFUND)
Customers without API access can use Excel ingestion to start Day 0 immediately - same milestones, same audit chain, same Day 90 warranty mechanism.
Do my team and I need a crypto wallet, MetaMask, or any blockchain knowledge to use AssetShop?
No. AssetShop SCO is accessed through a standard web browser like any enterprise SaaS application. No wallet, no MetaMask, no browser extension, no on-chain transactions, no gas fees, no token holdings - nothing about your daily use of AssetShop touches a blockchain in any way you would notice.
You may have noticed the AssetShop domains end in .eth.limo (for example, sco.enterprise.assetshop.eth.limo). That is an architecture choice for our infrastructure - we publish to IPFS (content-addressable storage) and use Ethereum Name Service (ENS) for the domain ownership. The eth.limo gateway translates that to standard HTTPS for any browser, on any device, by anyone. It works exactly like vendor.com from your team's perspective.
Why this architecture matters: our content is cryptographically tamper-evident (you can verify the exact bytes you see were the bytes we published, against a public IPFS hash). That is a security property that benefits you - it imposes no special-software or plugin requirement on your users, your IT team, or your buyers.
If your CISO or InfoSec team has questions about the eth.limo gateway as a delivery channel, our Security Review packet (available under MNDA) includes their security posture documentation, status history, and our DR plan if the gateway becomes unavailable. Trust Center →
What browsers, devices, and SSO methods does AssetShop SCO support?
Browsers (LIVE): Chrome, Safari, Edge, Firefox - latest two major versions on each. Internet Explorer 11 is not supported (deprecated by Microsoft).
Mobile (LIVE): iOS Safari (iOS 16+) and Android Chrome (last two major versions). Every operational signal accessible on phone, tablet, or desktop. No native app required - we built mobile-responsive web so your CFO can vote on a proposal from an airport without an install.
SSO methods (LIVE today, listed in calibration order): Microsoft Entra ID (formerly Azure AD) · Okta · Google Workspace · SAML 2.0 generic. SCIM provisioning available with all four. Additional IdPs (Ping, Auth0, OneLogin) ship Q3 2026 - flag at MNDA and we will prioritize your IdP in the queue.
Network requirements: standard outbound HTTPS to our load balancer (allowlisted by IP range, documented in DPA Section 4). No inbound connectivity required - we read from your ERP APIs over your existing egress. No VPN required, no on-premise installation, no firewall changes for the typical deployment.
What we deliberately do not support: consumer email domains (gmail.com, yahoo.com, etc.) for production tenants - enterprise SSO required. This is a security posture, not a limitation.
Built for regulated industries from day one.
Multi-region · zero-trust · hash-chained audit · custody-grade key management. Designed against the same security expectations a enterprise-tier enterprise applies to its core systems.
RTO = Recovery Time Objective (max time to restore service). RPO = Recovery Point Objective (max acceptable data loss).
Active-active deployment across US East · US West · EU Central · APAC. Tenant residency election at sign-up. Zero-trust network · custody-grade key management on Cloud KMS.
Every event is hash-chained - including approvals, MRP runs, signal traces, and integration calls. Tamper-evident by construction. Signed receipts available on request.
90 days. Three plants. One intelligence layer.
A representative outcome model based on the documented Working Capital Methodology applied to a synthetic manufacturer profile at the $450M-revenue tier. No real customer is referenced. Smaller manufacturers and large-enterprise operators see proportional scaling against their own profiles during Day 0 baseline validation.
Use the calculator below to model your own profile.
A common pattern across manufacturers and industrial operators: previous attempts to consolidate operational visibility through a central procurement suite ate years of effort and never produced the cross-functional view the operations team actually needed. AssetShop's read-only overlay sits beside what's already there. Within eight weeks, cross-domain signals route across plants - without modifying source systems, without a multi-year migration project, without a rip-and-replace.
Project your Year 1 release.
Based on a documented Working Capital methodology shared with customers under MSA. Five conversion paths, calibration multipliers from category benchmarks, transparent math. Adjust the inputs to your operational profile; the calculator works against your numbers, not vendor ranges.
Combined cash impact across five conversion paths. Calibrated against documented category benchmarks; refined post-launch with cohort data. Methodology details below.
Year-1 capture is conservative - methodology assumes 60% of identified leakage is recovered as the engagement matures. Year-2 capture (80%) reflects pattern-library expansion and process integration. Year-3 capture (95%) reflects steady-state operational discipline.
Without AssetShop SCO, each path's working capital remains trapped or exposure remains untracked. With AssetShop SCO, each path's leakage is surfaced, quantified, and released into measurable annual outcomes. The released figures above are net of the conservative 60% Year-1 capture rate already applied.
Calculator outputs are methodology projections, not customer outcomes. Pre-launch, AssetShop has zero deployed customers; multipliers are calibrated to category benchmarks rather than observed data. Below is an honest breakdown of confidence per element so you can pressure-test our claims.
Recommendation: use the conservative calibration (0.5×) for board materials and budget approval. The conservative case still produces 15:1-30:1 ROI for typical profiles; if your CFO finds even that defensible, the base and aggressive cases are upside.
Four ways to engage · one platform.
Everyone gets the same complete platform. These differ only in commitment and price — never in what you can do.
Priced to your procurement spend - the value driver.
Working-capital release, leakage recovery, and variance capture all scale with procurement spend, so Enterprise pricing scales with it too — the value you keep stays far larger than the fee at every size. There is no upper limit on the procurement spend we can support; the largest and most complex environments are simply scoped individually rather than slotted into a fixed band.
How Founding-5 compares: Founding-5 is one flat $175K/yr at any size — well below standard Enterprise pricing, and proportionally far more valuable the larger your operation (the biggest operations save the most against a scoped Enterprise quote). The larger your operation, the more a charter seat is worth, and there are only 5.
For a large operation whose scoped Enterprise quote would run several hundred thousand per year, the flat $175K charter rate is a substantial multi-year saving, locked for three years. The charter is priced per operating company — one seat covers all your divisions, regions, and entities (including ones you later acquire), and the rate holds even if your spend grows across a band during the term. Genuinely separate businesses under a holding company are handled as additional charter seats while any remain. One operating company, one seat — and there are only 5.
How is AssetShop different from the alternatives?
platform.assetshop.com with conventional TLS, CDN, and DNS failover - the infrastructure CIOs already approve for production SaaS. EU customers receive platform-eu.assetshop.com with Frankfurt-region edge for Schrems II compliance.Underneath, we maintain a cryptographic identity layer that gives every tenant a portable, verifiable identity across current and future AssetShop products. The benefit you see: tamper-evident audit anchoring, customer-side verification via open-source CLI, and identity portability if you adopt additional AssetShop products later. The underlying infrastructure is implementation detail; what matters to your security team is that the customer-facing surface runs standard enterprise web infrastructure.
Capital allocation, not feature procurement.
AssetShop is a working-capital instrument, not a software line item. The CFOs who evaluate AssetShop translate operational outcomes into the language that matters at the board: cash conversion cycle, return on invested capital, audit-defensibility, predictability.
Enter your customer-side baselines below. The worksheet calculates per-path impact across five conversion paths, three-year cumulative ROI, and a risk-mitigated investment recommendation - against your numbers, not vendor ranges. Methodology calibrated against category benchmarks; multipliers documented in your MSA.
Five domains. One layer. Yours, today.
Walk through the platform with seven personas, six cross-domain signals, and eight wired action workflows. No signup. No deck. Just the working software.