AssetShop Workforce · BUILT

The capacity your HRIS counts but can't connect to the work.

ROI positive Year 1 No migrationNo replacementFirst signal in 14 days

AssetShop Workforce Intelligence runs on top of your HRIS and core HR records, ATS and requisition systems, payroll and compensation data, and Excel - reading what those systems already hold, surfacing the capacity gaps, critical-role vacancy, span-of-control imbalances, DEI representation gaps, and attrition and labor-cost risk they cannot see, reconciling across them when your stack spans more than one.

Outcomes calibrated against your annual workforce cost and capacity base*. First signal delivered within 14 days of security-and-counsel sign-off.

* Outcome calculations applied against the customer's annual workforce cost and capacity base. Validated jointly at Day 0 with the customer CHRO and Head of Finance.

EXECUTIVE BRIEFING LAYER · ENTERPRISE TWIN
Per-persona executive briefings, generated from your operational data.
Enterprise Twin synthesizes cross-team signals into role-specific briefings for CHRO, VP People, Head of Workforce Planning, and COO - the same operational reality, told in the vocabulary each executive uses for decision-making. Live during 90-day pilots.
Connectors
57 in portfolio
First signal
14 days*
Pilot warranty
Day 90 binary outcome
SOC 2 Type II
est. Q1 2027
Why this exists

Your HRIS counts heads. It doesn't see the gap.

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 Workforce ends the trade.

Headcount counted, capacity unknown

Your HRIS knows how many people you have. It doesn't know whether that matches the work. The critical-role gap becomes a stalled project before the vacancy count rises.

Signals scattered across systems

Compensation in payroll, tenure in the HRIS, engagement somewhere else. The attrition risk spans all of them. No single system sees the pattern that precedes a departure.

Planning on an annual cadence

When workforce planning is a once-a-year spreadsheet, capacity decisions lag reality by quarters. The gap compounds between cycles. Cost is managed against budget, not against the work.

Read-only intelligence across every enterprise domain
Trust posture · verified attestations
Tamper-evident audit chain · independently verifiable
Read-only architecture · ERPs remain authoritative
Cryptographic provenance · every signal
Tenant isolation · Firestore + role-gated callables
WCAG 2.2 AA · conformance v1.0
AI Safety Policy v1.0 · NIST AI RMF · EU AI Act
Legal bundle to counsel-review standard (counsel pass pre-signature) · MSA · DPA · SLA
SOC 2 Type II · report estimated Q1 2027
What changes for your operation

Five outcomes your ERP cannot deliver alone.

AssetShop Workforce Intelligence 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 workforce cost and capacity base. ROI positive year one across every reference scenario.

01 · 21 critical
Capacity gaps before the work stalls

Open requisitions connected to the projects and lines that depend on them - the 21 critical roles tied to specific work at risk, not a vacancy count in a dashboard.

02 · 11.2% tracked
Attrition risk, surfaced early

Patterns across compensation, tenure, and team signals that precede departures - flagged while there is still time to act, not explained in an exit interview.

03 · 2,140 mapped
Workforce cost, connected to output

Headcount and compensation mapped against the work it produces, across HRIS, payroll, and operational systems - so cost decisions are made against capacity, not just budget.

04 · SHA-256 anchored
Every number traced to source

Each capacity, cost, and attrition signal links to its HRIS, ATS, or payroll record. Audit-ready, hash-anchored, never written back.

05 · 64 live
Planning that sees the whole picture

Workforce planning stops being an annual spreadsheet exercise and becomes a live view across hiring, attrition, and capacity - 64 open reqs against real demand.

The architectural moat

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.

MOAT 01 · Additive architecture

On top of your stack - never between.

AssetShop reads only. Your ERPs remain authoritative. Disconnect us tomorrow and every authoritative record stays exactly where it lives today. Zero board-level migration risk. Zero rip-and-replace.

MOAT 02 · Cross-domain by construction

Five domains. One substrate.

Incumbents operate within single functional silos. A demand surprise dies in email threads on its way to workforce planning. AssetShop routes signals across all five domains by design - cross-functional reality in one platform.

MOAT 03 · Calibration discipline

Outcome warranty contractual.

Day 90 joint measurement against the dollar-denominated baseline agreed Day 0. Miss it, the pilot fee is refunded cleanly. No vendor in the category writes this into the MSA. Outcomes are the unit of accountability.

Customer-side conditions · bilateral commitment
Warranty applies when: (1) savings reach 75% of the low-end baseline projection, (2) transaction volume is 90%+ of Day 0 assumption, (3) product-mix gross-profit impact stays within 10% decline, (4) full department utilization across all functions, (5) all Workforce layers are exercised, (6) savings are tracked in detail per Exhibit F methodology.
MOAT 04 · Audit chain anchored

SHA-256 hashes anchored every 60 min.

Only opaque hashes leave the tenant. The public anchor stores only one-way SHA-256 fingerprints. Customer data, observations, and contents remain entirely within the tenant. The anchor proves the data existed at the timestamp without exposing what it is.

Every operational signal carries a cryptographic SHA-256 fingerprint anchored to a tamper-evident chain. Your audit firm verifies independently via verify-cli on npm. Trust is mathematical - not promotional.

