The front door
Brand, website, model library, local discovery and useful photography.
Where this comes from
neonburro / shop
Website and catalog patterns exist. Phosphor integration is proposed.
PHOSPHOR / BUSINESS ESSENTIALS
A whole business.
Working together.
The store is the front door. The useful part is everything behind it.
Build my operating brief ↗
Local design study. Service requests, owner accounts, auctions and payments are not connected.
ONE COHERENT OPERATING KIT
Everything has a place.
Nothing gets lost.
Reuse what the studio has learned. Build the actual Phosphor workflow deliberately. Keep every dealer’s records separate.
The inquiry desk
One clear brief, a named next step and follow-up that keeps the conversation.
Where this comes from
Spanwise / Pulse patterns
Architecture is a reference, not a shared client database.
The service counter
Condition photos, estimates, owner authorization, work orders and updates.
Where this comes from
Cimarron workflow lessons
Workflow pattern only. No client code or records are reused.
The money record
Quotes, invoices, provider-confirmed payments and clear reconciliation.
Where this comes from
nixie / burropay patterns
Phosphor payments are not connected. No wallet, escrow or financing promise.
The team
Role-based onboarding, practice, manager review and an operating playbook.
Where this comes from
Janda Dealer Academy patterns
Architecture only. Janda branding and curriculum need explicit rights before reuse.
The return visit
Owner records, service reminders, parts requests and a path to resale.
Where this comes from
The truck passport
A proposed Phosphor product, not an existing customer system.
The operating picture
Sources, lead stages, service turnaround and measured costs in one view.
Where this comes from
Spanwise / neonburro
Real records, not invented sales or fabricated performance charts.
The keeping
Access controls, updates, backups, consent and a clean customer handoff.
Where this comes from
Studio operations
Each dealer owns its records. Support and exit terms must be agreed.
THE DELIVERY SEQUENCE
Shape it.
Run it.
Keep improving it.
Map the business.
Inventory, sourcing, service, team roles and the way customers already arrive.
Build one working route.
An inquiry becomes a reviewed brief, an authorized job and a useful record.
Connect the approved rails.
Provider onboarding, server-owned amounts and payment evidence before any live money flow.
Measure the real work.
Keep the dashboard honest, the permissions clear and the exit usable.
Business boundaries and reuse
Spanwise, Janda and Cimarron are distinct projects or clients. This proposal uses general workflow lessons, not their private data, proprietary curriculum, customer lists or source code. No partnership, endorsement or engineering service is implied.
nixie and burropay are reference directions. Their existence does not establish Phosphor payment capability. Dealer licensing, auction terms, provider support, financing and commercial commitments require separate review.