Public Product

Home Base

A public shop-management product surface backed by real app design and build work.

Specimen Sheethome-base

typeWeb App / Product Site

roleProduct, UI, build, launch

year2026

Home BasePublic Product

Customer intakeUnit statusWork queueHandoff trail

intake / estimate / work orderShop workflow

Turn scattered service work into one readable path before the app asks for trust.

What this proves.

Challenge

Show a service-shop workflow without importing the private shop system into the public product story.

Outcome

A product and app surface that explains the workflow, names Gauge and Lens clearly, and gives visitors a demo path.

Combines product positioning, app UI, and launch mechanics.
Useful proof that the same design eye can carry into operational software.
Stays separate from the original shop-specific system while sharing the problem space.

Product siteApplication UIDemo flowLaunch support

Demo artifacts

WorkflowShop workflow

intake / estimate / work order

GaugeGauge assistant

ask / inspect / act

LensLens video

record / attach / share

DemoDemo path

public / safe / wired

Product jobName the shop pain before showing screens.

Interface jobInspect Gauge, Lens, and workflow states.

Launch jobKeep the demo path obvious enough to try.

Build read

A product-site build should start by naming the workflow pain in plain language, then prove the interface can handle it.

The product surface had to make operational software feel understandable before a visitor ever opens the app.

Gauge and Lens need to read as product features, not random AI labels.

The public site and app surface share the same standard: useful before decorative.