Priority / Horizon · five domains

People operations, performance, and org effectiveness · five integrated domains.

For CHROs who need to see the organization as it actually functions - HRIS data joined with performance signals, cross-functional collaboration patterns, and capacity utilization, read-only and source-attributed.

HR Ops
Headcount vs. plan
Open-role tracking
Time-to-fill
Cost-per-hire
Org-structure view
Span-of-control
Performance
Performance signals
Goal attainment
Calibration view
Skill-gap mapping
Succession depth
Promotion velocity
Org Health
Collaboration patterns
Bottleneck teams
Attrition risk
Engagement signals
Manager effectiveness
Network analysis
Capacity
Utilization vs. demand
Contractor backfill
Overtime exposure
Project staffing
Capacity forecast
Cost-of-instability
Analytics
Workforce cost walk
Productivity by function
Retention economics
Scenario compare
Executive briefing
Board pack export
Shared across every domain · included at every tier
8 connectors validated, 10 more in active development. 8 conformance-tested ERP & source-system adapters (SAP S/4HANA · Oracle Fusion · NetSuite · Dynamics 365 · Infor CloudSuite · Coupa · Workday · Generic REST) plus 10 in active development on the same read-only framework (SAP Ariba · SAP ECC · Jaggaer · Ivalua · Anaplan · o9 · DocuSign CLM · Ironclad · Salesforce) — on a roadmap extending across Workforce planning · Planning · payroll system · ATS · MES · Visibility · Team Management.
5 canonical drill paths. L0 Mission Control → L4 transaction-line in 8 seconds. Audit chain entry at L4.
Role-based access L0-L5+. External · IC · Manager · Director · Executive · C-Suite. Default filters and approval thresholds per authority.
Per-persona briefings. CFO · CPO · COO · CIO · CEO. Auto-generated daily, executive-grade narrative.
Cross-device responsive web. Desktop browsers (Chrome, Safari, Edge, Firefox) · iOS Safari · Android Chrome. Every operational signal accessible on PC, phone, or tablet.
Notifications. In-app + email + SMS (Enterprise) + status page. SIEM webhooks to Splunk HEC · Elastic Logstash.
Audit chain integrity. SHA-256 hash-chained per event; tamper-evident anchoring activates Q3 2026 post security audit (dry-run mode until then). verify-cli on npm for independent customer-side verification today.
Excel/CSV interop. Every list exports CSV/XLSX. Every import accepts CSV/XLSX. System-integrated and spreadsheet tracks run in parallel.
Specialized capabilities · in the platform today
QR Code Hub · Traceability
QR-anchored handoffs across the operations

Generate audit-anchored QR codes for every lot, pallet, shipment, and asset transfer. Scans are signed events on your audit chain. Team-side scans, customs scans, customer-receipt scans - all tied back to the originating PO or work order.

Open in demo →
Multi-Tier Team Map · Analytics
Visibility beyond Tier-1 into Tier-2 + Tier-3

Continuity, compliance, and cyber risk classification across your team network beyond Tier-1. Surfaces concentration risk you cannot see when you only buy from your direct teams and functions. 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.

Open in demo →
Markets & Macro Trends · Cockpit
FX exposure, team-stock signals, commodity hedging

6 reference currencies vs your workforce planning spend. 4 major exchanges with industrial-relevance ranking. Team-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.

Open in demo →

Plus 85+ additional routes across the 13 capability groups - all in the no-sign-up demo →

Flagship feature · 01

Capacity-gap economics · cost-of-instability quantified.

Open roles and budget variance look like two problems on two systems. Capacity-gap economics maps them onto the same cost centers and shows the true run-rate hiding behind contractor backfill and overtime - the people cost of instability, counted.

Attrition-risk surfacing - Performance, collaboration, and tenure signals read together to surface risk before resignation.
Org-effectiveness view - Collaboration patterns that reveal the teams gating delivery - the structural bottleneck no org chart shows.
Capacity vs. demand - Utilization read against real demand, with the contractor backfill that masks the true run-rate.
Read-only by architecture - You see the capacity picture; HR actions execute in your systems. Never write-back.
21
Critical roles mapped
$3.4M
Backfill cost exposed
14
Bottleneck teams found
Signal outputs · read-only
Attrition-risk surfacinglive
Org-effectiveness viewlive
Capacity vs. demandlive
Read-only by architecturelive
Synthesized from the Meridian demo profile. Every output is source-attributed and traceable to the originating system. Execution stays in your systems of record.
Flagship feature · 02

Recommendation intelligence · ranked actions, not dashboards.

Most platforms give you reports. This gives you specific, dollar-quantified, ranked recommendations - which roles to fill first, which retention risks to address, which teams to unblock - each citing its math and running on live data. The recommendation is read-only; the decision and the execution stay in your systems.

