Operating model

Five source systems. One living picture.

CRM holds the contract. Shop tools hold the build. Strativue sits in the middle and composes them — it does not replace those systems.

Full picture

Strativue reads CRM, the shop scheduler, timekeeping, inventory/ERP, and the work-order tracker. Click a signal to see which system feeds it.

1 CaptureCRM holds the contract and units. Scheduler, timekeeping, inventory, and work orders keep owning the build.

2 ConvergeStrativue stitches those feeds into one build record per vehicle.

3 SurfaceThe portal shows the composed view — and flags the unit when any signal breaks.

Gold path = selected signal · On the portal: dropdowns, pipeline stages, and vehicle rows are clickable

What the operator sees

CRM + shop systems, composed

Live composition. CRM, scheduler, timekeeping, inventory, and work orders stay in place. Strativue pulls those feeds into one vehicle row.

STRATIVUE Battleborn Upfitters

Composed 2s ago

Vehicle builds — click a row for the composed record

Unit	Stage	Done	Target	Why it looks like this

All units on this contract

Unit	Vehicle	Stage	Done	Target	Status

Click any row to open the unit. Use the stage dropdown to filter.

encrypted hop · app and jobs never sit on the public SQL port

composed rows written over an encrypted database connection

How a refresh works

Click a box. This is the generic pattern small shops use: DigitalOcean hosts the app, Codex jobs refresh source systems into SQL, TLS covers the wire, and the database encrypts disks. Multiple people can sign in without sharing one password or one data pile.

What the operator sees

Build pipeline — from the work-order tracker · click a stage to filter

Vehicle builds — click a row for the composed record

Budget — labor + parts + overhead CRM ceiling · accounting actuals

Open issues — click to open the unit

All units on this contract

Report snapshot — this month

How a refresh works