Loading
Loading
PLG · time-to-value
LiveSoftware that needs a consultant to open a job will lose independents. Day 0 should create a tenant, an owner, a bay, and a path to the board — then deepen configuration.
Primary persona: Owner (new tenant)
The problem
Legacy DMS onboarding is project-shaped; modern shops expect trial-to-value in a sitting.
Why it matters
Signup API creates tenant isolation from the first second (tenantId everywhere).
Default bay and roles reduce blank-canvas paralysis.
Demo credentials prove the product before migration risk.
Import of customers/vehicles/parts is staged honestly — parallel week recommended.
Proof from the live demo
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.


Stage sequence
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
Action
Create account; API provisions tenant + owner user.
Why this stage
Multi-tenant isolation is a security feature that starts at signup.
Action
Name, timezone, tax defaults, bay count intent, rates as available.
Why this stage
Invoices and bookings need jurisdiction-aware defaults early.
Action
Invite advisor/tech; RBAC least privilege by default.
Why this stage
Floor adoption fails if everyone shares the owner login.
Action
Create customer + vehicle + RO or use seed patterns; run board → invoice once.
Why this stage
Muscle memory beats feature tours; one full money path builds trust.
Related search intent