Dollar-quantified recommendations - Not a dashboard - specific, ranked actions: which roles to fill first, which retention risks to address, which teams to unblock. Every recommendation cites its math.
Live data, conservative coefficients - Runs on the signals your systems already hold, with documented, adjustable multipliers you control.
Full causal citation - Every recommendation traces to the source signals behind it - you see why, not just what.
Read-only by architecture - The recommendation is surfaced; you decide and execute in your systems of record. Never write-back.
21
Critical roles mapped
$3.4M
Backfill cost exposed
14
Bottleneck teams found
Ranked recommendations · read-only
Dollar-quantified recommendationsranked
Live data, conservative coefficientsranked
Full causal citationranked
Read-only by architectureranked
Synthesized from the Meridian demo profile. Each recommendation is source-attributed and cites its coefficients. Execution stays in your systems of record.
Flagship feature · 02

Cross-domain signal trace · the chain no single system shows.

The deepest value is not any single reading - it is the chain. Workforce 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.

Cross-system causal chain - The signal traced from symptom to source across every connected system - the cause, not the alert.
Other-domain linkage - Where this exposure implicates finance, risk, or operations - the cross-functional reach made explicit.
Conservative, adjustable coefficients - Every economic estimate uses documented, conservative multipliers you can see and tune per tenant.
Read-only by architecture - You see the trace; every decision and action executes in your systems of record. Never write-back.
21
Critical roles mapped
$3.4M
Backfill cost exposed
14
Bottleneck teams found
Signal outputs · read-only
Cross-system causal chainlive
Other-domain linkagelive
Conservative, adjustable coefficientslive
Read-only by architecturelive
Synthesized from the Meridian demo profile. Every output is source-attributed and traceable to the originating system. Execution stays in your systems of record.
Featured use case · end-to-end

A cycle of HR activity in. one org-truth view out - in a single integrated pass.

One review cycle. HRIS joined with performance, collaboration, and capacity signals in a single pass - the org as it actually functions, not five disconnected reports. The value no HRIS delivers, because no HRIS reads performance and collaboration together.

Stage 1 - ingest
Read across systems
HRIS, performance, collaboration, and project systems read together, read-only.
Stage 2 - join
Capacity meets cost
Open roles mapped onto the cost centers showing variance - the gap and the overrun shown as one event.
Stage 3 - surface
Rank by exposure
Attrition risk and capacity gaps ranked by impact, with the bottleneck teams they expose.
Stage 4 - hand off
Decisions stay yours
Every signal traced to its source. HR actions execute in your systems of record.
Read-only across every stage. AssetShop surfaces the cross-system picture; the decision and the execution stay in your systems of record.
The spine

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.

Signal anatomy
Source domain · what detected the event (e.g. team risk monitor)
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)
Walk through six signals in the demo
Signals routed last 24h · 6 active
Pruitt Forging - financial-distress flag · $8.4M exposure
HRPERFORMANCEORGANALYTICS
V2200-series demand sensing - +28% Q3 - $3.2M/yr revenue at risk
ORGHRPERFORMANCECAPACITY
Workforce costsCo time-to-fill SLA degradation - 91% → 72% · 14 at-risk shipments
CAPACITYHRPERFORMANCEANALYTICS
Section 301 tariff - Cat 84 · +12.5pp · $513k annual
ANALYTICSHRORG
Plan coherence drift · LINE-3 17% · 480-unit gap
ORGPERFORMANCEANALYTICS
Mass-PO consolidation - Pruitt - $270K/yr annualized opportunity
HRCAPACITYANALYTICS
Network effect · ships when networked

When your teams and functions run AssetShop Workforce too, the chain becomes visible.

Most operational platforms see your operation. AssetShop Workforce 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 team from inside their own tenant. Each customer's data stays private to that customer. The relationship between them becomes auditable, not assumed.

End-to-end operations visibility · multi-tier reconciliation
Tier 4+
Commodity & raw material
Mining, refining, primary extraction. Origin certification, ESG provenance, conflict-mineral attestations.
Tier 3
Sub-component manufacturer
Specialty parts, sub-assemblies, intermediate processed materials.
Tier 2
Component team
Finished components, modules, packaged sub-systems shipped to tier 1.
Tier 1
Direct team
Your direct vendors. POs land in their order book; they ship to your sites.
You · OEM
Manufacturer of record
Final assembly, brand-owner. Ships to distributors, retailers, or end customers.
Cross-tier PO reconciliation

Your PO to tier 1 team matches what they shipped. Their PO to tier 2 sub-component team shows what they ordered to fulfill yours. Variance attribution traces back to its actual origin instead of stopping at the first vendor boundary.

Disruption propagation forecast

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."

Audit-chain provenance to origin

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.

Forward visibility · distributor & channel

When distributors or channel partners run AssetShop too, your sell-through becomes visible upstream. Capacity positioning, channel sell-out, end-customer demand signal reconciles against your shipment plan in near-real-time.

Calibration · ships when networked

Multi-tier visibility activates when two or more customers in the same operations run AssetShop Workforce. 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.

Why the network effect matters

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 workforce planning) 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 teams and functions and customers progressively enable the network as adoption deepens.

Product architecture

A layer, not a replatform.

AssetShop Workforce is the intelligence layer on top of your existing systems-of-record. Your ERP, MES, payroll 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.

