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.

Book a roadmap walkthrough See connected modules

Sprints 213-224, 226-235

Buyer-ready command center

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 236-244

Pilot and production rollout

Polish customer-facing readiness language, finalize pricing and billing operations, then run the first production pilot with support, rollback discipline, customer feedback, launch hardening, partner groundwork, product governance, and long-term maintenance habits.

pilot evidencesupport readinesslaunch polishmaintenance cadence

Sprints 245-316

Mobile, kiosk, and GPS surfaces

Extend the same operating record into mobile field workflows, offline sync, device policy, real-device pilots, GPS-assisted work, and the workforce time-clock/site-access kiosk appliance train.

mobile API contractsoffline strategyGPS signalkiosk appliance

Sprints 317

Next-era review

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

Already proven foundation

The next work builds on finished web depth instead of starting from a brochure.

Sprints 62-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 67-78

Fleet enterprise hardening

Fleet history, event evidence, geofences, maintenance, device health, and driver accountability gained the depth needed for serious operating demos.

Sprints 79-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.

Roadmap discipline

The order is intentional because connected hardware only matters when the operating record is trusted.

The near-term work is focused on buyer conversion, reliability, access control, observability, reporting, onboarding, trust posture, commercial readiness, mobile device testing, and kiosk hardware validation. The differentiation is not another app screen; it is one record fed by web users, field crews, terminals, and GPS devices.

What a buyer should see

Every roadmap item should make the demo stronger.

Show how a customer request becomes owned work instead of scattered notes.

Show how field, fleet, inventory, documents, finance, compliance, and reporting stay connected.

Show where blockers, evidence gaps, access controls, GPS exceptions, kiosk punches, and follow-up live.

Show why web, mobile, kiosk, and GPS hardware are one operating system instead of separate products.

Execution phases

The delivery plan stays detailed. The buyer story stays simple.

Talk through fit

Phase 31-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 62-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 67-78

Fleet enterprise hardening

Deepen trip evidence, device-signal quality, road context, geofences, maintenance, driver identity, coaching, and fleet rollout confidence.

Phase 79-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 213-224, 226-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 236-244

Pilot, launch, and operating cadence

Customer-facing blocker cleanup, pricing and billing operations, production pilot, pilot remediation, rollout, post-launch polish, partner groundwork, product program governance, and long-term maintenance after the web platform is credible.

Phase 245-316

Mobile, field app, kiosk, and GPS expansion

Mobile API readiness, mobile app foundation, field capture, offline sync, GPS-assisted workflows, device policy, mobile rollout, then the workforce time clock kiosk appliance with NFC credentials, offline replay, hardware validation, and production readiness.

Phase 317

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.