06 — Fleet Control OS
Fleet Tower
Control tower for vehicles, machines, tools, stock, maintenance and costs — built for construction and equipment-rental teams running 10 to 100 assets.
- Cliente
- Operaciones de equipos y maquinaria
- Año
- 2026
- Línea
- Digital Product
- Rol
- Producto: modelo de datos, OS y landing
- Estado
- Live · fleet-tower.vercel.app
- En línea
- fleet-tower.vercel.app
El punto de partida
The reality on most sites is a whiteboard, three group chats and a spreadsheet nobody trusts. Fleet Tower replaces that with one dashboard: a Today panel that opens the shift, then live views of fleet, machinery and tools.
Maintenance scheduling carries a ninety-day expiry radar, so documents and services surface before they become a stopped machine. Stock, per-project costs and the team behind it all sit in the same system.
Lo que construimos
- 01Today panel — the shift opens here, not in a chat
- 02Live views: fleet, machinery and tools with status per asset
- 03Maintenance scheduling + ninety-day expiry radar
- 04Stock, per-project cost and team views
- 05Landing page with i18n and a hand-built product preview fed from the same seed data as the dashboard
Cómo se hizo
The interface follows a blueprint language: hairline rules, seal squares, an ultra-fine sidebar rail that collapses at a click. The preview a visitor sees on the landing is rendered from the same seed data as the real product — no fake screenshots, no drift between marketing and software.
Dónde quedó
One screen instead of the usual whiteboard plus three group chats — and a demo that is the actual product.
- 10–100 activos
- Radar de vencimiento 90 días
- Preview = datos reales
Stack
- Next.js
- shadcn/ui
- Blueprint design language
- i18n
- Seed-driven preview
¿Tenés un operativo que se maneja con planillas y chats de grupo? Ese es exactamente el trabajo que hacemos.
hello@c-c.studioC_C® · Essential by Creative Collective · publicar siempre es un click humano · ver el índice completo