Layer 3 · AssetShop Workforce
Intelligence layer · read-only
Cross-domain pattern computation across 60 platform surfaces. Joins spend cube + team health + capacity + working capital + regulatory exposure + carbon. Surfaces variance, leakage, opportunity, risk to humans for decision-capture. Anonymous weighted-vote governance + executive signoff queue captures the decision-record. Read-only by default.
read-only connector framework · conformance-certified
Layer 2 · Your systems-of-record
ERP · MES · payroll system · PLM · CRM · unchanged
SAP (ECC + S/4HANA), Oracle (EBS + Fusion), NetSuite, Microsoft D365, Infor CloudSuite, Coupa, Workday. Plus 15+ adjacent systems (APS, capacity engine, ATS, team master, visibility platforms). Your transactional truth lives here; AssetShop does not modify or migrate it. Your buyers buy in your ERP; your AP team pays in your ERP. All execution unchanged.
transactional execution
Layer 1 · Physical operations
Teams and functions · Sites · Logistics · Customers
Where the actual goods, money, and information flow. Multi-tier supply network with tier-1 partners, tier-2 choke-points, and tier-3 raw-material sources. AssetShop indexes this network as observed through your ERP and (where customer-shared) via team-side adapters - producing visibility no single-tenant platform can compute alone.
Posture
Read-only
Cannot break your ERP. No migration. No transactional pass-through. No write-back surprises.
Residency
Customer cloud, per-tenant
Each customer is a separate isolated project. BYO cloud included with Enterprise tier. Cross-tenant queries impossible by IAM policy.
Decision capture
Auditable + anonymous
Anonymous weighted-vote governance. Immutable executive signoff trail. Decision-record stays in AssetShop; execution stays in your ERP.
Continuity
Founder Continuity Plan™
On any wind-down or acquisition event, AssetShop becomes a maintained open-source artifact under a managed Continuity license - preserving continuity of operations for customers. Code release does not equal product replication: governance, hosted infrastructure, model tuning, and operations remain non-trivial and 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.
Enterprise lifecycle

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.

PHASE 1 Week 1 · ~10-15 IT hrs

Setup

Read-only ERP service accounts. SSO via customer IdP (Okta, Azure AD, Google Workspace, Ping). Per-tenant isolated cloud project (GCP / AWS / customer choice on Enterprise tier). VPC peering or PrivateLink where policy requires. Conformance scorecard reviewed per adapter; certificates issue at each adapter's live gate (12/12).
Outcome: connector green · audit log emitting
PHASE 2 Week 2 · ~3-5 data hrs

Integration

Initial mirror of spend cube, team master, open POs, AR/AP, org structure, capacity, contracts. Sample-join validation against your master data. Pilot-baseline diagnostic produced jointly with your CFO/CPO. Three highest-value opportunities scoped with dollar targets.
Outcome: joint baseline signed · opportunities scoped
PHASE 3 Week 3 · ~6-8 admin hrs

Launch

Industry template applied (Automotive, Aerospace, Industrial, Electronics, Medical, CPG). RBAC + role-based default views. Workflow templates enabled (executive briefing, CBAM alert, counterparty distress, feedstock spike). Joint workshop with named users covering navigation, drilldowns, governance.
Outcome: users authenticated · workflows active
PHASE 4 Months 1-3 · embedded CS

Maintenance

Daily Monday-morning executive briefing. Weekly captured-value measurement with your finance team. Monthly RSO command-center review across all 60 surfaces. Day-90 Outcome Warranty™ trigger evaluation - if first captured value isn't documented and signed, annual fees refunded.
Outcome: first $ captured · cadence locked
PHASE 5 Quarter+ · continuous

Sustenance

Quarterly platform review with your buying committee. Annual roadmap alignment (Early customers steer the roadmap). Continuous adapter additions as your system landscape evolves. Network-effect deepens as more of your teams and functions and customers enable their own AssetShop tenants - producing visibility no single-tenant platform can compute.
Outcome: compounding value · deepening moat
Total customer effort
~30-40 hours
across 4 roles over 30 days
AssetShop commitment
Dedicated SE
full-time through Week 4; CS lead 8-10 hrs/wk
Time to first value
Day 30
backstopped by Day-90 Outcome Warranty
Steady-state lift
Self-service
monthly QBR · quarterly roadmap input
Comparison vs adjacent categories

Where AssetShop sits in your stack.

We are not a replacement for workforce planning 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 Workforce Workforce planning replatforms
Coupa, Ariba, Oracle Workforce planning
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 workforce planning workflow Data modeling per dashboard Team-master enrichment
Cross-domain pattern computation 60 surfaces joined Within workforce planning 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
A note on competitive framing AssetShop is genuinely complementary to all three categories. If you have already replatformed to Coupa or Ariba, we work with what you have. If your team lives in Tableau or PowerBI, we feed those tools via API and provide the cross-domain join logic that user-defined queries cannot replicate. If you subscribe to D&B or Interos for team risk, we integrate those signals into our composite resilience score rather than duplicate them. We compete only with the status quo of teams stitching spreadsheets manually.
Unique value · competitive moat

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.

1

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.

2

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 team-side adapters, producing choke-point detection no single-tenant platform can compute. Network deepens as early customers adopt.

3

