Utah Road Trip Rentals
A local outdoor gear rental site for cargo boxes, bike racks, and carriers, built around practical booking flows, local SEO, and small-business operations.
Utah Road Trip Rentals is a local rental business I built to help families and outdoor travelers in Northern Utah get the gear they need without buying equipment they only use a few times a year.
The product focuses on practical road-trip gear: cargo boxes, bike racks, hitch carriers, and related travel equipment. It is based in Syracuse, Utah and serves Davis County, Weber County, and the broader Wasatch Front.
The Problem
The image above shows the live public rental site, captured October 19, 2026.
Families often need extra cargo space or bike capacity for one specific trip. Buying a premium cargo box or rack can be expensive, storing it is inconvenient, and figuring out fit requirements can be confusing.
The site needed to answer a simple customer question quickly: Can I get the right gear for my trip, on the dates I need it, without a lot of back-and-forth?
What I Built
As founder and product engineer, I built the customer-facing site and the operational tools behind it. The scope connects product design, implementation, local discovery, and the practical details of running the rental workflow.
I built the public rental site, booking flow, and operational tooling around that customer path:
- Browse rental inventory with photos, fit notes, rates, and item details
- Request dates through item-level booking flows
- Prevent conflicts with real availability checks
- Support daily, weekend, and weekly pricing models
- Send booking notifications and customer communication through email workflows
- Track booking status from request to confirmation, pickup, return, and cancellation
- Support admin workflows for bookings, financial reporting, item analytics, and customer follow-up
The business also needed local trust signals: clear pickup expectations, practical FAQs, local service-area copy, and SEO-focused landing pages for the kinds of searches customers actually make before a trip.
Technical Notes
A request is not a confirmed booking
The site explicitly separates a customer’s request from final confirmation. Availability, pickup timing, and vehicle fit still need to be checked. That distinction keeps the interface aligned with the real service instead of promising an instant reservation the operator may not be able to fulfill.
Availability has to reflect the physical gear
An item that is still checked out should not appear available just because its scheduled return date has passed. The availability logic extends an overdue, picked-up booking through the current day. It is a small rule with a direct operational consequence.
Walk through the customer path
- Browse the equipment and read its vehicle-fit notes.
- Choose dates and submit a request on the item page.
- Confirm availability, fit, and pickup or delivery details with the operator.
- Pick up the gear, receive the applicable installation walkthrough, and return it at the agreed time.
Explore the public rental catalog.
The implementation
The project is built with Next.js, React, TypeScript, Tailwind CSS, Neon Postgres, Resend, and Vercel. The interesting work is less about a complex stack and more about aligning public UX with the real operational workflow behind the scenes.
The booking system has to balance simplicity for customers with enough structure for the operator: availability, deposits, pickup timing, delivery requests, item fit, status changes, and payment follow-up all need to stay coherent.
What It Proves
Utah Road Trip Rentals is a useful proof point for small-business software because it combines strategy, customer-facing copy, local SEO, booking flows, operational admin tools, and practical product launch work in one live business.
It is not just a brochure site. It is a small operating system for a real local rental workflow.
The delivered result is a live catalog, a request-and-confirm booking path, and administrative workflows for running the service. Revenue, conversion, and utilization figures are not part of this case study.
If your business has a similar workflow challenge, explore my software consulting approach for a practical guide to choosing between existing tools, integrations, automation, and a custom build.