The risk in your portfolio your status reports smooth over.
AssetShop Project & PMO runs on top of your project and portfolio management systems, resource and capacity data, financial and cost systems, and Excel - reading what those systems already hold, surfacing the schedule slip, resource conflict, stage-gate and RAID-log exceptions, percent-complete drift, and stalled value they cannot see, reconciling across them when your stack spans more than one.
Outcomes calibrated against your annual portfolio investment and delivery base*. First signal delivered within 14 days of security-and-counsel sign-off.
* Outcome calculations applied against the customer's annual portfolio investment and delivery base. Validated jointly at Day 0 with the customer Head of PMO and CFO.
Your status report said green. The data said otherwise.
For forty years, every enterprise suite demanded the same trade: migrate to us, re-implement your system of record. Teams paid the price - in re-platforming quarters, in reconciliation spreadsheets, in answers that arrive too late. AssetShop Pmo ends the trade.
The status field says green. The schedule, spend, and resource data say otherwise. The at-risk project is flagged by a project manager's optimism, not by the data behind it.
Schedule in one tool, cost in another, resources in a third. The project's real health spans all of them. No single view connects the slip to its cause.
When capacity demands aren't connected across the portfolio, the same team is committed three times. The conflict surfaces as three separate delays.
Five outcomes your ERP cannot deliver alone.
AssetShop Project & PMO is benchmarked against five concrete outcomes - what your team actually has after the platform is in their hands, not what the brochure says. Each scales with your annual portfolio investment and delivery base. ROI positive year one across every reference scenario.
Four advantages competitors cannot replicate without re-platforming their stack.
Coupa, Ariba, Anaplan, a planning suite - 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.
Program and portfolio-management intelligence · five integrated domains.
Milestone slippage, resource contention, and benefit realization read across your PMO and delivery systems - the slipping program traced to the open roles and bottleneck teams that gate it. Read-only, source-attributed.
Generate audit-anchored QR codes for every lot, pallet, shipment, and asset transfer. Scans are signed events on your audit chain. Project-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 project network beyond Tier-1. Surfaces concentration risk you cannot see when you only buy from your direct projects and workstreams. 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 portfolio management spend. 4 major exchanges with industrial-relevance ranking. Project-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 →
Slippage root-cause linkage · schedule risk traced to cause.
A slipping milestone reads as a delivery problem. Root-cause linkage ties it to the open roles and bottleneck teams that gate it and the budget Finance shows over - the schedule risk traced to its cause, not just flagged.
Recommendation intelligence · ranked actions, not dashboards.
Most platforms give you reports. This gives you specific, dollar-quantified, ranked recommendations - which slippages to escalate, which contentions to resolve, which benefits to protect - each citing its math and running on live data. The recommendation is read-only; the decision and the execution stay in your systems.
Cross-domain signal trace · the chain no single system shows.
The deepest value is not any single reading - it is the chain. Pmo signals read beside the other domains reveal the cause that no single system holds: where this domain's exposure originates, and which other functions it implicates. Surfaced read-only, fully traceable.
A portfolio of programs in. one slippage-root view out - in a single integrated pass.
One delivery cycle. Schedule, resource, and budget signals read together in a single pass - milestone slippage traced to the roles and teams that gate it, not five disconnected reports. The value no PPM delivers alone.
Cross-domain signals · the architecture in motion.
Every signal travels from where the problem is found to the teams who can act on it, 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 projects and workstreams run AssetShop Pmo too, the chain becomes visible.
Most operational platforms see your operation. AssetShop Pmo 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 project 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 project matches what they shipped. Their PO to tier 2 sub-component project 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 operations run AssetShop Pmo. 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 early customers come online 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 portfolio management) reach economic moat status when ~30-40% of a category adopts the same tool. AssetShop's early customers are calibrated to seed that adoption density in industrial operationss - 5 anchor customers whose projects and workstreams and customers progressively enable the network as adoption deepens.
A layer, not a replatform.
AssetShop Pmo is the intelligence layer on top of your existing systems-of-record. Your ERP, MES, PPM system, 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 portfolio management 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 Pmo | Portfolio management replatforms Coupa, Ariba, Oracle Portfolio management |
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 portfolio management workflow | Data modeling per dashboard | Project-master enrichment |
| Cross-domain pattern computation | 60 surfaces joined | Within portfolio management 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 | 12-check scorecard · certificate at live gate | SOW-based integration | Per-connector spec | Vendor-managed |
What makes this defensible.
Eight distinct moat dimensions, each independently meaningful and collectively compounding. Early customers engage with all eight, 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 project-side adapters, producing choke-point detection no single-tenant platform can compute. Network deepens as early customers adopt.
Cross-domain pattern computation
A milestone slip, an open role, and a budget overrun are often three names for one delivery problem. Point solutions cannot see these connections because they index one domain. AssetShop joins your enterprise systems into one composable intelligence layer.
Anonymous weighted governance
Every "proceed with project X from RFQ event" becomes auditable, defensible, anonymous. Portfolio management-savings claims to the board are no longer single-buyer judgment. SOC 2 and ISO auditors love this. M&A diligence loves this. Project-negotiation leverage benefits because counter-parties see formal governance.
30-day implementation commitment
The portfolio management-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 12-check conformance scorecard and a public calibration entry documenting endpoints, fields, rate limits, and read-only attestation. A cryptographically-signed certificate issues at each adapter's live gate (12/12), verifiable 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™
Early 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. Early access opens the full engine - every domain, one read-only layer. This compounds annual rate for three years, with locked-rate renewal and quarterly roadmap influence. Early-customer pricing protection is time-limited. 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 early-customer priority for what ships next. No third-party middleware. No ETL surprise.
Scorecards anchor to the ledger; a signed certificate issues at each adapter's live gate (12/12). 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, Projects and workstreams 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 projects and workstreams 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 / portfolio engine / resource system / PPM system 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 · Microsoft Dynamics), or a pre-formatted Excel/CSV template handed to your data team or project - round-tripped cleanly with the platform.
Six analytics views, built and browsable today: Variance Analytics · Working Capital live dashboard · Cost-to-Serve attribution · Risk Radar with live project signals · Spend Treemap · project-segmentation Portfolio matrix. Plus eleven additional analytics views on the Pmo roadmap through Q2 2027: global project network · network topology · risk heat maps · shipping lane flow · capacity projection · pallet storage forecast · decision audit trail with cryptographic provenance · project financial-trend monitoring · ESG attribution · scenario library · and more. Multi-level project 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 delivery 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 operations 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 project 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 projects, 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 projects 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, project 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, project insolvency, demand surge, program outage, FX shifts, capacity constraint, port strike, regulatory expansion - each modeling impact across portfolio management, operations, planning, and logistics with auto-generated response playbooks. Run multiple in parallel to compare strategic resilience.
Filter projects and workstreams by category × capability × performance metrics × financial trend. 21 capabilities organized in process / certification / commercial groups. Six performance/financial filters including credit grade, on-time delivery, 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, portfolio engine, PPM system, MES, resource system, portfolio management, 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 Pmo. The certified ERP/portfolio engine/resource system/PPM system connectors handle real-time observation harvesting. Excel handles everything else: legacy systems without modern APIs, project-side data your delivery 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 Pmo 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 (Live today) means it works now. BUILT_AND_INTEGRATING (In integration - engine built, first customer connection pending) 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. As of June 2026 the ledger is enforced in CI: a calibration-ledger sweep fails any build where an adapter claims BUILT_AND_OPERATING without a true 12/12 live proof - on its first run it caught one overclaim and forced the correction. The full ledger is designed to be anchored to a tamper-evident, append-only chain at general availability, at which point entries can be independently verified via npx @assetshop/verify-cli.
Questions the Head of PMO and COO brings to the table.
Direct answers to what a serious evaluation surfaces - read-only posture, system-of-record authority, integration scope, and time to value.
Can AssetShop PMO modify our project systems?
No. AssetShop PMO is strictly read-only. It reads project, resource, and cost data and surfaces connected portfolio intelligence. Your PPM systems remain authoritative. Nothing is written back.
How is this different from our PPM tool?
PPM tools hold project plans and status. AssetShop PMO connects that status to the underlying data - schedule, spend, resource, dependency - surfacing the at-risk project the status field calls green, across the whole portfolio.
What systems does it connect to?
PPM (Planview, Anaplan, ServiceNow SPM, Microsoft Project), work management (Jira, Smartsheet), financial systems, plus Excel ingestion.
How fast do we see value?
First signal within 14 days of security and counsel sign-off, on a paid assessment against your own data. The Day-90 pilot carries a binary outcome warranty.
Is it SOC 2 certified?
SOC 2 Type II is in progress, estimated Q1 2027. Read-only and audit-anchored by construction; a trust center documents current control status.
Built for regulated industries from day one.
Multi-region · zero-trust · hash-chained audit · bank-grade key management. Designed against the same security expectations an 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 design across US East · US West · EU Central · APAC. Tenant residency election at sign-up. Zero-trust network · bank-grade key management on Cloud KMS.
Every event is hash-chained - including approvals, portfolio runs, signal traces, and integration calls. Tamper-evident by construction. Signed receipts available on request.
90 days. Three programs. 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 portfolio management 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-team signals route across programs - without modifying source systems, without a multi-year migration project, without a rip-and-replace.
Why an overlay, when your ERP already has modules?
The numbers behind the decisions you already make.
Reading your systems is the start. The platform also assembles the cross-system economics behind recurring decisions in this domain - surfaced read-only, with conservative coefficients you can see and adjust. Decisions and execution stay in your systems of record.
From a paid assessment to enterprise scale.
Engagements start with a paid operational assessment on your own data, then scale through pilot, pilot, and enterprise - each backed by a binary Day-90 warranty. The full tier breakdown lives on the enterprise site.
See the full pricing & tiers →How is AssetShop different from the alternatives?
platform.assetshop.com front door with CDN and DNS failover ships at commercial GA - the infrastructure CIOs already approve for production SaaS. At GA, EU tenants 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 portfolio management.
AssetShop pays for itself out of the cash it frees. 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-team signals, and eight wired action workflows. No signup. No deck. Just the working software.