Cross-domain pattern computation

An open role, a budget overrun, and a delivery slip are often three names for one capacity problem. Point solutions cannot see these connections because they index one domain. AssetShop joins your enterprise systems into one composable intelligence layer.

4

Anonymous weighted governance

Every "proceed with team X from RFQ event" becomes auditable, defensible, anonymous. Workforce planning-savings claims to the board are no longer single-buyer judgment. SOC 2 and ISO auditors love this. M&A diligence loves this. Team-negotiation leverage benefits because counter-parties see formal governance.

5

30-day implementation commitment

The workforce planning-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.

6

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
7

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.

8

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.

Early-customer access

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.

Connector ecosystem

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.

Conformance scorecard · every adapter
Every connector ships with a 12-check conformance scorecard and public calibration entry documenting endpoints, fields, rate limits, and read-only attestation.

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.

Trust Center →
SAP S/4HANA
CDS views · OData · IDoc
Built · integrating
Oracle Fusion
ERP Cloud · REST · BIP
Built · integrating
NetSuite
SuiteTalk · SuiteScript
Built · integrating
Workday
PRISM · Reports-as-a-service
Built · integrating
Microsoft D365
Dataverse · Power Platform
Q3 2026
Infor CloudSuite
ION · M3 · LN
Q3 2026
Coupa
Procure-to-pay extension
Q3 2026
Generic REST
JSON · OAuth2 · webhooks
Built · integrating
Multi-ERP customers · same-system or cross-system

One platform. Multiple ERPs. System-of-record election per entity type.

Cross-system (different ERPs)

Multi-ERP customers configure system-of-record per entity type: Purchase Orders may live in SAP S/4, Teams and functions in Coupa, Work Orders in Oracle Fusion. AssetShop reads each authoritative source, surfaces cross-system variance, and never overwrites any of them.

Same-system multi-tenant (M&A)

Two NetSuite instances after an acquisition. Three SAP instances from regional rollouts. AssetShop deduplicates teams and functions 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.

Provenance: every canonical field carries a _provenance sub-record naming the source system, source entity ID, source field name, ingestion timestamp, and confidence score. Auditors re-trace any reported number back to the originating system without opening a ticket.
Ingest · Analyze · Decide · Export

Every input from your systems. Every output exported clean.

INPUT
From your ERPs, capacity engine, payroll system, ATS, Excel, or CSV - via read-only adapters
PROCESS
AssetShop Workforce surfaces variance, leakage, cross-system drift - cryptographically anchored
OUTPUT
Exported clean - JSON / CSV / Excel / PDF - with full provenance hash

AssetShop slots into your stack rather than replacing it. Master data flows in through certified ERP / capacity engine / ATS / payroll 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.

01 · Ingest
ERP · capacity engine · ATS · payroll system connectors or Excel

Every supported data flow runs through one of two paths: a certified read-only connector to your system of record (Workday · SAP SuccessFactors · Oracle HCM · UKG · Microsoft Dynamics), or a pre-formatted Excel/CSV template handed to your data team or team - round-tripped cleanly with the platform.

Sync cadence: real-time webhooks where supported · 15-min poll · 1-hour batch · daily full-sync
02 · Analyze + Decide
Analytics suite + scenario simulations + your AI

Six analytics views, built and browsable today: Variance Analytics · Working Capital live dashboard · Cost-to-Serve attribution · Risk Radar with live team signals · Spend Treemap · role-criticality Portfolio matrix. Plus eleven additional analytics views on the Workforce roadmap through Q2 2027: global team network · network topology · risk heat maps · shipping lane flow · capacity projection · pallet storage forecast · decision audit trail with cryptographic provenance · team financial-trend monitoring · ESG attribution · scenario library · and more. Multi-level team 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.

Plus: BYO-AI connector lets your AI provider query your tenant data through scoped read-only tokens - your AI, your security boundary, your governance.
03 · Export
Every view exports to Excel

Every list, table, chart, dataset, and analytics view ships with one-click CSV and XLSX export. The people 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.

Spend cube · team capabilities · capacity projection · pallet storage forecast · network topology · audit log · everything.
ERP
SAP S/4 · Oracle · NetSuite · Workday · Microsoft Dynamics 365 · Infor · Sage · Acumatica · QAD
capacity engine / Planning
SAP IBP · Anaplan · Oracle · Workday · Microsoft · Anaplan
ATS
ADP · Ceridian · Paychex · Oracle Payroll · SAP Payroll · Rippling
payroll system
Greenhouse · Lever · SmartRecruiters · iCIMS · Eightfold · Phenom
Workforce planning Suites
Coupa · Ariba · Jaggaer · Ivalua · Zycus · GEP SMART
Excel / CSV
Pre-formatted templates for teams and functions, items, org structure, POs, capacity, forecast - round-trip cleanly
BYO-AI
OpenAI · Azure OpenAI · Anthropic Claude · Google Vertex · AWS Bedrock · private endpoints
Identity
Firebase Auth + SAML 2.0 (live) · Okta · Azure AD · Google Workspace via SAML · SCIM provisioning (Q3 2026) · Ping · OneLogin (Q3 2026)

