Howdy Dispatch
Live SaaS with paying fleets, dispatcher web HQ, driver iOS, photo proof of delivery, and Stripe-billed subscriptions.
Role
Studio · build + ship
Status
Live
Year
2025 → 2026
Surfaces
Web + iOS
Live
In production
The problem
Howdy Dispatch is a freight and logistics SaaS for small trucking companies. Dispatchers create jobs in a web HQ from scratch or straight from a broker rate-confirmation PDF, drivers see them on their phone with photo proof of pickup and delivery, and the platform handles GPS tracking, push notifications, customer address books, driver-safety workflows, and subscription billing. Multi-tenant from day one, every fleet gets its own data isolation, its own user limits, and its own billing.
What we built
- Dispatcher HQ, job creation from scratch or a broker rate-conf PDF, live status board
- Driver iOS app via Capacitor, push notifications, GPS, photo proof of pickup and delivery
- DVIR pre/post-trip inspections, HOS self-report, shift clock, and detention timers
- Customer address book with one-tap repeat orders
- Stripe subscription tiers ($149–$1,990/mo) with truck-count limits
- Platform admin dashboard for the operator
- Full audit trail on every job, every driver, every photo
Numbers that matter
Status
Live
paying customers
Plans
$149–$1,990/mo
1–10+ trucks
Surfaces
HQ + Driver iOS
cross-platform
Tenant model
Multi-tenant
isolated per fleet
Stack
- Frontend
- Next.js 16React 19Tailwind
- Backend
- FastAPIPython 3.12Alembic migrations
- AI / ML
- Vertex AI (rate-conf PDF parsing)
- Data
- PostgreSQL (multi-tenant)Cloud Storage
- Infra
- Cloud RunCapacitor iOSFirebase Auth + FCMStripe Billing
What we learned
A dispatch platform is only as good as its proof-of-delivery flow. We rebuilt that loop three times before drivers stopped calling the office.
Pricing tiers had to map to truck count, not feature flags. Every other axis confused operators.
Have something that looks like this?
Tell us what is broken. We’ll tell you what the first week looks like.
Next case study →
RunLink