Operations-first UI

Grease hauling, routed and reconciled on the same screen.

HaulerBack’s overhauled interface pairs live dispatch with permit-ready paperwork. Dispatchers stay ahead of route changes, crews sign digital manifests, and cities receive clean, compliant data without email ping-pong.

Open the Ops Portal Schedule a walkthrough

Driver-ready manifests
Automated permit checks
Live route visibility

99.9% Portal uptime with regional failover

24 hr Average time to onboard a new municipality

Zero Manual spreadsheets needed for manifests

Today’s Control Center

Routes, jobs, and signatures in one responsive layout that mirrors the app.

Dispatch Driver Console Compliance

Responsive shell

The same layout components from the overhauled UI render here—cards, compact rails, and timeline chips—so your marketing page matches the product shell.

Permit-backed workflows

State + city metadata flow directly into manifests and PDFs without extra reentry.

Built to mirror the in-app layout.

The marketing site now uses the same spacing, color system, and card structure as the HaulerBack dashboard. Visitors see the UI they’ll use—no surprises between promise and product.

Cards + Rails

Familiar surfaces

Glassmorphic cards, rounded rails, and compact headers mirror the authenticated shell so brand consistency carries from S3 to production.

Reuses app spacing scale
Consistent corner radius

Responsive

Mobile-first structure

The layout collapses cleanly: hero content stacks, CTAs stay reachable, and cards keep the same rhythm used in the mobile driver console.

Sticky, minimal header
Tap-friendly CTAs

Performance

Static and fast

Zero extra assets beyond fonts and this stylesheet. Deployed to S3 + CloudFront for sub-100ms TTFB in primary markets.

Minimal JS (year + menu)
Ready for S3 static hosting

Plan

Schedule routes, enforce service windows, and assign crews with the same cards drivers see.

Execute

Drivers receive mobile-friendly manifests, capture signatures, and log grease volumes on-site.

Prove

Manifests roll into exportable PDFs and CSVs already matched to city requirements.

Compliance baked in.

Metadata fields for state and city requirements mirror the JSON-driven validators used inside the portal. Marketing copy stays honest because it is powered by the same data.

City-ready

Permit-aware manifests

City requirement metadata flows into every export—no duplicate entry or PDF fiddling. Use the same identifiers the admin UI validates.

Audit trail

Trustworthy timelines

Timestamped events, signed manifests, and GPS breadcrumbs so regulators see what happened without extra calls.

Security

Identity + sessions

Matches the portal’s authentication hardening—device sessions, MFA ready, and rapid lockouts if a tablet goes missing.