We're here
The web command center is the working product.
The browser app is the current operating record for customers, service, fleet visibility, workforce, finance, compliance, reporting, and administration.
Some companies have a workhorse. We're building you a War Horse.
Roadmap
Web command center, mobile field work, kiosk terminals, and GPS devices share one roadmap.
The public roadmap is not a sprint archive. It is the buyer-facing sequence that protects the product: keep the web command center reliable, prove it with production pilots, validate mobile on real devices, then validate kiosk hardware and physical GPS workflows against the same operating record.
Every roadmap item should make the demo stronger while keeping public status honest about what is current, alpha, or waiting on hardware design.
Sprint numbering uses product tracks: W.### for web application work, M.### for mobile work, and K.### for kiosk work.
This is next
Field validation continues.
Mobile remains early alpha, the kiosk appliance is ship-ready, and production pilot work turns working flows into customer-ready proof.
This is coming
Full-company coverage gets closed deliberately.
ATS, ERP, EAM, EHS, CLM, rollout, support, partner readiness, and long-term maintenance remain mapped work, not loose marketing promises.
Current sprint position
W.301
Mobile pilot readiness dependency gate
W.248-W.311 replacement audits, blocker gates, full-company coverage, production rollout, and issue-intake follow-through
Current work has moved past the closed W.269-W.300 ATS, full ERP, full EAM, full EHS, full CLM, fleet live-map, Ironvale demo-readiness, and lint/build hygiene stack into mobile pilot readiness before cross-module acceptance and production-pilot readiness.
Web command center foundation: completedFinance and accounting depth: completedReplacement gap closure: W.267 final audit closedFull company coverage map: W.268 closedATS requisition foundation: W.269 closedATS candidate intake and source tracking: W.270 closedATS interview loops and scorecards: W.271 closedATS offer and prehire lifecycle: W.272 closedATS onboarding handoff: W.273 closedATS dashboard, audit export, docs, and acceptance script: W.274 closedERP operating model, cost centers, and approval foundation: W.275 closedERP procurement requests, purchase orders, and approval routing: W.276 closedERP receiving, vendor bills, three-way match, and AP closeout: W.277 closedERP inventory locations, item costing, movements, and reorder controls: W.278 closedERP project job costing, budgets, commitments, and margin controls: W.279 closedERP demand planning, revenue/cash forecast, and management reports: W.280 closedERP finance provider handoffs, accountant exports, and migration acceptance: W.281 closedEAM asset registry, hierarchy, ownership, and location foundation: W.282 closedEAM asset lifecycle, assignment, warranty, condition, and field evidence: W.283 closedEAM meter, telematics, preventive maintenance, and work-order planning: W.284 closedEAM parts, downtime, reliability, failure analysis, and maintenance costing: W.285 closedEAM depreciation, capital planning, replacement review, and disposal: W.286 closedEAM dashboards, permissions, notifications, audit, docs, and acceptance: W.287 closedEHS safety program templates, policy, and field reporting foundation: W.288 closedEHS incident, near miss, injury, illness, and OSHA-style logs: W.289 closedEHS JHA/JSA, toolbox talks, inspections, and mobile evidence: W.290 closedEHS investigation, root cause, corrective action, and claims evidence: W.291 closedEHS safety training, credential links, dashboards, exports, and acceptance: W.292 closedCLM intake, templates, clause library, and request controls: W.293 closedCLM drafting, versioning, redline negotiation, and counterparty review: W.294 closedCLM approval, signature routing, provider boundaries, and execution evidence: W.295 closedCLM obligations, renewals, amendments, terminations, legal hold, and retention controls: W.296 closedCLM repository, migration, permissions, audit, dashboards, docs, and acceptance: W.297 closedFleet unified map overlay filters and trip trail command: W.298 closedIronvale demo full coverage seed and subscription tier simulator: W.299 closedWeb/kiosk lint, build, and artifact hygiene blocker: W.300 closedMobile pilot readiness dependency gate: W.301 activeKiosk hardware, case, and field pilot readiness gate: W.302 closedPublic claim boundary and whole company copy gate: W.303 queuedFull company operations cross-module workflow acceptance and claim readiness: W.304 queuedProduction pilot and customer readiness: W.305 queuedMobile app: early alphaKiosk appliance: ship ready
Sprints W.213-W.224, W.226-W.235
CompletedBuyer-ready command center
Web foundation proved
Tighten the public story, dashboard communication, configurable command views, granular access, observability, backups, jobs, integrations, communications depth, scale, reporting, onboarding, trust, APIs, templates, AI, automation, analytics, accessibility, procurement readiness, and capacity discipline for the web command center.
clear buyer walkthroughbuyer-facing pagesweb command centeradmin trust controls
Sprints W.236-W.247
CompletedCommercial finance and accounting
Finance depth proved
Finalize pricing and billing operations, connect CRM billing data to finance, and build the provider-agnostic accounting replacement track: ledger, AR, customer-owned payment processor connections, clearing, reconciliation, AP, statements, tax evidence, migration, and finance audit controls.
ledger foundationhosted pay linksbank reconciliationaccountant close
Sprints W.248-W.311
CurrentReplacement audits, blocker gates, full-company coverage, and rollout
Now working: W.301
Audit public software replacement claims one category at a time, close industry gaps across CRM, service, workforce, learning, fleet, compliance, finance, analytics, communications, payments, tax, scoped APIs, implemented webhooks, and documents/contracts, perform a final gap coverage roll-up, build feature stacks for ATS, full ERP, full EAM, full EHS, and full CLM, then clear lint/build, mobile pilot, kiosk pilot, and public-claim blockers before full-company acceptance, pilot, rollout, governance, and maintenance habits.
target auditsfinal matrixblocker gatesmaintenance cadence
Sprints M.1-M.53
QueuedMobile field app
Early alpha track
Extend the same operating record into mobile field workflows, offline sync, device policy, real-device pilots, GPS-assisted work, and field closeout evidence. The mobile app is in early-alpha field validation.
mobile API contractsoffline strategyGPS-assisted workdevice policy
Sprints K.1-K.19
Ship readyKiosk terminals
Case design complete
Carry workforce time-clock and site-access events into shared terminals. The kiosk appliance is ship-ready with completed case design, hardware packaging, NFC credentials, offline replay, pairing, sync, Wi-Fi setup, update paths, and device governance.
NFC credentialsoffline replaydevice governanceship-ready case
Sprint K.20
QueuedNext-era review
After field evidence
Review what customers actually used, what resonated in buyer walkthroughs, what broke in production, and which expansion tracks deserve the next serious build cycle.
customer evidenceadoption signalsupport signalnext-era plan
Full company coverage guardrails
The next feature stacks close known gaps before production pilot starts.
DestrierOS is intended to become one subscription for web, mobile, and kiosk operations, but the roadmap keeps professional and provider boundaries explicit. The sprint stacks below must close product workflows, permissions, notifications, audit evidence, dashboards, docs, tests, and acceptance before public claims get stronger.
W.269-W.274
ATS
Applicant Tracking System
Build requisition-to-employee handoff features with permissions, notifications, audit evidence, dashboards, quick starts, and acceptance before any ATS replacement claim.
Roles: Hiring manager, HR owner, recruiter, department lead, candidate reviewer, onboarding owner
Workflows: requisitions, candidate intake, source tracking, interview scorecards, offer approvals, background status, prehire docs, onboarding handoff
Why it matters: Hiring stays disconnected from HR onboarding, training, permissions, and labor planning.
W.275-W.281
ERP
Enterprise Resource Planning
Build the operating backbone from approval through procurement, receiving, inventory, job cost, planning, provider handoff, accountant export, migration, and acceptance.
Roles: Operations leader, finance owner, purchaser, receiver, project manager, accountant, executive reviewer
Workflows: cost centers, approvals, procurement requests, purchase orders, receiving, three-way AP match, inventory costing, job budgets, forecasts, exports
Why it matters: Finance, procurement, inventory, and job margin can drift apart before leadership sees the operating impact.
W.282-W.287
EAM
Enterprise Asset Management
Build asset lifecycle depth with meters/telematics, PM planning, parts, downtime, reliability, costing, capital planning, disposal, dashboards, audit evidence, docs, and acceptance.
Roles: Asset manager, mechanic, fleet owner, field supervisor, finance owner, reliability reviewer
Workflows: asset hierarchy, ownership, location, lifecycle, warranty, condition evidence, meters, telematics, preventive maintenance, downtime, replacement review, disposal
Why it matters: Equipment history, maintenance cost, reliability, capital planning, and field evidence remain too fragmented for full asset ownership.
W.288-W.292
EHS
Environmental Health & Safety
Build safety program, incident, inspection, investigation, corrective action, training linkage, exports, dashboards, notification, audit, docs, and acceptance coverage.
Roles: Safety manager, field supervisor, employee, compliance reviewer, claims owner, executive reviewer
Workflows: safety templates, incidents, near misses, injuries, illness logs, JHA/JSA, toolbox talks, inspections, investigations, corrective actions, training links
Why it matters: Safety work can become form storage instead of a controlled investigation, corrective-action, training, and reporting loop.
W.293-W.297
CLM
Contract Lifecycle Management
Build intake-to-archive CLM workflows with approval/signature evidence, obligations, amendments, legal hold, repository migration, permissions, dashboards, docs, and acceptance.
Roles: Contract owner, sales manager, legal reviewer, executive approver, counterparty contact, repository admin
Workflows: contract intake, templates, clause library, drafting, versioning, redline, counterparty review, approval routing, signature provider boundaries, obligations, renewals, legal hold
Why it matters: Contract records can prove storage and renewal visibility but not complete legal operations or negotiation lifecycle control.
W.300-W.303
BLOCKERS
App Blocker Gates
Close the lint/build gate, define mobile and kiosk pilot readiness, and correct public whole-company claims before full-company acceptance can close.
Roles: Implementation lead, mobile owner, kiosk owner, product owner, customer sponsor
Workflows: lint/build hygiene, mobile pilot readiness, kiosk hardware field-pilot readiness, public claim boundary review
Why it matters: Production pilot work can start with hidden app, mobile, kiosk, or public-copy blockers.
W.304
Acceptance
Full Company Operations Acceptance
Run cross-module acceptance, customer handoff docs, public-copy correction, support runbooks, migration guides, and claim review before production pilot starts.
Roles: Customer admin, operator, manager, field user, finance owner, HR owner, compliance reviewer, executive sponsor, support owner
Workflows: lead-to-cash, request-to-resolution, hire-to-productive, procure-to-pay, asset-to-maintenance, incident-to-corrective-action, contract-to-renewal, report-to-decision
Why it matters: Point features can pass while the company still cannot run end-to-end without support intervention.
Accountant review remains required
DestrierOS can organize accounting evidence, close packages, exports, reconciliation, and tax support, but formal close, tax, payroll, filing, and financial decisions remain customer/accountant responsibilities.
Customers own payment processors
Customers connect their own processors. DestrierOS orchestrates provider-hosted payment links, webhook status, reconciliation evidence, disputes, refunds, and fee visibility without becoming merchant of record.
No raw payment custody
DestrierOS does not handle raw card numbers, bank credentials, payment custody, or processor settlement. Provider tokens, safe status evidence, and audit metadata are the boundary.
Professional systems stay professional
DestrierOS does not replace accountants, tax professionals, legal counsel, payment processors, banks, or payroll processors. It gives operators the governed evidence and workflows those partners need.
Already proven foundation
The next work builds on finished web depth instead of starting from a brochure.
Sprints W.62-W.66
Release controls and platform administration
The product kept the main web platform on managed infrastructure while isolating fleet hardware ingestion as a dedicated edge concern.
Sprints W.67-W.78
Fleet enterprise hardening
Fleet history, event evidence, geofences, maintenance, support health, and driver accountability gained the depth needed for serious operating demos.
Sprints W.79-W.212
Enterprise module depth
CRM, service, communications, workforce, learning, compliance, finance, analytics, documents, operations, automation, platform administration, map identity, and lead capture moved from module claims into connected web workflows.
Execution phases
The delivery plan stays detailed. The buyer story stays simple.
Phase W.31-W.61
Web command center readiness
Harden the browser product as the command center for enterprise operating workflows, release-certification evidence, and the shared data model that mobile, kiosk, and device surfaces extend.
Phase W.62-W.66
Infrastructure pivot and release controls
Keep the web platform on managed cloud infrastructure, route fleet hardware through a dedicated ingestion edge, close release guardrails, and establish Schardt operator administration.
Phase W.67-W.78
Fleet enterprise hardening
Deepen trip evidence, device-signal quality, road context, geofences, maintenance, driver identity, coaching, and fleet rollout confidence.
Phase W.79-W.212
CRM, service, communications, and enterprise module buildout
Deepen the core operating layers buyers care about: revenue, service, communications, workforce, learning, compliance, finance, analytics, documents, operations, automation, and platform administration.
Phase W.213-W.224, W.226-W.235
Buyer-ready web product
Public positioning, dashboard release communication, configurable command views, granular access, observability, backups, background jobs, integrations, communications depth, scale, reporting infrastructure, onboarding, tenant administration, trust, APIs, industry packs, AI, automation, analytics, accessibility, procurement readiness, and capacity tuning.
Phase W.236-W.311
Pilot, launch, and operating cadence
Customer-facing product polish, pricing and billing operations, finance/accounting replacement depth, customer-owned payment processor connections, public replacement audits, customer-ready integration access, feature-build stacks for ATS, ERP, EAM, EHS, and CLM, lint/build hygiene, mobile and kiosk rollout gates, public claim cleanup, production pilot, pilot remediation, rollout, post-launch polish, partner groundwork, product program governance, and long-term maintenance after the web platform is credible.
Phase M.1-M.55
Mobile field app web parity
The mobile app is being rebuilt screen by screen around foundation, field capture, offline sync, GPS-assisted workflows, device policy, web parity, real-device testing, and production field crews.
Phase K.1-K.19
Kiosk terminal ship readiness
Workforce time-clock and site-access kiosk appliance work is ship-ready with completed case design, NFC, pairing, sync, Wi-Fi, update paths, offline replay, and device governance.
Phase K.20
Product maturity review
Review the full product after web, pilot, mobile, and kiosk tracks so the next era is driven by customer evidence instead of internal backlog noise.