Canonical schemas, field-level provenance, and integration specifications are shared during qualification with mutual NDA and engagement-grade access controls.

Visionary capabilities · competitive moat layer

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.

Working Capital · Live
CFO direct-line · drift detection

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 team extended terms, which customer slowed payment, which SKU is over-stocking. Collapses the CFO feedback loop from "discovered after quarter close" to "addressable today."

Cost-to-Serve
True margin per customer × product

Beyond gross margin per SKU: full attribution including customer-specific workforce costs, 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 workforce costs 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).

Decision Audit Trail
Cryptographic provenance per decision

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.

Risk Radar · Live
Signal-to-action collapse

Real-time signals across trade policy, weather, labor, regulatory, team 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.

Scenario Library
One-click what-if simulations

Eight pre-built scenarios - tariff shocks, team insolvency, demand surge, site outage, FX shifts, capacity constraint, port strike, regulatory expansion - each modeling impact across workforce planning, operations, planning, and logistics with auto-generated response playbooks. Run multiple in parallel to compare strategic resilience.

Multi-level Filtering
Stack filters across dimensions

Filter teams and functions by category × capability × performance metrics × financial trend. 21 capabilities organized in process / certification / commercial groups. Six performance/financial filters including credit grade, time-to-fill SLA, quality, revenue trend. Stack filters across dimensions for surgical sourcing analysis.

Data prepared for AI · BYO-AI

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, capacity engine, payroll system, MES, ATS, workforce planning, 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.

💬 Conversational analysis
Natural-language Q&A about open POs, team risk, capacity engine shortages, capacity hotspots - answers cite the underlying records.
◇ Variance investigation
Send your AI a flagged variance, ask why - your AI traces through spend cube, NCRs, team metrics to root cause.
◈ Scenario reasoning
Frame a what-if (tariff shift, team disruption, demand surge); your AI proposes mitigation plans grounded in live data.
⌖ Decision audit
Every AI response cites the data consulted, queries run, records returned - AI outputs as auditable as direct queries.
Need a custom connector?

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.

Talk to the founder →
Excel ingestion · Excel export

For teams that live in spreadsheets.

Two paths to data move through AssetShop Workforce. The certified ERP/capacity engine/ATS/payroll system connectors handle real-time observation harvesting. Excel handles everything else: legacy systems without modern APIs, team-side data your people 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.

01 · Excel ingestion · alternative to systems integration

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.

drop .xlsx or .csv here · or click to browse
7 canonical schemas · team master · purchase orders · contracts · capacity · work orders · forecast · shipments
Canonical schemas
Teams and functions Purchase Orders Contracts Capacity Work Orders Forecast Shipments
02 · Excel export · available in commercial platform

Download data, charts, and provenance.

Every view, chart, and signal in AssetShop Workforce 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.

Variance Attribution
9-row summary + 7-row detail + provenance
ROI Calculation
Inputs · Scenarios · Sensitivity
Connector Capacity
51 built of 57 in portfolio · calibration buckets
Audit Chain Anchors
Tamper-evident anchor transactions
Export templates are proprietary to authenticated tenants. Available on the commercial platform.
Open commercial platform →
Provenance: Excel ingestion is the Excel-ingestion connector - calibration status BUILT_AND_INTEGRATING (engine built and exercised end-to-end; live-proof lands with the first customer integration). Every uploaded record carries the same _provenance sub-record as records from API connectors: source adapter ID (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.
Calibration ledger · live filterable capacity

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.

Filter
Type
Identifier · Display Name
Calibration Status
Calibration Ledger Ref
Target Date
Loading calibration ledger...
Live entries: -
Anchored at assetshopenterprise.com/trust · tamper-evident
Questions the buying committee actually asks

Questions the CHRO and Head of Workforce Planning 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 Workforce modify our HRIS?

No. AssetShop Workforce is strictly read-only. It reads headcount, requisition, payroll, and skills data and surfaces connected capacity intelligence. Your HRIS remains authoritative. Nothing is written back.

How is this different from our HRIS analytics?

HRIS analytics report on the data inside one system. AssetShop Workforce connects workforce data to the operational systems where the work actually happens - so a capacity gap is tied to the project at risk, not just a headcount number.

What systems does it connect to?

HRIS (Workday, SAP SuccessFactors), payroll (ADP), ATS (Greenhouse), HR service delivery (ServiceNow HRSD), learning (Cornerstone), 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. Workforce data is handled with role-based access and PII safeguards.

Trust · security · compliance

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.

Compliance roadmap
SOC 2 Type I
Q4 2026 target
SOC 2 Type II
est. Q1 2027
ISO 27001
Y2 target
GDPR
DPA-standard posture
CCPA
Aligned by design
HIPAA
Not in scope (no PHI)
FedRAMP
Y3 target
HITRUST CSF
Y3 target
Pen test
Pre-GA gate, then quarterly
Full sub-processor list, encryption details, and incident response runbooks at assetshopenterprise.com/trust
SLA & recovery objectives

RTO = Recovery Time Objective (max time to restore service). RPO = Recovery Point Objective (max acceptable data loss).

Tier
Uptime
RTO ⓘ
RPO ⓘ
Enterprise
99.99%
1 hr
5 min
Standard
99.95%
2 hrs
15 min
Pro
99.97%
90 min
10 min
Enterprise
99.99%
1 hr
5 min
Multi-region · multi-tenant

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.

Hash-chained audit log

Every event is hash-chained - including approvals, capacity runs, signal traces, and integration calls. Tamper-evident by construction. Signed receipts available on request.

⚙ Illustrative reference model · synthetic profile

90 days. Three sites. 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.

Synthetic profile
~$450Mannual revenue
3 sitesmulti-site operations
~$54M annualworkforce planning spend
3/yearsupply disruptions

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 workforce planning 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 sites - without modifying source systems, without a multi-year migration project, without a rip-and-replace.

$5.6M/yr
Annualized instability cost avoided
Methodology: capacity-gap economics + attrition-risk surfacing + backfill reduction, conservatively modeled
28d
Time to first cross-team signal
Modeled · from contract execution to first signal trace across 3+ source systems
3.4x
Faster planning cycle
From annual guess to continuous with shared data
The first question every architect asks

Why an overlay, when your ERP already has modules?

The join is the product
A native HRIS sees only its own record. Your performance, collaboration and capacity signals live in separate systems. The overlay reads all of them and surfaces the org reality no single module can see.
Zero write path, zero process risk
Nothing is installed in the ERP, nothing migrates, nothing changes how your teams work. Security review measures an architecture with no write path - days, not months.
Value before commitment
Read-only extracts mean findings in week one. The assessment is observed and lineage-backed before you sign anything long-term; Day-90 keeps the pilot binary.
Decision support · built in

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.

Capacity-gap economics
Open critical roles mapped onto the cost centers already showing variance - the capacity gap and the cost overrun shown as the same event, with the true run-rate behind contractor backfill.
Open in the live demo →
Attrition-risk surfacing
Performance, collaboration, and tenure signals read together to surface attrition risk before it is a resignation - with the bottleneck teams it would most expose.
Open in the live demo →
Org-effectiveness view
Collaboration patterns read across systems reveal the teams that gate delivery - the structural bottleneck no org chart shows.
Open in the live demo →
Pricing & engagement

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 →
Competitive positioning

How is AssetShop different from the alternatives?

o9, a planning suite, and Anaplan are integrated business planning (IBP) platforms. They want to be the central planning environment - a customer migrates planning workflows into them. AssetShop is the read-only intelligence layer on top of these systems. We do not compete for planning ownership; we surface cross-platform variance (where the IBP plan diverges from workforce planning, operations, and logistics reality) and quantify the leakage. Customers who already invested in a planning suite or o9 keep using them as their plan-of-record and use AssetShop to surface what those systems cannot see across the rest of the stack. We integrate with all three as adapter connectors.
point analytics tools are logistics visibility platforms - they track shipments-in-motion across carriers. AssetShop is a cross-domain intelligence layer that includes logistics but extends across workforce planning, operations, planning, and analytics. We ingest from point analytics tools (we have adapters for both) and combine that real-time workforce costs signal with workforce planning variance, capacity positioning, and capacity constraints to produce decisions that no single-domain platform can surface. Customers can keep a point analytics tool for visibility and run AssetShop for cross-domain decisioning.
A multi-product enterprise suite is a system of record with consolidation ambitions in each domain it touches. It is a migration play - "make us the center of your operations." AssetShop is the opposite architectural choice - we sit on top of your existing systems, including that suite when you have it, and surface cross-team signals. We have read-only adapters across the systems you run, payroll system, and ATS. Customers running such a suite do not need to migrate; AssetShop reads from it and routes the signals it cannot generate alone.
Every engagement starts read-only and scales with you - assessment, pilot, then enterprise, each scoped to your footprint. at Year 3, explicitly written into the MSA: (1) Reference-customer renewal: continue your engagement for an additional 3 years in exchange for case-study rights, reference call obligation (~1/quarter), and listing as an AssetShop reference partner; (2) Standard renewal: transition to the then-current Enterprise tier rate (capped at CPI+5% annual escalation from your Year 3 rate). Both options are explicitly available; the choice is the customer's. This is unusual for enterprise SaaS and intentional - we want early customers to stay long-term customers indefinitely as the structural foundation of our reference program.
Current state: AssetShop LLC (Pennsylvania sole-proprietor LLC). Transitioning to Delaware C-Corp before first signed customer (counsel-paced, 4-6 weeks). Target insurance limits binding before first customer signature: Cyber Liability $10M aggregate / $5M per occurrence, Tech E&O $5M aggregate, Commercial General Liability $2M / $4M aggregate. Insurance binding is on the standing readiness checklist. Early-customer LOIs include a "binding-by" milestone and a kill-switch if insurance is not bound within 60 days of LOI signature.
The architecture itself is the answer. AssetShop is read-only - your ERPs remain authoritative. The durable parts of your stack - data contracts, the provenance chain, the workflow outputs - stay in the stable layer, so the intelligence layer does not have to be re-architected when the technology underneath it changes. AssetShop writes nothing back to your systems of record - not approvals, not audit entries, nothing; findings export for action in your own systems. Beyond that: every early-customer contract includes (1) 30-day notice + full data export rights to XLSX/CSV/JSON of all observed records, renders, and audit chain entries; (2) 90-day run-down obligation - we keep your tenant operational for 90 days after termination at no charge to enable orderly transition; (3) source code escrow with a third-party escrow agent (Iron Mountain Software Escrow or equivalent) released to customers on AssetShop insolvency. Continuity Pack (F-08) details are in the Trust Center.
Coupa and Ariba are workforce planning suites - they want to be the system of record for your workforce planning function. AssetShop is an operations-intelligence platform that runs across workforce planning, operations, planning, logistics, and analytics simultaneously. We sit on top of Coupa or Ariba (or SAP Ariba) and surface the cross-team signals they cannot - because they are scoped to workforce planning only. Customers can keep Coupa for transactional workforce planning and run AssetShop for cross-domain decisioning - both operate at once without conflict.
No. AssetShop adds to your stack rather than replacing it. Our SAP and Oracle connectors are first-party and deterministic. You keep your system of record where it is. AssetShop reads from it, surfaces patterns and recommendations from the data, and exports release packages or audit-ready evidence that your team executes back into the source system. AssetShop writes nothing back to your systems of record - not approvals, not audit entries, nothing; findings export for action in your own systems.
Once connectivity is live, time to first cross-team signal is typically 14 days or less. Standard adapters (SAP S/4HANA, Oracle Fusion, NetSuite, D365, Infor CloudSuite, Coupa, Workday, Generic REST) are pre-built and configured per tenant; custom data contracts add 2-4 weeks. Critical reality: pre-work (security review 4-6 weeks, DPA negotiation 3-4 weeks, IT connectivity 2-3 weeks, executive sign-off variable) typically takes 6-12 weeks before the technical clock starts. Early customers get a dedicated implementation engineer through the full lifecycle. Walk through what live looks like →
Tenants elect a primary region at sign-up: US East · US West · EU Central · APAC. Data, encryption keys, and audit logs all reside in the elected region. Cross-region replication is opt-in for DR purposes only. EU tenants can elect EU-only replication for full GDPR sovereignty. Custody-grade key management on Cloud KMS - cloud provider does not have access to tenant data. Customer-managed encryption keys (CMK) available at Enterprise tier: customer brings their own KMS key (Cloud KMS, AWS KMS, Azure Key Vault, or on-premise HSM via External Key Manager). Key rotation under customer control. Key revocation effectively decommissions the AssetShop tenant's access to encrypted data without requiring AssetShop cooperation.
Standard. The customer-data-handling commercial platform serves over standard HTTPS today via the eth.limo gateway; a conventional 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.
Yes. Same inputs produce the same outputs, byte-for-byte. Every capacity run emits a SHA-256 hash. Two planners running the same data on different days get identical action messages. This is critical for audit and approval workflows - a deterministic result means no "who ran the numbers when" disputes. Our reference implementation uses Kahn's algorithm with deterministic alphabetical tie-break, time-phased lot sizing, and UTC-safe date handling. Request the technical spec →
$ For CFOs and capital-allocation decision-makers

Capital allocation, not feature workforce planning.

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.

TIME-TO-FILL + RAMP + CAPACITY
Workforce-cost economics
This worksheet translates workforce outcomes - faster time-to-fill, shorter onboarding ramp, capacity-drift detection - into avoided cost. The levers AssetShop most influences (open-role duration and ramp time) compound on loaded workforce cost, so each day of compression reduces the cost of unfilled and under-ramped capacity. Coefficients are conservative and adjustable. Illustrative at the Meridian demo scale; every figure scales with your own inputs and is validated against your actuals at the Day-0 baseline.
Payback & value
Months, not years
Customer-side methodology (handed to your CFO during qualification) calculates Year 1 working capital release and 3-year cumulative impact against your scope and adapter coverage. Conservative calibration is the recommended floor for board materials - every figure traces to a named path with a documented capture rate, so the result is defensible under scrutiny rather than impressive on a slide. Value is calculated against your subscription cost - the engagement scope set with you, the Enterprise tier, or Customer Inquiry pricing scoped per engagement - full tiers on the enterprise site.
Audit-defensibility
Cryptographic provenance
Every operational signal carries audit-chain provenance. Big-4 auditors discount working capital adjustments when provenance is defensible. Reduces audit-cycle costs and regulatory contingent-liability cash holdings.
Predictability
3-year locked subscription
Terms are set with you and written into the MSA. No auto-renewal escalations. No surprise changes. Predictable expense line for board reporting.
Interactive · CFO worksheet Client-side only · no data transmitted
CFO Justification Deck

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.

Ready to see it work

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.

SOC 2 Type II · est. Q1 2027 99.95% SLA Multi-region · US · EU · APAC assetshopenterprise.com/enterprise
Privacy notice · no tracking
This site uses no third-party tracking, no advertising cookies, no analytics beacons.
A single first-party cookie remembers your preference for dismissing this notice. We follow GDPR + CCPA + state-equivalent privacy laws by default. Full detail in our Privacy Policy and Cookies Policy.